Packages now failing:
- 0install.2.12.1 on 4.03 had its build status changed: internal failure to failing
- 0install.2.12.3 on 4.02 had its build status changed: passing to failing
- 0install.2.12.3 on 4.03 had its build status changed: passing to failing
- 0install.2.12.3 on 4.04 had its build status changed: passing to failing
- 0install.2.12.3 on 4.05 had its build status changed: passing to failing
- 0install.2.12.3 on 4.06 had its build status changed: passing to failing
- 0install.2.14 on 4.03 had its build status changed: passing to failing
- 0install.2.14 on 4.04 had its build status changed: passing to failing
- 0install.2.14 on 4.05 had its build status changed: passing to failing
- 0install.2.14 on 4.06 had its build status changed: passing to failing
- 0install.2.14 on 4.07 had its build status changed: passing to failing
- 0install.2.14.1 on 4.03 had its build status changed: passing to failing
- 0install.2.14.1 on 4.04 had its build status changed: passing to failing
- 0install.2.14.1 on 4.05 had its build status changed: passing to failing
- 0install.2.14.1 on 4.06 had its build status changed: passing to failing
- 0install.2.14.1 on 4.07 had its build status changed: passing to failing
- 0install.2.14.1 on 4.08 had its build status changed: passing to failing
- 0install.2.14.1 on 4.09 had its build status changed: passing to failing
- 0install.2.14.1 on 4.11 had its build status changed: passing to failing
- ANSITerminal.0.7 on 5.0 is now installable. Current state is: failing
- ANSITerminal.0.7 on 5.0+alpha-repo is now installable. Current state is: failing
- BetterErrors.0.0.1 on 5.0 is now installable. Current state is: failing
- BetterErrors.0.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- DrawGrammar.0.1.0 on 4.02 had its build status changed: partially failing to failing
- DrawGrammar.0.1.0 on 4.03 had its build status changed: partially failing to failing
- DrawGrammar.0.1.0 on 4.04 had its build status changed: partially failing to failing
- DrawGrammar.0.1.0 on 4.05 had its build status changed: partially failing to failing
- DrawGrammar.0.2.0 on 4.02 had its build status changed: partially failing to failing
- DrawGrammar.0.2.0 on 4.03 had its build status changed: partially failing to failing
- DrawGrammar.0.2.0 on 4.05 had its build status changed: partially failing to failing
- GuaCaml.0.02 on 5.0 is now installable. Current state is: failing
- GuaCaml.0.02 on 5.0+alpha-repo is now installable. Current state is: failing
- TCSLib.0.1 on 5.0 is now installable. Current state is: failing
- TCSLib.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- TCSLib.0.2 on 5.0 is now installable. Current state is: failing
- TCSLib.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- TCSLib.0.3 on 5.0 is now installable. Current state is: failing
- TCSLib.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- acgtk.1.5.0 on 5.0 is now installable. Current state is: failing
- acgtk.1.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- aez.0.3 on 5.0 is now installable. Current state is: failing
- aez.0.3 on 5.0+alpha-repo is now installable. Current state is: 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- aio.0.0.3 on 5.0 is now installable. Current state is: failing
- aio.0.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- alba.0.4.0 on 5.0 is now installable. Current state is: failing
- alba.0.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- alba.0.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- alba.0.4.2 on 5.0+alpha-repo is now installable. Current state is: failing
- alba.0.4.3 on 5.0+alpha-repo is now installable. Current state is: failing
- alt-ergo-free.2.2.0 on 5.0 is now installable. Current state is: failing
- alt-ergo-free.2.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- alt-ergo-lib.2.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- alt-ergo-lib.2.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- alt-ergo.0.95.2 on 5.0 is now installable. Current state is: failing
- alt-ergo.0.95.2 on 5.0+alpha-repo is now installable. Current state is: failing
- alt-ergo.0.99.1 on 5.0 is now installable. Current state is: failing
- alt-ergo.0.99.1 on 5.0+alpha-repo is now installable. Current state is: failing
- alt-ergo.1.01 on 5.0 is now installable. Current state is: failing
- alt-ergo.1.01 on 5.0+alpha-repo is now installable. Current state is: failing
- ancient.0.9.1 on 5.0 is now installable. Current state is: failing
- ancient.0.9.1 on 5.0+alpha-repo is now installable. Current state is: failing
- archimedes.0.4.18 on 5.0+alpha-repo is now installable. Current state is: failing
- asl.0.10 on 5.0 is now installable. Current state is: failing
- asl.0.10 on 5.0+alpha-repo is now installable. Current state is: failing
- asl.0.9 on 5.0 is now installable. Current state is: failing
- asl.0.9 on 5.0+alpha-repo is now installable. Current state is: failing
- assertions.0.1 on 5.0 is now installable. Current state is: failing
- assertions.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- atd.1.1.2 on 5.0 is now installable. Current state is: failing
- atd.1.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- atd.1.2.0 on 5.0 is now installable. Current state is: failing
- atd.1.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- atd.2.2.1 on 5.0 is now installable. Current state is: failing
- atd.2.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- atdgen-runtime.2.2.1.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
- atdgen-runtime.2.2.1.1~alpha-repo on 5.0+alpha-repo 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
- atdgen.2.2.1 on 4.14+alpha-repo is now installable. Current state is: failing
- atdgen.2.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- atds.2.2.1.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
- atds.2.2.1.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
- aws-s3.4.1.0 on 4.05 had its build status changed: passing to failing
- aws-s3.4.1.0 on 4.06 had its build status changed: passing to failing
- aws-s3.4.1.0 on 4.07 had its build status changed: passing to failing
- aws-s3.4.2.0 on 4.05 had its build status changed: passing to failing
- aws-s3.4.2.0 on 4.06 had its build status changed: passing to failing
- aws-s3.4.2.0 on 4.07 had its build status changed: passing to failing
- aws-s3.4.3.0 on 4.05 had its build status changed: passing to failing
- aws-s3.4.3.0 on 4.06 had its build status changed: passing to failing
- aws-s3.4.3.0 on 4.07 had its build status changed: passing to failing
- aws-s3.4.4.0 on 4.07 had its build status changed: passing to failing
- aws-s3.4.4.1 on 4.07 had its build status changed: passing to failing
- aws-s3.4.5.1 on 4.07 had its build status changed: passing to failing
- bap-ghidra.2.4.0 on 4.08 is now installable. Current state is: failing
- bap-ghidra.2.4.0 on 4.09 is now installable. Current state is: failing
- bap-ghidra.2.4.0 on 4.10 is now installable. Current state is: failing
- bap-ghidra.2.4.0 on 4.11 is now installable. Current state is: failing
- bap-ghidra.2.4.0 on 4.12 is now installable. Current state is: failing
- bap-ghidra.2.4.0 on 4.13 is now installable. Current state is: failing
- bap-ghidra.2.4.0 on 4.14 is now installable. Current state is: failing
- bap-ghidra.2.4.0 on 4.14+alpha-repo 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
- bap-ghidra.2.5.0 on 4.14+alpha-repo is now installable. Current state is: failing
- bear.0.0.1 on 5.0 is now installable. Current state is: failing
- bear.0.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- bechamel-js.0.2.0.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
- bechamel-js.0.2.0.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
- bechamel-notty.0.2.0.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
- bechamel-notty.0.2.0.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
- bechamel.0.1.0 on 5.0 is now installable. Current state is: failing
- bechamel.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- bechamel.0.2.0 on 5.0 is now installable. Current state is: failing
- bechamel.0.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- beluga.1.0 on 5.0 is now installable. Current state is: failing
- beluga.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- bimage-display.0.3.0 on 5.0 is now installable. Current state is: failing
- bimage-display.0.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- bimage-display.0.3.1 on 5.0 is now installable. Current state is: failing
- bimage-display.0.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- bimage-display.0.4.0 on 5.0 is now installable. Current state is: failing
- bimage-display.0.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- bimage-display.0.5.0 on 5.0 is now installable. Current state is: failing
- bimage-display.0.5.0 on 5.0+alpha-repo 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
- binsec.0.4.1 on 5.0 is now installable. Current state is: failing
- binsec.0.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- binsec.0.5.0 on 5.0 is now installable. Current state is: failing
- binsec.0.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- bisect.1.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- bisect_ppx.2.6.0 on 5.0 is now installable. Current state is: failing
- bisect_ppx.2.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- bisect_ppx.2.7.0 on 5.0 is now installable. Current state is: failing
- bisect_ppx.2.7.0 on 5.0+alpha-repo is now installable. Current state is: failing
- bisect_ppx.2.7.1 on 5.0 is now installable. Current state is: failing
- bisect_ppx.2.7.1 on 5.0+alpha-repo is now installable. Current state is: failing
- bisect_ppx.2.8.0 on 5.0 is now installable. Current state is: failing
- bisect_ppx.2.8.0 on 5.0+alpha-repo is now installable. Current state is: failing
- bisect_ppx.2.8.0.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
- bisect_ppx.2.8.0.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
- bitcoin.2.0 on 5.0 is now installable. Current state is: failing
- bitcoin.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.02 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.03 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.04 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.05 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.06 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.07 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.08 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.09 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.10 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.11 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.12 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.13 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.14 is now installable. Current state is: failing
- bitwuzla-bin.0.0.0 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- blake3.0.1 on 4.14 is now installable. Current state is: failing
- blake3.0.1 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- bracetax.0.4 on 5.0 is now installable. Current state is: failing
- bracetax.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- cairo2.0.5 on 5.0 is now installable. Current state is: failing
- cairo2.0.5 on 5.0+alpha-repo 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
- camlbz2.0.6.0 on 5.0 is now installable. Current state is: failing
- camlbz2.0.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- camlbz2.0.7.0 on 5.0 is now installable. Current state is: failing
- camlbz2.0.7.0 on 5.0+alpha-repo is now installable. Current state is: failing
- camlidl.1.05 on 5.0 is now installable. Current state is: failing
- camlidl.1.05 on 5.0+alpha-repo is now installable. Current state is: failing
- camlidl.1.07 on 5.0 is now installable. Current state is: failing
- camlidl.1.07 on 5.0+alpha-repo is now installable. Current state is: failing
- camlidl.1.09 on 5.0 is now installable. Current state is: failing
- camlidl.1.09 on 5.0+alpha-repo is now installable. Current state is: 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
- camlimages.5.0.3 on 5.0 is now installable. Current state is: failing
- camlimages.5.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- camlimages.5.0.4 on 5.0 is now installable. Current state is: failing
- camlimages.5.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- camlimages.5.0.4-1 on 5.0 is now installable. Current state is: failing
- camlimages.5.0.4-1 on 5.0+alpha-repo is now installable. Current state is: failing
- camllib.1.3.3 on 5.0 is now installable. Current state is: failing
- camllib.1.3.3 on 5.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- camlon.3.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- camlpdf.2.3 on 5.0 is now installable. Current state is: failing
- camlpdf.2.3 on 5.0+alpha-repo is now installable. Current state is: failing
- camlpdf.2.4 on 5.0 is now installable. Current state is: failing
- camlpdf.2.4 on 5.0+alpha-repo is now installable. Current state is: failing
- camlpdf.2.5 on 5.0 is now installable. Current state is: failing
- camlpdf.2.5 on 5.0+alpha-repo 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
- camltc.0.9.7.0 on 5.0 is now installable. Current state is: failing
- camltc.0.9.7.0 on 5.0+alpha-repo is now installable. Current state is: failing
- capnp-rpc-net.1.1 on 4.08 had its build status changed: passing to failing
- capnp-rpc-net.1.1 on 4.09 had its build status changed: passing to failing
- capnp-rpc-net.1.1 on 4.10 had its build status changed: passing to failing
- capnp-rpc-net.1.1 on 4.11 had its build status changed: passing to failing
- capnp-rpc-net.1.1 on 4.12 had its build status changed: passing to failing
- capnp-rpc-net.1.1 on 4.13 had its build status changed: not available to failing
- capnp-rpc-net.1.2 on 4.08 is now installable. Current state is: failing
- capnp-rpc-net.1.2 on 4.09 is now installable. Current state is: failing
- capnp-rpc-net.1.2 on 4.10 is now installable. Current state is: failing
- capnp-rpc-net.1.2 on 4.11 is now installable. Current state is: failing
- capnp-rpc-net.1.2 on 4.12 is now installable. Current state is: failing
- capnp-rpc-net.1.2 on 4.13 is now installable. Current state is: failing
- captureio.0.1.1 on 5.0 is now installable. Current state is: failing
- captureio.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- captureio.0.1.2 on 5.0 is now installable. Current state is: failing
- captureio.0.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- caqti.1.0.0 on 5.0 is now installable. Current state is: failing
- caqti.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- caqti.1.1.0 on 5.0 is now installable. Current state is: failing
- caqti.1.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- cconv.0.2 on 5.0 is now installable. Current state is: failing
- cconv.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- cconv.0.3 on 5.0 is now installable. Current state is: failing
- cconv.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- cconv.0.3.1 on 5.0 is now installable. Current state is: failing
- cconv.0.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- cconv.0.4 on 5.0 is now installable. Current state is: failing
- cconv.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- cfstream.1.2.1 on 4.03 had its build status changed: passing to failing
- cfstream.1.2.1 on 4.04 had its build status changed: passing to failing
- cfstream.1.2.1 on 4.05 had its build status changed: passing to failing
- cfstream.1.2.2 on 4.03 had its build status changed: passing to failing
- cfstream.1.2.2 on 4.04 had its build status changed: passing to failing
- cfstream.1.2.2 on 4.05 had its build status changed: passing to failing
- cfstream.1.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- cgi.0.10 on 5.0 is now installable. Current state is: failing
- cgi.0.10 on 5.0+alpha-repo is now installable. Current state is: failing
- cgi.0.9 on 5.0 is now installable. Current state is: failing
- cgi.0.9 on 5.0+alpha-repo is now installable. Current state is: failing
- charrua-unix.1.2.2 on 5.0+alpha-repo is now installable. Current state is: failing
- charrua-unix.1.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- charrua-unix.1.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- charrua-unix.1.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- clangml.4.6.0 on 4.08 is now installable. Current state is: failing
- clangml.4.6.0 on 4.09 is now installable. Current state is: failing
- clangml.4.6.0 on 4.10 is now installable. Current state is: failing
- clangml.4.6.0 on 4.11 is now installable. Current state is: failing
- clangml.4.6.0 on 4.12 is now installable. Current state is: failing
- clangml.4.6.0 on 4.13 is now installable. Current state is: failing
- clangml.4.6.0 on 4.14 is now installable. Current state is: failing
- clangml.4.6.0 on 4.14+alpha-repo is now installable. Current state is: failing
- clangml.4.6.0 on 5.0 is now installable. Current state is: failing
- clangml.4.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- cmark.0.2.0 on 5.0 is now installable. Current state is: failing
- cmark.0.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- cmdtui.0.3.0 on 5.0 is now installable. Current state is: failing
- cmdtui.0.3.0 on 5.0+alpha-repo 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.04 had its build status changed: passing to failing
- cohttp-lwt-jsoo.2.1.3 on 4.08 had its build status changed: passing to failing
- coin.0.1.0 on 4.08 had its build status changed: passing to failing
- coin.0.1.1 on 4.08 had its build status changed: passing to failing
- combine.0.55 on 4.03 had its build status changed: passing to failing
- combine.0.55 on 4.04 had its build status changed: passing to failing
- combine.0.55 on 4.05 had its build status changed: passing to failing
- conex.0.10.0 on 5.0 is now installable. Current state is: failing
- conex.0.10.0 on 5.0+alpha-repo is now installable. Current state is: failing
- conex.0.10.1 on 5.0 is now installable. Current state is: failing
- conex.0.10.1 on 5.0+alpha-repo is now installable. Current state is: failing
- conex.0.9.2 on 5.0 is now installable. Current state is: failing
- conex.0.9.2 on 5.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- conf-libclang.13 on 4.02 is now installable. Current state is: failing
- conf-libclang.13 on 4.03 is now installable. Current state is: failing
- conf-libclang.13 on 4.04 is now installable. Current state is: failing
- conf-libclang.13 on 4.05 is now installable. Current state is: failing
- conf-libclang.13 on 4.06 is now installable. Current state is: failing
- conf-libclang.13 on 4.07 is now installable. Current state is: failing
- conf-libclang.13 on 4.08 is now installable. Current state is: failing
- conf-libclang.13 on 4.09 is now installable. Current state is: failing
- conf-libclang.13 on 4.10 is now installable. Current state is: failing
- conf-libclang.13 on 4.11 is now installable. Current state is: failing
- conf-libclang.13 on 4.12 is now installable. Current state is: failing
- conf-libclang.13 on 4.13 is now installable. Current state is: failing
- conf-libclang.13 on 4.14 is now installable. Current state is: failing
- conf-libclang.13 on 4.14+alpha-repo is now installable. Current state is: failing
- conf-libclang.13 on 5.0 is now installable. Current state is: failing
- conf-libclang.13 on 5.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- config-file.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- config-file.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- config-file.1.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- coq.8.10.1 on 4.05 had its build status changed: passing to failing
- coq.8.12.0 on 4.08 had its build status changed: passing to failing
- coq.8.12.0 on 4.09 had its build status changed: passing to failing
- coq.8.13.1 on 4.13 had its build status changed: passing to failing
- coq.8.14.0 on 4.05 is now installable. Current state is: failing
- coq.8.14.1 on 4.14+alpha-repo is now installable. Current state is: failing
- coq.8.15.1 on 4.12 is now installable. Current state is: failing
- coq.8.15.2 on 4.12 is now installable. Current state is: failing
- coq.8.16.0 on 4.09 is now installable. Current state is: failing
- cow.2.2.0 on 5.0 is now installable. Current state is: failing
- cow.2.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- cpdf.2.2.1 on 4.02 had its build status changed: passing to failing
- cpdf.2.2.1 on 4.03 had its build status changed: passing to failing
- cpdf.2.2.1 on 4.04 had its build status changed: passing to failing
- cpdf.2.2.1 on 4.05 had its build status changed: passing to failing
- crdt-ml.0.10.0 on 5.0 is now installable. Current state is: failing
- crdt-ml.0.10.0 on 5.0+alpha-repo is now installable. Current state is: failing
- cry.0.6.5 on 5.0 is now installable. Current state is: failing
- cry.0.6.5 on 5.0+alpha-repo is now installable. Current state is: failing
- cry.0.6.6 on 5.0 is now installable. Current state is: failing
- cry.0.6.6 on 5.0+alpha-repo is now installable. Current state is: failing
- cry.0.6.7 on 5.0 is now installable. Current state is: failing
- cry.0.6.7 on 5.0+alpha-repo is now installable. Current state is: failing
- csv.1.4 on 5.0 is now installable. Current state is: failing
- csv.1.4 on 5.0+alpha-repo is now installable. Current state is: failing
- csv.1.4.1 on 5.0 is now installable. Current state is: failing
- csv.1.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- csv.1.4.2 on 5.0 is now installable. Current state is: failing
- csv.1.4.2 on 5.0+alpha-repo is now installable. Current state is: failing
- csv.1.5 on 5.0 is now installable. Current state is: failing
- csv.1.5 on 5.0+alpha-repo is now installable. Current state is: failing
- csv.1.6 on 5.0 is now installable. Current state is: failing
- csv.1.6 on 5.0+alpha-repo is now installable. Current state is: failing
- csv.2.2 on 5.0 is now installable. Current state is: failing
- csv.2.2 on 5.0+alpha-repo is now installable. Current state is: failing
- csvfields.v0.15.0 on 5.0+alpha-repo is now installable. Current state is: failing
- cubicle.1.1.2 on 5.0 is now installable. Current state is: failing
- cubicle.1.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- data-encoding.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- data-encoding.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- datakit-client.0.12.0 on 4.08 had its build status changed: passing to failing
- datakit-client.0.12.0 on 4.09 had its build status changed: passing to failing
- datakit-client.0.12.0 on 4.10 had its build status changed: passing to failing
- datakit-client.0.12.0 on 4.11 had its build status changed: passing to failing
- datakit-client.0.12.0 on 4.12 had its build status changed: passing to failing
- datakit-client.0.12.0 on 4.13 had its build status changed: passing to failing
- datakit-client.0.12.2 on 4.08 had its build status changed: passing to failing
- datakit-client.0.12.2 on 4.09 had its build status changed: passing to failing
- datakit-client.0.12.2 on 4.10 had its build status changed: passing to failing
- datakit-client.0.12.2 on 4.11 had its build status changed: passing to failing
- datakit-client.0.12.2 on 4.12 had its build status changed: passing to failing
- datakit-client.0.12.2 on 4.13 had its build status changed: passing to failing
- datakit-client.0.12.3 on 4.08 had its build status changed: passing to failing
- datakit-client.0.12.3 on 4.09 had its build status changed: passing to failing
- datakit-client.0.12.3 on 4.10 had its build status changed: passing to failing
- datakit-client.0.12.3 on 4.11 had its build status changed: passing to failing
- datakit-client.0.12.3 on 4.12 had its build status changed: passing to failing
- datakit-client.0.12.3 on 4.13 had its build status changed: passing to failing
- datakit-client.1.0.0 on 4.08 had its build status changed: passing to failing
- datakit-client.1.0.0 on 4.09 had its build status changed: passing to failing
- datakit-client.1.0.0 on 4.10 had its build status changed: passing to failing
- datakit-client.1.0.0 on 4.11 had its build status changed: passing to failing
- datakit-client.1.0.0 on 4.12 had its build status changed: passing to failing
- datakit-client.1.0.0 on 4.13 had its build status changed: passing to failing
- datakit-client.1.0.0.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
- datakit-client.1.0.0.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
- datalog.0.6 on 5.0 is now installable. Current state is: failing
- datalog.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- debian-formats.0.1.1 on 5.0 is now installable. Current state is: failing
- debian-formats.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- depyt.0.2.0 on 4.12 had its build status changed: passing to failing
- depyt.0.2.0 on 4.13 had its build status changed: passing to failing
- 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.10 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.07 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
- diet.0.2 on 5.0 is now installable. Current state is: failing
- diet.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- diet.0.3 on 5.0 is now installable. Current state is: failing
- diet.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- distributed.0.6.0 on 5.0 is now installable. Current state is: failing
- distributed.0.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- diy.5.01 on 5.0 is now installable. Current state is: failing
- diy.5.01 on 5.0+alpha-repo is now installable. Current state is: failing
- dkml-component-staging-opam64.2.2.0~dkml20220801 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.6.1 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.6.2 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.4.6.3 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.5.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dns.5.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- docker-api.0.1 on 5.0 is now installable. Current state is: failing
- docker-api.0.1 on 5.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- dockerfile.1.0.0 on 5.0 is now installable. Current state is: failing
- dockerfile.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dockerfile.1.1.0 on 5.0 is now installable. Current state is: failing
- dockerfile.1.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dockerfile.1.1.1 on 5.0 is now installable. Current state is: failing
- dockerfile.1.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- dolmen.0.1 on 5.0 is now installable. Current state is: failing
- dolmen.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- dolmen.0.2 on 5.0 is now installable. Current state is: failing
- dolmen.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- dolmen.0.4.1 on 5.0 is now installable. Current state is: failing
- dolmen.0.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- dolog.1.1 on 5.0 is now installable. Current state is: failing
- dolog.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- dolog.2.0 on 5.0 is now installable. Current state is: failing
- dolog.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dolog.3.0 on 5.0 is now installable. Current state is: failing
- dolog.3.0 on 5.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- dream-httpaf.1.0.0~alpha1 on 5.0 is now installable. Current state is: failing
- dream-httpaf.1.0.0~alpha1 on 5.0+alpha-repo is now installable. Current state is: failing
- dream.1.0.0~alpha1 on 5.0 is now installable. Current state is: failing
- dream.1.0.0~alpha1 on 5.0+alpha-repo is now installable. Current state is: failing
- dream.1.0.0~alpha2 on 5.0 is now installable. Current state is: failing
- dream.1.0.0~alpha2 on 5.0+alpha-repo is now installable. Current state is: failing
- dtools.0.3.0 on 5.0 is now installable. Current state is: failing
- dtools.0.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dtools.0.3.2 on 5.0 is now installable. Current state is: failing
- dtools.0.3.2 on 5.0+alpha-repo is now installable. Current state is: failing
- dtools.0.3.3 on 5.0 is now installable. Current state is: failing
- dtools.0.3.3 on 5.0+alpha-repo is now installable. Current state is: failing
- dtools.0.3.4 on 5.0 is now installable. Current state is: failing
- dtools.0.3.4 on 5.0+alpha-repo is now installable. Current state is: failing
- dtools.0.4.0 on 5.0 is now installable. Current state is: failing
- dtools.0.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- dtools.0.4.1 on 5.0 is now installable. Current state is: failing
- dtools.0.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- dum.1.0.1 on 5.0 is now installable. Current state is: failing
- dum.1.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- dum.1.0.3 on 5.0 is now installable. Current state is: failing
- dum.1.0.3 on 5.0+alpha-repo 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
- edn.0.1.6-1-gff9db95 on 5.0 is now installable. Current state is: failing
- edn.0.1.6-1-gff9db95 on 5.0+alpha-repo is now installable. Current state is: failing
- eio.0.1 on 5.0 is now installable. Current state is: failing
- eio.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- eio.0.3 on 5.0 is now installable. Current state is: failing
- eio.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- eio.0.4 on 5.0 is now installable. Current state is: failing
- eio.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- eio.0.5 on 5.0 is now installable. Current state is: failing
- eio.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- elasticsearch-cli.1.0 on 4.14+alpha-repo is now installable. Current state is: failing
- elasticsearch-cli.1.1 on 4.14+alpha-repo is now installable. Current state is: failing
- elasticsearch-cli.1.2 on 4.14+alpha-repo is now installable. Current state is: failing
- elpi.1.15.0 on 5.0 is now installable. Current state is: failing
- elpi.1.15.0 on 5.0+alpha-repo is now installable. Current state is: failing
- elpi.1.15.2 on 5.0 is now installable. Current state is: failing
- elpi.1.15.2 on 5.0+alpha-repo is now installable. Current state is: failing
- elpi.1.16.1 on 5.0 is now installable. Current state is: failing
- elpi.1.16.1 on 5.0+alpha-repo is now installable. Current state is: failing
- esperanto.0.0.1 on 4.14 is now installable. Current state is: failing
- esperanto.0.0.1 on 4.14+alpha-repo is now installable. Current state is: failing
- exenum.0.7 on 5.0 is now installable. Current state is: failing
- exenum.0.7 on 5.0+alpha-repo is now installable. Current state is: failing
- extunix.0.1.4 on 5.0+alpha-repo is now installable. Current state is: failing
- extunix.0.1.5 on 5.0+alpha-repo is now installable. Current state is: failing
- extunix.0.1.6 on 5.0+alpha-repo is now installable. Current state is: failing
- ez_config.0.1.1 on 5.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- fat-filesystem.0.6.2 on 4.02 had its build status changed: internal failure to failing
- ffmpeg.0.4.2 on 5.0 is now installable. Current state is: failing
- ffmpeg.0.4.2 on 5.0+alpha-repo is now installable. Current state is: failing
- ffmpeg.0.4.3 on 5.0 is now installable. Current state is: failing
- ffmpeg.0.4.3 on 5.0+alpha-repo is now installable. Current state is: failing
- fftw3.0.8.4 on 5.0 is now installable. Current state is: failing
- fftw3.0.8.4 on 5.0+alpha-repo is now installable. Current state is: failing
- fmlib_parse.0.5.0 on 5.0 is now installable. Current state is: failing
- fmlib_parse.0.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- fmlib_parse.0.5.1 on 5.0 is now installable. Current state is: failing
- fmlib_parse.0.5.1 on 5.0+alpha-repo is now installable. Current state is: failing
- format.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- frama-c.22.0 on 4.08 had its build status changed: passing to failing
- frama-c.22.0 on 4.09 had its build status changed: passing to failing
- frama-c.22.0 on 4.10 had its build status changed: passing to failing
- frama-c.22.0 on 4.11 had its build status changed: passing to failing
- frama-c.22.0 on 4.12 had its build status changed: passing to failing
- frama-c.22.0 on 4.13 had its build status changed: passing to failing
- frama-c.22.0 on 4.14 is now installable. Current state is: failing
- frama-c.22.0 on 4.14+alpha-repo is now installable. Current state is: failing
- freetds.0.7 on 5.0 is now installable. Current state is: failing
- freetds.0.7 on 5.0+alpha-repo is now installable. Current state is: failing
- fsml.0.2.1 on 5.0 is now installable. Current state is: failing
- fsml.0.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- fsml.0.3.0 on 5.0 is now installable. Current state is: failing
- fsml.0.3.0 on 5.0+alpha-repo 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
- fstreams.0.2.1 on 5.0 is now installable. Current state is: failing
- fstreams.0.2.1 on 5.0+alpha-repo is now installable. Current state is: 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
- functory.0.6 on 5.0 is now installable. Current state is: failing
- functory.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- gadelac.0.6 on 5.0 is now installable. Current state is: failing
- gadelac.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- gadelac.0.6.1 on 5.0 is now installable. Current state is: failing
- gadelac.0.6.1 on 5.0+alpha-repo 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.0+alpha-repo 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
- gbddml.2.71.10 on 5.0+alpha-repo is now installable. Current state is: 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
- geoip.0.0.3 on 5.0 is now installable. Current state is: failing
- geoip.0.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- getopt.20120615 on 5.0 is now installable. Current state is: failing
- getopt.20120615 on 5.0+alpha-repo is now installable. Current state is: failing
- gg.0.9.2 on 5.0 is now installable. Current state is: failing
- gg.0.9.2 on 5.0+alpha-repo is now installable. Current state is: failing
- gg.0.9.3 on 5.0 is now installable. Current state is: failing
- gg.0.9.3 on 5.0+alpha-repo is now installable. Current state is: failing
- git-mirage.1.11.2 on 4.04 had its build status changed: partially failing to failing
- git-mirage.1.11.2 on 4.05 had its build status changed: partially failing to failing
- git-mirage.1.11.4 on 4.04 had its build status changed: partially failing to failing
- git.1.10.0 on 4.03 had its build status changed: passing to failing
- git.1.8.0 on 4.03 had its build status changed: passing to failing
- git.1.8.0 on 4.04 had its build status changed: passing to failing
- git.1.8.0 on 4.05 had its build status changed: passing to failing
- git.1.9.0 on 4.03 had its build status changed: passing to failing
- git.1.9.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
- git.2.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- git.3.2.0 on 4.08 had its build status changed: passing to failing
- git.3.2.0 on 4.09 had its build status changed: passing to failing
- git.3.2.0 on 4.10 had its build status changed: passing to failing
- git.3.2.0 on 4.11 had its build status changed: passing to failing
- git.3.2.0 on 4.12 had its build status changed: passing to failing
- git.3.3.0 on 4.08 had its build status changed: passing to failing
- git.3.3.0 on 4.09 had its build status changed: passing to failing
- git.3.3.0 on 4.10 had its build status changed: passing to failing
- git.3.3.0 on 4.11 had its build status changed: passing to failing
- git.3.3.0 on 4.12 had its build status changed: passing to failing
- git.3.3.1 on 4.08 had its build status changed: passing to failing
- git.3.3.1 on 4.09 had its build status changed: passing to failing
- git.3.3.1 on 4.10 had its build status changed: passing to failing
- git.3.3.1 on 4.11 had its build status changed: passing to failing
- git.3.3.1 on 4.12 had its build status changed: passing to failing
- git.3.3.2 on 4.08 had its build status changed: passing to failing
- git.3.3.2 on 4.09 had its build status changed: passing to failing
- git.3.3.2 on 4.10 had its build status changed: passing to failing
- git.3.3.2 on 4.11 had its build status changed: passing to failing
- git.3.3.2 on 4.12 had its build status changed: passing to failing
- git.3.3.3 on 4.08 had its build status changed: passing to failing
- git.3.3.3 on 4.09 had its build status changed: passing to failing
- git.3.3.3 on 4.10 had its build status changed: passing to failing
- git.3.3.3 on 4.11 had its build status changed: passing to failing
- git.3.3.3 on 4.12 had its build status changed: passing to failing
- gitlab.0.1.0 on 4.14+alpha-repo is now installable. Current state is: failing
- gitlab.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- gitlab.0.1.1 on 4.14+alpha-repo is now installable. Current state is: failing
- gitlab.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- gitlab.0.1.2 on 4.14+alpha-repo is now installable. Current state is: failing
- gitlab.0.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- glMLite.0.03.53 on 5.0 is now installable. Current state is: failing
- glMLite.0.03.53 on 5.0+alpha-repo is now installable. Current state is: failing
- glicko2.1.0.0 on 5.0 is now installable. Current state is: failing
- glicko2.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- goblint-cil.1.7.3 on 5.0 is now installable. Current state is: failing
- goblint-cil.1.7.3 on 5.0+alpha-repo is now installable. Current state is: failing
- goblint-cil.1.7.4 on 5.0 is now installable. Current state is: failing
- goblint-cil.1.7.4 on 5.0+alpha-repo is now installable. Current state is: failing
- gopcaml-mode.0.0.6 on 5.0+alpha-repo 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
- gsl.1.19.1 on 5.0 is now installable. Current state is: failing
- gsl.1.19.1 on 5.0+alpha-repo is now installable. Current state is: failing
- gsl.1.19.3 on 5.0 is now installable. Current state is: failing
- gsl.1.19.3 on 5.0+alpha-repo is now installable. Current state is: failing
- gsl.1.24.0 on 5.0 is now installable. Current state is: failing
- gsl.1.24.0 on 5.0+alpha-repo is now installable. Current state is: failing
- gsl.1.24.1 on 5.0 is now installable. Current state is: failing
- gsl.1.24.1 on 5.0+alpha-repo is now installable. Current state is: failing
- gsl.1.24.2 on 5.0 is now installable. Current state is: failing
- gsl.1.24.2 on 5.0+alpha-repo is now installable. Current state is: failing
- gsl.1.24.3 on 4.14 is now installable. Current state is: failing
- gsl.1.24.3 on 5.0 is now installable. Current state is: failing
- gsl.1.24.3 on 5.0+alpha-repo is now installable. Current state is: failing
- h2-async.0.8.0 on 4.06 had its build status changed: passing to failing
- h2-async.0.8.0 on 4.07 had its build status changed: passing to failing
- h2-async.0.8.0 on 4.08 had its build status changed: passing to failing
- h2-async.0.8.0 on 4.09 had its build status changed: passing to failing
- h2-async.0.8.0 on 4.10 had its build status changed: passing to failing
- h2-async.0.8.0 on 4.11 had its build status changed: passing to failing
- h2.0.1.0 on 5.0 is now installable. Current state is: failing
- h2.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- h2.0.2.0 on 5.0 is now installable. Current state is: failing
- h2.0.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- h2.0.3.0 on 5.0 is now installable. Current state is: failing
- h2.0.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- h2.0.4.0 on 5.0 is now installable. Current state is: failing
- h2.0.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- h2.0.5.0 on 5.0 is now installable. Current state is: failing
- h2.0.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- h2.0.6.0 on 5.0 is now installable. Current state is: failing
- h2.0.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- h2.0.6.1 on 5.0 is now installable. Current state is: failing
- h2.0.6.1 on 5.0+alpha-repo is now installable. Current state is: failing
- h2.0.7.0 on 5.0 is now installable. Current state is: failing
- h2.0.7.0 on 5.0+alpha-repo is now installable. Current state is: failing
- h2.0.8.0 on 5.0 is now installable. Current state is: failing
- h2.0.8.0 on 5.0+alpha-repo is now installable. Current state is: failing
- hack_parallel.0.1.1 on 4.07 had its build status changed: passing to failing
- hack_parallel.0.1.1 on 4.08 had its build status changed: passing to failing
- hack_parallel.0.1.1 on 4.09 had its build status changed: passing to failing
- hamt.1.0.0 on 5.0 is now installable. Current state is: failing
- hamt.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- hashcons.1.0.1 on 5.0 is now installable. Current state is: failing
- hashcons.1.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- headache.1.04 on 5.0+alpha-repo is now installable. Current state is: failing
- headache.1.05 on 5.0+alpha-repo is now installable. Current state is: failing
- heptagon.1.03.03 on 5.0+alpha-repo is now installable. Current state is: failing
- heptagon.1.03.04 on 5.0+alpha-repo is now installable. Current state is: failing
- heptagon.1.04.00 on 5.0+alpha-repo is now installable. Current state is: failing
- heptagon.1.05.00 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.42 on 5.0 is now installable. Current state is: failing
- herdtools7.7.42 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.42-beta.3 on 5.0 is now installable. Current state is: failing
- herdtools7.7.42-beta.3 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.43 on 5.0 is now installable. Current state is: failing
- herdtools7.7.43 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.44 on 5.0 is now installable. Current state is: failing
- herdtools7.7.44 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.45 on 5.0 is now installable. Current state is: failing
- herdtools7.7.45 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.46 on 5.0 is now installable. Current state is: failing
- herdtools7.7.46 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.47 on 5.0 is now installable. Current state is: failing
- herdtools7.7.47 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.48 on 5.0 is now installable. Current state is: failing
- herdtools7.7.48 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.49 on 5.0 is now installable. Current state is: failing
- herdtools7.7.49 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.50 on 5.0 is now installable. Current state is: failing
- herdtools7.7.50 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.51 on 5.0 is now installable. Current state is: failing
- herdtools7.7.51 on 5.0+alpha-repo is now installable. Current state is: failing
- herdtools7.7.52 on 5.0 is now installable. Current state is: failing
- herdtools7.7.52 on 5.0+alpha-repo is now installable. Current state is: failing
- hevea.2.25 on 5.0 is now installable. Current state is: failing
- hevea.2.25 on 5.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- hidapi.1.1 on 5.0 is now installable. Current state is: failing
- hidapi.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- hidapi.1.1.1 on 5.0 is now installable. Current state is: failing
- hidapi.1.1.1 on 5.0+alpha-repo 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
- http-lwt-client.0.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- http-lwt-client.0.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- http-lwt-client.0.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- http-lwt-client.0.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- http-lwt-client.0.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- http-lwt-client.0.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- hweak.1.1 on 5.0 is now installable. Current state is: failing
- hweak.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- icalendar.0.1.0 on 5.0 is now installable. Current state is: failing
- icalendar.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- icalendar.0.1.1 on 5.0 is now installable. Current state is: failing
- icalendar.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- icalendar.0.1.2 on 5.0 is now installable. Current state is: failing
- icalendar.0.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- imagelib.20200929 on 5.0 is now installable. Current state is: failing
- imagelib.20200929 on 5.0+alpha-repo is now installable. Current state is: failing
- imagelib.20210116 on 5.0 is now installable. Current state is: failing
- imagelib.20210116 on 5.0+alpha-repo is now installable. Current state is: failing
- imagelib.20210402 on 5.0 is now installable. Current state is: failing
- imagelib.20210402 on 5.0+alpha-repo is now installable. Current state is: failing
- imagelib.20210511 on 5.0 is now installable. Current state is: failing
- imagelib.20210511 on 5.0+alpha-repo is now installable. Current state is: failing
- imagemagick.0.34 on 4.02 had its build status changed: internal failure to failing
- imagemagick.0.34 on 4.03 had its build status changed: internal failure to failing
- imagemagick.0.34 on 4.04 had its build status changed: internal failure to failing
- imagemagick.0.34 on 4.05 had its build status changed: internal failure to failing
- inquire.0.2.1 on 5.0 is now installable. Current state is: failing
- inquire.0.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- inquire.0.3.0 on 5.0 is now installable. Current state is: failing
- inquire.0.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- interval_intel.1.5 on 5.0 is now installable. Current state is: failing
- interval_intel.1.5 on 5.0+alpha-repo is now installable. Current state is: failing
- interval_intel.1.5.1 on 5.0 is now installable. Current state is: failing
- interval_intel.1.5.1 on 5.0+alpha-repo is now installable. Current state is: failing
- inuit.0.4 on 5.0 is now installable. Current state is: failing
- inuit.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- irmin.1.3.2 on 4.12 had its build status changed: passing to failing
- irmin.1.3.2 on 4.13 had its build status changed: passing to failing
- irmin.1.4.0 on 4.12 had its build status changed: passing to failing
- irmin.1.4.0 on 4.13 had its build status changed: passing to failing
- iter.1.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- iter.1.3 on 5.0+alpha-repo is now installable. Current state is: failing
- itv-tree.2.1 on 5.0 is now installable. Current state is: failing
- itv-tree.2.1 on 5.0+alpha-repo is now installable. Current state is: 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
- javalib.2.3.6 on 5.0+alpha-repo is now installable. Current state is: failing
- javalib.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- javalib.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- javalib.3.1.1 on 5.0 is now installable. Current state is: failing
- javalib.3.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- javalib.3.2 on 5.0 is now installable. Current state is: failing
- javalib.3.2 on 5.0+alpha-repo is now installable. Current state is: failing
- javalib.3.2.1 on 5.0 is now installable. Current state is: failing
- javalib.3.2.1 on 5.0+alpha-repo is now installable. Current state is: 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
- jingoo.1.2.16 on 5.0 is now installable. Current state is: failing
- jingoo.1.2.16 on 5.0+alpha-repo is now installable. Current state is: failing
- jingoo.1.2.17 on 5.0 is now installable. Current state is: failing
- jingoo.1.2.17 on 5.0+alpha-repo is now installable. Current state is: failing
- jingoo.1.2.18 on 5.0 is now installable. Current state is: failing
- jingoo.1.2.18 on 5.0+alpha-repo is now installable. Current state is: failing
- js_of_ocaml.2.8.4 on 4.02 had its build status changed: passing to failing
- js_of_ocaml.2.8.4 on 4.03 had its build status changed: passing to failing
- js_of_ocaml.2.8.4 on 4.04 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
- json-rpc.0.5.0-0 on 5.0 is now installable. Current state is: failing
- json-rpc.0.5.0-0 on 5.0+alpha-repo is now installable. Current state is: failing
- jsonxt.1.0.0 on 5.0 is now installable. Current state is: failing
- jsonxt.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- jsonxt.1.0.1 on 5.0 is now installable. Current state is: failing
- jsonxt.1.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- junit.0.1 on 5.0 is now installable. Current state is: failing
- junit.0.1 on 5.0+alpha-repo is now installable. Current state is: 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.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.02 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
- kafka_lwt.0.5 on 5.0 is now installable. Current state is: failing
- kafka_lwt.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- kappa-library.4.1.0 on 4.05 had its build status changed: internal failure to failing
- kappa-library.4.1.0 on 4.06 had its build status changed: internal failure to failing
- kappa-library.4.1.0 on 4.07 had its build status changed: internal failure to failing
- kappa-library.4.1.0 on 4.08 had its build status changed: internal failure to failing
- kappa-library.4.1.0 on 4.09 had its build status changed: internal failure to failing
- kappa-library.4.1.0 on 4.10 had its build status changed: internal failure to failing
- kappa-library.4.1.0 on 4.11 had its build status changed: internal failure to failing
- kaputt.1.2 on 5.0 is now installable. Current state is: failing
- kaputt.1.2 on 5.0+alpha-repo is now installable. Current state is: 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
- key-parsers.1.4.0 on 5.0 is now installable. Current state is: failing
- key-parsers.1.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- kind2.1.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- kind2.1.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- kind2.1.4.0 on 5.0+alpha-repo 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.1 on 4.14+alpha-repo 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
- kinetic-client.0.0.9 on 4.14+alpha-repo is now installable. Current state is: failing
- lablgtk3-extras.3.0 on 4.12 is now installable. Current state is: failing
- lablqml.0.5.2 on 4.03 is now installable. Current state is: failing
- lablqml.0.5.2 on 4.04 is now installable. Current state is: failing
- lablqml.0.5.2 on 4.05 is now installable. Current state is: failing
- lablqml.0.5.2 on 4.06 is now installable. Current state is: failing
- lablqml.0.5.2 on 4.07 is now installable. Current state is: failing
- lablqml.0.5.2 on 4.08 is now installable. Current state is: failing
- lablqml.0.6 on 4.04 is now installable. Current state is: failing
- lablqml.0.6 on 4.05 is now installable. Current state is: failing
- lablqml.0.6 on 4.06 is now installable. Current state is: failing
- lablqml.0.6 on 4.07 is now installable. Current state is: failing
- lablqml.0.6 on 4.08 is now installable. Current state is: failing
- lablqml.0.6.2 on 4.04 is now installable. Current state is: failing
- lablqml.0.6.2 on 4.05 is now installable. Current state is: failing
- lablqml.0.6.2 on 4.06 is now installable. Current state is: failing
- lablqml.0.6.2 on 4.07 is now installable. Current state is: failing
- lablqml.0.6.2 on 4.08 is now installable. Current state is: failing
- lablqml.0.6.2 on 4.09 is now installable. Current state is: failing
- lablqml.0.7 on 5.0 is now installable. Current state is: failing
- lablqml.0.7 on 5.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- lacaml.7.2.1 on 5.0 is now installable. Current state is: failing
- lacaml.7.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.7.2.2 on 5.0 is now installable. Current state is: failing
- lacaml.7.2.2 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.7.2.6 on 5.0 is now installable. Current state is: failing
- lacaml.7.2.6 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.8.0.4 on 5.0 is now installable. Current state is: failing
- lacaml.8.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.8.0.5 on 5.0 is now installable. Current state is: failing
- lacaml.8.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.8.0.6 on 5.0 is now installable. Current state is: failing
- lacaml.8.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.8.0.7 on 5.0 is now installable. Current state is: failing
- lacaml.8.0.7 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.8.1.1 on 5.0 is now installable. Current state is: failing
- lacaml.8.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.9.0.0 on 5.0 is now installable. Current state is: failing
- lacaml.9.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.9.1.0 on 5.0 is now installable. Current state is: failing
- lacaml.9.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.9.1.1 on 5.0 is now installable. Current state is: failing
- lacaml.9.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.9.2.2 on 5.0 is now installable. Current state is: failing
- lacaml.9.2.2 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.9.2.3 on 5.0 is now installable. Current state is: failing
- lacaml.9.2.3 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.9.3.1 on 5.0 is now installable. Current state is: failing
- lacaml.9.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lacaml.9.3.2 on 5.0 is now installable. Current state is: failing
- lacaml.9.3.2 on 5.0+alpha-repo is now installable. Current state is: failing
- lambda-term.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lambda-term.2.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lambda-term.2.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- lambda-term.2.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- lambda-term.3.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lambda-term.3.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lambda-term.3.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lambdasoup.0.5 on 5.0 is now installable. Current state is: failing
- lambdasoup.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- lambdasoup.0.5.1 on 5.0 is now installable. Current state is: failing
- lambdasoup.0.5.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lambdasoup.0.6 on 5.0 is now installable. Current state is: failing
- lambdasoup.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- lambdasoup.0.6.1 on 5.0 is now installable. Current state is: failing
- lambdasoup.0.6.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lambdasoup.0.6.4 on 5.0 is now installable. Current state is: failing
- lambdasoup.0.6.4 on 5.0+alpha-repo is now installable. Current state is: failing
- lambdasoup.0.7.0 on 5.0 is now installable. Current state is: failing
- lambdasoup.0.7.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lambdasoup.0.7.1 on 5.0 is now installable. Current state is: failing
- lambdasoup.0.7.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lambdasoup.0.7.2 on 5.0 is now installable. Current state is: failing
- lambdasoup.0.7.2 on 5.0+alpha-repo is now installable. Current state is: failing
- lambdasoup.0.7.3 on 5.0 is now installable. Current state is: failing
- lambdasoup.0.7.3 on 5.0+alpha-repo is now installable. Current state is: failing
- lascar.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- lascar.0.6-alpha on 5.0 is now installable. Current state is: failing
- lascar.0.6-alpha on 5.0+alpha-repo is now installable. Current state is: failing
- lascar.0.6.0 on 5.0 is now installable. Current state is: failing
- lascar.0.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lascar.0.7.0 on 5.0 is now installable. Current state is: failing
- lascar.0.7.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lem.2020-06-03 on 5.0 is now installable. Current state is: failing
- lem.2020-06-03 on 5.0+alpha-repo is now installable. Current state is: failing
- lens.1.0.0 on 5.0 is now installable. Current state is: failing
- lens.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lens.1.0.2 on 5.0 is now installable. Current state is: failing
- lens.1.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- lens.1.1.0 on 5.0 is now installable. Current state is: failing
- lens.1.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- leveldb.1.3.0 on 5.0 is now installable. Current state is: failing
- leveldb.1.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- libssh.0.1 on 4.14 is now installable. Current state is: failing
- libssh.0.1 on 4.14+alpha-repo is now installable. Current state is: failing
- libsvm.0.10.0 on 5.0 is now installable. Current state is: failing
- libsvm.0.10.0 on 5.0+alpha-repo is now installable. Current state is: failing
- linkage.0.1 on 5.0 is now installable. Current state is: failing
- linkage.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- links.0.9.3 on 5.0 is now installable. Current state is: failing
- links.0.9.3 on 5.0+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.0 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.0~rc1 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.1 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.2 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.2-1 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.3 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.3-1 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.4 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.4-1 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.4-1 on 5.0+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.4-2 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.4-2 on 5.0+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.5 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.6 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.7 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.0.7 on 5.0+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.1.0-1 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.1.1 on 4.14+alpha-repo is now installable. Current state is: failing
- liquidsoap.2.1.2 on 4.14+alpha-repo is now installable. Current state is: failing
- lua-ml.0.9 on 5.0 is now installable. Current state is: failing
- lua-ml.0.9 on 5.0+alpha-repo is now installable. Current state is: failing
- lutils.1.44 on 5.0+alpha-repo is now installable. Current state is: failing
- lutils.1.49.5 on 5.0 is now installable. Current state is: failing
- lutils.1.49.5 on 5.0+alpha-repo is now installable. Current state is: failing
- lutils.1.51.2 on 5.0 is now installable. Current state is: failing
- lutils.1.51.2 on 5.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- lwt_domain.0.1.0 on 5.0 is now installable. Current state is: failing
- lwt_domain.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lwt_domain.0.2.0 on 5.0 is now installable. Current state is: failing
- lwt_domain.0.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- lwt_glib.1.0.1 on 5.0 is now installable. Current state is: failing
- lwt_glib.1.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lymp.0.2.4 on 5.0 is now installable. Current state is: failing
- lymp.0.2.4 on 5.0+alpha-repo is now installable. Current state is: failing
- lymp.0.2.5 on 5.0 is now installable. Current state is: failing
- lymp.0.2.5 on 5.0+alpha-repo is now installable. Current state is: failing
- lz4.1.1.1 on 5.0 is now installable. Current state is: failing
- lz4.1.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- lzo.0.0.2 on 5.0 is now installable. Current state is: failing
- lzo.0.0.2 on 5.0+alpha-repo 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
- mariadb.1.1.4.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: 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 4.14+alpha-repo 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.0+alpha-repo 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-mirage.0.2.1.2.1 on 5.0 is now installable. Current state is: failing
- memtrace-mirage.0.2.1.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- memtrace-mirage.0.2.1.2.2 on 5.0 is now installable. Current state is: failing
- memtrace-mirage.0.2.1.2.2 on 5.0+alpha-repo is now installable. Current state is: failing
- memtrace.0.1 on 5.0 is now installable. Current state is: failing
- memtrace.0.1 on 5.0+alpha-repo 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
- 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
- merlin.4.5-414 on 4.14+alpha-repo is now installable. Current state is: failing
- mesh-triangle.0.9.5 on 5.0 is now installable. Current state is: failing
- mesh-triangle.0.9.5 on 5.0+alpha-repo is now installable. Current state is: failing
- mesh.0.8.7 on 5.0 is now installable. Current state is: failing
- mesh.0.8.7 on 5.0+alpha-repo is now installable. Current state is: failing
- mesh.0.8.8 on 5.0 is now installable. Current state is: failing
- mesh.0.8.8 on 5.0+alpha-repo is now installable. Current state is: 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
- mindstorm.0.6 on 5.0 is now installable. Current state is: failing
- mindstorm.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- mindstorm.0.6.1 on 5.0 is now installable. Current state is: failing
- mindstorm.0.6.1 on 5.0+alpha-repo is now installable. Current state is: 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- minisat.0.1 on 5.0 is now installable. Current state is: failing
- minisat.0.1 on 5.0+alpha-repo 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-btrees.0.1.0 on 5.0 is now installable. Current state is: failing
- mirage-btrees.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mirage-clock-unix.1.0.0 on 5.0 is now installable. Current state is: failing
- mirage-clock-unix.1.0.0 on 5.0+alpha-repo is now installable. Current state is: 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-lwt.1.2.0 on 5.0 is now installable. Current state is: failing
- mirage-fs-lwt.1.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mirage-fs.0.3.0 on 5.0 is now installable. Current state is: failing
- mirage-fs.0.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mirage-fs.0.4.0 on 5.0 is now installable. Current state is: failing
- mirage-fs.0.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mirage-fs.0.5.0 on 5.0 is now installable. Current state is: failing
- mirage-fs.0.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mirage-logs.0.1 on 5.0 is now installable. Current state is: failing
- mirage-logs.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- mirage-logs.0.2 on 5.0 is now installable. Current state is: failing
- mirage-logs.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- mirage-unix.3.0.3 on 5.0 is now installable. Current state is: failing
- mirage-unix.3.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- mirage-unix.3.0.4 on 5.0 is now installable. Current state is: failing
- mirage-unix.3.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- mirage-xen-minios.0.2 on 4.14 is now installable. Current state is: failing
- mirage-xen-minios.0.2 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mirage-xen-minios.0.3 on 4.14 is now installable. Current state is: failing
- mirage-xen-minios.0.3 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mirage-xen-minios.0.4 on 4.14 is now installable. Current state is: failing
- mirage-xen-minios.0.4 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mirage-xen-minios.0.4.1 on 4.14 is now installable. Current state is: failing
- mirage-xen-minios.0.4.1 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mirage-xen-minios.0.4.2 on 4.14 is now installable. Current state is: failing
- mirage-xen-minios.0.4.2 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mirage-xen-minios.0.5.0 on 4.14 is now installable. Current state is: failing
- mirage-xen-minios.0.5.0 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mirage-xen-minios.0.6.0 on 4.14 is now installable. Current state is: failing
- mirage-xen-minios.0.6.0 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mirage-xen-minios.0.7.0 on 4.14 is now installable. Current state is: failing
- mirage-xen-minios.0.7.0 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mixture.0.2.0 on 5.0 is now installable. Current state is: failing
- mixture.0.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mixture.0.2.1 on 5.0 is now installable. Current state is: failing
- mixture.0.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- mixture.1.0.0 on 5.0 is now installable. Current state is: failing
- mixture.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mlcuddidl.3.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- mlcuddidl.3.0.7 on 5.0+alpha-repo 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
- mlgmpidl.1.2.11 on 5.0+alpha-repo is now installable. Current state is: failing
- mlgmpidl.1.2.12 on 5.0+alpha-repo is now installable. Current state is: failing
- mlgmpidl.1.2.13 on 5.0+alpha-repo is now installable. Current state is: failing
- mlgmpidl.1.2.14 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.3.1 on 5.0 is now installable. Current state is: failing
- mm.0.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.4.0 on 5.0 is now installable. Current state is: failing
- mm.0.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.4.1 on 5.0 is now installable. Current state is: failing
- mm.0.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.5.0 on 5.0 is now installable. Current state is: failing
- mm.0.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.5.1 on 5.0 is now installable. Current state is: failing
- mm.0.5.1 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.6.0 on 5.0 is now installable. Current state is: failing
- mm.0.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.7.0 on 5.0 is now installable. Current state is: failing
- mm.0.7.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.7.1 on 5.0 is now installable. Current state is: failing
- mm.0.7.1 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.7.2 on 5.0 is now installable. Current state is: failing
- mm.0.7.2 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.7.4 on 5.0 is now installable. Current state is: failing
- mm.0.7.4 on 5.0+alpha-repo is now installable. Current state is: failing
- mm.0.8.0 on 5.0 is now installable. Current state is: failing
- mm.0.8.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mock.0.1.1 on 5.0 is now installable. Current state is: failing
- mock.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- monomorphic.1.2 on 5.0 is now installable. Current state is: failing
- monomorphic.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- monomorphic.2.0 on 5.0 is now installable. Current state is: failing
- monomorphic.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- morbig.0.9 on 5.0 is now installable. Current state is: failing
- morbig.0.9 on 5.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mosquitto.0.2.1-0 on 5.0 is now installable. Current state is: failing
- mosquitto.0.2.1-0 on 5.0+alpha-repo is now installable. Current state is: failing
- mparser.1.2 on 5.0 is now installable. Current state is: failing
- mparser.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- mparser.1.2.2 on 5.0 is now installable. Current state is: failing
- mparser.1.2.2 on 5.0+alpha-repo is now installable. Current state is: failing
- mparser.1.2.3 on 5.0 is now installable. Current state is: failing
- mparser.1.2.3 on 5.0+alpha-repo is now installable. Current state is: failing
- mpp.0.3.4 on 5.0 is now installable. Current state is: failing
- mpp.0.3.4 on 5.0+alpha-repo is now installable. Current state is: failing
- mpp.0.3.5 on 5.0 is now installable. Current state is: failing
- mpp.0.3.5 on 5.0+alpha-repo is now installable. Current state is: failing
- mrmime.0.1.0 on 5.0 is now installable. Current state is: failing
- mrmime.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.1 on 5.0 is now installable. Current state is: failing
- msat.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.2 on 5.0 is now installable. Current state is: failing
- msat.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.3 on 5.0 is now installable. Current state is: failing
- msat.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.4 on 5.0 is now installable. Current state is: failing
- msat.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.4.1 on 5.0 is now installable. Current state is: failing
- msat.0.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.5 on 5.0 is now installable. Current state is: failing
- msat.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.5.1 on 5.0 is now installable. Current state is: failing
- msat.0.5.1 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.6 on 5.0 is now installable. Current state is: failing
- msat.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.6.1 on 5.0 is now installable. Current state is: failing
- msat.0.6.1 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.7 on 5.0 is now installable. Current state is: failing
- msat.0.7 on 5.0+alpha-repo is now installable. Current state is: failing
- msat.0.8 on 5.0 is now installable. Current state is: failing
- msat.0.8 on 5.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- mustache.2.2.0 on 5.0 is now installable. Current state is: failing
- mustache.2.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mustache.2.3.0 on 5.0 is now installable. Current state is: failing
- mustache.2.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- mysql8.1.0 on 4.13 had its build status changed: not available to failing
- mysql8.1.0 on 4.14 is now installable. Current state is: failing
- mysql8.1.0 on 4.14+alpha-repo is now installable. Current state is: failing
- mysql8.1.0 on 5.0 is now installable. Current state is: failing
- mysql8.1.0 on 5.0+alpha-repo 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
- netlink.0.2.1 on 5.0 is now installable. Current state is: failing
- netlink.0.2.1 on 5.0+alpha-repo is now installable. Current state is: 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
- nonstd.0.0.1 on 5.0 is now installable. Current state is: failing
- nonstd.0.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- nonstd.0.0.2 on 5.0 is now installable. Current state is: failing
- nonstd.0.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- not-ocamlfind.0.05 on 5.0 is now installable. Current state is: failing
- not-ocamlfind.0.05 on 5.0+alpha-repo is now installable. Current state is: failing
- not-ocamlfind.0.07.01 on 5.0 is now installable. Current state is: failing
- not-ocamlfind.0.07.01 on 5.0+alpha-repo is now installable. Current state is: failing
- not-ocamlfind.0.07.02 on 5.0 is now installable. Current state is: failing
- not-ocamlfind.0.07.02 on 5.0+alpha-repo is now installable. Current state is: failing
- not-ocamlfind.0.08 on 5.0 is now installable. Current state is: failing
- not-ocamlfind.0.08 on 5.0+alpha-repo is now installable. Current state is: failing
- nproc.0.5.1 on 5.0 is now installable. Current state is: failing
- nproc.0.5.1 on 5.0+alpha-repo 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
- objsize.0.18 on 5.0+alpha-repo is now installable. Current state is: failing
- obus.1.2.3 on 5.0 is now installable. Current state is: failing
- obus.1.2.3 on 5.0+alpha-repo is now installable. Current state is: 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-inifiles.1.2 on 5.0 is now installable. Current state is: failing
- ocaml-inifiles.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- ocaml-makefile.6.37.0 on 4.14 is now installable. Current state is: failing
- ocaml-makefile.6.37.0 on 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- ocaml-monadic.0.3.2 on 5.0 is now installable. Current state is: failing
- ocaml-monadic.0.3.2 on 5.0+alpha-repo is now installable. Current state is: failing
- ocaml-protoc-plugin.1.0.0 on 5.0 is now installable. Current state is: failing
- ocaml-protoc-plugin.1.0.0 on 5.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- ocaml-sat-solvers.0.3 on 5.0 is now installable. Current state is: failing
- ocaml-sat-solvers.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- ocaml-sat-solvers.0.4 on 5.0 is now installable. Current state is: failing
- ocaml-sat-solvers.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- ocaml-systemd.1.1 on 5.0 is now installable. Current state is: failing
- ocaml-systemd.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- ocaml-systemd.1.2 on 5.0 is now installable. Current state is: failing
- ocaml-systemd.1.2 on 5.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- ocamlbuild-pkg.0.1 on 5.0 is now installable. Current state is: failing
- ocamlbuild-pkg.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlbuild-pkg.0.2 on 5.0 is now installable. Current state is: failing
- ocamlbuild-pkg.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlbuild-pkg.0.2.1 on 5.0 is now installable. Current state is: failing
- ocamlbuild-pkg.0.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamldiff.1.1 on 4.02 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.03 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.04 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.05 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.06 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.07 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.08 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.09 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.10 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.11 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.12 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.13 had its build status changed: passing to failing
- ocamldiff.1.1 on 4.14 is now installable. Current state is: failing
- ocamldiff.1.1 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- ocamldsort.0.15.0 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamldsort.0.16.0 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlfind-lint.0.1.0 on 5.0 is now installable. Current state is: failing
- ocamlfind-lint.0.1.0 on 5.0+alpha-repo 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
- ocamlformat.0.21.0.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlfuse.2.7.1-cvs on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlfuse.2.7.1-cvs2 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlfuse.2.7.1-cvs3 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlfuse.2.7.1-cvs4 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlfuse.2.7.1-cvs5 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlfuse.2.7.1-cvs7 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlrss.2.0 on 5.0 is now installable. Current state is: failing
- ocamlrss.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlscript.2.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlscript.2.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlsdl.0.9.1 on 5.0 is now installable. Current state is: failing
- ocamlsdl.0.9.1 on 5.0+alpha-repo is now installable. Current state is: failing
- ocamlviz.1.01 on 4.02 had its build status changed: internal failure to failing
- ocamlviz.1.01 on 4.03 had its build status changed: internal failure to failing
- ocamlviz.1.01 on 4.04 had its build status changed: internal failure to failing
- ocamlviz.1.01 on 4.05 had its build status changed: internal failure to failing
- ocf.0.2.0 on 4.02 had its build status changed: internal failure to failing
- ocf.0.4.0 on 4.02 had its build status changed: internal failure to failing
- 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
- ocf.0.6.0 on 5.0 is now installable. Current state is: failing
- ocf.0.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- ocf.0.7.0 on 5.0 is now installable. Current state is: failing
- ocf.0.7.0 on 5.0+alpha-repo is now installable. Current state is: failing
- ocp-indent-nlfork.1.5.4 on 5.0 is now installable. Current state is: failing
- ocp-indent-nlfork.1.5.4 on 5.0+alpha-repo is now installable. Current state is: 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-pack-split.1.0.1 on 5.0 is now installable. Current state is: failing
- ocp-pack-split.1.0.1 on 5.0+alpha-repo 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.7 on 5.0 is now installable. Current state is: failing
- odepack.0.6.7 on 5.0+alpha-repo is now installable. Current state is: failing
- odepack.0.6.8 on 5.0 is now installable. Current state is: failing
- odepack.0.6.8 on 5.0+alpha-repo is now installable. Current state is: failing
- odepack.0.6.9 on 4.14 is now installable. Current state is: failing
- odepack.0.6.9 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- odepack.0.7 on 4.14 is now installable. Current state is: failing
- odepack.0.7 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- odig.0.0.3 on 4.08 had its build status changed: passing to failing
- odig.0.0.3 on 4.09 had its build status changed: passing to failing
- odig.0.0.3 on 4.10 had its build status changed: passing to failing
- odig.0.0.3 on 4.11 had its build status changed: passing to failing
- offheap.0.1.0 on 5.0 is now installable. Current state is: failing
- offheap.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- offheap.0.1.1 on 5.0 is now installable. Current state is: failing
- offheap.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- offheap.0.1.2 on 5.0 is now installable. Current state is: failing
- offheap.0.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- ogg.0.6.0 on 4.14 is now installable. Current state is: failing
- ogg.0.6.0 on 4.14+alpha-repo is now installable. Current state is: failing
- ogg.0.7.0 on 4.14 is now installable. Current state is: failing
- ogg.0.7.0 on 4.14+alpha-repo is now installable. Current state is: failing
- ogg.0.7.1 on 4.14 is now installable. Current state is: failing
- ogg.0.7.1 on 4.14+alpha-repo is now installable. Current state is: failing
- ogg.0.7.2 on 4.14 is now installable. Current state is: failing
- ogg.0.7.2 on 4.14+alpha-repo is now installable. Current state is: failing
- ojs-base.0.5.0 on 4.03 had its build status changed: partially failing to failing
- ojs-base.0.6.0 on 4.14+alpha-repo is now installable. Current state is: failing
- ojs-base.0.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- olinq.0.1 on 5.0 is now installable. Current state is: failing
- olinq.0.1 on 5.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- olmi.1.0 on 5.0 is now installable. Current state is: failing
- olmi.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- olmi.1.1 on 5.0 is now installable. Current state is: failing
- olmi.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- omd.1.3.1 on 5.0 is now installable. Current state is: failing
- omd.1.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- oolc.0.2 on 5.0 is now installable. Current state is: failing
- oolc.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- oolc.0.3 on 5.0 is now installable. Current state is: failing
- oolc.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- opal.0.1.0 on 5.0 is now installable. Current state is: failing
- opal.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- opal.0.1.1 on 5.0 is now installable. Current state is: failing
- opal.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- opam-core.2.0.2 on 5.0 is now installable. Current state is: failing
- opam-core.2.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- opam-core.2.0.3 on 5.0 is now installable. Current state is: failing
- opam-core.2.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- opam-core.2.0.4 on 5.0 is now installable. Current state is: failing
- opam-core.2.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- opam-core.2.0.5 on 5.0 is now installable. Current state is: failing
- opam-core.2.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- opam-core.2.0.6 on 5.0 is now installable. Current state is: failing
- opam-core.2.0.6 on 5.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- opam-sync-github-prs.1.1.0 on 4.02 had its build status changed: partially failing to failing
- opam-sync-github-prs.1.1.0 on 4.03 had its build status changed: partially failing to failing
- opam2web.1.5.0 on 4.06 had its build status changed: passing to failing
- 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
- operf-micro.1.1.1 on 5.0 is now installable. Current state is: failing
- operf-micro.1.1.1 on 5.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- optint.0.0.2 on 5.0 is now installable. Current state is: failing
- optint.0.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- ordma.0.0.5.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
- ordma.0.0.5.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
- orun.0.0.1 on 4.07 had its build status changed: passing to failing
- orun.0.0.1 on 4.08 had its build status changed: passing to failing
- orun.0.0.1 on 4.09 had its build status changed: passing to failing
- orun.0.0.1 on 4.10 had its build status changed: passing to failing
- orun.0.0.1 on 4.11 had its build status changed: passing to failing
- orun.0.0.1 on 4.12 had its build status changed: passing to failing
- orun.0.0.1 on 4.13 had its build status changed: passing to failing
- orun.0.0.1 on 4.14 is now installable. Current state is: failing
- orun.0.0.1 on 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- osdp.0.6.0 on 5.0+alpha-repo is now installable. Current state is: failing
- osdp.1.1.0 on 5.0 is now installable. Current state is: failing
- osdp.1.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- ott.0.26 on 5.0 is now installable. Current state is: failing
- ott.0.26 on 5.0+alpha-repo is now installable. Current state is: failing
- ott.0.27 on 5.0 is now installable. Current state is: failing
- ott.0.27 on 5.0+alpha-repo is now installable. Current state is: failing
- ott.0.28 on 5.0 is now installable. Current state is: failing
- ott.0.28 on 5.0+alpha-repo is now installable. Current state is: failing
- ott.0.29 on 5.0 is now installable. Current state is: failing
- ott.0.29 on 5.0+alpha-repo is now installable. Current state is: failing
- ott.0.30 on 5.0 is now installable. Current state is: failing
- ott.0.30 on 5.0+alpha-repo is now installable. Current state is: failing
- ott.0.31 on 5.0 is now installable. Current state is: failing
- ott.0.31 on 5.0+alpha-repo is now installable. Current state is: failing
- ott.0.32 on 5.0 is now installable. Current state is: failing
- ott.0.32 on 5.0+alpha-repo is now installable. Current state is: failing
- owl-base.0.4.0 on 5.0 is now installable. Current state is: failing
- owl-base.0.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- owl-base.0.5.0 on 5.0 is now installable. Current state is: failing
- owl-base.0.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- owl-base.0.6.0 on 5.0 is now installable. Current state is: failing
- owl-base.0.6.0 on 5.0+alpha-repo 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_monad_custom.v6.0.0 on 5.0+alpha-repo 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.0.0.7 on 5.0+alpha-repo is now installable. Current state is: failing
- paf.0.0.8 on 5.0+alpha-repo is now installable. Current state is: failing
- paf.0.0.8-1 on 5.0+alpha-repo is now installable. Current state is: failing
- paf.0.0.9 on 5.0+alpha-repo is now installable. Current state is: failing
- papi.0.1.0 on 4.14 is now installable. Current state is: failing
- papi.0.1.0 on 4.14+alpha-repo is now installable. Current state is: failing
- papi.0.1.0 on 5.0 is now installable. Current state is: failing
- papi.0.1.0 on 5.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- parmap.1.0-rc11 on 5.0 is now installable. Current state is: failing
- parmap.1.0-rc11 on 5.0+alpha-repo is now installable. Current state is: failing
- parmap.1.1.1 on 5.0 is now installable. Current state is: failing
- parmap.1.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- parmap.1.2 on 5.0 is now installable. Current state is: failing
- parmap.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- parmap.1.2.1 on 5.0 is now installable. Current state is: failing
- parmap.1.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- parmap.1.2.3 on 5.0 is now installable. Current state is: failing
- parmap.1.2.3 on 5.0+alpha-repo is now installable. Current state is: failing
- parmap.1.2.4 on 5.0 is now installable. Current state is: failing
- parmap.1.2.4 on 5.0+alpha-repo is now installable. Current state is: failing
- patch.1.0.0 on 5.0 is now installable. Current state is: failing
- patch.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- pci.1.0.1 on 5.0 is now installable. Current state is: failing
- pci.1.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- petr4.0.1 on 4.04 had its build status changed: passing to failing
- petr4.0.1 on 4.05 had its build status changed: passing to failing
- petr4.0.1 on 4.06 had its build status changed: passing to failing
- petr4.0.1 on 4.07 had its build status changed: passing to failing
- petr4.0.1 on 4.08 had its build status changed: passing to failing
- petr4.0.1 on 4.09 had its build status changed: passing to failing
- petr4.0.1.1 on 4.04 had its build status changed: passing to failing
- petr4.0.1.1 on 4.05 had its build status changed: passing to failing
- petr4.0.1.1 on 4.06 had its build status changed: passing to failing
- petr4.0.1.1 on 4.07 had its build status changed: passing to failing
- petr4.0.1.1 on 4.08 had its build status changed: passing to failing
- petr4.0.1.1 on 4.09 had its build status changed: passing to failing
- pfff.0.40.4 on 4.08 had its build status changed: passing to failing
- pfff.0.40.4 on 4.09 had its build status changed: passing to failing
- pfff.0.40.4 on 4.10 had its build status changed: passing to failing
- pfff.0.40.4 on 4.11 had its build status changed: passing to failing
- pgx.1.0 on 5.0 is now installable. Current state is: failing
- pgx.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- pgx.2.0 on 5.0 is now installable. Current state is: failing
- pgx.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- pgx.2.1 on 5.0 is now installable. Current state is: failing
- pgx.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- piaf.0.1.0 on 5.0 is now installable. Current state is: failing
- piaf.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- piqi.0.7.0 on 4.06 had its build status changed: not available to failing
- piqi.0.7.0 on 4.07 had its build status changed: not available to failing
- piqi.0.7.0 on 4.08 had its build status changed: not available to failing
- piqi.0.7.0 on 4.09 had its build status changed: not available to failing
- piqi.0.7.0 on 4.10 had its build status changed: not available to failing
- piqi.0.7.0 on 4.11 had its build status changed: not available to failing
- piqi.0.7.0 on 4.12 had its build status changed: not available to failing
- piqi.0.7.0 on 4.13 had its build status changed: not available to failing
- piqi.0.7.0 on 4.14 is now installable. Current state is: failing
- piqi.0.7.0 on 4.14+alpha-repo is now installable. Current state is: failing
- piqi.0.7.1 on 4.06 had its build status changed: not available to failing
- piqi.0.7.1 on 4.07 had its build status changed: not available to failing
- piqi.0.7.1 on 4.08 had its build status changed: not available to failing
- piqi.0.7.1 on 4.09 had its build status changed: not available to failing
- piqi.0.7.1 on 4.10 had its build status changed: not available to failing
- piqi.0.7.1 on 4.11 had its build status changed: not available to failing
- piqi.0.7.1 on 4.12 had its build status changed: not available to failing
- piqi.0.7.1 on 4.13 had its build status changed: not available to failing
- piqi.0.7.1 on 4.14 is now installable. Current state is: failing
- piqi.0.7.1 on 4.14+alpha-repo is now installable. Current state is: failing
- piqi.0.7.4 on 4.06 had its build status changed: not available to failing
- piqi.0.7.4 on 4.07 had its build status changed: not available to failing
- piqi.0.7.4 on 4.08 had its build status changed: not available to failing
- piqi.0.7.4 on 4.09 had its build status changed: not available to failing
- piqi.0.7.4 on 4.10 had its build status changed: not available to failing
- piqi.0.7.4 on 4.11 had its build status changed: not available to failing
- piqi.0.7.4 on 4.12 had its build status changed: not available to failing
- piqi.0.7.4 on 4.13 had its build status changed: not available to failing
- piqi.0.7.4 on 4.14 is now installable. Current state is: failing
- piqi.0.7.4 on 4.14+alpha-repo is now installable. Current state is: failing
- piqi.0.7.5 on 4.06 had its build status changed: not available to failing
- piqi.0.7.5 on 4.07 had its build status changed: not available to failing
- piqi.0.7.5 on 4.08 had its build status changed: not available to failing
- piqi.0.7.5 on 4.09 had its build status changed: not available to failing
- piqi.0.7.5 on 4.10 had its build status changed: not available to failing
- piqi.0.7.5 on 4.11 had its build status changed: not available to failing
- piqi.0.7.5 on 4.12 had its build status changed: not available to failing
- piqi.0.7.5 on 4.13 had its build status changed: not available to failing
- piqi.0.7.5 on 4.14 is now installable. Current state is: failing
- piqi.0.7.5 on 4.14+alpha-repo is now installable. Current state is: failing
- plebeia.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- plplot.5.11.0 on 5.0 is now installable. Current state is: failing
- plplot.5.11.0 on 5.0+alpha-repo is now installable. Current state is: failing
- plplot.5.11.0-1 on 5.0 is now installable. Current state is: failing
- plplot.5.11.0-1 on 5.0+alpha-repo is now installable. Current state is: 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
- posix-math.0.3.0-0 on 5.0 is now installable. Current state is: failing
- posix-math.0.3.0-0 on 5.0+alpha-repo is now installable. Current state is: failing
- posix-math.0.3.1-0 on 5.0 is now installable. Current state is: failing
- posix-math.0.3.1-0 on 5.0+alpha-repo is now installable. Current state is: failing
- posix-time.0.3.0-0 on 5.0 is now installable. Current state is: failing
- posix-time.0.3.0-0 on 5.0+alpha-repo is now installable. Current state is: failing
- posix-time.0.5.1-0 on 5.0 is now installable. Current state is: failing
- posix-time.0.5.1-0 on 5.0+alpha-repo is now installable. Current state is: failing
- posix-time.0.5.2-0 on 5.0 is now installable. Current state is: failing
- posix-time.0.5.2-0 on 5.0+alpha-repo is now installable. Current state is: failing
- posix-time.0.5.3-0 on 5.0 is now installable. Current state is: failing
- posix-time.0.5.3-0 on 5.0+alpha-repo is now installable. Current state is: failing
- posix-time.1.0.0-0 on 5.0 is now installable. Current state is: failing
- posix-time.1.0.0-0 on 5.0+alpha-repo is now installable. Current state is: failing
- posix-time.1.0.1-0 on 5.0 is now installable. Current state is: failing
- posix-time.1.0.1-0 on 5.0+alpha-repo is now installable. Current state is: failing
- postgresql.3.2.1 on 4.02 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.03 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.04 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.05 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.06 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.07 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.08 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.09 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.10 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.11 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.12 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.13 had its build status changed: passing to failing
- postgresql.3.2.1 on 4.14 is now installable. Current state is: failing
- postgresql.3.2.1 on 4.14+alpha-repo is now installable. Current state is: failing
- postgresql.3.2.1 on 5.0 is now installable. Current state is: failing
- postgresql.3.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- postgresql.4.0.0 on 4.02 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.03 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.04 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.05 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.06 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.07 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.08 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.09 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.10 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.11 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.12 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.13 had its build status changed: passing to failing
- postgresql.4.0.0 on 4.14 is now installable. Current state is: failing
- postgresql.4.0.0 on 4.14+alpha-repo is now installable. Current state is: failing
- postgresql.4.0.0 on 5.0 is now installable. Current state is: failing
- postgresql.4.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- postgresql.4.0.1 on 4.02 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.03 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.04 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.05 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.06 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.07 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.08 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.09 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.10 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.11 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.12 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.13 had its build status changed: passing to failing
- postgresql.4.0.1 on 4.14 is now installable. Current state is: failing
- postgresql.4.0.1 on 4.14+alpha-repo is now installable. Current state is: failing
- postgresql.4.0.1 on 5.0 is now installable. Current state is: failing
- postgresql.4.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- postgresql.4.1.0 on 4.04 had its build status changed: passing to failing
- postgresql.4.1.0 on 4.05 had its build status changed: passing to failing
- postgresql.4.1.0 on 4.06 had its build status changed: passing to failing
- postgresql.4.1.0 on 4.07 had its build status changed: passing to failing
- postgresql.4.1.0 on 4.08 had its build status changed: passing to failing
- postgresql.4.1.0 on 4.09 had its build status changed: passing to failing
- postgresql.4.1.0 on 4.10 had its build status changed: passing to failing
- postgresql.4.1.0 on 4.11 had its build status changed: passing to failing
- postgresql.4.2.0 on 4.04 had its build status changed: passing to failing
- postgresql.4.2.0 on 4.05 had its build status changed: passing to failing
- postgresql.4.2.0 on 4.06 had its build status changed: passing to failing
- postgresql.4.2.0 on 4.07 had its build status changed: passing to failing
- postgresql.4.2.0 on 4.08 had its build status changed: passing to failing
- postgresql.4.2.0 on 4.09 had its build status changed: passing to failing
- postgresql.4.2.0 on 4.10 had its build status changed: passing to failing
- postgresql.4.2.0 on 4.11 had its build status changed: passing to failing
- postgresql.4.2.1 on 4.04 had its build status changed: passing to failing
- postgresql.4.2.1 on 4.05 had its build status changed: passing to failing
- postgresql.4.2.1 on 4.06 had its build status changed: passing to failing
- postgresql.4.2.1 on 4.07 had its build status changed: passing to failing
- postgresql.4.2.1 on 4.08 had its build status changed: passing to failing
- postgresql.4.2.1 on 4.09 had its build status changed: passing to failing
- postgresql.4.2.1 on 4.10 had its build status changed: passing to failing
- postgresql.4.2.1 on 4.11 had its build status changed: passing to failing
- postgresql.4.3.0 on 4.04 had its build status changed: passing to failing
- postgresql.4.3.0 on 4.05 had its build status changed: passing to failing
- postgresql.4.3.0 on 4.06 had its build status changed: passing to failing
- postgresql.4.3.0 on 4.07 had its build status changed: passing to failing
- postgresql.4.3.0 on 4.08 had its build status changed: passing to failing
- postgresql.4.3.0 on 4.09 had its build status changed: passing to failing
- postgresql.4.3.0 on 4.10 had its build status changed: passing to failing
- postgresql.4.3.0 on 4.11 had its build status changed: passing to failing
- postgresql.4.4.0 on 4.04 had its build status changed: passing to failing
- postgresql.4.4.0 on 4.05 had its build status changed: passing to failing
- postgresql.4.4.0 on 4.06 had its build status changed: passing to failing
- postgresql.4.4.0 on 4.07 had its build status changed: passing to failing
- postgresql.4.4.0 on 4.08 had its build status changed: passing to failing
- postgresql.4.4.0 on 4.09 had its build status changed: passing to failing
- postgresql.4.4.0 on 4.10 had its build status changed: passing to failing
- postgresql.4.4.0 on 4.11 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.05 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.06 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.07 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.08 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.09 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.10 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.11 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.12 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.13 had its build status changed: passing to failing
- postgresql.4.4.1 on 4.14 is now installable. Current state is: failing
- postgresql.4.4.1 on 4.14+alpha-repo is now installable. Current state is: failing
- postgresql.4.4.1 on 5.0 is now installable. Current state is: failing
- postgresql.4.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- postgresql.4.4.2 on 4.05 had its build status changed: passing to failing
- postgresql.4.4.2 on 4.06 had its build status changed: passing to failing
- postgresql.4.4.2 on 4.07 had its build status changed: passing to failing
- postgresql.4.4.2 on 4.08 had its build status changed: passing to failing
- postgresql.4.4.2 on 4.09 had its build status changed: passing to failing
- postgresql.4.4.2 on 4.10 had its build status changed: passing to failing
- postgresql.4.4.2 on 4.11 had its build status changed: passing to failing
- postgresql.4.4.2 on 4.12 had its build status changed: passing to failing
- postgresql.4.4.2 on 4.13 had its build status changed: passing to failing
- postgresql.4.4.2 on 4.14 is now installable. Current state is: failing
- postgresql.4.4.2 on 4.14+alpha-repo is now installable. Current state is: failing
- postgresql.4.4.2 on 5.0 is now installable. Current state is: failing
- postgresql.4.4.2 on 5.0+alpha-repo is now installable. Current state is: failing
- postgresql.4.5.0 on 4.05 had its build status changed: passing to failing
- postgresql.4.5.0 on 4.06 had its build status changed: passing to failing
- postgresql.4.5.0 on 4.07 had its build status changed: passing to failing
- postgresql.4.5.0 on 4.08 had its build status changed: passing to failing
- postgresql.4.5.0 on 4.09 had its build status changed: passing to failing
- postgresql.4.5.0 on 4.10 had its build status changed: passing to failing
- postgresql.4.5.0 on 4.11 had its build status changed: passing to failing
- postgresql.4.5.0 on 4.12 had its build status changed: passing to failing
- postgresql.4.5.0 on 4.13 had its build status changed: passing to failing
- postgresql.4.5.0 on 4.14 is now installable. Current state is: failing
- postgresql.4.5.0 on 4.14+alpha-repo is now installable. Current state is: failing
- postgresql.4.5.0 on 5.0 is now installable. Current state is: failing
- postgresql.4.5.0 on 5.0+alpha-repo is now installable. Current state is: 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_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
- pratter.0.1.1 on 5.0 is now installable. Current state is: failing
- pratter.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- pratter.1.0 on 5.0 is now installable. Current state is: failing
- pratter.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- pratter.1.1 on 5.0 is now installable. Current state is: failing
- pratter.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- pratter.1.2 on 5.0 is now installable. Current state is: failing
- pratter.1.2 on 5.0+alpha-repo is now installable. Current state is: 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.0 on 5.0+alpha-repo is now installable. Current state is: failing
- protocol-9p.1.0.1 on 5.0 is now installable. Current state is: failing
- protocol-9p.1.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- pyml.20170730 on 5.0 is now installable. Current state is: failing
- pyml.20170730 on 5.0+alpha-repo is now installable. Current state is: failing
- pyml.20170807 on 5.0 is now installable. Current state is: failing
- pyml.20170807 on 5.0+alpha-repo is now installable. Current state is: failing
- pyml.20200518 on 5.0 is now installable. Current state is: failing
- pyml.20200518 on 5.0+alpha-repo is now installable. Current state is: failing
- pyml.20210226 on 5.0 is now installable. Current state is: failing
- pyml.20210226 on 5.0+alpha-repo is now installable. Current state is: failing
- pyml.20210924 on 5.0 is now installable. Current state is: failing
- pyml.20210924 on 5.0+alpha-repo is now installable. Current state is: failing
- pyml.20211015 on 5.0 is now installable. Current state is: failing
- pyml.20211015 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck-core.0.10 on 5.0 is now installable. Current state is: failing
- qcheck-core.0.10 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck-core.0.11 on 5.0 is now installable. Current state is: failing
- qcheck-core.0.11 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck-core.0.12 on 5.0 is now installable. Current state is: failing
- qcheck-core.0.12 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck-core.0.9 on 5.0 is now installable. Current state is: failing
- qcheck-core.0.9 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck.0.3 on 5.0 is now installable. Current state is: failing
- qcheck.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck.0.4 on 5.0 is now installable. Current state is: failing
- qcheck.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck.0.5.2 on 5.0 is now installable. Current state is: failing
- qcheck.0.5.2 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck.0.5.3 on 5.0 is now installable. Current state is: failing
- qcheck.0.5.3 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck.0.5.3.1 on 5.0 is now installable. Current state is: failing
- qcheck.0.5.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck.0.6 on 5.0 is now installable. Current state is: failing
- qcheck.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- qcheck.0.7 on 5.0 is now installable. Current state is: failing
- qcheck.0.7 on 5.0+alpha-repo is now installable. Current state is: failing
- qcow.0.11.0.1~alpha-repo on 4.14+alpha-repo is now installable. Current state is: failing
- qcow.0.11.0.1~alpha-repo on 5.0+alpha-repo is now installable. Current state is: failing
- qtest.2.10.1 on 5.0 is now installable. Current state is: failing
- qtest.2.10.1 on 5.0+alpha-repo is now installable. Current state is: failing
- qtest.2.7 on 5.0 is now installable. Current state is: failing
- qtest.2.7 on 5.0+alpha-repo is now installable. Current state is: failing
- qtest.2.8 on 5.0 is now installable. Current state is: failing
- qtest.2.8 on 5.0+alpha-repo is now installable. Current state is: failing
- quest.0.1 on 5.0 is now installable. Current state is: failing
- quest.0.1 on 5.0+alpha-repo 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
- radare2.0.0.2 on 4.14+alpha-repo is now installable. Current state is: failing
- randoml.0.1.5 on 5.0+alpha-repo 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: passing to failing
- rdf.0.11.0 on 4.08 had its build status changed: passing to failing
- rdf.0.11.0 on 4.09 had its build status changed: passing to failing
- rdf.0.11.0 on 4.10 had its build status changed: passing to failing
- rdf.0.12.0 on 4.12 is now installable. Current state is: failing
- rdf.0.7.0 on 4.02 had its build status changed: passing to failing
- rdr.1.0 on 5.0 is now installable. Current state is: failing
- rdr.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- rdr.1.1 on 5.0 is now installable. Current state is: failing
- rdr.1.1 on 5.0+alpha-repo is now installable. Current state is: 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
- redis.0.4 on 5.0 is now installable. Current state is: failing
- redis.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- redis.0.5 on 5.0 is now installable. Current state is: failing
- redis.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- resource-pooling.0.3.2 on 5.0 is now installable. Current state is: failing
- resource-pooling.0.3.2 on 5.0+alpha-repo is now installable. Current state is: failing
- resource-pooling.0.5 on 5.0 is now installable. Current state is: failing
- resource-pooling.0.5 on 5.0+alpha-repo is now installable. Current state is: failing
- resource-pooling.0.5.1 on 5.0 is now installable. Current state is: failing
- resource-pooling.0.5.1 on 5.0+alpha-repo is now installable. Current state is: failing
- resource-pooling.0.5.2 on 5.0 is now installable. Current state is: failing
- resource-pooling.0.5.2 on 5.0+alpha-repo is now installable. Current state is: failing
- resource-pooling.0.6 on 5.0 is now installable. Current state is: failing
- resource-pooling.0.6 on 5.0+alpha-repo is now installable. Current state is: failing
- resource-pooling.0.7 on 5.0 is now installable. Current state is: failing
- resource-pooling.0.7 on 5.0+alpha-repo is now installable. Current state is: failing
- resource-pooling.0.8 on 5.0 is now installable. Current state is: failing
- resource-pooling.0.8 on 5.0+alpha-repo is now installable. Current state is: failing
- rfc7748.1.0 on 5.0 is now installable. Current state is: failing
- rfc7748.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- rfsm.1.0 on 4.13 had its build status changed: not available to failing
- rfsm.1.0 on 4.14 is now installable. Current state is: failing
- rfsm.1.0 on 4.14+alpha-repo 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.4.2 on 4.14+alpha-repo 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
- rfsm.1.5 on 4.14+alpha-repo is now installable. Current state is: failing
- rml.1.09.05 on 5.0 is now installable. Current state is: failing
- rml.1.09.05 on 5.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- root1d.0.4 on 5.0 is now installable. Current state is: failing
- root1d.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- rope.0.6.2 on 5.0 is now installable. Current state is: failing
- rope.0.6.2 on 5.0+alpha-repo 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
- safepass.2.0 on 5.0 is now installable. Current state is: failing
- safepass.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- scid.1.0 on 5.0 is now installable. Current state is: failing
- scid.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- semver.0.1.0 on 5.0 is now installable. Current state is: failing
- semver.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- sequence.0.2 on 5.0 is now installable. Current state is: failing
- sequence.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- sessions.0.1.0 on 5.0 is now installable. Current state is: failing
- sessions.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- setr.0.1 on 5.0 is now installable. Current state is: failing
- setr.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- setr.0.1.1 on 5.0 is now installable. Current state is: failing
- setr.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- sha.1.10 on 5.0 is now installable. Current state is: failing
- sha.1.10 on 5.0+alpha-repo is now installable. Current state is: failing
- sha.1.11 on 5.0 is now installable. Current state is: failing
- sha.1.11 on 5.0+alpha-repo is now installable. Current state is: failing
- sha.1.13 on 5.0 is now installable. Current state is: failing
- sha.1.13 on 5.0+alpha-repo is now installable. Current state is: failing
- sha.1.14 on 5.0 is now installable. Current state is: failing
- sha.1.14 on 5.0+alpha-repo is now installable. Current state is: failing
- sha.1.15.1 on 5.0 is now installable. Current state is: failing
- sha.1.15.1 on 5.0+alpha-repo is now installable. Current state is: failing
- shcaml.0.2.1 on 5.0 is now installable. Current state is: failing
- shcaml.0.2.1 on 5.0+alpha-repo 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
- sodium.0.2.1 on 5.0 is now installable. Current state is: failing
- sodium.0.2.1 on 5.0+alpha-repo is now installable. Current state is: 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 4.14+alpha-repo 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.0+alpha-repo 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.11 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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.08 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo 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 4.14+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- sosa.0.2.0 on 5.0 is now installable. Current state is: failing
- sosa.0.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- sosa.0.3.0 on 5.0 is now installable. Current state is: failing
- sosa.0.3.0 on 5.0+alpha-repo 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
- spelll.0.2 on 5.0 is now installable. Current state is: failing
- spelll.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- spelll.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- spin.0.8.0 on 5.0 is now installable. Current state is: failing
- spin.0.8.0 on 5.0+alpha-repo is now installable. Current state is: failing
- spin.0.8.1 on 5.0 is now installable. Current state is: failing
- spin.0.8.1 on 5.0+alpha-repo is now installable. Current state is: failing
- spin.0.8.2 on 5.0 is now installable. Current state is: failing
- spin.0.8.2 on 5.0+alpha-repo is now installable. Current state is: failing
- spin.0.8.3 on 5.0 is now installable. Current state is: failing
- spin.0.8.3 on 5.0+alpha-repo is now installable. Current state is: failing
- spreadsheet.0.1 on 5.0 is now installable. Current state is: failing
- spreadsheet.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- sqlgg.0.4.4 on 5.0 is now installable. Current state is: failing
- sqlgg.0.4.4 on 5.0+alpha-repo is now installable. Current state is: failing
- sqlgg.0.4.5 on 5.0 is now installable. Current state is: failing
- sqlgg.0.4.5 on 5.0+alpha-repo is now installable. Current state is: 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
- statverif.1.97pl1.1 on 5.0 is now installable. Current state is: failing
- statverif.1.97pl1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- statverif.1.97pl1.2 on 5.0 is now installable. Current state is: failing
- statverif.1.97pl1.2 on 5.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- stdcompat.1 on 5.0 is now installable. Current state is: failing
- stdcompat.1 on 5.0+alpha-repo is now installable. Current state is: failing
- stemmer.0.2 on 5.0 is now installable. Current state is: failing
- stemmer.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- stemming.0.2.1 on 5.0 is now installable. Current state is: failing
- stemming.0.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- stog-writing.0.19.0 on 4.12 is now installable. Current state is: failing
- stog.0.19.0 on 4.12 is now installable. Current state is: failing
- stog_server.0.20.0 on 4.12 is now installable. Current state is: failing
- swagger.0.1.0 on 4.14+alpha-repo is now installable. Current state is: failing
- swagger.0.2.0 on 4.14+alpha-repo is now installable. Current state is: failing
- swagger.0.2.0 on 5.0+alpha-repo 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.1 on 5.0 is now installable. Current state is: failing
- syndic.1.5.1 on 5.0+alpha-repo is now installable. Current state is: 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.2 on 5.0 is now installable. Current state is: failing
- syndic.1.5.2 on 5.0+alpha-repo is now installable. Current state is: 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.5.3 on 5.0 is now installable. Current state is: failing
- syndic.1.5.3 on 5.0+alpha-repo is now installable. Current state is: 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
- taglib.0.2.0 on 4.02 had its build status changed: passing to failing
- taglib.0.2.0 on 4.03 had its build status changed: passing to failing
- taglib.0.2.0 on 4.04 had its build status changed: passing to failing
- taglib.0.2.0 on 4.05 had its build status changed: passing to failing
- taglib.0.2.0 on 4.06 had its build status changed: passing to failing
- taglib.0.2.0 on 4.07 had its build status changed: passing to failing
- taglib.0.2.0 on 4.08 had its build status changed: passing to failing
- taglib.0.2.0 on 4.09 had its build status changed: passing to failing
- taglib.0.3.0 on 4.02 had its build status changed: passing to failing
- taglib.0.3.0 on 4.03 had its build status changed: passing to failing
- taglib.0.3.0 on 4.04 had its build status changed: passing to failing
- taglib.0.3.0 on 4.05 had its build status changed: passing to failing
- taglib.0.3.0 on 4.06 had its build status changed: passing to failing
- taglib.0.3.0 on 4.07 had its build status changed: passing to failing
- taglib.0.3.0 on 4.08 had its build status changed: passing to failing
- taglib.0.3.0 on 4.09 had its build status changed: passing to failing
- taglib.0.3.2 on 4.02 had its build status changed: passing to failing
- taglib.0.3.2 on 4.03 had its build status changed: passing to failing
- taglib.0.3.2 on 4.04 had its build status changed: passing to failing
- taglib.0.3.2 on 4.05 had its build status changed: passing to failing
- taglib.0.3.2 on 4.06 had its build status changed: passing to failing
- taglib.0.3.2 on 4.07 had its build status changed: passing to failing
- taglib.0.3.2 on 4.08 had its build status changed: passing to failing
- taglib.0.3.2 on 4.09 had its build status changed: passing to failing
- taglib.0.3.3 on 4.02 had its build status changed: passing to failing
- taglib.0.3.3 on 4.03 had its build status changed: passing to failing
- taglib.0.3.3 on 4.04 had its build status changed: passing to failing
- taglib.0.3.3 on 4.05 had its build status changed: passing to failing
- taglib.0.3.3 on 4.06 had its build status changed: passing to failing
- taglib.0.3.3 on 4.07 had its build status changed: passing to failing
- taglib.0.3.3 on 4.08 had its build status changed: passing to failing
- taglib.0.3.3 on 4.09 had its build status changed: passing to failing
- taglib.0.3.6 on 4.02 had its build status changed: passing to failing
- taglib.0.3.6 on 4.03 had its build status changed: passing to failing
- taglib.0.3.6 on 4.04 had its build status changed: passing to failing
- taglib.0.3.6 on 4.05 had its build status changed: passing to failing
- taglib.0.3.6 on 4.06 had its build status changed: passing to failing
- taglib.0.3.6 on 4.07 had its build status changed: passing to failing
- taglib.0.3.6 on 4.08 had its build status changed: passing to failing
- taglib.0.3.6 on 4.09 had its build status changed: passing to failing
- taglib.0.3.6 on 4.10 had its build status changed: passing to failing
- taglib.0.3.6 on 4.11 had its build status changed: passing to failing
- taglib.0.3.6 on 4.12 had its build status changed: passing to failing
- taglib.0.3.6 on 4.13 had its build status changed: passing to failing
- taglib.0.3.6 on 4.14 is now installable. Current state is: failing
- taglib.0.3.6 on 4.14+alpha-repo is now installable. Current state is: failing
- taglib.0.3.6 on 5.0 is now installable. Current state is: failing
- taglib.0.3.6 on 5.0+alpha-repo is now installable. Current state is: failing
- tar.1.0.0 on 5.0 is now installable. Current state is: failing
- tar.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- tar.1.0.1 on 5.0 is now installable. Current state is: failing
- tar.1.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- tar.1.1.0 on 5.0 is now installable. Current state is: failing
- tar.1.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- tar.2.0.0 on 5.0 is now installable. Current state is: failing
- tar.2.0.0 on 5.0+alpha-repo is now installable. Current state is: 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
- tdk.0.1.1 on 5.0 is now installable. Current state is: failing
- tdk.0.1.1 on 5.0+alpha-repo is now installable. Current state is: failing
- tdk.0.2.0 on 5.0 is now installable. Current state is: failing
- tdk.0.2.0 on 5.0+alpha-repo is now installable. Current state is: 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: passing 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
- textwrap.0.2 on 5.0 is now installable. Current state is: failing
- textwrap.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- thrift.0.10.0 on 5.0 is now installable. Current state is: failing
- thrift.0.10.0 on 5.0+alpha-repo 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+alpha-repo is now installable. Current state is: failing
- torch.0.4 on 5.0 is now installable. Current state is: failing
- torch.0.4 on 5.0+alpha-repo is now installable. Current state is: failing
- torch.0.5 on 5.0 is now installable. Current state is: failing
- torch.0.5 on 5.0+alpha-repo 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.0+alpha-repo is now installable. Current state is: failing
- tptp.0.3.2 on 5.0 is now installable. Current state is: failing
- tptp.0.3.2 on 5.0+alpha-repo is now installable. Current state is: failing
- travis-opam.1.0.0 on 5.0 is now installable. Current state is: failing
- travis-opam.1.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- travis-opam.1.0.2 on 5.0 is now installable. Current state is: failing
- travis-opam.1.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- travis-opam.1.0.3 on 5.0 is now installable. Current state is: failing
- travis-opam.1.0.3 on 5.0+alpha-repo is now installable. Current state is: failing
- travis-opam.1.1.0 on 5.0 is now installable. Current state is: failing
- travis-opam.1.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- travis-opam.1.5.0 on 5.0 is now installable. Current state is: failing
- travis-opam.1.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- tree_layout.0.1.0 on 5.0 is now installable. Current state is: failing
- tree_layout.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- type_conv.113.00.02 on 5.0+alpha-repo is now installable. Current state is: failing
- typpx.1.2.1 on 4.04 had its build status changed: internal failure to failing
- typpx.1.3.0 on 4.05 had its build status changed: internal failure to failing
- ubpf.0.1 on 4.08 had its build status changed: passing to failing
- ubpf.0.1 on 4.09 had its build status changed: passing to failing
- ubpf.0.1 on 4.10 had its build status changed: passing to failing
- ubpf.0.1 on 4.11 had its build status changed: passing to failing
- ubpf.0.1 on 4.12 had its build status changed: passing to failing
- ubpf.0.1 on 4.13 had its build status changed: passing to failing
- ubpf.0.1 on 4.14 is now installable. Current state is: failing
- ubpf.0.1 on 4.14+alpha-repo is now installable. Current state is: failing
- ubpf.0.1 on 5.0 is now installable. Current state is: failing
- ubpf.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- ucaml.0.1 on 5.0 is now installable. Current state is: failing
- ucaml.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- ulex.1.2 on 5.0+alpha-repo is now installable. Current state is: failing
- unix-errno.0.3.0 on 5.0 is now installable. Current state is: failing
- unix-errno.0.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- unix-errno.0.4.0 on 5.0 is now installable. Current state is: failing
- unix-errno.0.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- unix-errno.0.4.1 on 5.0 is now installable. Current state is: failing
- unix-errno.0.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- unix-errno.0.4.2 on 5.0 is now installable. Current state is: failing
- unix-errno.0.4.2 on 5.0+alpha-repo is now installable. Current state is: failing
- unix-type-representations.0.1.0 on 5.0 is now installable. Current state is: failing
- unix-type-representations.0.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- utop.2.9.0 on 5.0+alpha-repo is now installable. Current state is: failing
- utop.2.9.1 on 5.0+alpha-repo 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
- vector3.0.2.1 on 5.0 is now installable. Current state is: failing
- vector3.0.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- vhd-format.0.12.0 on 4.08 had its build status changed: passing to failing
- vhd-format.0.12.0 on 4.09 had its build status changed: passing to failing
- vhd-format.0.12.0 on 4.10 had its build status changed: passing to failing
- vhd-format.0.12.0 on 4.11 had its build status changed: passing to failing
- vhd-format.0.12.0 on 4.12 had its build status changed: passing to failing
- vhd-format.0.12.1 on 4.08 is now installable. Current state is: failing
- vhd-format.0.12.1 on 4.09 is now installable. Current state is: failing
- vhd-format.0.12.1 on 4.10 is now installable. Current state is: failing
- vhd-format.0.12.1 on 4.11 is now installable. Current state is: failing
- vhd-format.0.12.1 on 4.12 is now installable. Current state is: failing
- vlq.0.2.1 on 5.0 is now installable. Current state is: failing
- vlq.0.2.1 on 5.0+alpha-repo is now installable. Current state is: failing
- volt.1.4 on 5.0+alpha-repo is now installable. Current state is: failing
- voqc.0.2.0 on 5.0 is now installable. Current state is: failing
- voqc.0.2.0 on 5.0+alpha-repo is now installable. Current state is: failing
- voqc.0.2.1 on 5.0 is now installable. Current state is: failing
- voqc.0.2.1 on 5.0+alpha-repo is now installable. Current state is: 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.0+alpha-repo is now installable. Current state is: failing
- wcs-lib.2017-05-26.05 on 4.08 had its build status changed: passing to failing
- wcs-lib.2017-05-26.05 on 4.09 had its build status changed: passing to failing
- wcs-lib.2017-05-26.05 on 4.10 had its build status changed: passing to failing
- wcs-lib.2017-05-26.05 on 4.11 had its build status changed: passing to failing
- wcs-lib.2017-05-26.05 on 4.12 had its build status changed: passing to failing
- websocket.2.3 on 4.03 had its build status changed: passing to failing
- websocket.2.3 on 4.04 had its build status changed: passing to failing
- websocket.2.3 on 4.05 had its build status changed: passing to failing
- websocket.2.3 on 4.06 had its build status changed: passing to failing
- why3.1.3.0 on 5.0 is now installable. Current state is: failing
- why3.1.3.0 on 5.0+alpha-repo is now installable. Current state is: failing
- why3.1.3.1 on 5.0 is now installable. Current state is: failing
- why3.1.3.1 on 5.0+alpha-repo is now installable. Current state is: failing
- why3.1.3.2 on 5.0 is now installable. Current state is: failing
- why3.1.3.2 on 5.0+alpha-repo is now installable. Current state is: failing
- why3.1.3.3 on 5.0 is now installable. Current state is: failing
- why3.1.3.3 on 5.0+alpha-repo is now installable. Current state is: failing
- why3.1.4.0 on 5.0 is now installable. Current state is: failing
- why3.1.4.0 on 5.0+alpha-repo is now installable. Current state is: failing
- why3.1.4.1 on 5.0 is now installable. Current state is: failing
- why3.1.4.1 on 5.0+alpha-repo is now installable. Current state is: failing
- why3.1.5.0 on 5.0 is now installable. Current state is: failing
- why3.1.5.0 on 5.0+alpha-repo is now installable. Current state is: failing
- win-error.0.2 on 5.0 is now installable. Current state is: failing
- win-error.0.2 on 5.0+alpha-repo is now installable. Current state is: failing
- win-eventlog.0.1 on 5.0 is now installable. Current state is: failing
- win-eventlog.0.1 on 5.0+alpha-repo 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
- xen-gnt-unix.3.1.0 on 5.0 is now installable. Current state is: failing
- xen-gnt-unix.3.1.0 on 5.0+alpha-repo is now installable. Current state is: failing
- xen-gnt-unix.4.0.0 on 5.0 is now installable. Current state is: failing
- xen-gnt-unix.4.0.0 on 5.0+alpha-repo is now installable. Current state is: failing
- xen-gnt-unix.4.0.1 on 5.0 is now installable. Current state is: failing
- xen-gnt-unix.4.0.1 on 5.0+alpha-repo is now installable. Current state is: failing
- xml-light.2.3 on 5.0 is now installable. Current state is: failing
- xml-light.2.3 on 5.0+alpha-repo is now installable. Current state is: failing
- xml-light.2.4 on 5.0 is now installable. Current state is: failing
- xml-light.2.4 on 5.0+alpha-repo is now installable. Current state is: failing
- xmlplaylist.0.1.3 on 5.0 is now installable. Current state is: failing
- xmlplaylist.0.1.3 on 5.0+alpha-repo is now installable. Current state is: failing
- yajl.0.7.0 on 5.0 is now installable. Current state is: failing
- yajl.0.7.0 on 5.0+alpha-repo is now installable. Current state is: failing
- yajl.0.7.1 on 5.0 is now installable. Current state is: failing
- yajl.0.7.1 on 5.0+alpha-repo is now installable. Current state is: failing
- yajl.0.7.2 on 5.0 is now installable. Current state is: failing
- yajl.0.7.2 on 5.0+alpha-repo is now installable. Current state is: failing
- yajl.0.7.3 on 5.0 is now installable. Current state is: failing
- yajl.0.7.3 on 5.0+alpha-repo is now installable. Current state is: 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.10.1 on 4.11 is now installable. Current state is: failing
- z3.4.11.2 on 4.08 is now installable. Current state is: failing
- z3.4.7.1 on 5.0 is now installable. Current state is: failing
- z3.4.7.1 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.8.1 on 4.05 had its build status changed: passing to failing
- z3.4.8.1 on 5.0 is now installable. Current state is: failing
- z3.4.8.1 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.8.11 on 4.14+alpha-repo is now installable. Current state is: failing
- z3.4.8.11 on 5.0 is now installable. Current state is: failing
- z3.4.8.11 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.8.17 on 5.0 is now installable. Current state is: failing
- z3.4.8.4 on 5.0 is now installable. Current state is: failing
- z3.4.8.4 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.8.5 on 5.0 is now installable. Current state is: failing
- z3.4.8.5 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.8.6 on 4.11 had its build status changed: passing to failing
- z3.4.8.6 on 5.0 is now installable. Current state is: failing
- z3.4.8.6 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.8.7 on 5.0 is now installable. Current state is: failing
- z3.4.8.7 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.8.8 on 4.04 had its build status changed: passing to failing
- z3.4.8.8 on 5.0 is now installable. Current state is: failing
- z3.4.8.8 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.8.8-1 on 4.11 had its build status changed: passing to failing
- z3.4.8.8-1 on 5.0 is now installable. Current state is: failing
- z3.4.8.8-1 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.8.9-1 on 5.0 is now installable. Current state is: failing
- z3.4.8.9-1 on 5.0+alpha-repo is now installable. Current state is: failing
- z3.4.9.1 on 4.09 is now installable. Current state is: failing
- zenon.0.8.4 on 5.0 is now installable. Current state is: failing
- zenon.0.8.4 on 5.0+alpha-repo is now installable. Current state is: failing
- zmq.4.0-8 on 5.0+alpha-repo is now installable. Current state is: failing
Packages now partially failing:
Home|Differences with the last checks|Previous runs