Home|Differences with the last checks|Previous runs

Differences between a221535 and 86961ac (git diff)

Packages now failing:

• acgtk.1.5.1 on 5.1 is now installable. Current state is: 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.14 is now installable. Current state is: failing
• ahrocksdb.0.2.2 on 5.0 is now installable. Current state is: failing
• ahrocksdb.0.2.2 on 5.1 is now installable. Current state is: failing
• alt-ergo-free.2.0.0 on 4.08 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.10 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.11 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.12 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.14 is now installable. Current state is: 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.14 is now installable. Current state is: failing
• alt-ergo.2.0.0 on 4.10 had its build status changed: passing to failing
• alt-ergo.2.0.0 on 4.11 had its build status changed: passing to failing
• alt-ergo.2.0.0 on 4.14 is now installable. Current state is: failing
• alt-ergo.2.1.0 on 4.08 had its build status changed: passing to failing
• alt-ergo.2.1.0 on 4.09 had its build status changed: passing to failing
• alt-ergo.2.1.0 on 4.10 had its build status changed: passing to failing
• alt-ergo.2.1.0 on 4.11 had its build status changed: passing to failing
• alt-ergo.2.1.0 on 4.12 had its build status changed: passing to failing
• alt-ergo.2.1.0 on 4.14 is now installable. Current state is: failing
• alt-ergo.2.2.0 on 4.08 had its build status changed: passing to failing
• alt-ergo.2.2.0 on 4.09 had its build status changed: passing to failing
• alt-ergo.2.2.0 on 4.10 had its build status changed: passing to failing
• alt-ergo.2.2.0 on 4.11 had its build status changed: passing to failing
• alt-ergo.2.2.0 on 4.12 had its build status changed: passing to failing
• b0.0.0.2 on 5.1 is now installable. Current state is: failing
• b0.0.0.3 on 5.1 is now installable. Current state is: failing
• b0.0.0.4 on 5.1 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.08 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.09 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.10 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.11 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.12 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.14 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.08 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.09 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.10 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.11 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.12 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.14 is now installable. Current state is: failing
• batteries.3.6.0 on 5.1 is now installable. Current state is: failing
• bitmasks.1.4.0 on 5.1 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.14 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 5.0 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 5.1 is now installable. Current state is: failing
• blake3.0.1 on 4.09 had its build status changed: passing to failing
• blake3.0.1 on 4.10 had its build status changed: passing to failing
• blake3.0.1 on 4.11 had its build status changed: passing to failing
• blake3.0.1 on 4.12 had its build status changed: passing to failing
• blake3.0.1 on 4.14 is now installable. Current state is: failing
• blake3.0.1 on 5.0 is now installable. Current state is: failing
• blake3.0.1 on 5.1 is now installable. Current state is: failing
• calculon.0.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.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
• camllib.1.3.3 on 5.0 is now installable. Current state is: failing
• camllib.1.3.3 on 5.1 is now installable. Current state is: failing
• camlmix.1.3.0 on 5.0 is now installable. Current state is: failing
• camlmix.1.3.0 on 5.1 is now installable. Current state is: failing
• cca.0.1 on 4.11 is now installable. Current state is: failing
• cca.0.1 on 4.12 is now installable. Current state is: failing
• cca.0.2 on 4.11 is now installable. Current state is: failing
• cca.0.2 on 4.12 is now installable. Current state is: failing
• cca.0.2 on 4.14 is now installable. Current state is: failing
• cca.0.4 on 4.12 is now installable. Current state is: failing
• cca.0.4 on 4.14 is now installable. Current state is: failing
• cca.0.5 on 4.11 is now installable. Current state is: failing
• cca.0.5 on 4.12 is now installable. Current state is: failing
• cca.0.5 on 4.14 is now installable. Current state is: failing
• cca.0.6.2 on 4.14 is now installable. Current state is: failing
• charrua-unix.1.0.0 on 4.08 had its build status changed: passing to failing
• charrua-unix.1.0.0 on 4.09 had its build status changed: passing to failing
• charrua-unix.1.0.0 on 4.10 had its build status changed: passing to failing
• charrua-unix.1.0.0 on 4.11 had its build status changed: passing to failing
• charset.0.1.0 on 5.1 is now installable. Current state is: failing
• 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
• conan.0.0.3 on 5.1 is now installable. Current state is: 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.14 is now installable. Current state is: failing
• conf-libclang.12 on 5.0 is now installable. Current state is: failing
• conf-libclang.12 on 5.1 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.08 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.09 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.10 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.11 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.12 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.14 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 5.0 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 5.1 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.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.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
• config-file.1.1 on 4.09 had its build status changed: passing to failing
• core.v0.15.1 on 5.1 is now installable. Current state is: failing
• core.v0.16.0 on 5.1 is now installable. Current state is: failing
• datakit-client-9p.0.12.0 on 4.12 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.08 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.09 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.10 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.11 had its build status changed: passing to failing
• datakit-client-9p.0.12.2 on 4.12 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.08 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.09 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.10 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.11 had its build status changed: passing to failing
• datakit-client-9p.0.12.3 on 4.12 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.08 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.09 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.10 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.11 had its build status changed: passing to failing
• datakit-client-9p.1.0.0 on 4.12 had its build status changed: passing to failing
• 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
• 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.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.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
• distributed.0.6.0 on 5.0 is now installable. Current state is: failing
• distributed.0.6.0 on 5.1 is now installable. Current state is: failing
• docker-api.0.2 on 5.0 is now installable. Current state is: failing
• docker-api.0.2 on 5.1 is now installable. Current state is: failing
• docker-api.0.2.1 on 5.0 is now installable. Current state is: failing
• docker-api.0.2.1 on 5.1 is now installable. Current state is: failing
• docker-api.0.2.2 on 5.0 is now installable. Current state is: failing
• docker-api.0.2.2 on 5.1 is now installable. Current state is: failing
• dolmen.0.1 on 5.0 is now installable. Current state is: failing
• dolmen.0.1 on 5.1 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.1 is now installable. Current state is: failing
• domainslib.0.3.0 on 5.0 is now installable. Current state is: failing
• domainslib.0.3.0 on 5.1 is now installable. Current state is: failing
• domainslib.0.3.1 on 5.0 is now installable. Current state is: failing
• domainslib.0.3.1 on 5.1 is now installable. Current state is: failing
• domainslib.0.4.0 on 5.0 is now installable. Current state is: failing
• domainslib.0.4.0 on 5.1 is now installable. Current state is: failing
• domainslib.0.4.1 on 5.0 is now installable. Current state is: failing
• domainslib.0.4.1 on 5.1 is now installable. Current state is: failing
• duff.0.2 on 5.1 is now installable. Current state is: failing
• duff.0.3 on 5.1 is now installable. Current state is: failing
• duff.0.4 on 5.1 is now installable. Current state is: failing
• 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
• 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.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.08 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.09 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.10 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.11 had its build status changed: passing to failing
• easy_logging_yojson.0.5.2 on 4.12 had its build status changed: passing to failing
• eigen.0.1.4 on 5.1 is now installable. Current state is: failing
• eigen.0.1.5 on 5.1 is now installable. Current state is: failing
• errpy.0.0.7 on 5.1 is now installable. Current state is: failing
• errpy.0.0.8 on 5.1 is now installable. Current state is: failing
• facile.1.1 on 5.0 is now installable. Current state is: failing
• facile.1.1 on 5.1 is now installable. Current state is: failing
• fm-simplex-plugin.1.01 on 4.08 had its build status changed: passing to failing
• frama-c.22.0 on 4.08 had its build status changed: passing to failing
• frama-c.22.0 on 4.10 had its build status changed: passing to failing
• frama-c.22.0 on 4.14 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
• gadelac.0.6 on 5.0 is now installable. Current state is: failing
• gadelac.0.6 on 5.1 is now installable. Current state is: failing
• gammu.0.9.3 on 5.0 is now installable. Current state is: failing
• gammu.0.9.3 on 5.1 is now installable. Current state is: failing
• 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.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.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
• git-unix.3.2.0 on 4.08 had its build status changed: passing to failing
• git-unix.3.2.0 on 4.09 had its build status changed: passing to failing
• git-unix.3.2.0 on 4.10 had its build status changed: passing to failing
• git-unix.3.2.0 on 4.11 had its build status changed: passing to failing
• git-unix.3.2.0 on 4.12 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.08 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.09 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.10 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.11 had its build status changed: passing to failing
• git-unix.3.3.0 on 4.12 had its build status changed: passing to failing
• git-unix.3.3.1 on 4.08 is now installable. Current state is: failing
• git-unix.3.3.1 on 4.09 is now installable. Current state is: failing
• git-unix.3.3.1 on 4.10 is now installable. Current state is: failing
• git-unix.3.3.1 on 4.11 is now installable. Current state is: failing
• git-unix.3.3.1 on 4.12 is now installable. Current state is: failing
• git-unix.3.3.2 on 4.08 is now installable. Current state is: failing
• git-unix.3.3.2 on 4.09 is now installable. Current state is: failing
• git-unix.3.3.2 on 4.10 is now installable. Current state is: failing
• git-unix.3.3.2 on 4.11 is now installable. Current state is: failing
• git-unix.3.3.2 on 4.12 is now installable. Current state is: failing
• git-unix.3.3.3 on 4.08 is now installable. Current state is: failing
• git-unix.3.3.3 on 4.09 is now installable. Current state is: failing
• git-unix.3.3.3 on 4.10 is now installable. Current state is: failing
• git-unix.3.3.3 on 4.11 is now installable. Current state is: failing
• git-unix.3.3.3 on 4.12 is now installable. Current state is: 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.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.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.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.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.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