Home|Differences with the last checks|Previous runs

Differences between 9c3fe9d and 064e616 (git diff)

Packages now failing:

• acgtk.1.5.1 on 5.1 is now installable. Current state is: failing
• acpc.1.0 on 4.02 had its build status changed: passing to failing
• acpc.1.0 on 4.03 had its build status changed: passing to failing
• acpc.1.0 on 4.04 had its build status changed: passing to failing
• acpc.1.0 on 4.05 had its build status changed: passing to failing
• acpc.1.1 on 4.02 had its build status changed: passing to failing
• acpc.1.1 on 4.03 had its build status changed: passing to failing
• acpc.1.1 on 4.04 had its build status changed: passing to failing
• acpc.1.1 on 4.05 had its build status changed: passing to failing
• acpc.1.1.1 on 4.02 had its build status changed: passing to failing
• acpc.1.1.1 on 4.03 had its build status changed: passing to failing
• acpc.1.1.1 on 4.04 had its build status changed: passing to failing
• acpc.1.1.1 on 4.05 had its build status changed: passing to failing
• acpc.1.1.1 on 4.06 had its build status changed: passing to failing
• acpc.1.1.1 on 4.07 had its build status changed: passing to failing
• acpc.1.2 on 4.02 had its build status changed: passing to failing
• acpc.1.2 on 4.03 had its build status changed: passing to failing
• acpc.1.2 on 4.04 had its build status changed: passing to failing
• acpc.1.2 on 4.05 had its build status changed: passing to failing
• acpc.1.2.1 on 4.02 had its build status changed: passing to failing
• acpc.1.2.1 on 4.03 had its build status changed: passing to failing
• acpc.1.2.1 on 4.04 had its build status changed: passing to failing
• acpc.1.2.1 on 4.05 had its build status changed: passing to failing
• acpc.1.2.2 on 4.02 had its build status changed: passing to failing
• acpc.1.2.2 on 4.03 had its build status changed: passing to failing
• acpc.1.2.2 on 4.04 had its build status changed: passing to failing
• acpc.1.2.2 on 4.05 had its build status changed: passing to failing
• acpc.1.2.3 on 4.02 had its build status changed: passing to failing
• acpc.1.2.3 on 4.03 had its build status changed: passing to failing
• acpc.1.2.3 on 4.04 had its build status changed: passing to failing
• acpc.1.2.3 on 4.05 had its build status changed: passing to failing
• acpc.1.2.3 on 4.06 had its build status changed: passing to failing
• acpc.1.2.3 on 4.07 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.06 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.07 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.08 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.09 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.10 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.11 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.12 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.13 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.14 is now installable. Current state is: failing
• ahrocksdb.0.2.2 on 5.0 is now installable. Current state is: failing
• ahrocksdb.0.2.2 on 5.1 is now installable. Current state is: failing
• atdgen.1.4.0 on 4.02 had its build status changed: passing to failing
• atdgen.1.4.1 on 4.02 had its build status changed: passing to failing
• atdgen.1.5.0 on 4.02 had its build status changed: passing to failing
• atdgen.1.6.0 on 4.02 had its build status changed: passing to failing
• atdgen.1.6.1 on 4.02 had its build status changed: passing to failing
• atdgen.1.7.1 on 4.02 had its build status changed: passing to failing
• atdgen.1.7.2 on 4.02 had its build status changed: passing to failing
• atdgen.1.8.0 on 4.02 had its build status changed: passing to 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
• b0.0.0.2 on 5.1 is now installable. Current state is: failing
• b0.0.0.3 on 5.1 is now installable. Current state is: failing
• b0.0.0.4 on 5.1 is now installable. Current state is: 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
• bap-ghidra.2.5.0 on 4.08 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.09 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.10 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.11 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.12 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.13 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.14 is now installable. Current state is: failing
• batteries.3.6.0 on 5.1 is now installable. Current state is: failing
• binsec.0.3 on 4.06 had its build status changed: passing to failing
• binsec.0.3 on 4.07 had its build status changed: passing to failing
• bitmasks.1.4.0 on 5.1 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.02 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.03 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.04 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.05 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.06 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.07 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.08 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.09 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.10 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.11 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.12 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.13 had its build status changed: passing to 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
• bitwuzla-bin.0.0.0 on 5.1 is now installable. Current state is: 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
• blake3.0.1 on 5.1 is now installable. Current state is: failing
• calculon.0.1 on 4.02 had its build status changed: passing to failing
• calculon.0.1 on 4.03 had its build status changed: passing to failing
• calculon.0.1 on 4.04 had its build status changed: passing to failing
• calculon.0.1 on 4.05 had its build status changed: passing to failing
• calculon.0.1 on 4.06 had its build status changed: passing to failing
• calculon.0.1 on 4.07 had its build status changed: passing to failing
• calculon.0.2 on 4.02 had its build status changed: passing to failing
• calculon.0.2 on 4.03 had its build status changed: passing to failing
• calculon.0.2 on 4.04 had its build status changed: passing to failing
• calculon.0.2 on 4.05 had its build status changed: passing to failing
• calculon.0.2 on 4.06 had its build status changed: passing to failing
• calculon.0.2 on 4.07 had its build status changed: passing to failing
• calculon.0.3 on 4.02 had its build status changed: passing to failing
• calculon.0.3 on 4.03 had its build status changed: partially failing to failing
• calculon.0.3 on 4.04 had its build status changed: passing to failing
• calculon.0.3 on 4.05 had its build status changed: passing to failing
• calculon.0.3 on 4.06 had its build status changed: passing to failing
• calculon.0.3 on 4.07 had its build status changed: passing to failing
• calculon.0.3 on 4.08 had its build status changed: passing to failing
• calculon.0.3 on 4.09 had its build status changed: passing to failing
• calculon.0.3 on 4.10 had its build status changed: passing to failing
• calculon.0.3 on 4.11 had its build status changed: passing to failing
• calculon.0.4 on 4.03 had its build status changed: partially failing to failing
• calculon.0.4 on 4.04 had its build status changed: passing to failing
• calculon.0.4 on 4.05 had its build status changed: passing to failing
• calculon.0.4 on 4.06 had its build status changed: passing to failing
• calculon.0.4 on 4.07 had its build status changed: passing to failing
• calculon.0.4 on 4.08 had its build status changed: passing to failing
• calculon.0.4 on 4.09 had its build status changed: passing to failing
• calculon.0.4 on 4.10 had its build status changed: passing to failing
• calculon.0.4 on 4.11 had its build status changed: passing to failing
• camlimages.4.1.2 on 4.03 had its build status changed: internal failure to failing
• camlimages.4.1.2 on 4.04 had its build status changed: internal failure to failing
• camlimages.4.1.2 on 4.05 had its build status changed: internal failure to failing
• camlimages.4.2.0 on 4.03 had its build status changed: internal failure to failing
• camlimages.4.2.0 on 4.04 had its build status changed: internal failure to failing
• camlimages.4.2.0 on 4.05 had its build status changed: internal failure to failing
• camlimages.4.2.2 on 4.03 had its build status changed: internal failure to failing
• camlimages.4.2.2 on 4.04 had its build status changed: internal failure to failing
• camlimages.4.2.2 on 4.05 had its build status changed: internal failure to failing
• camlimages.4.2.3 on 4.03 had its build status changed: internal failure to failing
• camlimages.4.2.3 on 4.04 had its build status changed: internal failure to failing
• camlimages.4.2.3 on 4.05 had its build status changed: internal failure to failing
• camlimages.4.2.4 on 4.03 had its build status changed: internal failure to failing
• camlimages.4.2.4 on 4.04 had its build status changed: internal failure to failing
• camlimages.4.2.4 on 4.05 had its build status changed: internal failure to failing
• camllib.1.3.3 on 5.0 is now installable. Current state is: failing
• camllib.1.3.3 on 5.1 is now installable. Current state is: failing
• camlmix.1.3.0 on 5.0 is now installable. Current state is: failing
• camlmix.1.3.0 on 5.1 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
• 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
• charrua-unix.1.0.0 on 4.08 had its build status changed: passing to failing
• charrua-unix.1.0.0 on 4.09 had its build status changed: passing to failing
• charrua-unix.1.0.0 on 4.10 had its build status changed: passing to failing
• charrua-unix.1.0.0 on 4.11 had its build status changed: passing to failing
• charset.0.1.0 on 5.1 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
• combine.0.6 on 5.0 is now installable. Current state is: failing
• combine.0.6 on 5.1 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-libclang.12 on 5.1 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.02 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.03 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.04 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.05 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.06 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.07 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.08 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.09 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.10 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.11 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.12 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.13 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.14 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 5.0 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 5.1 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.02 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.03 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.04 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.05 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.06 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.07 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.08 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.09 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.10 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.11 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.12 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.13 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.14 is now installable. Current state is: failing
• conf-trexio.0.1 on 5.0 is now installable. Current state is: failing
• conf-trexio.0.1 on 5.1 is now installable. Current state is: failing
• coq.8.12.1 on 4.07 had its build status changed: passing to failing
• coq.8.12.2 on 4.11 had its build status changed: passing to failing
• coq.8.13.0 on 4.06 had its build status changed: passing to failing
• coq.8.13.2 on 4.14 is now installable. Current state is: failing
• coq.8.14.1 on 4.07 is now installable. Current state is: failing
• coqide.8.4.5 on 4.02 had its build status changed: passing to failing
• coqide.8.4.6 on 4.02 had its build status changed: passing to failing
• csvfields.v0.15.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: passing 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: passing 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: passing 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: passing to failing
• datalog.0.1 on 5.1 is now installable. Current state is: failing
• datalog.0.2 on 5.1 is now installable. Current state is: failing
• datalog.0.3 on 5.1 is now installable. Current state is: failing
• datalog.0.3.1 on 5.1 is now installable. Current state is: failing
• deriving-yojson.0.2 on 4.02 had its build status changed: passing to failing
• deriving-yojson.0.2 on 4.03 had its build status changed: passing to failing
• deriving-yojson.0.2 on 4.04 had its build status changed: passing to failing
• deriving-yojson.0.2 on 4.05 had its build status changed: passing to failing
• deriving-yojson.0.2 on 4.06 had its build status changed: passing to failing
• deriving-yojson.0.2 on 4.07 had its build status changed: passing to failing
• deriving-yojson.0.3 on 4.02 had its build status changed: passing to failing
• deriving-yojson.0.3 on 4.03 had its build status changed: passing to failing
• deriving-yojson.0.3 on 4.04 had its build status changed: passing to failing
• deriving-yojson.0.3 on 4.05 had its build status changed: passing to failing
• deriving-yojson.0.3 on 4.06 had its build status changed: passing to failing
• deriving-yojson.0.3 on 4.07 had its build status changed: passing to failing
• deriving-yojson.0.3.1 on 4.02 had its build status changed: passing to failing
• deriving-yojson.0.3.1 on 4.03 had its build status changed: passing to failing
• deriving-yojson.0.3.1 on 4.04 had its build status changed: passing to failing
• deriving-yojson.0.3.1 on 4.05 had its build status changed: passing to failing
• deriving-yojson.0.3.1 on 4.06 had its build status changed: passing to failing
• deriving-yojson.0.3.1 on 4.07 had its build status changed: passing to failing
• deriving-yojson.0.4 on 4.02 had its build status changed: passing to failing
• deriving-yojson.0.4 on 4.03 had its build status changed: passing to failing
• deriving-yojson.0.4 on 4.04 had its build status changed: passing to failing
• deriving-yojson.0.4 on 4.05 had its build status changed: passing to failing
• devkit.0.4 on 4.03 had its build status changed: passing to failing
• devkit.0.4 on 4.04 had its build status changed: passing to failing
• devkit.0.4 on 4.05 had its build status changed: passing to failing
• devkit.0.5 on 4.04 had its build status changed: passing to failing
• devkit.0.5 on 4.05 had its build status changed: passing to failing
• devkit.0.5 on 4.06 had its build status changed: passing to failing
• devkit.0.5 on 4.07 had its build status changed: passing to failing
• devkit.0.6 on 4.04 had its build status changed: passing to failing
• devkit.0.6 on 4.05 had its build status changed: passing to failing
• devkit.0.6 on 4.06 had its build status changed: passing to failing
• devkit.0.6 on 4.07 had its build status changed: passing to failing
• devkit.0.6 on 4.08 had its build status changed: passing to failing
• devkit.0.6 on 4.09 had its build status changed: passing to failing
• devkit.0.6 on 4.10 had its build status changed: passing to failing
• devkit.0.6 on 4.11 had its build status changed: passing to failing
• devkit.0.7 on 4.05 had its build status changed: passing to failing
• devkit.0.7 on 4.06 had its build status changed: passing to failing
• devkit.0.7 on 4.07 had its build status changed: passing to failing
• devkit.0.7 on 4.08 had its build status changed: passing to failing
• devkit.0.7 on 4.09 had its build status changed: passing to failing
• devkit.0.7 on 4.11 had its build status changed: passing to failing
• devkit.1.0 on 4.05 had its build status changed: passing to failing
• devkit.1.0 on 4.06 had its build status changed: passing to failing
• devkit.1.0 on 4.08 had its build status changed: passing to failing
• devkit.1.0 on 4.09 had its build status changed: passing to failing
• devkit.1.0 on 4.10 had its build status changed: passing to failing
• devkit.1.0 on 4.11 had its build status changed: passing to failing
• disml.0.2.5 on 4.05 had its build status changed: passing to failing
• distributed.0.6.0 on 5.0 is now installable. Current state is: failing
• distributed.0.6.0 on 5.1 is now installable. Current state is: failing
• docker-api.0.2 on 5.0 is now installable. Current state is: failing
• docker-api.0.2 on 5.1 is now installable. Current state is: failing
• docker-api.0.2.1 on 5.0 is now installable. Current state is: failing
• docker-api.0.2.1 on 5.1 is now installable. Current state is: failing
• docker-api.0.2.2 on 5.0 is now installable. Current state is: failing
• docker-api.0.2.2 on 5.1 is now installable. Current state is: failing
• dolmen.0.1 on 5.0 is now installable. Current state is: failing
• dolmen.0.2 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.0 on 5.1 is now installable. Current state is: failing
• domainslib.0.3.1 on 5.0 is now installable. Current state is: failing
• domainslib.0.3.1 on 5.1 is now installable. Current state is: failing
• domainslib.0.4.0 on 5.0 is now installable. Current state is: failing
• domainslib.0.4.0 on 5.1 is now installable. Current state is: failing
• domainslib.0.4.1 on 5.0 is now installable. Current state is: failing
• domainslib.0.4.1 on 5.1 is now installable. Current state is: failing
• duff.0.2 on 5.1 is now installable. Current state is: failing
• duff.0.3 on 5.1 is now installable. Current state is: failing
• duff.0.4 on 5.1 is now installable. Current state is: failing
• duff.0.5 on 5.1 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
• 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_logging_yojson.0.4 on 4.04 had its build status changed: passing to failing
• easy_logging_yojson.0.4 on 4.05 had its build status changed: passing to failing
• easy_logging_yojson.0.4 on 4.06 had its build status changed: passing to failing
• easy_logging_yojson.0.4 on 4.07 had its build status changed: passing to failing
• easy_logging_yojson.0.4 on 4.08 had its build status changed: passing to failing
• easy_logging_yojson.0.4 on 4.09 had its build status changed: passing to failing
• easy_logging_yojson.0.4 on 4.10 had its build status changed: passing to failing
• easy_logging_yojson.0.4 on 4.11 had its build status changed: passing to failing
• easy_logging_yojson.0.4 on 4.12 had its build status changed: passing to failing
• easy_logging_yojson.0.5 on 4.04 had its build status changed: passing to failing
• easy_logging_yojson.0.5 on 4.05 had its build status changed: passing to failing
• easy_logging_yojson.0.5 on 4.06 had its build status changed: passing to failing
• easy_logging_yojson.0.5 on 4.07 had its build status changed: passing to failing
• easy_logging_yojson.0.5 on 4.08 had its build status changed: passing to failing
• easy_logging_yojson.0.5 on 4.09 had its build status changed: passing to failing
• easy_logging_yojson.0.5 on 4.10 had its build status changed: passing to failing
• easy_logging_yojson.0.5 on 4.11 had its build status changed: passing to failing
• easy_logging_yojson.0.5 on 4.12 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.04 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.05 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.06 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.07 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.08 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.09 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.10 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.11 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.12 had its build status changed: passing to failing
• eigen.0.1.4 on 5.1 is now installable. Current state is: failing
• eigen.0.1.5 on 5.1 is now installable. Current state is: failing
• errpy.0.0.7 on 4.02 is now installable. Current state is: failing
• errpy.0.0.7 on 4.03 is now installable. Current state is: failing
• facile.1.1 on 5.0 is now installable. Current state is: failing
• facile.1.1 on 5.1 is now installable. Current state is: failing
• fasmifra.1.0.0 on 4.03 is now installable. Current state is: failing
• fasmifra.1.0.0 on 4.04 is now installable. Current state is: failing
• fasmifra.1.0.0 on 4.05 is now installable. Current state is: failing
• fasmifra.1.0.0 on 4.06 is now installable. Current state is: failing
• fasmifra.1.0.0 on 4.07 is now installable. Current state is: failing
• fasmifra.1.1.0 on 4.03 is now installable. Current state is: failing
• fasmifra.1.1.0 on 4.04 is now installable. Current state is: failing
• fasmifra.1.1.0 on 4.05 is now installable. Current state is: failing
• fasmifra.1.1.0 on 4.06 is now installable. Current state is: failing
• fasmifra.1.1.0 on 4.07 is now installable. Current state is: failing
• fat-filesystem.0.6.2 on 4.02 had its build status changed: internal failure to failing
• frama-c.21.1 on 4.06 had its build status changed: passing to 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
• gadelac.0.6 on 5.0 is now installable. Current state is: failing
• gammu.0.9.3 on 5.0 is now installable. Current state is: failing
• gammu.0.9.3 on 5.1 is now installable. Current state is: failing
• gapi-ocaml.0.2 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.1 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.1 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.1 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.1 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.10 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.10 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.10 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.10 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.13 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.13 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.13 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.13 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.14 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.14 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.14 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.14 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.3 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.3 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.3 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.3 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.4 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.4 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.4 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.4 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.5 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.5 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.5 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.5 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.6 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.6 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.6 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.6 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.7 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.7 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.7 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.7 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.8 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.8 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.8 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.8 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.2.9 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.2.9 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.2.9 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.2.9 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.3.1 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.3.1 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.3.1 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.3.1 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.3.2 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.3.2 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.3.2 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.3.2 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.3.3 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.3.3 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.3.3 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.3.3 on 4.05 had its build status changed: passing to failing
• gapi-ocaml.0.3.4 on 4.02 had its build status changed: passing to failing
• gapi-ocaml.0.3.4 on 4.03 had its build status changed: passing to failing
• gapi-ocaml.0.3.4 on 4.04 had its build status changed: passing to failing
• gapi-ocaml.0.3.4 on 4.05 had its build status changed: passing to failing
• gdbprofiler.0.1 on 4.04 had its build status changed: passing to failing
• gdbprofiler.0.1 on 4.05 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.03 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.04 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.05 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.06 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.07 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.08 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.09 had its build status changed: passing to failing
• gdbprofiler.0.3 on 4.10 had its build status changed: passing to failing
• gdbprofiler.0.3 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
• gemini.0.1 on 4.08 had its build status changed: passing to failing
• gemini.0.1 on 4.09 had its build status changed: passing to failing
• gemini.0.2.0 on 4.08 had its build status changed: passing to failing
• gemini.0.2.0 on 4.09 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
• get_line.2.1.1 on 4.02 had its build status changed: passing to failing
• get_line.2.1.1 on 4.03 had its build status changed: passing to failing
• get_line.2.1.1 on 4.04 had its build status changed: passing to failing
• get_line.2.1.1 on 4.05 had its build status changed: passing to failing
• get_line.2.1.1 on 4.06 had its build status changed: passing to failing
• get_line.2.1.1 on 4.07 had its build status changed: passing to failing
• get_line.3.0.0 on 4.02 had its build status changed: passing to failing
• get_line.3.0.0 on 4.03 had its build status changed: passing to failing
• get_line.3.0.0 on 4.04 had its build status changed: passing to failing
• get_line.3.0.0 on 4.05 had its build status changed: passing to failing
• get_line.3.0.0 on 4.06 had its build status changed: passing to failing
• get_line.3.0.0 on 4.07 had its build status changed: passing to failing
• get_line.7.0.0 on 4.02 had its build status changed: passing to failing
• get_line.7.0.0 on 4.03 had its build status changed: passing to failing
• get_line.7.0.0 on 4.04 had its build status changed: passing to failing
• get_line.7.0.0 on 4.05 had its build status changed: passing to failing
• get_line.7.0.0 on 4.06 had its build status changed: passing to failing
• get_line.7.0.0 on 4.07 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-unix.3.2.0 on 4.08 had its build status changed: passing to failing
• git-unix.3.2.0 on 4.09 had its build status changed: passing to failing
• git-unix.3.2.0 on 4.10 had its build status changed: passing to failing
• git-unix.3.2.0 on 4.11 had its build status changed: passing to failing
• git-unix.3.2.0 on 4.12 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.08 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.09 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.10 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.11 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.12 had its build status changed: passing to failing
• git-unix.3.3.1 on 4.08 had its build status changed: passing to failing
• git-unix.3.3.1 on 4.09 had its build status changed: passing to failing
• git-unix.3.3.1 on 4.10 had its build status changed: passing to failing
• git-unix.3.3.1 on 4.11 had its build status changed: passing to failing
• git-unix.3.3.1 on 4.12 had its build status changed: passing to failing
• git-unix.3.3.2 on 4.08 had its build status changed: passing to failing
• git-unix.3.3.2 on 4.09 had its build status changed: passing to failing
• git-unix.3.3.2 on 4.10 had its build status changed: passing to failing
• git-unix.3.3.2 on 4.11 had its build status changed: passing to failing
• git-unix.3.3.2 on 4.12 had its build status changed: passing to failing
• git-unix.3.3.3 on 4.08 had its build status changed: passing to failing
• git-unix.3.3.3 on 4.09 had its build status changed: passing to failing
• git-unix.3.3.3 on 4.10 had its build status changed: passing to failing
• git-unix.3.3.3 on 4.11 had its build status changed: passing to failing
• git-unix.3.3.3 on 4.12 had its build status changed: passing 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.0 on 4.04 had its build status changed: passing to failing
• git.1.9.0 on 4.05 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.1 on 4.04 had its build status changed: passing to failing
• git.1.9.1 on 4.05 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.2 on 4.04 had its build status changed: passing to failing
• git.1.9.2 on 4.05 had its build status changed: passing to failing
• git.1.9.3 on 4.03 had its build status changed: passing to failing
• git.1.9.3 on 4.04 had its build status changed: passing to failing
• git.1.9.3 on 4.05 had its build status changed: passing to failing
• goblint-cil.1.8.0 on 4.04 had its build status changed: passing to failing
• goblint-cil.1.8.0 on 4.05 had its build status changed: passing to failing
• goblint-cil.1.8.0 on 4.06 had its build status changed: passing to failing
• goblint-cil.1.8.0 on 4.07 had its build status changed: passing to failing
• goblint-cil.1.8.2 on 4.05 is now installable. Current state is: failing
• goblint-cil.1.8.2 on 4.06 is now installable. Current state is: failing
• goblint-cil.1.8.2 on 4.07 is now installable. Current state is: failing
• graphql.0.1.0 on 4.03 had its build status changed: passing to failing
• graphql.0.1.0 on 4.04 had its build status changed: passing to failing
• graphql.0.1.0 on 4.05 had its build status changed: passing to failing
• graphql.0.1.0 on 4.06 had its build status changed: passing to failing
• graphql.0.1.0 on 4.07 had its build status changed: passing to failing
• graphql.0.1.0 on 4.08 had its build status changed: passing to failing
• graphql.0.1.0 on 4.09 had its build status changed: passing to failing
• graphql.0.1.0 on 4.10 had its build status changed: passing to failing
• graphql.0.1.0 on 4.11 had its build status changed: passing to failing
• graphql.0.1.0 on 4.12 had its build status changed: passing to failing
• graphql.0.2.0 on 4.03 had its build status changed: passing to failing
• graphql.0.2.0 on 4.04 had its build status changed: passing to failing
• graphql.0.2.0 on 4.05 had its build status changed: passing to failing
• graphql.0.2.0 on 4.06 had its build status changed: passing to failing
• graphql.0.2.0 on 4.07 had its build status changed: passing to failing
• graphql.0.2.0 on 4.08 had its build status changed: passing to failing
• graphql.0.2.0 on 4.09 had its build status changed: passing to failing
• graphql.0.2.0 on 4.10 had its build status changed: passing to failing
• graphql.0.2.0 on 4.11 had its build status changed: passing to failing
• graphql.0.2.0 on 4.12 had its build status changed: passing to failing
• graphql.0.4.0 on 4.03 had its build status changed: passing to failing
• graphql.0.4.0 on 4.04 had its build status changed: passing to failing
• graphql.0.4.0 on 4.05 had its build status changed: passing to failing
• graphql.0.4.0 on 4.06 had its build status changed: passing to failing
• graphql.0.4.0 on 4.07 had its build status changed: passing to failing
• graphql.0.4.0 on 4.08 had its build status changed: passing to failing
• graphql.0.4.0 on 4.09 had its build status changed: passing to failing
• graphql.0.4.0 on 4.10 had its build status changed: passing to failing
• graphql.0.4.0 on 4.11 had its build status changed: passing to failing
• graphql.0.4.0 on 4.12 had its build status changed: passing to failing
• graphql.0.5.0 on 4.03 had its build status changed: passing to failing
• graphql.0.5.0 on 4.04 had its build status changed: passing to failing
• graphql.0.5.0 on 4.05 had its build status changed: passing to failing
• graphql.0.5.0 on 4.06 had its build status changed: passing to failing
• graphql.0.5.0 on 4.07 had its build status changed: passing to failing
• graphql.0.5.0 on 4.08 had its build status changed: passing to failing
• graphql.0.5.0 on 4.09 had its build status changed: passing to failing
• graphql.0.5.0 on 4.10 had its build status changed: passing to failing
• graphql.0.5.0 on 4.11 had its build status changed: passing to failing
• graphql.0.5.0 on 4.12 had its build status changed: passing to failing
• graphql.0.6.0 on 4.03 had its build status changed: passing to failing
• graphql.0.6.0 on 4.04 had its build status changed: passing to failing
• graphql.0.6.0 on 4.05 had its build status changed: passing to failing
• graphql.0.6.0 on 4.06 had its build status changed: passing to failing
• graphql.0.6.0 on 4.07 had its build status changed: passing to failing
• graphql.0.6.0 on 4.08 had its build status changed: passing to failing
• graphql.0.6.0 on 4.09 had its build status changed: passing to failing
• graphql.0.6.0 on 4.10 had its build status changed: passing to failing
• graphql.0.6.0 on 4.11 had its build status changed: passing to failing
• graphql.0.6.0 on 4.12 had its build status changed: passing to failing
• graphql.0.7.0 on 4.03 had its build status changed: passing to failing
• graphql.0.7.0 on 4.04 had its build status changed: passing to failing
• graphql.0.7.0 on 4.05 had its build status changed: passing to failing
• graphql.0.7.0 on 4.06 had its build status changed: passing to failing
• graphql.0.7.0 on 4.07 had its build status changed: passing to failing
• graphql.0.7.0 on 4.08 had its build status changed: passing to failing
• graphql.0.7.0 on 4.09 had its build status changed: passing to failing
• graphql.0.7.0 on 4.10 had its build status changed: passing to failing
• graphql.0.7.0 on 4.11 had its build status changed: passing to failing
• graphql.0.7.0 on 4.12 had its build status changed: passing to failing
• graphql.0.8.0 on 4.03 had its build status changed: passing to failing
• graphql.0.8.0 on 4.04 had its build status changed: passing to failing
• graphql.0.8.0 on 4.05 had its build status changed: passing to failing
• graphql.0.8.0 on 4.06 had its build status changed: passing to failing
• graphql.0.8.0 on 4.07 had its build status changed: passing to failing
• graphql.0.8.0 on 4.08 had its build status changed: passing to failing
• graphql.0.8.0 on 4.09 had its build status changed: passing to failing
• graphql.0.8.0 on 4.10 had its build status changed: passing to failing
• graphql.0.8.0 on 4.11 had its build status changed: passing to failing
• graphql.0.8.0 on 4.12 had its build status changed: passing to failing
• grenier.0.11 on 5.1 is now installable. Current state is: failing
• grenier.0.12 on 5.1 is now installable. Current state is: failing
• grenier.0.13 on 5.1 is now installable. Current state is: failing
• grenier.0.14 on 5.1 is now installable. Current state is: failing
• gsl.1.24.3 on 4.13 had its build status changed: passing to 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
• hevea.2.25 on 5.0 is now installable. Current state is: failing
• hevea.2.25 on 5.1 is now installable. Current state is: failing
• hevea.2.28 on 5.0 is now installable. Current state is: failing
• hevea.2.28 on 5.1 is now installable. Current state is: failing
• hevea.2.29 on 5.0 is now installable. Current state is: failing
• hevea.2.29 on 5.1 is now installable. Current state is: failing
• hevea.2.32 on 5.0 is now installable. Current state is: failing
• hevea.2.32 on 5.1 is now installable. Current state is: failing
• hevea.2.35 on 5.0 is now installable. Current state is: failing
• hevea.2.35 on 5.1 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
• horned_worm.0.1.1 on 4.04 had its build status changed: passing to failing
• horned_worm.0.1.1 on 4.05 had its build status changed: passing to failing
• horned_worm.0.3.3 on 4.04 had its build status changed: passing to failing
• horned_worm.0.3.3 on 4.05 had its build status changed: passing to failing
• horned_worm.0.3.3 on 4.06 had its build status changed: passing to failing
• horned_worm.0.3.3 on 4.07 had its build status changed: passing to failing
• horned_worm.0.3.4 on 4.04 had its build status changed: passing to failing
• horned_worm.0.3.4 on 4.05 had its build status changed: passing to failing
• horned_worm.0.3.4 on 4.06 had its build status changed: passing to failing
• horned_worm.0.3.4 on 4.07 had its build status changed: passing to failing
• hts_shrink.2.0.0 on 4.03 had its build status changed: passing to failing
• hts_shrink.2.0.0 on 4.04 had its build status changed: passing to failing
• hts_shrink.2.0.0 on 4.05 had its build status changed: passing to failing
• hts_shrink.2.0.0 on 4.06 had its build status changed: passing to failing
• hts_shrink.2.0.0 on 4.07 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.03 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.04 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.05 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.06 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.07 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.03 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.04 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.05 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.06 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.07 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.03 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.04 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.05 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.06 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.07 had its build status changed: passing to failing
• hweak.1.1 on 5.0 is now installable. Current state is: failing
• hweak.1.1 on 5.1 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
• index.1.2.1 on 4.08 had its build status changed: passing to failing
• index.1.2.1 on 4.09 had its build status changed: passing to failing
• index.1.2.1 on 4.10 had its build status changed: passing to failing
• index.1.2.1 on 4.11 had its build status changed: passing to failing
• iri.0.1.0 on 4.02 had its build status changed: internal failure to failing
• iri.0.1.0 on 4.03 had its build status changed: internal failure to failing
• iri.0.1.0 on 4.04 had its build status changed: internal failure to failing
• iri.0.1.0 on 4.05 had its build status changed: internal failure to failing
• iri.0.2.0 on 4.02 had its build status changed: internal failure to failing
• iri.0.2.0 on 4.03 had its build status changed: internal failure to failing
• iri.0.2.0 on 4.04 had its build status changed: internal failure to failing
• iri.0.2.0 on 4.05 had its build status changed: internal failure to failing
• iri.0.3.0 on 4.02 had its build status changed: internal failure to failing
• iri.0.3.0 on 4.03 had its build status changed: internal failure to failing
• iri.0.3.0 on 4.04 had its build status changed: internal failure to failing
• iri.0.3.0 on 4.05 had its build status changed: internal failure 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
• jhupllib.0.1 on 4.02 had its build status changed: passing to failing
• jhupllib.0.1 on 4.03 had its build status changed: passing to failing
• jhupllib.0.1 on 4.04 had its build status changed: passing to failing
• jhupllib.0.1 on 4.05 had its build status changed: passing to failing
• jhupllib.0.1 on 4.06 had its build status changed: passing to failing
• jhupllib.0.1 on 4.07 had its build status changed: passing to failing
• jhupllib.0.1 on 4.08 had its build status changed: passing to failing
• jhupllib.0.1 on 4.09 had its build status changed: passing to failing
• jhupllib.0.1.1 on 4.05 had its build status changed: passing to failing
• jhupllib.0.1.1 on 4.06 had its build status changed: passing to failing
• jhupllib.0.1.1 on 4.07 had its build status changed: passing to failing
• jhupllib.0.1.1 on 4.08 had its build status changed: passing to failing
• jhupllib.0.1.1 on 4.09 had its build status changed: passing to failing
• jhupllib.0.2.1 on 4.05 had its build status changed: passing to failing
• jhupllib.0.2.1 on 4.06 had its build status changed: passing to failing
• jhupllib.0.2.1 on 4.07 had its build status changed: passing to failing
• jhupllib.0.2.1 on 4.08 had its build status changed: passing to failing
• jhupllib.0.2.1 on 4.09 had its build status changed: passing to failing
• json-pointer.0.1.1-0 on 4.02 had its build status changed: passing to failing
• json-pointer.0.1.1-0 on 4.03 had its build status changed: passing to failing
• json-pointer.0.1.1-0 on 4.04 had its build status changed: passing to failing
• json-pointer.0.1.1-0 on 4.05 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.08 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.09 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.10 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.11 had its build status changed: passing to failing
• jupyter.0.0.0 on 4.04 had its build status changed: passing to failing
• jupyter.0.0.0 on 4.05 had its build status changed: passing to failing
• jupyter.0.0.0 on 4.06 had its build status changed: passing to failing
• jupyter.0.0.0 on 4.07 had its build status changed: passing to failing
• jupyter.0.1.0 on 4.04 had its build status changed: passing to failing
• jupyter.0.1.0 on 4.05 had its build status changed: passing to failing
• jupyter.0.1.0 on 4.06 had its build status changed: passing to failing
• jupyter.0.1.0 on 4.07 had its build status changed: passing to failing
• jupyter.1.0.0 on 4.04 had its build status changed: passing to failing
• jupyter.1.0.0 on 4.05 had its build status changed: passing to failing
• jupyter.1.0.0 on 4.06 had its build status changed: passing to failing
• jupyter.1.0.0 on 4.07 had its build status changed: passing to failing
• jupyter.1.0.1 on 4.04 had its build status changed: passing to failing
• jupyter.1.0.1 on 4.05 had its build status changed: passing to failing
• jupyter.1.0.1 on 4.06 had its build status changed: passing to failing
• jupyter.1.0.1 on 4.07 had its build status changed: passing to failing
• jupyter.1.0.2 on 4.04 had its build status changed: passing to failing
• jupyter.1.0.2 on 4.05 had its build status changed: passing to failing
• jupyter.1.0.2 on 4.06 had its build status changed: passing to failing
• jupyter.1.0.2 on 4.07 had its build status changed: passing to failing
• jupyter.1.1.0 on 4.04 had its build status changed: passing to failing
• jupyter.1.1.0 on 4.05 had its build status changed: passing to failing
• jupyter.1.1.0 on 4.06 had its build status changed: passing to failing
• jupyter.1.1.0 on 4.07 had its build status changed: passing to failing
• jupyter.2.0.0 on 4.02 had its build status changed: passing to failing
• jupyter.2.0.0 on 4.06 had its build status changed: passing to failing
• jupyter.2.0.0 on 4.07 had its build status changed: passing to failing
• jupyter.2.1.0 on 4.02 had its build status changed: passing to failing
• jupyter.2.1.0 on 4.06 had its build status changed: passing to failing
• jupyter.2.1.0 on 4.07 had its build status changed: passing to failing
• jupyter.2.2.0 on 4.06 had its build status changed: passing to failing
• jupyter.2.2.0 on 4.07 had its build status changed: passing to failing
• jupyter.2.2.1 on 4.06 had its build status changed: passing to failing
• jupyter.2.2.1 on 4.07 had its build status changed: passing to failing
• jupyter.2.2.2 on 4.04 had its build status changed: passing to failing
• jupyter.2.3.2 on 4.05 had its build status changed: passing to failing
• jupyter.2.3.2 on 4.06 had its build status changed: passing to failing
• jupyter.2.3.2 on 4.07 had its build status changed: passing to failing
• jupyter.2.3.3 on 4.05 had its build status changed: passing to failing
• jupyter.2.3.3 on 4.06 had its build status changed: passing to failing
• jupyter.2.3.3 on 4.07 had its build status changed: passing to failing
• jupyter.2.3.4 on 4.05 had its build status changed: passing to failing
• jupyter.2.3.4 on 4.06 had its build status changed: passing to failing
• jupyter.2.3.4 on 4.07 had its build status changed: passing to failing
• jupyter.2.3.5 on 4.05 had its build status changed: passing to failing
• jupyter.2.3.5 on 4.06 had its build status changed: passing to failing
• jupyter.2.3.5 on 4.07 had its build status changed: passing to failing
• jupyter.2.4.0 on 4.05 had its build status changed: passing to failing
• jupyter.2.4.0 on 4.06 had its build status changed: passing to failing
• jupyter.2.4.0 on 4.07 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.05 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.06 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.07 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.08 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.09 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.10 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.11 had its build status changed: passing 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
• key-parsers.0.9.1 on 4.04 had its build status changed: passing to failing
• key-parsers.0.9.1 on 4.05 had its build status changed: passing to failing
• key-parsers.0.9.2 on 4.04 had its build status changed: passing to failing
• key-parsers.0.9.2 on 4.05 had its build status changed: passing to failing
• key-parsers.0.9.2 on 4.06 had its build status changed: passing to failing
• key-parsers.0.9.2 on 4.07 had its build status changed: passing to failing
• key-parsers.0.9.2 on 4.08 had its build status changed: passing to failing
• key-parsers.0.9.2 on 4.09 had its build status changed: passing to failing
• key-parsers.0.9.2 on 4.10 had its build status changed: passing to failing
• key-parsers.0.9.2 on 4.11 had its build status changed: passing to failing
• key-parsers.0.9.2 on 4.12 had its build status changed: passing to failing
• kind2.1.5.0 on 5.1 is now installable. Current state is: failing
• kinetic-client.0.0.1 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.08 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.09 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.10 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.11 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.12 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.13 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.14 is now installable. Current state is: failing
• kinetic-client.0.0.3 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.3 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.4 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.4 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.5 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.5 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.6 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.6 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.08 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.09 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.10 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.11 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.12 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.13 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.14 is now installable. Current state is: failing
• labltk.8.06.11 on 4.14 is now installable. Current state is: failing
• labltk.8.06.11 on 5.0 is now installable. Current state is: failing
• labltk.8.06.11 on 5.1 is now installable. Current state is: failing
• labltk.8.06.12 on 4.14 is now installable. Current state is: failing
• labltk.8.06.12 on 5.0 is now installable. Current state is: failing
• labltk.8.06.12 on 5.1 is now installable. Current state is: failing
• libssh.0.1 on 4.14 is now installable. Current state is: failing
• linwrap.0.0.1 on 4.02 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.03 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.04 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.05 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.06 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.07 had its build status changed: passing to failing
• lua-ml.0.9 on 5.0 is now installable. Current state is: failing
• lua-ml.0.9 on 5.1 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
• luv.0.5.0 on 5.0 is now installable. Current state is: failing
• luv.0.5.0 on 5.1 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+11 on 5.0 is now installable. Current state is: failing
• mccs.1.1+11 on 5.1 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
• memtrace.0.1 on 5.0 is now installable. Current state is: failing
• memtrace.0.1 on 5.1 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.20220210 on 5.1 is now installable. Current state is: failing
• merlin-acme.0.1 on 4.02 had its build status changed: passing to failing
• merlin-acme.0.1 on 4.03 had its build status changed: passing to failing
• merlin-acme.0.1 on 4.04 had its build status changed: passing to failing
• merlin-acme.0.1 on 4.05 had its build status changed: passing to failing
• merlin.3.0.3 on 4.02 had its build status changed: passing to failing
• merlin.3.0.3 on 4.03 had its build status changed: passing to failing
• merlin.3.0.3 on 4.04 had its build status changed: passing to failing
• merlin.3.0.3 on 4.05 had its build status changed: passing to failing
• mesh-triangle.0.9.5 on 5.0 is now installable. Current state is: failing
• mesh-triangle.0.9.5 on 5.1 is now installable. Current state is: failing
• meta_conv.1.1.5 on 4.02 had its build status changed: internal failure 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
• minios-xen.0.7 on 4.02 had its build status changed: passing to failing
• minios-xen.0.7 on 4.03 had its build status changed: passing to failing
• minios-xen.0.7 on 4.04 had its build status changed: passing to failing
• minios-xen.0.7 on 4.05 had its build status changed: passing to failing
• minios-xen.0.7 on 4.06 had its build status changed: passing to failing
• minios-xen.0.7 on 4.07 had its build status changed: passing to failing
• minios-xen.0.7 on 4.08 had its build status changed: passing to failing
• minios-xen.0.7 on 4.09 had its build status changed: passing to failing
• minios-xen.0.7 on 4.10 had its build status changed: passing to failing
• minios-xen.0.7 on 4.11 had its build status changed: passing to failing
• minios-xen.0.7 on 4.12 had its build status changed: passing to failing
• minios-xen.0.7 on 4.13 had its build status changed: passing to failing
• minios-xen.0.7 on 4.14 is now installable. Current state is: failing
• minios-xen.0.7 on 5.0 is now installable. Current state is: failing
• minios-xen.0.7 on 5.1 is now installable. Current state is: failing
• minisat.0.3 on 5.1 is now installable. Current state is: failing
• minisat.0.4 on 5.1 is now installable. Current state is: 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
• mirage-fs-unix.1.6.0 on 5.0 is now installable. Current state is: failing
• mirage-fs-unix.1.6.0 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.2 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.07 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.08 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.13 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.14 is now installable. Current state is: failing
• mirage-xen-minios.0.2 on 5.0 is now installable. Current state is: failing
• mirage-xen-minios.0.2 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.3 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.07 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.08 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.13 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.14 is now installable. Current state is: failing
• mirage-xen-minios.0.3 on 5.0 is now installable. Current state is: failing
• mirage-xen-minios.0.3 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.4 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.07 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.08 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.13 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.14 is now installable. Current state is: failing
• mirage-xen-minios.0.4 on 5.0 is now installable. Current state is: failing
• mirage-xen-minios.0.4 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.4.1 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.07 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.08 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.13 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.14 is now installable. Current state is: failing
• mirage-xen-minios.0.4.1 on 5.0 is now installable. Current state is: failing
• mirage-xen-minios.0.4.1 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.4.2 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.07 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.08 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.13 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.14 is now installable. Current state is: failing
• mirage-xen-minios.0.4.2 on 5.0 is now installable. Current state is: failing
• mirage-xen-minios.0.4.2 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.5.0 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.07 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.08 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.13 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.14 is now installable. Current state is: failing
• mirage-xen-minios.0.5.0 on 5.0 is now installable. Current state is: failing
• mirage-xen-minios.0.5.0 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.6.0 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.07 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.08 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.13 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.14 is now installable. Current state is: failing
• mirage-xen-minios.0.6.0 on 5.0 is now installable. Current state is: failing
• mirage-xen-minios.0.6.0 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.7.0 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.08 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.13 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.14 is now installable. Current state is: failing
• mirage-xen-minios.0.7.0 on 5.0 is now installable. Current state is: failing
• mirage-xen-minios.0.7.0 on 5.1 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
• molenc.0.0.1 on 4.04 had its build status changed: passing to failing
• molenc.0.0.1 on 4.05 had its build status changed: passing to failing
• molenc.0.0.1 on 4.06 had its build status changed: passing to failing
• molenc.0.0.1 on 4.07 had its build status changed: passing to failing
• molenc.1.0.0 on 4.04 had its build status changed: passing to failing
• molenc.1.0.0 on 4.05 had its build status changed: passing to failing
• molenc.1.0.0 on 4.06 had its build status changed: passing to failing
• molenc.1.0.0 on 4.07 had its build status changed: passing to failing
• molenc.1.1.0 on 4.04 had its build status changed: passing to failing
• molenc.1.1.0 on 4.05 had its build status changed: passing to failing
• molenc.1.1.0 on 4.06 had its build status changed: passing to failing
• molenc.1.1.0 on 4.07 had its build status changed: passing to failing
• molenc.11.4.0 on 4.06 had its build status changed: passing to failing
• molenc.11.4.0 on 4.07 had its build status changed: passing to failing
• molenc.2.0.0 on 4.04 had its build status changed: passing to failing
• molenc.2.0.0 on 4.05 had its build status changed: passing to failing
• molenc.2.0.0 on 4.06 had its build status changed: passing to failing
• molenc.2.0.0 on 4.07 had its build status changed: passing to failing
• molenc.4.0.2 on 4.04 had its build status changed: passing to failing
• molenc.4.0.2 on 4.05 had its build status changed: passing to failing
• molenc.4.0.2 on 4.06 had its build status changed: passing to failing
• molenc.4.0.2 on 4.07 had its build status changed: passing to failing
• molenc.5.0.0 on 4.04 had its build status changed: passing to failing
• molenc.5.0.0 on 4.05 had its build status changed: passing to failing
• molenc.5.0.0 on 4.06 had its build status changed: passing to failing
• molenc.5.0.0 on 4.07 had its build status changed: passing to failing
• molenc.5.0.1 on 4.04 had its build status changed: passing to failing
• molenc.5.0.1 on 4.05 had its build status changed: passing to failing
• molenc.5.0.1 on 4.06 had its build status changed: passing to failing
• molenc.5.0.1 on 4.07 had its build status changed: passing to failing
• molenc.7.0.1 on 4.02 had its build status changed: passing to failing
• molenc.7.0.1 on 4.03 had its build status changed: passing to failing
• molenc.7.0.1 on 4.04 had its build status changed: passing to failing
• molenc.7.0.1 on 4.05 had its build status changed: passing to failing
• molenc.7.0.1 on 4.06 had its build status changed: passing to failing
• molenc.7.0.1 on 4.07 had its build status changed: passing to failing
• molenc.8.0.2 on 4.02 had its build status changed: passing to failing
• molenc.8.0.2 on 4.03 had its build status changed: passing to failing
• molenc.8.0.2 on 4.04 had its build status changed: passing to failing
• molenc.8.0.2 on 4.05 had its build status changed: passing to failing
• molenc.8.0.2 on 4.06 had its build status changed: passing to failing
• molenc.8.0.2 on 4.07 had its build status changed: passing to failing
• morbig.0.9 on 5.0 is now installable. Current state is: failing
• mosquitto.0.1-0 on 5.0 is now installable. Current state is: failing
• mosquitto.0.1-0 on 5.1 is now installable. Current state is: failing
• mparser.1.2.1 on 5.0 is now installable. Current state is: failing
• mparser.1.2.1 on 5.1 is now installable. Current state is: failing
• multicont.1.0.0~rc.1 on 5.0 is now installable. Current state is: failing
• multicont.1.0.0~rc.1 on 5.1 is now installable. Current state is: failing
• mysql8.1.0 on 4.14 is now installable. Current state is: failing
• mysql8.1.0 on 5.0 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.07 had its build status changed: passing to failing
• netkat.0.1 on 4.08 had its build status changed: passing to failing
• netkat.0.1 on 4.09 had its build status changed: passing to failing
• netkat.0.1 on 4.10 had its build status changed: passing to failing
• netkat.0.1 on 4.11 had its build status changed: passing to failing
• noCanren.0.3.0 on 4.13 is now installable. Current state is: failing
• noCanren.0.3.0~alpha1 on 4.13 is now installable. Current state is: 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
• ocaml-freestanding.0.2.1 on 4.02 had its build status changed: passing to failing
• ocaml-freestanding.0.2.1 on 4.03 had its build status changed: passing to failing
• ocaml-freestanding.0.2.1 on 4.04 had its build status changed: passing to failing
• ocaml-freestanding.0.2.2 on 4.02 had its build status changed: passing to failing
• ocaml-freestanding.0.2.2 on 4.03 had its build status changed: passing to failing
• ocaml-freestanding.0.2.2 on 4.04 had its build status changed: passing to failing
• ocaml-freestanding.0.2.2 on 4.05 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.37.0 on 5.1 is now installable. Current state is: 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.38.0 on 5.1 is now installable. Current state is: 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-makefile.6.39.0 on 5.1 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.3.1 on 5.0 is now installable. Current state is: failing
• ocaml-r.0.3.1 on 5.1 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.4.0 on 5.0 is now installable. Current state is: failing
• ocaml-r.0.4.0 on 5.1 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-r.0.5.0 on 5.0 is now installable. Current state is: failing
• ocaml-r.0.5.0 on 5.1 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 on 5.1 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.93.2 on 5.1 is now installable. Current state is: failing
• ocaml-twt.0.94.0 on 5.0 is now installable. Current state is: failing
• ocaml-twt.0.94.0 on 5.1 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: internal failure 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
• ocamldiff.1.1 on 5.0 is now installable. Current state is: failing
• ocamldiff.1.1 on 5.1 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
• 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.5.0 on 4.03 had its build status changed: passing to failing
• ocf.0.5.0 on 4.04 had its build status changed: passing to failing
• ocf.0.5.0 on 4.05 had its build status changed: passing to failing
• ocf.0.5.0 on 4.06 had its build status changed: passing to failing
• ocf.0.5.0 on 4.07 had its build status changed: passing to failing
• ocp-index-top.0.4.1 on 4.08 had its build status changed: passing to failing
• ocp-index-top.0.4.1 on 4.09 had its build status changed: passing to failing
• ocp-index-top.0.4.3 on 4.08 had its build status changed: passing to failing
• ocp-index-top.0.4.3 on 4.09 had its build status changed: passing to failing
• ocp-index-top.0.5.0 on 4.08 had its build status changed: passing to failing
• ocp-index-top.0.5.0 on 4.09 had its build status changed: passing to failing
• ocp-index.1.3.3 on 5.1 is now installable. Current state is: failing
• ocp-index.1.3.4 on 5.1 is now installable. Current state is: failing
• ocp-pack-split.1.0.1 on 5.0 is now installable. Current state is: failing
• ocp-pack-split.1.0.1 on 5.1 is now installable. Current state is: failing
• ocplib-simplex.0.3 on 5.1 is now installable. Current state is: failing
• ocplib-simplex.0.4 on 5.1 is now installable. Current state is: failing
• ocsigen-start.1.1.0 on 4.03 had its build status changed: partially failing to failing
• ocsigen-start.1.1.0 on 4.04 had its build status changed: partially failing to failing
• ocsigen-start.1.1.0 on 4.05 had its build status changed: partially failing to failing
• ocsigen-start.1.1.0 on 4.06 had its build status changed: partially failing to failing
• odepack.0.6.9 on 4.14 is now installable. Current state is: failing
• odepack.0.6.9 on 5.0 is now installable. Current state is: failing
• odepack.0.6.9 on 5.1 is now installable. Current state is: failing
• odepack.0.7 on 4.14 is now installable. Current state is: failing
• odepack.0.7 on 5.0 is now installable. Current state is: failing
• odepack.0.7 on 5.1 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
• odoc.2.1.1 on 5.1 is now installable. Current state is: failing
• odoc.2.2.0 on 5.1 is now installable. Current state is: failing
• ogg.0.6.0 on 4.14 is now installable. Current state is: failing
• ogg.0.7.0 on 4.14 is now installable. Current state is: failing
• ogg.0.7.1 on 4.14 is now installable. Current state is: failing
• ogg.0.7.2 on 4.14 is now installable. Current state is: failing
• ojs-base.0.5.0 on 4.03 had its build status changed: internal failure to failing
• ojs-base.0.5.0 on 4.04 had its build status changed: internal failure to failing
• olinq.0.1 on 5.0 is now installable. Current state is: failing
• olinq.0.1 on 5.1 is now installable. Current state is: failing
• olinq.0.2 on 5.0 is now installable. Current state is: failing
• olinq.0.2 on 5.1 is now installable. Current state is: failing
• olinq.0.3 on 5.0 is now installable. Current state is: failing
• olinq.0.3 on 5.1 is now installable. Current state is: failing
• opam-depext.1.2.0 on 5.0 is now installable. Current state is: failing
• opam-depext.1.2.0 on 5.1 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.2 on 5.1 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.3 on 5.1 is now installable. Current state is: failing
• opam-file-format.2.1.4 on 5.0 is now installable. Current state is: failing
• opam-file-format.2.1.4 on 5.1 is now installable. Current state is: failing
• opam-monorepo.0.3.4 on 5.1 is now installable. Current state is: failing
• opam-monorepo.0.3.5 on 5.1 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
• openai-gym.0.01 on 4.08 had its build status changed: passing to failing
• openai-gym.0.01 on 4.09 had its build status changed: passing to failing
• openai-gym.0.01 on 4.10 had its build status changed: passing to failing
• openai-gym.0.01 on 4.11 had its build status changed: passing to failing
• openai-gym.0.01 on 4.12 had its build status changed: passing to failing
• opentelemetry-cohttp-lwt.0.4 on 4.08 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.09 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.10 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.11 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.12 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.13 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.14 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 5.0 is now installable. Current state is: failing
• operf-micro.1.1.1 on 5.0 is now installable. Current state is: failing
• operf-micro.1.1.1 on 5.1 is now installable. Current state is: failing
• opium.0.15.1 on 4.03 had its build status changed: passing to failing
• opium.0.15.1 on 4.04 had its build status changed: passing to failing
• opium.0.15.1 on 4.05 had its build status changed: passing to failing
• opium.0.15.1 on 4.06 had its build status changed: passing to 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
• oplsr.8.0.1 on 5.0 is now installable. Current state is: failing
• opsian.0.1 on 5.0 is now installable. Current state is: failing
• opsian.0.1 on 5.1 is now installable. Current state is: failing
• orpie.1.6.0 on 4.05 had its build status changed: passing to failing
• orpie.1.6.1 on 4.05 had its build status changed: passing to 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
• orun.0.0.1 on 5.0 is now installable. Current state is: failing
• orun.0.0.1 on 5.1 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
• paf-cohttp.0.5.0 on 4.08 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.09 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.10 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.11 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.12 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.13 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.14 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 5.0 is now installable. Current state is: failing
• paf.0.0.1 on 4.08 had its build status changed: passing to failing
• paf.0.0.1 on 4.09 had its build status changed: passing to failing
• paf.0.0.1 on 4.10 had its build status changed: passing to failing
• paf.0.0.1 on 4.11 had its build status changed: passing to failing
• paf.0.0.1 on 4.12 had its build status changed: passing to failing
• paf.0.0.1 on 4.13 had its build status changed: passing to failing
• paf.0.0.1 on 4.14 is now installable. Current state is: failing
• paf.0.0.1 on 5.0 is now installable. Current state is: failing
• paf.0.0.2 on 4.08 had its build status changed: passing to failing
• paf.0.0.2 on 4.09 had its build status changed: passing to failing
• paf.0.0.2 on 4.10 had its build status changed: passing to failing
• paf.0.0.2 on 4.11 had its build status changed: passing to failing
• paf.0.0.2 on 4.12 had its build status changed: passing to failing
• paf.0.0.2 on 4.13 had its build status changed: passing to failing
• paf.0.0.2 on 4.14 is now installable. Current state is: failing
• paf.0.0.3 on 4.08 had its build status changed: passing to failing
• paf.0.0.3 on 4.09 had its build status changed: passing to failing
• paf.0.0.3 on 4.10 had its build status changed: passing to failing
• paf.0.0.3 on 4.11 had its build status changed: passing to failing
• paf.0.0.3 on 4.12 had its build status changed: passing to failing
• paf.0.0.3 on 4.13 had its build status changed: passing to failing
• paf.0.0.3 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
• papi.0.1.1 on 5.1 is now installable. Current state is: failing
• pardi.1.0.1 on 4.05 had its build status changed: passing to failing
• pardi.1.0.1 on 4.06 had its build status changed: passing to failing
• pardi.1.0.1 on 4.07 had its build status changed: passing to failing
• pardi.2.0.2 on 4.05 had its build status changed: passing to failing
• pardi.2.0.2 on 4.06 had its build status changed: passing to failing
• pardi.2.0.2 on 4.07 had its build status changed: passing to failing
• pardi.2.0.3 on 4.05 had its build status changed: passing to failing
• pardi.2.0.3 on 4.06 had its build status changed: passing to failing
• pardi.2.0.3 on 4.07 had its build status changed: passing to failing
• pardi.2.0.4 on 4.05 had its build status changed: passing to failing
• pardi.2.0.4 on 4.06 had its build status changed: passing to failing
• pardi.2.0.4 on 4.07 had its build status changed: passing to failing
• pds-reachability.0.2 on 4.07 had its build status changed: passing to failing
• pds-reachability.0.2.1 on 4.07 had its build status changed: passing 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
• podge.0.4 on 4.02 had its build status changed: passing to failing
• podge.0.4 on 4.03 had its build status changed: passing to failing
• podge.0.4 on 4.04 had its build status changed: passing to failing
• podge.0.4 on 4.05 had its build status changed: passing to failing
• podge.0.5 on 4.02 had its build status changed: passing to failing
• podge.0.5 on 4.03 had its build status changed: passing to failing
• podge.0.5 on 4.04 had its build status changed: passing to failing
• podge.0.5 on 4.05 had its build status changed: passing to failing
• podge.0.7.0 on 4.02 had its build status changed: passing to failing
• podge.0.7.0 on 4.03 had its build status changed: passing to failing
• podge.0.7.0 on 4.04 had its build status changed: passing to failing
• podge.0.7.0 on 4.05 had its build status changed: passing to failing
• podge.0.8.0 on 4.04 had its build status changed: passing to failing
• podge.0.8.0 on 4.05 had its build status changed: passing to failing
• ppx_deriving_protocol.0.8 on 4.03 had its build status changed: passing to failing
• ppx_deriving_protocol.0.8 on 4.04 had its build status changed: passing to failing
• ppx_deriving_protocol.0.8 on 4.05 had its build status changed: passing to failing
• ppx_deriving_protocol.0.8 on 4.06 had its build status changed: passing to failing
• ppx_deriving_protocol.0.8 on 4.07 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.02 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.03 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.04 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.05 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.06 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.07 had its build status changed: passing to 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_pbt.0.2.1 on 4.10 is now installable. Current state is: failing
• ppx_pbt.0.2.1 on 4.11 is now installable. Current state is: failing
• ppx_pbt.0.2.1 on 4.12 is now installable. Current state is: failing
• ppx_pbt.0.2.1 on 4.13 is now installable. Current state is: 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.1 on 4.02 had its build status changed: internal failure to failing
• prof_spacetime.0.1.0 on 4.04 had its build status changed: passing to failing
• prof_spacetime.0.1.0 on 4.05 had its build status changed: passing to failing
• protocol-9p.1.0.0 on 5.0 is now installable. Current state is: failing
• protocol-9p.1.0.1 on 5.0 is now installable. Current state is: failing
• proverif.2.00 on 5.0 is now installable. Current state is: failing
• proverif.2.00 on 5.1 is now installable. Current state is: failing
• radare2.0.0.1 on 4.03 had its build status changed: passing to failing
• radare2.0.0.1 on 4.04 had its build status changed: passing to failing
• radare2.0.0.1 on 4.05 had its build status changed: passing to failing
• radare2.0.0.2 on 4.03 had its build status changed: passing to failing
• radare2.0.0.2 on 4.04 had its build status changed: passing to failing
• radare2.0.0.2 on 4.05 had its build status changed: passing to failing
• radare2.0.0.2 on 4.06 had its build status changed: passing to failing
• radare2.0.0.2 on 4.07 had its build status changed: passing to failing
• radare2.0.0.2 on 4.08 had its build status changed: passing to failing
• radare2.0.0.2 on 4.09 had its build status changed: passing to failing
• radare2.0.0.2 on 4.10 had its build status changed: passing to failing
• radare2.0.0.2 on 4.11 had its build status changed: passing to failing
• radare2.0.0.2 on 4.12 had its build status changed: passing to failing
• radare2.0.0.2 on 4.13 had its build status changed: passing to failing
• radare2.0.0.2 on 4.14 is now installable. Current state is: failing
• randoml.0.1.5 on 5.0 is now installable. Current state is: failing
• rdf.0.11.0 on 4.03 had its build status changed: passing to failing
• rdf.0.11.0 on 4.04 had its build status changed: passing to failing
• rdf.0.11.0 on 4.05 had its build status changed: passing to failing
• rdf.0.11.0 on 4.06 had its build status changed: passing to failing
• rdf.0.11.0 on 4.07 had its build status changed: internal failure to failing
• rdf.0.11.0 on 4.08 had its build status changed: internal failure to failing
• rdf.0.11.0 on 4.09 had its build status changed: passing to failing
• rdf.0.11.0 on 4.10 had its build status changed: passing to failing
• rdf.0.12.0 on 4.12 had its build status changed: passing to failing
• rdf.0.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
• records.0.6.0 on 4.02 had its build status changed: passing to failing
• records.0.6.0 on 4.03 had its build status changed: passing to failing
• records.0.6.0 on 4.04 had its build status changed: passing to failing
• records.0.6.0 on 4.05 had its build status changed: passing to failing
• records.0.6.0 on 4.06 had its build status changed: passing to failing
• records.0.6.0 on 4.07 had its build status changed: passing to failing
• records.0.6.0 on 4.08 had its build status changed: passing to failing
• resto-cohttp-server.1.1 on 4.10 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 4.11 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 4.12 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 4.13 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 4.14 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 5.0 is now installable. Current state is: 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.13 had its build status changed: not available to failing
• rfsm.1.5 on 4.14 is now installable. Current state is: failing
• rml.1.09.06 on 5.1 is now installable. Current state is: failing
• rml.1.09.07 on 5.1 is now installable. Current state is: failing
• rmlbuild.0.14.0-00 on 5.0 is now installable. Current state is: failing
• rmlbuild.0.14.0-00 on 5.1 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
• rpc.2.2.0 on 4.02 had its build status changed: passing to failing
• rpc.2.2.0 on 4.03 had its build status changed: passing to failing
• rpc.2.2.0 on 4.04 had its build status changed: passing to failing
• rpc.2.2.0 on 4.05 had its build status changed: passing to failing
• rpclib.6.0.0 on 4.04 had its build status changed: passing to failing
• rpclib.6.0.0 on 4.05 had its build status changed: passing to failing
• rpclib.6.0.0 on 4.06 had its build status changed: passing to failing
• rpclib.6.0.0 on 4.07 had its build status changed: passing to failing
• rpclib.6.0.0 on 4.08 had its build status changed: passing to failing
• rpclib.6.0.0 on 4.09 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
• scid.1.0 on 5.0 is now installable. Current state is: failing
• scid.1.0 on 5.1 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
• slacko.0.10.0 on 4.02 had its build status changed: passing to failing
• slacko.0.10.0 on 4.03 had its build status changed: passing to failing
• slacko.0.10.0 on 4.04 had its build status changed: passing to failing
• slacko.0.10.0 on 4.05 had its build status changed: passing to failing
• slacko.0.11.0 on 4.02 had its build status changed: passing to failing
• slacko.0.11.0 on 4.03 had its build status changed: passing to failing
• slacko.0.11.0 on 4.04 had its build status changed: passing to failing
• slacko.0.11.0 on 4.05 had its build status changed: passing to failing
• slacko.0.11.0 on 4.06 had its build status changed: passing to failing
• slacko.0.12.0 on 4.02 had its build status changed: passing to failing
• slacko.0.12.0 on 4.03 had its build status changed: passing to failing
• slacko.0.12.0 on 4.04 had its build status changed: passing to failing
• slacko.0.12.0 on 4.05 had its build status changed: passing to failing
• slacko.0.12.0 on 4.06 had its build status changed: passing to failing
• slacko.0.13.0 on 4.04 had its build status changed: passing to failing
• slacko.0.13.0 on 4.05 had its build status changed: passing to failing
• slacko.0.13.0 on 4.06 had its build status changed: passing to failing
• slacko.0.9.0 on 4.02 had its build status changed: passing to failing
• slacko.0.9.0 on 4.03 had its build status changed: passing to failing
• slacko.0.9.0 on 4.04 had its build status changed: passing to failing
• slacko.0.9.0 on 4.05 had its build status changed: passing to failing
• slacko.0.9.1 on 4.02 had its build status changed: passing to failing
• slacko.0.9.1 on 4.03 had its build status changed: passing to failing
• slacko.0.9.1 on 4.04 had its build status changed: passing to failing
• slacko.0.9.1 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.02 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.03 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.04 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.06 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.07 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.08 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.09 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.10 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.11 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.12 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.13 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.14 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.5 on 5.0 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.5 on 5.1 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.6 on 4.02 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.07 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.08 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.09 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.10 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.12 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.13 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.14 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.6 on 5.0 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.6 on 5.1 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.7 on 4.02 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.07 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.08 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.09 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.10 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.11 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.12 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.13 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.14 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.7 on 5.0 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.7 on 5.1 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.8 on 4.02 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.07 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.08 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.09 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.10 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.11 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.12 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.13 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.14 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.8 on 5.0 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.8 on 5.1 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.02 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.03 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.04 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.05 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.06 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.07 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.09 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.10 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.11 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.12 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.13 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.5 on 4.02 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.03 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.04 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.05 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.06 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.07 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.08 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.09 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.10 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.11 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.12 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.13 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.14 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.5 on 5.0 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.5 on 5.1 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.6 on 4.02 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.07 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.08 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.09 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.10 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.11 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.12 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.13 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.14 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.6 on 5.0 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.6 on 5.1 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.7 on 4.02 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.07 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.08 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.09 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.10 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.11 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.12 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.13 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.14 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.7 on 5.0 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.7 on 5.1 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.8 on 4.02 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.07 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.08 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.09 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.10 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.11 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.12 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.13 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.14 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.8 on 5.0 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.8 on 5.1 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.02 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.03 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.04 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.05 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.06 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.07 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.08 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.09 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.10 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.11 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.12 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.13 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.5 on 4.02 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.03 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.04 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.05 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.06 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.07 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.08 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.09 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.10 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.11 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.12 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.13 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.14 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.5 on 5.0 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.5 on 5.1 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.6 on 4.02 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.07 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.08 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.09 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.10 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.11 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.12 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.13 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.14 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.6 on 5.0 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.6 on 5.1 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.7 on 4.02 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.07 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.08 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.09 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.10 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.11 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.12 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.13 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.14 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.7 on 5.0 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.7 on 5.1 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.8 on 4.02 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.07 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.08 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.09 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.10 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.11 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.12 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.13 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.14 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.8 on 5.0 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.8 on 5.1 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.02 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.03 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.04 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.05 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.06 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.07 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.08 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.09 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.10 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.11 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.12 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.13 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.5 on 4.02 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.03 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.04 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.05 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.06 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.07 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.08 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.09 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.10 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.11 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.12 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.13 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.14 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.5 on 5.0 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.5 on 5.1 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.6 on 4.02 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.07 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.08 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.09 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.10 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.11 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.12 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.13 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.14 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.6 on 5.0 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.6 on 5.1 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.7 on 4.02 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.07 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.08 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.09 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.10 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.11 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.12 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.13 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.14 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.7 on 5.0 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.7 on 5.1 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.8 on 4.02 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.07 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.08 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.09 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.10 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.11 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.12 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.13 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.14 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.8 on 5.0 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.8 on 5.1 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.02 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.03 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.04 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.05 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.06 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.07 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.08 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.09 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.10 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.11 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.12 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.13 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.6 on 4.02 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.07 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.08 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.09 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.10 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.11 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.12 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.13 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.14 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.6 on 5.0 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.6 on 5.1 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.7 on 4.02 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.07 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.08 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.09 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.10 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.11 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.12 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.13 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.14 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.7 on 5.0 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.7 on 5.1 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.8 on 4.02 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.07 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.08 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.09 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.10 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.11 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.12 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.13 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.14 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.8 on 5.0 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.8 on 5.1 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.02 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.03 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.04 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.05 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.06 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.07 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.08 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.09 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.10 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.11 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.12 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.13 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5.0.7.0 on 4.02 is now installable. Current state is: failing
• solo5.0.7.0 on 4.03 is now installable. Current state is: failing
• solo5.0.7.0 on 4.04 is now installable. Current state is: failing
• solo5.0.7.0 on 4.05 is now installable. Current state is: failing
• solo5.0.7.0 on 4.06 is now installable. Current state is: failing
• solo5.0.7.0 on 4.07 is now installable. Current state is: failing
• solo5.0.7.0 on 4.08 is now installable. Current state is: failing
• solo5.0.7.0 on 4.09 is now installable. Current state is: failing
• solo5.0.7.0 on 4.10 is now installable. Current state is: failing
• solo5.0.7.0 on 4.11 is now installable. Current state is: failing
• solo5.0.7.0 on 4.12 is now installable. Current state is: failing
• solo5.0.7.0 on 4.13 is now installable. Current state is: failing
• solo5.0.7.0 on 4.14 is now installable. Current state is: failing
• solo5.0.7.0 on 5.0 is now installable. Current state is: failing
• solo5.0.7.0 on 5.1 is now installable. Current state is: failing
• solo5.0.7.1 on 4.02 is now installable. Current state is: failing
• solo5.0.7.1 on 4.03 is now installable. Current state is: failing
• solo5.0.7.1 on 4.04 is now installable. Current state is: failing
• solo5.0.7.1 on 4.05 is now installable. Current state is: failing
• solo5.0.7.1 on 4.06 is now installable. Current state is: failing
• solo5.0.7.1 on 4.07 is now installable. Current state is: failing
• solo5.0.7.1 on 4.08 is now installable. Current state is: failing
• solo5.0.7.1 on 4.09 is now installable. Current state is: failing
• solo5.0.7.1 on 4.10 is now installable. Current state is: failing
• solo5.0.7.1 on 4.11 is now installable. Current state is: failing
• solo5.0.7.1 on 4.12 is now installable. Current state is: failing
• solo5.0.7.1 on 4.13 is now installable. Current state is: failing
• solo5.0.7.1 on 4.14 is now installable. Current state is: failing
• solo5.0.7.1 on 5.0 is now installable. Current state is: failing
• solo5.0.7.1 on 5.1 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
• sparrow.0.1 on 4.03 had its build status changed: passing to failing
• srt.0.2.2 on 4.03 is now installable. Current state is: failing
• srt.0.2.2 on 4.04 is now installable. Current state is: failing
• srt.0.2.2 on 4.05 is now installable. Current state is: failing
• srt.0.2.2 on 4.06 is now installable. Current state is: failing
• srt.0.2.2 on 4.07 is now installable. Current state is: failing
• srt.0.3.0 on 4.03 is now installable. Current state is: failing
• srt.0.3.0 on 4.04 is now installable. Current state is: failing
• srt.0.3.0 on 4.05 is now installable. Current state is: failing
• srt.0.3.0 on 4.06 is now installable. Current state is: failing
• srt.0.3.0 on 4.07 is now installable. Current state is: failing
• stb_truetype.0.5 on 4.02 had its build status changed: passing to failing
• stb_truetype.0.5 on 4.03 had its build status changed: passing to failing
• stb_truetype.0.5 on 4.04 had its build status changed: passing to failing
• stb_truetype.0.6 on 4.02 had its build status changed: passing to failing
• stb_truetype.0.6 on 4.03 had its build status changed: passing to failing
• stb_truetype.0.6 on 4.04 had its build status changed: passing to failing
• stdcompat.0 on 5.0 is now installable. Current state is: failing
• stdcompat.0 on 5.1 is now installable. Current state is: failing
• stdcompat.1 on 5.0 is now installable. Current state is: failing
• stdcompat.1 on 5.1 is now installable. Current state is: failing
• stog.0.19.0 on 4.12 had its build status changed: passing to failing
• stog.0.20.0 on 4.12 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.03 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.04 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.05 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.06 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.07 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.08 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.09 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.10 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.11 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.12 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.13 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.03 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.04 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.05 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.06 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.07 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.08 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.09 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.10 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.11 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.12 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.13 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.03 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.04 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.05 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.06 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.07 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.08 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.09 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.10 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.11 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.12 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.13 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.03 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.04 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.05 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.06 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.07 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.08 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.09 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.10 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.11 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.12 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.13 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.03 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.04 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.05 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.06 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.07 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.08 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.09 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.10 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.11 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.12 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.13 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.14 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
• 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
• telegraml.1.0 on 4.02 had its build status changed: passing to failing
• telegraml.1.0 on 4.03 had its build status changed: passing to failing
• telegraml.1.0 on 4.04 had its build status changed: passing to failing
• telegraml.1.0 on 4.05 had its build status changed: passing to failing
• telegraml.1.0 on 4.06 had its build status changed: passing to failing
• telegraml.1.1 on 4.02 had its build status changed: passing to failing
• telegraml.1.1 on 4.03 had its build status changed: passing to failing
• telegraml.1.1 on 4.04 had its build status changed: passing to failing
• telegraml.1.1 on 4.05 had its build status changed: passing to failing
• telegraml.1.1 on 4.06 had its build status changed: passing to failing
• telegraml.1.2 on 4.02 had its build status changed: passing to failing
• telegraml.1.2 on 4.03 had its build status changed: passing to failing
• telegraml.1.2 on 4.04 had its build status changed: passing to failing
• telegraml.1.2 on 4.05 had its build status changed: passing to failing
• telegraml.1.2 on 4.06 had its build status changed: passing to failing
• telegraml.2.0.0 on 4.02 had its build status changed: passing to failing
• telegraml.2.0.0 on 4.03 had its build status changed: passing to failing
• telegraml.2.0.0 on 4.04 had its build status changed: passing to failing
• telegraml.2.0.0 on 4.05 had its build status changed: passing to failing
• telegraml.2.0.0 on 4.06 had its build status changed: passing to failing
• telegraml.2.1.0 on 4.02 had its build status changed: passing to failing
• telegraml.2.1.0 on 4.03 had its build status changed: passing to failing
• telegraml.2.1.0 on 4.04 had its build status changed: passing to failing
• telegraml.2.1.0 on 4.05 had its build status changed: passing to failing
• telegraml.2.1.0 on 4.06 had its build status changed: passing to failing
• telegraml.2.1.1 on 4.02 had its build status changed: passing to failing
• telegraml.2.1.1 on 4.03 had its build status changed: passing to failing
• telegraml.2.1.1 on 4.04 had its build status changed: passing to failing
• telegraml.2.1.1 on 4.05 had its build status changed: passing to failing
• telegraml.2.1.1 on 4.06 had its build status changed: passing to failing
• telegraml.2.1.2 on 4.02 had its build status changed: passing to failing
• telegraml.2.1.2 on 4.03 had its build status changed: passing to failing
• telegraml.2.1.2 on 4.04 had its build status changed: passing to failing
• telegraml.2.1.2 on 4.05 had its build status changed: passing to failing
• telegraml.2.1.2 on 4.06 had its build status changed: passing to failing
• telegraml.2.1.3 on 4.02 had its build status changed: passing to failing
• telegraml.2.1.3 on 4.03 had its build status changed: passing to failing
• telegraml.2.1.3 on 4.04 had its build status changed: passing to failing
• telegraml.2.1.3 on 4.05 had its build status changed: passing to failing
• telegraml.2.1.3 on 4.06 had its build status changed: passing to failing
• telegraml.2.1.4 on 4.02 had its build status changed: passing to failing
• telegraml.2.1.4 on 4.03 had its build status changed: passing to failing
• telegraml.2.1.4 on 4.04 had its build status changed: passing to failing
• telegraml.2.1.4 on 4.05 had its build status changed: passing to failing
• telegraml.2.1.4 on 4.06 had its build status changed: passing to failing
• testrunner.0.1.0 on 4.03 had its build status changed: passing to failing
• testrunner.0.1.0 on 4.04 had its build status changed: passing to failing
• testrunner.0.1.0 on 4.05 had its build status changed: internal failure to failing
• testrunner.0.1.0 on 4.06 had its build status changed: passing to failing
• testrunner.0.1.0 on 4.07 had its build status changed: passing to failing
• tezos-sapling.11.0 on 4.12 is now installable. Current state is: failing
• tezos-sapling.11.0 on 4.13 is now installable. Current state is: failing
• tezos-sapling.11.0 on 4.14 is now installable. Current state is: failing
• tezos-sapling.11.1 on 4.12 is now installable. Current state is: failing
• tezos-sapling.11.1 on 4.13 is now installable. Current state is: failing
• tezos-sapling.11.1 on 4.14 is now installable. Current state is: failing
• tezos-sapling.12.0 on 4.12 is now installable. Current state is: failing
• tezos-sapling.12.0 on 4.13 is now installable. Current state is: failing
• tezos-sapling.12.0 on 4.14 is now installable. Current state is: failing
• tezos-sapling.12.3 on 4.12 is now installable. Current state is: failing
• tezos-sapling.12.3 on 4.13 is now installable. Current state is: failing
• tezos-sapling.12.3 on 4.14 is now installable. Current state is: failing
• tezos-stdlib-unix.10.2 on 4.08 is now installable. Current state is: failing
• tezos-stdlib-unix.10.2 on 4.09 is now installable. Current state is: failing
• tezos-stdlib-unix.10.2 on 4.10 is now installable. Current state is: failing
• tezos-stdlib-unix.10.2 on 4.11 is now installable. Current state is: failing
• tezos-stdlib-unix.8.0 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.8.0 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.8.0 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.8.0 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.8.1 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.8.1 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.8.1 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.8.1 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.8.2 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.8.2 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.8.2 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.8.2 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.8.3 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.8.3 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.8.3 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.8.3 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.2 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.2 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.2 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.2 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.3 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.3 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.3 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.3 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.4 on 4.08 is now installable. Current state is: failing
• tezos-stdlib-unix.9.4 on 4.09 is now installable. Current state is: failing
• tezos-stdlib-unix.9.4 on 4.10 is now installable. Current state is: failing
• tezos-stdlib-unix.9.4 on 4.11 is now installable. Current state is: failing
• tezos-stdlib-unix.9.7 on 4.08 is now installable. Current state is: failing
• tezos-stdlib-unix.9.7 on 4.09 is now installable. Current state is: failing
• tezos-stdlib-unix.9.7 on 4.10 is now installable. Current state is: failing
• tezos-stdlib-unix.9.7 on 4.11 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
• toplevel_backend.v0.15.0 on 5.0 is now installable. Current state is: failing
• toplevel_expect_test.v0.15.0 on 5.0 is now installable. Current state is: failing
• tplib.1.3 on 5.0 is now installable. Current state is: failing
• tplib.1.3 on 5.1 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
• utop.2.10.0 on 5.1 is now installable. Current state is: failing
• utop.2.11.0 on 5.1 is now installable. Current state is: 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
• 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 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.09 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.10 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.11 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.12 had its build status changed: passing to failing
• wamp.0.1 on 4.05 had its build status changed: passing to failing
• wamp.0.1 on 4.06 had its build status changed: passing to failing
• wamp.0.1 on 4.07 had its build status changed: passing to failing
• wamp.0.1 on 4.08 had its build status changed: passing to failing
• wamp.0.1 on 4.09 had its build status changed: passing to failing
• wamp.0.1 on 4.10 had its build status changed: passing to failing
• wamp.0.1 on 4.11 had its build status changed: passing to failing
• wamp.0.1 on 4.12 had its build status changed: passing to failing
• wasm.2.0.0 on 5.0 is now installable. Current state is: failing
• wasm.2.0.0 on 5.1 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-async.2.16 on 4.11 is now installable. Current state is: failing
• websocket-async.2.16 on 4.12 is now installable. Current state is: failing
• websocket-async.2.16 on 4.13 is now installable. Current state is: failing
• websocket-async.2.16 on 4.14 is now installable. Current state is: failing
• websocket-async.2.16 on 5.0 is now installable. Current state is: failing
• xen-api-client.0.9.10 on 4.02 had its build status changed: partially failing to failing
• xen-api-client.0.9.8 on 4.02 had its build status changed: partially failing to 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
• xtmpl.0.15.0 on 4.03 had its build status changed: internal failure to failing
• xtmpl.0.15.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
• z3.4.11.0 on 5.0 is now installable. Current state is: failing
• z3.4.8.13 on 4.02 is now installable. Current state is: failing
• z3.4.8.14 on 5.0 is now installable. Current state is: failing
• z3.4.8.14 on 5.1 is now installable. Current state is: failing