Packages now failing:
- alt-ergo-parsers.2.3.0 on 4.08 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.0 on 4.09 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.0 on 4.10 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.0 on 4.11 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.0 on 4.12 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.0 on 4.13 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.0 on 4.14 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.1 on 4.08 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.1 on 4.09 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.1 on 4.10 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.1 on 4.11 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.1 on 4.12 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.1 on 4.13 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.1 on 4.14 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.2 on 4.08 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.2 on 4.09 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.2 on 4.10 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.2 on 4.11 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.2 on 4.12 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.2 on 4.13 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.2 on 4.14 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.3 on 4.08 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.3 on 4.09 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.3 on 4.10 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.3 on 4.11 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.3 on 4.12 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.3 on 4.13 had its build status changed: passing to failing
- alt-ergo-parsers.2.3.3 on 4.14 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.0 on 4.08 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.0 on 4.09 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.0 on 4.10 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.0 on 4.11 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.0 on 4.12 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.0 on 4.13 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.0 on 4.14 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.1 on 4.08 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.1 on 4.09 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.1 on 4.10 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.1 on 4.11 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.1 on 4.12 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.1 on 4.13 had its build status changed: passing to failing
- alt-ergo-parsers.2.4.1 on 4.14 had its build status changed: passing to failing
- alt-ergo.1.30 on 4.08 had its build status changed: passing to failing
- alt-ergo.1.30 on 4.09 had its build status changed: passing to failing
- alt-ergo.1.30 on 4.10 had its build status changed: passing to failing
- alt-ergo.1.30 on 4.11 had its build status changed: passing to failing
- alt-ergo.1.30 on 4.12 had its build status changed: passing to failing
- alt-ergo.1.30 on 4.13 had its build status changed: passing to failing
- alt-ergo.1.30 on 4.14 had its build status changed: passing to failing
- balancer.1.0 on 4.08 had its build status changed: passing to failing
- balancer.1.0 on 4.09 had its build status changed: passing to failing
- balancer.1.0 on 4.10 had its build status changed: passing to failing
- balancer.1.0 on 4.11 had its build status changed: passing to failing
- binaryen.0.3.0 on 4.08 had its build status changed: passing to failing
- binaryen.0.3.0 on 4.09 had its build status changed: passing to failing
- binaryen.0.3.0 on 4.10 had its build status changed: passing to failing
- binaryen.0.3.0 on 4.11 had its build status changed: passing to failing
- bitwuzla-bin.1.0.0 on 4.08 had its build status changed: passing to failing
- bitwuzla-bin.1.0.0 on 4.09 had its build status changed: passing to failing
- bitwuzla-bin.1.0.0 on 4.10 had its build status changed: passing to failing
- bitwuzla-bin.1.0.0 on 4.11 had its build status changed: passing to failing
- bitwuzla-bin.1.0.0 on 4.12 had its build status changed: passing to failing
- bitwuzla-bin.1.0.0 on 4.13 had its build status changed: passing to failing
- bitwuzla-bin.1.0.0 on 4.14 had its build status changed: passing to failing
- bitwuzla-bin.1.0.0 on 5.0 had its build status changed: passing to failing
- bitwuzla-bin.1.0.0 on 5.1 is now installable. Current state is: failing
- camlmix.1.3.0 on 5.1 is now installable. Current state is: failing
- camlp4.4.08+1 on 4.08 had its build status changed: passing to failing
- camlp4.4.09+1 on 4.09 had its build status changed: passing to failing
- camlp4.4.10+1 on 4.10 had its build status changed: passing to failing
- camlp4.4.11+1 on 4.11 had its build status changed: passing to failing
- camlp4.4.12+1 on 4.12 had its build status changed: passing to failing
- camlp4.4.13+1 on 4.13 had its build status changed: passing to failing
- camlp4.4.14+1 on 4.14 had its build status changed: passing to failing
- cohttp-lwt.1.0.0 on 4.08 had its build status changed: passing to failing
- cohttp-lwt.1.0.0 on 4.09 had its build status changed: passing to failing
- cohttp-lwt.1.0.0 on 4.10 had its build status changed: passing to failing
- cohttp-lwt.1.0.0 on 4.11 had its build status changed: passing to failing
- conf-libclang.12 on 5.1 is now installable. Current state is: failing
- conf-libclang.15 on 4.08 is now installable. Current state is: failing
- conf-libclang.15 on 4.09 is now installable. Current state is: failing
- conf-libclang.15 on 4.10 is now installable. Current state is: failing
- conf-libclang.15 on 4.11 is now installable. Current state is: failing
- conf-libclang.15 on 4.12 is now installable. Current state is: failing
- conf-libclang.15 on 4.13 is now installable. Current state is: failing
- conf-libclang.15 on 4.14 is now installable. Current state is: failing
- conf-libclang.15 on 5.0 is now installable. Current state is: failing
- conf-libclang.15 on 5.1 is now installable. Current state is: failing
- conf-trexio.0.1 on 4.08 is now installable. Current state is: failing
- conf-trexio.0.1 on 4.09 is now installable. Current state is: failing
- conf-trexio.0.1 on 4.10 is now installable. Current state is: failing
- conf-trexio.0.1 on 4.11 is now installable. Current state is: failing
- conf-trexio.0.1 on 4.12 is now installable. Current state is: failing
- conf-trexio.0.1 on 4.13 is now installable. Current state is: failing
- conf-trexio.0.1 on 4.14 is now installable. Current state is: failing
- conf-trexio.0.1 on 5.0 is now installable. Current state is: failing
- conf-trexio.0.1 on 5.1 is now installable. Current state is: failing
- datalog.0.1 on 5.1 is now installable. Current state is: failing
- datalog.0.2 on 5.1 is now installable. Current state is: failing
- datalog.0.3 on 5.1 is now installable. Current state is: failing
- datalog.0.3.1 on 5.1 is now installable. Current state is: failing
- dune.3.12.1 on 4.08 is now installable. Current state is: failing
- dune.3.12.1 on 4.09 is now installable. Current state is: failing
- dune.3.12.1 on 4.10 is now installable. Current state is: failing
- dune.3.12.1 on 4.11 is now installable. Current state is: failing
- dune.3.12.1 on 4.12 is now installable. Current state is: failing
- dune.3.12.1 on 4.13 is now installable. Current state is: failing
- dune.3.12.1 on 4.14 is now installable. Current state is: failing
- dune.3.12.1 on 5.0 is now installable. Current state is: failing
- dune.3.12.1 on 5.1 is now installable. Current state is: failing
- fm-simplex-plugin.1.01 on 4.08 had its build status changed: passing to failing
- functoria-runtime.2.0.0 on 4.08 had its build status changed: passing to failing
- functoria-runtime.2.0.0 on 4.09 had its build status changed: passing to failing
- functoria-runtime.2.0.0 on 4.10 had its build status changed: passing to failing
- functoria-runtime.2.0.0 on 4.11 had its build status changed: passing to failing
- functoria-runtime.2.1.0 on 4.08 had its build status changed: passing to failing
- functoria-runtime.2.1.0 on 4.09 had its build status changed: passing to failing
- functoria-runtime.2.1.0 on 4.10 had its build status changed: passing to failing
- functoria-runtime.2.1.0 on 4.11 had its build status changed: passing to failing
- functoria-runtime.2.2.0 on 4.08 had its build status changed: passing to failing
- functoria-runtime.2.2.0 on 4.09 had its build status changed: passing to failing
- functoria-runtime.2.2.0 on 4.10 had its build status changed: passing to failing
- functoria-runtime.2.2.0 on 4.11 had its build status changed: passing to failing
- functoria-runtime.2.2.1 on 4.08 had its build status changed: passing to failing
- functoria-runtime.2.2.1 on 4.09 had its build status changed: passing to failing
- functoria-runtime.2.2.1 on 4.10 had its build status changed: passing to failing
- functoria-runtime.2.2.1 on 4.11 had its build status changed: passing to failing
- gammu.0.9.3 on 5.0 had its build status changed: partially failing to failing
- gammu.0.9.3 on 5.1 is now installable. Current state is: 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
- 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
- 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.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.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.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.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.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
- 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
- hweak.1.1 on 5.1 is now installable. Current state is: failing
- labltk.8.06.11 on 4.14 had its build status changed: passing to failing
- labltk.8.06.11 on 5.0 had its build status changed: passing to failing
- labltk.8.06.11 on 5.1 is now installable. Current state is: failing
- labltk.8.06.12 on 4.14 is now installable. Current state is: failing
- labltk.8.06.12 on 5.0 is now installable. Current state is: failing
- labltk.8.06.12 on 5.1 is now installable. Current state is: failing
- learn-ocaml.0.13.0 on 4.12 had its build status changed: passing to failing
- learn-ocaml.0.13.1 on 4.12 had its build status changed: passing to failing
- learn-ocaml.0.14.0 on 4.12 is now installable. Current state is: failing
- learn-ocaml.0.14.1 on 4.12 is now installable. Current state is: failing
- learn-ocaml.0.15.0 on 4.12 is now installable. Current state is: failing
- lem.2020-06-03 on 4.08 had its build status changed: passing to failing
- lem.2020-06-03 on 4.09 had its build status changed: passing to failing
- lem.2020-06-03 on 4.10 had its build status changed: passing to failing
- lem.2020-06-03 on 4.11 had its build status changed: passing to failing
- lem.2020-06-03 on 4.12 had its build status changed: passing to failing
- lem.2020-06-03 on 4.13 had its build status changed: passing to failing
- lem.2020-06-03 on 4.14 had its build status changed: passing to failing
- lem.2022-12-10 on 4.08 is now installable. Current state is: failing
- lem.2022-12-10 on 4.09 is now installable. Current state is: failing
- lem.2022-12-10 on 4.10 is now installable. Current state is: failing
- lem.2022-12-10 on 4.11 is now installable. Current state is: failing
- lem.2022-12-10 on 4.12 is now installable. Current state is: failing
- lem.2022-12-10 on 4.13 is now installable. Current state is: failing
- lem.2022-12-10 on 4.14 is now installable. Current state is: failing
- lem.2022-12-10 on 5.0 is now installable. Current state is: failing
- lem.2022-12-10 on 5.1 is now installable. Current state is: failing
- libssh.0.1 on 4.14 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 had its build status changed: passing to failing
- minios-xen.0.7 on 5.0 had its build status changed: passing to failing
- minios-xen.0.7 on 5.1 is now installable. Current state is: failing
- mirage-qubes.0.6 on 4.08 had its build status changed: passing to failing
- mirage-qubes.0.6 on 4.09 had its build status changed: passing to failing
- mirage-qubes.0.6 on 4.10 had its build status changed: passing to failing
- mirage-qubes.0.6 on 4.11 had its build status changed: passing to failing
- mirage-xen-minios.0.2 on 4.08 had its build status changed: passing to failing
- mirage-xen-minios.0.2 on 4.09 had its build status changed: passing to failing
- mirage-xen-minios.0.2 on 4.10 had its build status changed: passing to failing
- mirage-xen-minios.0.2 on 4.11 had its build status changed: passing to failing
- mirage-xen-minios.0.2 on 4.12 had its build status changed: passing to failing
- mirage-xen-minios.0.2 on 4.13 had its build status changed: passing to failing
- mirage-xen-minios.0.2 on 4.14 had its build status changed: passing to failing
- mirage-xen-minios.0.2 on 5.0 had its build status changed: passing to failing
- mirage-xen-minios.0.2 on 5.1 is now installable. Current state is: failing
- mirage-xen-minios.0.3 on 4.08 had its build status changed: passing to failing
- mirage-xen-minios.0.3 on 4.09 had its build status changed: passing to failing
- mirage-xen-minios.0.3 on 4.10 had its build status changed: passing to failing
- mirage-xen-minios.0.3 on 4.11 had its build status changed: passing to failing
- mirage-xen-minios.0.3 on 4.12 had its build status changed: passing to failing
- mirage-xen-minios.0.3 on 4.13 had its build status changed: passing to failing
- mirage-xen-minios.0.3 on 4.14 had its build status changed: passing to failing
- mirage-xen-minios.0.3 on 5.0 had its build status changed: passing to failing
- mirage-xen-minios.0.3 on 5.1 is now installable. Current state is: failing
- mirage-xen-minios.0.4 on 4.08 had its build status changed: passing to failing
- mirage-xen-minios.0.4 on 4.09 had its build status changed: passing to failing
- mirage-xen-minios.0.4 on 4.10 had its build status changed: passing to failing
- mirage-xen-minios.0.4 on 4.11 had its build status changed: passing to failing
- mirage-xen-minios.0.4 on 4.12 had its build status changed: passing to failing
- mirage-xen-minios.0.4 on 4.13 had its build status changed: passing to failing
- mirage-xen-minios.0.4 on 4.14 had its build status changed: passing to failing
- mirage-xen-minios.0.4 on 5.0 had its build status changed: passing to failing
- mirage-xen-minios.0.4 on 5.1 is now installable. Current state is: failing
- mirage-xen-minios.0.4.1 on 4.08 had its build status changed: passing to failing
- mirage-xen-minios.0.4.1 on 4.09 had its build status changed: passing to failing
- mirage-xen-minios.0.4.1 on 4.10 had its build status changed: passing to failing
- mirage-xen-minios.0.4.1 on 4.11 had its build status changed: passing to failing
- mirage-xen-minios.0.4.1 on 4.12 had its build status changed: passing to failing
- mirage-xen-minios.0.4.1 on 4.13 had its build status changed: passing to failing
- mirage-xen-minios.0.4.1 on 4.14 had its build status changed: passing to failing
- mirage-xen-minios.0.4.1 on 5.0 had its build status changed: passing to failing
- mirage-xen-minios.0.4.1 on 5.1 is now installable. Current state is: failing
- mirage-xen-minios.0.4.2 on 4.08 had its build status changed: passing to failing
- mirage-xen-minios.0.4.2 on 4.09 had its build status changed: passing to failing
- mirage-xen-minios.0.4.2 on 4.10 had its build status changed: passing to failing
- mirage-xen-minios.0.4.2 on 4.11 had its build status changed: passing to failing
- mirage-xen-minios.0.4.2 on 4.12 had its build status changed: passing to failing
- mirage-xen-minios.0.4.2 on 4.13 had its build status changed: passing to failing
- mirage-xen-minios.0.4.2 on 4.14 had its build status changed: passing to failing
- mirage-xen-minios.0.4.2 on 5.0 had its build status changed: passing to failing
- mirage-xen-minios.0.4.2 on 5.1 is now installable. Current state is: failing
- mirage-xen-minios.0.5.0 on 4.08 had its build status changed: passing to failing
- mirage-xen-minios.0.5.0 on 4.09 had its build status changed: passing to failing
- mirage-xen-minios.0.5.0 on 4.10 had its build status changed: passing to failing
- mirage-xen-minios.0.5.0 on 4.11 had its build status changed: passing to failing
- mirage-xen-minios.0.5.0 on 4.12 had its build status changed: passing to failing
- mirage-xen-minios.0.5.0 on 4.13 had its build status changed: passing to failing
- mirage-xen-minios.0.5.0 on 4.14 had its build status changed: passing to failing
- mirage-xen-minios.0.5.0 on 5.0 had its build status changed: passing to failing
- mirage-xen-minios.0.5.0 on 5.1 is now installable. Current state is: failing
- mirage-xen-minios.0.6.0 on 4.08 had its build status changed: passing to failing
- mirage-xen-minios.0.6.0 on 4.09 had its build status changed: passing to failing
- mirage-xen-minios.0.6.0 on 4.10 had its build status changed: passing to failing
- mirage-xen-minios.0.6.0 on 4.11 had its build status changed: passing to failing
- mirage-xen-minios.0.6.0 on 4.12 had its build status changed: passing to failing
- mirage-xen-minios.0.6.0 on 4.13 had its build status changed: passing to failing
- mirage-xen-minios.0.6.0 on 4.14 had its build status changed: passing to failing
- mirage-xen-minios.0.6.0 on 5.0 had its build status changed: passing to failing
- mirage-xen-minios.0.6.0 on 5.1 is now installable. Current state is: failing
- mirage-xen-minios.0.7.0 on 4.08 had its build status changed: passing to failing
- mirage-xen-minios.0.7.0 on 4.09 had its build status changed: passing to failing
- mirage-xen-minios.0.7.0 on 4.10 had its build status changed: passing to failing
- mirage-xen-minios.0.7.0 on 4.11 had its build status changed: passing to failing
- mirage-xen-minios.0.7.0 on 4.12 had its build status changed: passing to failing
- mirage-xen-minios.0.7.0 on 4.13 had its build status changed: passing to failing
- mirage-xen-minios.0.7.0 on 4.14 had its build status changed: passing to failing
- mirage-xen-minios.0.7.0 on 5.0 had its build status changed: passing to failing
- mirage-xen-minios.0.7.0 on 5.1 is now installable. Current state is: failing
- msat.0.5 on 4.08 had its build status changed: passing to failing
- msat.0.5 on 4.09 had its build status changed: passing to failing
- msat.0.5 on 4.10 had its build status changed: passing to failing
- msat.0.5 on 4.11 had its build status changed: passing to failing
- msat.0.5 on 4.12 had its build status changed: passing to failing
- msat.0.5 on 4.13 had its build status changed: passing to failing
- msat.0.5 on 4.14 had its build status changed: passing to failing
- msat.0.5.1 on 4.08 had its build status changed: passing to failing
- msat.0.5.1 on 4.09 had its build status changed: passing to failing
- msat.0.5.1 on 4.10 had its build status changed: passing to failing
- msat.0.5.1 on 4.11 had its build status changed: passing to failing
- msat.0.5.1 on 4.12 had its build status changed: passing to failing
- msat.0.5.1 on 4.13 had its build status changed: passing to failing
- msat.0.5.1 on 4.14 had its build status changed: passing to failing
- msat.0.6 on 4.08 had its build status changed: passing to failing
- msat.0.6 on 4.09 had its build status changed: passing to failing
- msat.0.6 on 4.10 had its build status changed: passing to failing
- msat.0.6 on 4.11 had its build status changed: passing to failing
- msat.0.6 on 4.12 had its build status changed: passing to failing
- msat.0.6 on 4.13 had its build status changed: passing to failing
- msat.0.6 on 4.14 had its build status changed: passing to failing
- obuild.0.1.10 on 4.08 had its build status changed: passing to failing
- obuild.0.1.10 on 4.09 had its build status changed: passing to failing
- obuild.0.1.10 on 4.10 had its build status changed: passing to failing
- obuild.0.1.10 on 4.11 had its build status changed: passing to failing
- obuild.0.1.10 on 4.12 had its build status changed: passing to failing
- obuild.0.1.10 on 4.13 had its build status changed: passing to failing
- obuild.0.1.10 on 4.14 had its build status changed: passing to failing
- obuild.0.1.11 on 4.08 is now installable. Current state is: failing
- obuild.0.1.11 on 4.09 is now installable. Current state is: failing
- obuild.0.1.11 on 4.10 is now installable. Current state is: failing
- obuild.0.1.11 on 4.11 is now installable. Current state is: failing
- obuild.0.1.11 on 4.12 is now installable. Current state is: failing
- obuild.0.1.11 on 4.13 is now installable. Current state is: failing
- obuild.0.1.11 on 4.14 is now installable. Current state is: failing
- obuild.0.1.11 on 5.0 is now installable. Current state is: failing
- obuild.0.1.11 on 5.1 is now installable. Current state is: failing
- obuild.0.1.9 on 4.08 had its build status changed: passing to failing
- obuild.0.1.9 on 4.09 had its build status changed: passing to failing
- obuild.0.1.9 on 4.10 had its build status changed: passing to failing
- obuild.0.1.9 on 4.11 had its build status changed: passing to failing
- obuild.0.1.9 on 4.12 had its build status changed: passing to failing
- obuild.0.1.9 on 4.13 had its build status changed: passing to failing
- obuild.0.1.9 on 4.14 had its build status changed: passing to failing
- ocaml-makefile.6.37.0 on 5.1 is now installable. Current state is: failing
- ocaml-makefile.6.38.0 on 5.1 is now installable. Current state is: failing
- ocaml-makefile.6.39.0 on 5.1 is now installable. Current state is: failing
- ocamldiff.1.1 on 5.1 is now installable. Current state is: failing
- ocamlformat-rpc.0.18.0 on 4.08 had its build status changed: passing to failing
- ocamlformat-rpc.0.18.0 on 4.09 had its build status changed: passing to failing
- ocamlformat-rpc.0.18.0 on 4.10 had its build status changed: passing to failing
- ocamlformat-rpc.0.18.0 on 4.11 had its build status changed: passing to failing
- ocamlformat-rpc.0.18.0 on 4.12 had its build status changed: passing to failing
- ocamlnet.4.1.6 on 4.08 had its build status changed: passing to failing
- ocamlnet.4.1.6 on 4.09 had its build status changed: passing to failing
- ocamlnet.4.1.7 on 4.08 had its build status changed: passing to failing
- ocamlnet.4.1.7 on 4.09 had its build status changed: passing to failing
- ocamlnet.4.1.7 on 4.10 had its build status changed: passing to failing
- ocamlnet.4.1.8 on 4.08 had its build status changed: passing to failing
- ocamlnet.4.1.8 on 4.09 had its build status changed: passing to failing
- ocamlnet.4.1.8 on 4.10 had its build status changed: passing to failing
- ocamlnet.4.1.8 on 4.11 had its build status changed: passing to failing
- ocamlnet.4.1.8 on 4.12 had its build status changed: passing to failing
- ocamlnet.4.1.8 on 4.13 had its build status changed: passing to failing
- ocamlnet.4.1.8 on 4.14 had its build status changed: passing to failing
- ocamlnet.4.1.9 on 4.08 had its build status changed: passing to failing
- ocamlnet.4.1.9 on 4.09 had its build status changed: passing to failing
- ocamlnet.4.1.9 on 4.10 had its build status changed: passing to failing
- ocamlnet.4.1.9 on 4.11 had its build status changed: passing to failing
- ocamlnet.4.1.9 on 4.12 had its build status changed: passing to failing
- ocamlnet.4.1.9 on 4.13 had its build status changed: passing to failing
- ocamlnet.4.1.9 on 4.14 had its build status changed: passing to failing
- ocamlnet.4.1.9-1 on 4.08 had its build status changed: passing to failing
- ocamlnet.4.1.9-1 on 4.09 had its build status changed: passing to failing
- ocamlnet.4.1.9-1 on 4.10 had its build status changed: passing to failing
- ocamlnet.4.1.9-1 on 4.11 had its build status changed: passing to failing
- ocamlnet.4.1.9-1 on 4.12 had its build status changed: passing to failing
- ocamlnet.4.1.9-1 on 4.13 had its build status changed: passing to failing
- ocamlnet.4.1.9-1 on 4.14 had its build status changed: passing to failing
- ocamlnet.4.1.9-2 on 4.08 had its build status changed: passing to failing
- ocamlnet.4.1.9-2 on 4.09 had its build status changed: passing to failing
- ocamlnet.4.1.9-2 on 4.10 had its build status changed: passing to failing
- ocamlnet.4.1.9-2 on 4.11 had its build status changed: passing to failing
- ocamlnet.4.1.9-2 on 4.12 had its build status changed: passing to failing
- ocamlnet.4.1.9-2 on 4.13 had its build status changed: passing to failing
- ocamlnet.4.1.9-2 on 4.14 had its build status changed: passing to failing
- ocamlrss.2.0 on 4.08 had its build status changed: passing to failing
- ocamlrss.2.0 on 4.09 had its build status changed: passing to failing
- ocamlrss.2.0 on 4.10 had its build status changed: passing to failing
- ocamlrss.2.0 on 4.11 had its build status changed: passing to failing
- ocamlrss.2.0 on 4.12 had its build status changed: passing to failing
- ocamlrss.2.0 on 4.13 had its build status changed: passing to failing
- ocamlrss.2.0 on 4.14 had its build status changed: passing to failing
- ocp-pack-split.1.0.1 on 5.1 is now installable. Current state is: failing
- ocplib-simplex.0.3 on 5.1 is now installable. Current state is: failing
- ott.0.27 on 4.08 had its build status changed: passing to failing
- ott.0.27 on 4.09 had its build status changed: passing to failing
- ott.0.27 on 4.10 had its build status changed: passing to failing
- ott.0.27 on 4.11 had its build status changed: passing to failing
- ott.0.27 on 4.12 had its build status changed: passing to failing
- ott.0.27 on 4.13 had its build status changed: passing to failing
- ott.0.27 on 4.14 had its build status changed: passing to failing
- ott.0.31 on 4.08 had its build status changed: passing to failing
- ott.0.31 on 4.09 had its build status changed: passing to failing
- ott.0.31 on 4.10 had its build status changed: passing to failing
- ott.0.31 on 4.11 had its build status changed: passing to failing
- ott.0.31 on 4.12 had its build status changed: passing to failing
- ott.0.31 on 4.13 had its build status changed: passing to failing
- ott.0.31 on 4.14 had its build status changed: passing to failing
- ott.0.32 on 4.08 is now installable. Current state is: failing
- ott.0.32 on 4.09 is now installable. Current state is: failing
- ott.0.32 on 4.10 is now installable. Current state is: failing
- ott.0.32 on 4.11 is now installable. Current state is: failing
- ott.0.32 on 4.12 is now installable. Current state is: failing
- ott.0.32 on 4.13 is now installable. Current state is: failing
- ott.0.32 on 4.14 is now installable. Current state is: 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
- rml.1.09.06 on 5.1 is now installable. Current state is: failing
- rml.1.09.07 on 5.1 is now installable. Current state is: failing
- 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
- sail_sv_backend.0.17.1 on 4.08 is now installable. Current state is: 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 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.5 on 5.0 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.5 on 5.1 is now installable. Current state is: failing
- solo5-bindings-hvt.0.6.6 on 4.08 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.6 on 4.09 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.6 on 4.10 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.6 on 4.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 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.6 on 5.0 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.6 on 5.1 is now installable. Current state is: failing
- solo5-bindings-hvt.0.6.7 on 4.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 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.7 on 5.0 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.7 on 5.1 is now installable. Current state is: failing
- solo5-bindings-hvt.0.6.8 on 4.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 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.8 on 5.0 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.8 on 5.1 is now installable. Current state is: failing
- solo5-bindings-hvt.0.6.9 on 4.08 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.9 on 4.09 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.9 on 4.10 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.9 on 4.11 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.9 on 4.12 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.9 on 4.13 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.9 on 4.14 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.9 on 5.0 had its build status changed: passing to failing
- solo5-bindings-hvt.0.6.9 on 5.1 is now installable. Current state is: failing
- solo5-bindings-muen.0.6.5 on 4.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 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.5 on 5.0 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.5 on 5.1 is now installable. Current state is: failing
- solo5-bindings-muen.0.6.6 on 4.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 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.6 on 5.0 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.6 on 5.1 is now installable. Current state is: failing
- solo5-bindings-muen.0.6.7 on 4.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 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.7 on 5.0 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.7 on 5.1 is now installable. Current state is: failing
- solo5-bindings-muen.0.6.8 on 4.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 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.8 on 5.0 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.8 on 5.1 is now installable. Current state is: failing
- solo5-bindings-muen.0.6.9 on 4.08 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.9 on 4.09 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.9 on 4.10 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.9 on 4.11 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.9 on 4.12 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.9 on 4.13 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.9 on 4.14 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.9 on 5.0 had its build status changed: passing to failing
- solo5-bindings-muen.0.6.9 on 5.1 is now installable. Current state is: failing
- solo5-bindings-spt.0.6.5 on 4.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 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.5 on 5.0 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.5 on 5.1 is now installable. Current state is: failing
- solo5-bindings-spt.0.6.6 on 4.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 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.6 on 5.0 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.6 on 5.1 is now installable. Current state is: failing
- solo5-bindings-spt.0.6.7 on 4.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 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.7 on 5.0 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.7 on 5.1 is now installable. Current state is: failing
- solo5-bindings-spt.0.6.8 on 4.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 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.8 on 5.0 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.8 on 5.1 is now installable. Current state is: failing
- solo5-bindings-spt.0.6.9 on 4.08 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.9 on 4.09 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.9 on 4.10 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.9 on 4.11 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.9 on 4.12 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.9 on 4.13 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.9 on 4.14 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.9 on 5.0 had its build status changed: passing to failing
- solo5-bindings-spt.0.6.9 on 5.1 is now installable. Current state is: failing
- solo5-bindings-virtio.0.6.5 on 4.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 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.5 on 5.0 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.5 on 5.1 is now installable. Current state is: failing
- solo5-bindings-virtio.0.6.6 on 4.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 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.6 on 5.0 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.6 on 5.1 is now installable. Current state is: failing
- solo5-bindings-virtio.0.6.7 on 4.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 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.7 on 5.0 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.7 on 5.1 is now installable. Current state is: failing
- solo5-bindings-virtio.0.6.8 on 4.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 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.8 on 5.0 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.8 on 5.1 is now installable. Current state is: failing
- solo5-bindings-virtio.0.6.9 on 4.08 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.9 on 4.09 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.9 on 4.10 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.9 on 4.11 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.9 on 4.12 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.9 on 4.13 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.9 on 4.14 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.9 on 5.0 had its build status changed: passing to failing
- solo5-bindings-virtio.0.6.9 on 5.1 is now installable. Current state is: failing
- solo5-bindings-xen.0.6.6 on 4.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 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.6 on 5.0 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.6 on 5.1 is now installable. Current state is: failing
- solo5-bindings-xen.0.6.7 on 4.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 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.7 on 5.0 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.7 on 5.1 is now installable. Current state is: failing
- solo5-bindings-xen.0.6.8 on 4.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 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.8 on 5.0 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.8 on 5.1 is now installable. Current state is: failing
- solo5-bindings-xen.0.6.9 on 4.08 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.9 on 4.09 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.9 on 4.10 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.9 on 4.11 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.9 on 4.12 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.9 on 4.13 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.9 on 4.14 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.9 on 5.0 had its build status changed: passing to failing
- solo5-bindings-xen.0.6.9 on 5.1 is now installable. Current state is: failing
- solo5.0.7.0 on 4.08 had its build status changed: passing to failing
- solo5.0.7.0 on 4.09 had its build status changed: passing to failing
- solo5.0.7.0 on 4.10 had its build status changed: passing to failing
- solo5.0.7.0 on 4.11 had its build status changed: passing to failing
- solo5.0.7.0 on 4.12 had its build status changed: passing to failing
- solo5.0.7.0 on 4.13 had its build status changed: passing to failing
- solo5.0.7.0 on 4.14 had its build status changed: passing to failing
- solo5.0.7.0 on 5.0 had its build status changed: passing to failing
- solo5.0.7.0 on 5.1 is now installable. Current state is: failing
- solo5.0.7.1 on 4.08 is now installable. Current state is: failing
- solo5.0.7.1 on 4.09 is now installable. Current state is: failing
- solo5.0.7.1 on 4.10 is now installable. Current state is: failing
- solo5.0.7.1 on 4.11 is now installable. Current state is: failing
- solo5.0.7.1 on 4.12 is now installable. Current state is: failing
- solo5.0.7.1 on 4.13 is now installable. Current state is: failing
- solo5.0.7.1 on 4.14 is now installable. Current state is: failing
- solo5.0.7.1 on 5.0 is now installable. Current state is: failing
- solo5.0.7.1 on 5.1 is now installable. Current state is: failing
- statverif.1.97pl1.1 on 4.08 had its build status changed: passing to failing
- statverif.1.97pl1.1 on 4.09 had its build status changed: passing to failing
- statverif.1.97pl1.1 on 4.10 had its build status changed: passing to failing
- statverif.1.97pl1.1 on 4.11 had its build status changed: passing to failing
- statverif.1.97pl1.1 on 4.12 had its build status changed: passing to failing
- statverif.1.97pl1.1 on 4.13 had its build status changed: passing to failing
- statverif.1.97pl1.1 on 4.14 had its build status changed: passing to failing
- statverif.1.97pl1.2 on 4.08 had its build status changed: passing to failing
- statverif.1.97pl1.2 on 4.09 had its build status changed: passing to failing
- statverif.1.97pl1.2 on 4.10 had its build status changed: passing to failing
- statverif.1.97pl1.2 on 4.11 had its build status changed: passing to failing
- statverif.1.97pl1.2 on 4.12 had its build status changed: passing to failing
- statverif.1.97pl1.2 on 4.13 had its build status changed: passing to failing
- statverif.1.97pl1.2 on 4.14 had its build status changed: passing to failing
- stdcompat.10 on 4.08 had its build status changed: passing to failing
- stdcompat.10 on 4.09 had its build status changed: passing to failing
- stdcompat.11 on 4.08 had its build status changed: passing to failing
- stdcompat.11 on 4.09 had its build status changed: passing to failing
- stdcompat.12 on 4.08 had its build status changed: passing to failing
- stdcompat.12 on 4.09 had its build status changed: passing to failing
- stdcompat.12 on 4.10 had its build status changed: passing to failing
- stdcompat.13 on 4.08 had its build status changed: passing to failing
- stdcompat.13 on 4.09 had its build status changed: passing to failing
- stdcompat.13 on 4.10 had its build status changed: passing to failing
- stdcompat.14 on 4.08 had its build status changed: passing to failing
- stdcompat.14 on 4.09 had its build status changed: passing to failing
- stdcompat.14 on 4.10 had its build status changed: passing to failing
- stdcompat.14 on 4.11 had its build status changed: passing to failing
- stdcompat.15 on 4.08 had its build status changed: passing to failing
- stdcompat.15 on 4.09 had its build status changed: passing to failing
- stdcompat.15 on 4.10 had its build status changed: passing to failing
- stdcompat.15 on 4.11 had its build status changed: passing to failing
- stdcompat.15 on 4.12 had its build status changed: passing to failing
- stdcompat.15 on 4.13 had its build status changed: passing to failing
- stdcompat.15 on 4.14 had its build status changed: passing to failing
- stdcompat.16 on 4.08 had its build status changed: passing to failing
- stdcompat.16 on 4.09 had its build status changed: passing to failing
- stdcompat.16 on 4.10 had its build status changed: passing to failing
- stdcompat.16 on 4.11 had its build status changed: passing to failing
- stdcompat.16 on 4.12 had its build status changed: passing to failing
- stdcompat.16 on 4.13 had its build status changed: passing to failing
- stdcompat.16 on 4.14 had its build status changed: passing to failing
- stdcompat.17 on 4.08 had its build status changed: passing to failing
- stdcompat.17 on 4.09 had its build status changed: passing to failing
- stdcompat.17 on 4.10 had its build status changed: passing to failing
- stdcompat.17 on 4.11 had its build status changed: passing to failing
- stdcompat.17 on 4.12 had its build status changed: passing to failing
- stdcompat.17 on 4.13 had its build status changed: passing to failing
- stdcompat.17 on 4.14 had its build status changed: passing to failing
- stdcompat.18 on 4.08 is now installable. Current state is: failing
- stdcompat.18 on 4.09 is now installable. Current state is: failing
- stdcompat.18 on 4.10 is now installable. Current state is: failing
- stdcompat.18 on 4.11 is now installable. Current state is: failing
- stdcompat.18 on 4.12 is now installable. Current state is: failing
- stdcompat.18 on 4.13 is now installable. Current state is: failing
- stdcompat.18 on 4.14 is now installable. Current state is: failing
- stdcompat.7 on 4.08 had its build status changed: passing to failing
- stdcompat.9 on 4.08 had its build status changed: passing to failing
- sundialsml.5.8.0p0 on 4.08 had its build status changed: passing to failing
- sundialsml.5.8.0p0 on 4.09 had its build status changed: passing to failing
- sundialsml.5.8.0p0 on 4.10 had its build status changed: passing to failing
- sundialsml.5.8.0p0 on 4.11 had its build status changed: passing to failing
- sundialsml.5.8.0p0 on 4.12 had its build status changed: passing to failing
- sundialsml.5.8.0p0 on 4.13 had its build status changed: passing to failing
- sundialsml.6.0.0p0 on 4.08 had its build status changed: passing to failing
- sundialsml.6.0.0p0 on 4.09 had its build status changed: passing to failing
- sundialsml.6.0.0p0 on 4.10 had its build status changed: passing to failing
- sundialsml.6.0.0p0 on 4.11 had its build status changed: passing to failing
- sundialsml.6.0.0p0 on 4.12 had its build status changed: passing to failing
- sundialsml.6.0.0p0 on 4.13 had its build status changed: passing to failing
- sundialsml.6.1.0p0 on 4.08 had its build status changed: passing to failing
- sundialsml.6.1.0p0 on 4.09 had its build status changed: passing to failing
- sundialsml.6.1.0p0 on 4.10 had its build status changed: passing to failing
- sundialsml.6.1.0p0 on 4.11 had its build status changed: passing to failing
- sundialsml.6.1.0p0 on 4.12 had its build status changed: passing to failing
- sundialsml.6.1.0p0 on 4.13 had its build status changed: passing to failing
- sundialsml.6.1.1p0 on 4.08 is now installable. Current state is: failing
- sundialsml.6.1.1p0 on 4.09 is now installable. Current state is: failing
- sundialsml.6.1.1p0 on 4.10 is now installable. Current state is: failing
- sundialsml.6.1.1p0 on 4.11 is now installable. Current state is: failing
- sundialsml.6.1.1p0 on 4.12 is now installable. Current state is: failing
- sundialsml.6.1.1p0 on 4.13 is now installable. Current state is: failing
- sundialsml.6.1.1p1 on 4.08 is now installable. Current state is: failing
- sundialsml.6.1.1p1 on 4.09 is now installable. Current state is: failing
- sundialsml.6.1.1p1 on 4.10 is now installable. Current state is: failing
- sundialsml.6.1.1p1 on 4.11 is now installable. Current state is: failing
- sundialsml.6.1.1p1 on 4.12 is now installable. Current state is: failing
- sundialsml.6.1.1p1 on 4.13 is now installable. Current state is: failing
- sundialsml.6.1.1p1 on 4.14 is now installable. Current state is: failing
- topiary.0.2.0 on 4.12 is now installable. Current state is: failing
- topiary.0.2.0 on 5.0 is now installable. Current state is: failing
- topiary.0.2.0 on 5.1 is now installable. Current state is: failing
- topiary.0.2.1 on 5.1 is now installable. Current state is: failing
- topiary.0.2.3 on 4.10 is now installable. Current state is: failing
- tplib.1.3 on 5.0 had its build status changed: partially failing to failing
- tplib.1.3 on 5.1 is now installable. Current state is: failing
- tuareg.2.0.10 on 4.08 had its build status changed: passing to failing
- tuareg.2.0.10 on 4.09 had its build status changed: passing to failing
- tuareg.2.0.10 on 4.10 had its build status changed: passing to failing
- tuareg.2.0.10 on 4.11 had its build status changed: passing to failing
- tuareg.2.0.10 on 4.12 had its build status changed: passing to failing
- tuareg.2.0.10 on 4.13 had its build status changed: passing to failing
- tuareg.2.0.10 on 4.14 had its build status changed: passing to failing
- tuareg.2.0.10 on 5.0 had its build status changed: passing to failing
- tuareg.2.0.10 on 5.1 is now installable. Current state is: failing
- tuareg.2.0.7 on 4.08 had its build status changed: passing to failing
- tuareg.2.0.7 on 4.09 had its build status changed: passing to failing
- tuareg.2.0.7 on 4.10 had its build status changed: passing to failing
- tuareg.2.0.7 on 4.11 had its build status changed: passing to failing
- tuareg.2.0.7 on 4.12 had its build status changed: passing to failing
- tuareg.2.0.7 on 4.13 had its build status changed: passing to failing
- tuareg.2.0.7 on 4.14 had its build status changed: passing to failing
- tuareg.2.0.7 on 5.0 had its build status changed: passing to failing
- tuareg.2.0.7 on 5.1 is now installable. Current state is: failing
- tuareg.2.1.0 on 4.10 had its build status changed: passing to failing
- tuareg.2.1.0 on 4.11 had its build status changed: passing to failing
- tuareg.2.2.0 on 4.08 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.13 is now installable. Current state is: failing
- z3.4.10.1 on 5.0 is now installable. Current state is: failing
- z3.4.10.2 on 4.08 is now installable. Current state is: failing
- z3.4.10.2 on 5.0 is now installable. Current state is: failing
- z3.4.11.0 on 4.14 is now installable. Current state is: failing
- z3.4.12.2 on 4.08 is now installable. Current state is: failing
- z3.4.12.2 on 4.09 is now installable. Current state is: failing
- z3.4.12.2 on 4.10 is now installable. Current state is: failing
- z3.4.12.2 on 4.11 is now installable. Current state is: failing
- z3.4.12.2 on 4.12 is now installable. Current state is: failing
- z3.4.12.2 on 4.13 is now installable. Current state is: failing
- z3.4.12.2 on 4.14 is now installable. Current state is: failing
- z3.4.12.2 on 5.0 is now installable. Current state is: failing
- z3.4.12.2 on 5.1 is now installable. Current state is: failing
- z3.4.8.14 on 5.0 had its build status changed: passing to failing
- z3.4.8.14 on 5.1 is now installable. Current state is: failing
- z3.4.8.17 on 5.1 is now installable. Current state is: failing
- z3.4.9.1 on 4.08 is now installable. Current state is: failing
Packages now partially failing:
Home|Differences with the last checks|Previous runs