Home|Differences with the last checks|Previous runs

Differences between a221535 and 7af4b29 (git diff)

Packages now failing:

• abella.2.0.7 on 4.13 is now installable. Current state is: failing
• bulletml.0.1.0 on 4.02 had its build status changed: passing to failing
• bulletml.0.1.0 on 4.03 had its build status changed: passing to failing
• bulletml.0.1.0 on 4.04 had its build status changed: passing to failing
• bulletml.0.2.0 on 4.02 had its build status changed: passing to failing
• bulletml.0.2.0 on 4.03 had its build status changed: passing to failing
• bulletml.0.2.0 on 4.04 had its build status changed: passing to failing
• cloudi.1.8.0 on 4.13 is now installable. Current state is: failing
• cloudi.2.0.0 on 4.13 is now installable. Current state is: failing
• cloudi.2.0.1 on 4.13 is now installable. Current state is: failing
• coccinelle.1.0.0-rc24 on 4.03 had its build status changed: not available to failing
• conduit.1.0.0 on 4.05 had its build status changed: partially failing to failing
• conduit.1.0.3 on 4.05 had its build status changed: partially failing to failing
• conduit.1.1.0 on 4.05 had its build status changed: partially failing to failing
• coq-of-ocaml.2.4.1 on 4.10 is now installable. Current state is: failing
• devkit.0.5 on 4.07 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.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
• dns.4.0.0 on 4.13 is now installable. Current state is: failing
• dns.4.1.0 on 4.13 is now installable. Current state is: failing
• dns.4.2.0 on 4.13 is now installable. Current state is: failing
• dns.4.3.0 on 4.13 is now installable. Current state is: failing
• dns.4.3.1 on 4.13 is now installable. Current state is: failing
• dns.4.4.0 on 4.13 is now installable. Current state is: failing
• dns.4.4.1 on 4.13 is now installable. Current state is: failing
• dns.4.5.0 on 4.13 is now installable. Current state is: failing
• dns.4.6.0 on 4.13 is now installable. Current state is: failing
• dns.4.6.1 on 4.13 is now installable. Current state is: failing
• dns.4.6.2 on 4.13 is now installable. Current state is: failing
• dns.4.6.3 on 4.13 is now installable. Current state is: failing
• eliom.6.3.0 on 4.03 had its build status changed: passing to failing
• eliom.6.3.0 on 4.04 had its build status changed: passing to failing
• eliom.6.3.0 on 4.05 had its build status changed: passing to failing
• fat-filesystem.0.12.0 on 4.02 had its build status changed: passing to failing
• frenetic.5.0.3 on 4.05 had its build status changed: passing to failing
• frenetic.5.0.3 on 4.06 had its build status changed: passing to failing
• frenetic.5.0.3 on 4.07 had its build status changed: passing to failing
• grain_wasm_spec.0.1 on 4.13 is now installable. Current state is: failing
• h2-async.0.6.1 on 4.06 had its build status changed: passing to failing
• h2-async.0.6.1 on 4.07 had its build status changed: passing to failing
• h2-async.0.6.1 on 4.08 had its build status changed: passing to failing
• h2-async.0.6.1 on 4.09 had its build status changed: passing to failing
• h2-async.0.6.1 on 4.10 had its build status changed: passing to failing
• h2-async.0.6.1 on 4.11 had its build status changed: passing to failing
• h2-lwt.0.6.1 on 4.06 had its build status changed: passing to failing
• h2-lwt.0.6.1 on 4.07 had its build status changed: passing to failing
• h2-lwt.0.6.1 on 4.08 had its build status changed: passing to failing
• h2-lwt.0.6.1 on 4.09 had its build status changed: passing to failing
• h2-lwt.0.6.1 on 4.10 had its build status changed: passing to failing
• h2-lwt.0.6.1 on 4.11 had its build status changed: passing to failing
• h2-lwt.0.6.1 on 4.12 had its build status changed: passing to failing
• h2-lwt.0.6.1 on 4.13 is now installable. Current state is: failing
• hlarp.0.0.1 on 4.13 is now installable. Current state is: failing
• hlarp.0.0.2 on 4.13 is now installable. Current state is: failing
• jupyter.2.7.4 on 4.04 is now installable. Current state is: failing
• lablgtk3.3.1.0 on 4.13 is now installable. Current state is: failing
• labltk.8.06.10 on 4.13 is now installable. Current state is: failing
• labltk.8.06.7 on 4.13 is now installable. Current state is: failing
• labltk.8.06.8 on 4.13 is now installable. Current state is: failing
• labltk.8.06.9 on 4.13 is now installable. Current state is: failing
• linenoise.1.1.0 on 4.13 is now installable. Current state is: failing
• linenoise.1.2.0 on 4.13 is now installable. Current state is: failing
• linenoise.1.3.0 on 4.13 is now installable. Current state is: failing
• lutin.2.70.4 on 4.07 had its build status changed: partially failing to failing
• mariadb.0.5.0 on 4.03 is now installable. Current state is: failing
• mariadb.0.5.0 on 4.04 is now installable. Current state is: failing
• mariadb.0.5.0 on 4.05 is now installable. Current state is: failing
• mariadb.0.5.1 on 4.03 is now installable. Current state is: failing
• mariadb.0.5.1 on 4.04 is now installable. Current state is: failing
• mariadb.0.5.1 on 4.05 is now installable. Current state is: failing
• mariadb.0.6.0 on 4.03 is now installable. Current state is: failing
• mariadb.0.6.0 on 4.04 is now installable. Current state is: failing
• mariadb.0.6.0 on 4.05 is now installable. Current state is: failing
• mariadb.1.0.0 on 4.03 is now installable. Current state is: failing
• mariadb.1.0.0 on 4.04 is now installable. Current state is: failing
• mariadb.1.0.0 on 4.05 is now installable. Current state is: failing
• memprof-limits.0.1 on 4.13 is now installable. Current state is: failing
• mirage-block-unix.0.2.1 on 4.02 had its build status changed: passing to failing
• mirage-block-unix.1.0.0 on 4.02 had its build status changed: passing to failing
• mirage-block-unix.1.1.0 on 4.02 had its build status changed: passing to failing
• mirage-block-unix.1.2.0 on 4.02 had its build status changed: passing to failing
• mirage-block-unix.1.2.1 on 4.02 had its build status changed: passing to failing
• mirage-block-unix.1.2.2 on 4.02 had its build status changed: passing to failing
• mirage-net-unix.2.2.1 on 4.02 had its build status changed: passing to failing
• mirage-net-unix.2.2.2 on 4.02 had its build status changed: passing to failing
• mirage-net-unix.2.2.3 on 4.02 had its build status changed: passing to failing
• mlcuddidl.2.3.0 on 4.02 had its build status changed: passing to failing
• mlcuddidl.2.3.0 on 4.03 had its build status changed: passing to failing
• mlcuddidl.2.3.0 on 4.04 had its build status changed: passing to failing
• mlcuddidl.2.3.0 on 4.05 had its build status changed: passing to failing
• mlcuddidl.3.0.0 on 4.02 had its build status changed: passing to failing
• mlcuddidl.3.0.0 on 4.03 had its build status changed: passing to failing
• mlcuddidl.3.0.0 on 4.04 had its build status changed: passing to failing
• mlcuddidl.3.0.0 on 4.05 had its build status changed: passing to failing
• mlcuddidl.3.0.1 on 4.02 had its build status changed: passing to failing
• mlcuddidl.3.0.1 on 4.03 had its build status changed: passing to failing
• mlcuddidl.3.0.1 on 4.04 had its build status changed: passing to failing
• mlcuddidl.3.0.1 on 4.05 had its build status changed: passing to failing
• mqtt.0.0.2 on 4.02 had its build status changed: passing to failing
• mrmime.0.1.0 on 4.13 is now installable. Current state is: failing
• obytelib.1.1 on 4.13 is now installable. Current state is: failing
• obytelib.1.2 on 4.13 is now installable. Current state is: failing
• obytelib.1.3 on 4.13 is now installable. Current state is: failing
• obytelib.1.4 on 4.13 is now installable. Current state is: failing
• obytelib.1.5 on 4.13 is now installable. Current state is: failing
• ocamlpp.1.1 on 4.13 is now installable. Current state is: failing
• ocamlsdl2.0.02 on 4.13 is now installable. Current state is: failing
• ocamlsdl2.0.03 on 4.13 is now installable. Current state is: failing
• ocamlsdl2.0.04 on 4.13 is now installable. Current state is: failing
• ocolor.1.1 on 4.13 is now installable. Current state is: failing
• ocolor.1.2 on 4.13 is now installable. Current state is: failing
• ocolor.1.2.1 on 4.13 is now installable. Current state is: failing
• odepack.0.6.9 on 4.13 is now installable. Current state is: failing
• odepack.0.7 on 4.13 is now installable. Current state is: failing
• opam-devel.2.0.0~beta5 on 4.02 had its build status changed: passing to failing
• opam-installer.2.0.0~beta5 on 4.02 had its build status changed: passing to failing
• opam-publish.0.2.0 on 4.02 had its build status changed: partially failing to failing
• opam-publish.0.2.1 on 4.02 had its build status changed: partially failing to failing
• opam-sync-github-prs.1.0.0 on 4.02 had its build status changed: partially failing to failing
• opam2web.1.5.0 on 4.07 had its build status changed: passing to failing
• qcow-format.0.1 on 4.02 had its build status changed: passing to failing
• qcow-format.0.2 on 4.02 had its build status changed: passing to failing
• sanlock.0.0.9 on 4.13 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.02 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.03 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.04 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.05 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.06 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.07 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.08 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.09 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.10 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.11 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.12 is now installable. Current state is: failing
• sundialsml.2.5.0p0 on 4.13 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.02 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.03 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.04 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.05 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.06 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.07 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.08 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.09 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.10 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.11 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.12 is now installable. Current state is: failing
• sundialsml.2.5.0p1 on 4.13 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.02 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.03 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.04 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.05 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.06 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.07 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.08 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.09 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.10 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.11 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.12 is now installable. Current state is: failing
• sundialsml.2.5.0p2 on 4.13 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.02 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.03 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.04 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.05 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.06 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.07 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.08 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.09 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.10 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.11 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.12 is now installable. Current state is: failing
• sundialsml.2.6.2p0 on 4.13 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.02 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.03 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.04 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.05 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.06 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.07 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.08 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.09 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.10 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.11 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.12 is now installable. Current state is: failing
• sundialsml.2.6.2p1 on 4.13 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.02 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.03 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.04 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.05 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.06 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.07 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.08 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.09 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.10 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.11 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.12 is now installable. Current state is: failing
• sundialsml.2.7.0p0 on 4.13 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.02 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.03 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.04 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.05 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.06 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.07 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.08 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.09 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.10 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.11 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.12 is now installable. Current state is: failing
• sundialsml.3.1.1p0 on 4.13 is now installable. Current state is: failing
• sundialsml.3.1.1p0-1 on 4.13 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.02 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.03 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.04 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.05 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.06 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.07 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.08 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.09 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.10 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.11 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.12 is now installable. Current state is: failing
• sundialsml.3.1.1p1 on 4.13 is now installable. Current state is: failing
• tuntap.1.0.0 on 4.02 had its build status changed: passing to failing
• wasm.1.0.1 on 4.13 is now installable. Current state is: failing
• wasm.1.1 on 4.13 is now installable. Current state is: failing
• wasm.1.1.1 on 4.13 is now installable. Current state is: failing

Packages now partially failing:

• DrawGrammar.0.1.0 on 4.05 had its build status changed: passing to partially failing
• DrawGrammar.0.2.0 on 4.02 had its build status changed: passing to partially failing
• DrawGrammar.0.2.0 on 4.05 had its build status changed: passing to partially failing
• aws-s3-async.3.0.0 on 4.06 had its build status changed: passing to partially failing
• bytepdf.0.1 on 4.13 is now installable. Current state is: partially failing
• calculon.0.3 on 4.02 had its build status changed: passing to partially failing
• coqide.8.10.0 on 4.05 had its build status changed: passing to partially failing
• coqide.8.10.1 on 4.05 had its build status changed: passing to partially failing
• coqide.8.10.2 on 4.05 had its build status changed: passing to partially failing
• coqide.8.11.0 on 4.05 had its build status changed: passing to partially failing
• coqide.8.11.1 on 4.05 had its build status changed: passing to partially failing
• coqide.8.11.2 on 4.05 had its build status changed: passing to partially failing
• coqide.8.12.0 on 4.05 had its build status changed: passing to partially failing
• coqide.8.12.1 on 4.05 had its build status changed: passing to partially failing
• coqide.8.12.2 on 4.05 had its build status changed: passing to partially failing
• coqide.8.13.0 on 4.05 had its build status changed: passing to partially failing
• coqide.8.13.1 on 4.05 had its build status changed: passing to partially failing
• coqide.8.13.2 on 4.05 is now installable. Current state is: partially failing
• dns-client.4.0.0 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.1.0 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.2.0 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.3.0 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.3.1 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.4.0 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.4.1 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.5.0 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.6.0 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.6.1 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.6.2 on 4.13 is now installable. Current state is: partially failing
• dns-client.4.6.3 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.0.0 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.1.0 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.2.0 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.3.0 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.3.1 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.4.0 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.4.1 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.5.0 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.6.0 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.6.1 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.6.2 on 4.13 is now installable. Current state is: partially failing
• dns-mirage.4.6.3 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.0.0 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.1.0 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.2.0 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.3.0 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.3.1 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.4.0 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.4.1 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.5.0 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.6.0 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.6.1 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.6.2 on 4.13 is now installable. Current state is: partially failing
• dns-resolver.4.6.3 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.0.0 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.1.0 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.2.0 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.3.0 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.3.1 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.4.0 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.4.1 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.5.0 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.6.0 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.6.1 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.6.2 on 4.13 is now installable. Current state is: partially failing
• dns-server.4.6.3 on 4.13 is now installable. Current state is: partially failing
• dns-stub.4.4.0 on 4.13 is now installable. Current state is: partially failing
• dns-stub.4.4.1 on 4.13 is now installable. Current state is: partially failing
• dns-stub.4.5.0 on 4.13 is now installable. Current state is: partially failing
• dns-stub.4.6.0 on 4.13 is now installable. Current state is: partially failing
• dns-stub.4.6.1 on 4.13 is now installable. Current state is: partially failing
• dns-stub.4.6.2 on 4.13 is now installable. Current state is: partially failing
• dns-stub.4.6.3 on 4.13 is now installable. Current state is: partially failing
• dns-tsig.4.4.0 on 4.13 is now installable. Current state is: partially failing
• dns-tsig.4.4.1 on 4.13 is now installable. Current state is: partially failing
• dns-tsig.4.5.0 on 4.13 is now installable. Current state is: partially failing
• dns-tsig.4.6.0 on 4.13 is now installable. Current state is: partially failing
• dns-tsig.4.6.1 on 4.13 is now installable. Current state is: partially failing
• dns-tsig.4.6.2 on 4.13 is now installable. Current state is: partially failing
• dns-tsig.4.6.3 on 4.13 is now installable. Current state is: partially failing
• elasticsearch-cli.0.1 on 4.03 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.1 on 4.04 is now installable. Current state is: partially failing
• gmp-freestanding.6.2.1 on 4.05 is now installable. Current state is: partially failing
• gmp-freestanding.6.2.1 on 4.06 is now installable. Current state is: partially failing
• gmp-freestanding.6.2.1 on 4.07 is now installable. Current state is: partially failing
• lablgtk3-gtkspell3.3.1.0 on 4.13 is now installable. Current state is: partially failing
• lablgtk3-sourceview3.3.1.0 on 4.13 is now installable. Current state is: partially failing
• ocamlsdl2-image.0.01 on 4.13 is now installable. Current state is: partially failing
• ocamlsdl2-ttf.0.01 on 4.13 is now installable. Current state is: partially failing
• ocamlsdl2-ttf.0.02 on 4.13 is now installable. Current state is: partially failing
• ocsigen-toolkit.1.1.0 on 4.03 had its build status changed: passing to partially failing
• ocsigen-toolkit.1.1.0 on 4.04 had its build status changed: passing to partially failing
• ocsigen-toolkit.1.1.0 on 4.05 had its build status changed: passing to partially failing
• owl-ode-sundials.0.0.7 on 4.13 is now installable. Current state is: partially failing
• owl-ode-sundials.0.0.9 on 4.13 is now installable. Current state is: partially failing
• owl-ode-sundials.0.1.0 on 4.13 is now installable. Current state is: partially failing
• owl-ode-sundials.0.2.0 on 4.13 is now installable. Current state is: partially failing
• owl-ode-sundials.0.3.0 on 4.13 is now installable. Current state is: partially failing
• owl-ode-sundials.0.4.0 on 4.13 is now installable. Current state is: partially failing
• ppx_typerep_conv.113.24.00 on 4.02 had its build status changed: passing to partially failing
• zarith-freestanding.1.12 on 4.04 is now installable. Current state is: partially failing
• zarith-freestanding.1.12 on 4.05 is now installable. Current state is: partially failing
• zarith-freestanding.1.12 on 4.06 is now installable. Current state is: partially failing
• zarith-freestanding.1.12 on 4.07 is now installable. Current state is: partially failing

Packages now not available:

• GT.0.2.0 on 4.07 is not available anymore. Previous state was: failing
• GT.0.2.0 on 4.08 is not available anymore. Previous state was: failing
• GT.0.2.0 on 4.09 is not available anymore. Previous state was: partially failing
• bddapron.2.2.5 on 4.06 had its build status changed: passing to not available
• bddapron.2.2.5 on 4.07 had its build status changed: passing to not available
• bddapron.2.2.5 on 4.08 had its build status changed: passing to not available
• nocrypto.0.5.4 on 4.02 had its build status changed: passing to not available
• nocrypto.0.5.4-1 on 4.02 had its build status changed: passing to not available
• nocrypto.0.5.4-2 on 4.02 had its build status changed: passing to not available
• obuilder.0.1 on 4.10 is not available anymore. Previous state was: passing
• obuilder.0.1 on 4.11 is not available anymore. Previous state was: passing
• obuilder.0.1 on 4.12 is not available anymore. Previous state was: passing
• obuilder.0.2 on 4.10 is not available anymore. Previous state was: passing
• obuilder.0.2 on 4.11 is not available anymore. Previous state was: passing
• obuilder.0.2 on 4.12 is not available anymore. Previous state was: passing
• ocsigenserver.2.18.0 on 4.06 had its build status changed: passing to not available
• ocsigenserver.2.18.0 on 4.07 had its build status changed: passing to not available
• pbkdf.0.3.0 on 4.02 had its build status changed: passing to not available
• pbkdf.1.0.0 on 4.02 had its build status changed: passing to not available
• plotkicadsch.0.2.0 on 4.06 had its build status changed: partially failing to not available
• plotkicadsch.0.2.0 on 4.07 had its build status changed: partially failing to not available
• plotkicadsch.0.3.0 on 4.06 had its build status changed: partially failing to not available
• plotkicadsch.0.3.0 on 4.07 had its build status changed: partially failing to not available
• text.0.6 on 4.03 had its build status changed: failing to not available
• text.0.6 on 4.04 had its build status changed: failing to not available
• text.0.6 on 4.05 had its build status changed: failing to not available
• text.0.7 on 4.03 had its build status changed: failing to not available
• text.0.7 on 4.04 had its build status changed: failing to not available
• text.0.7 on 4.05 had its build status changed: failing to not available
• text.0.7.1 on 4.03 had its build status changed: failing to not available
• text.0.7.1 on 4.04 had its build status changed: failing to not available
• text.0.7.1 on 4.05 had its build status changed: failing to not available
• tls.0.10.1 on 4.02 had its build status changed: failing to not available
• tls.0.8.0 on 4.02 had its build status changed: failing to not available
• tls.0.9.1 on 4.02 had its build status changed: failing to not available
• tls.0.9.2 on 4.02 had its build status changed: failing to not available
• tls.0.9.3 on 4.02 had its build status changed: failing to not available
• tlstunnel.0.2.0 on 4.02 had its build status changed: partially failing to not available
• uint.1.0.2 on 4.03 had its build status changed: failing to not available
• uint.1.0.2 on 4.04 had its build status changed: failing to not available
• uint.1.0.2 on 4.05 had its build status changed: failing to not available
• uint.1.0.3 on 4.03 had its build status changed: failing to not available
• uint.1.0.3 on 4.04 had its build status changed: failing to not available
• uint.1.0.3 on 4.05 had its build status changed: failing to not available
• uint.1.1.0 on 4.03 had its build status changed: failing to not available
• uint.1.1.0 on 4.04 had its build status changed: failing to not available
• uint.1.1.0 on 4.05 had its build status changed: failing to not available
• uint.1.1.1 on 4.03 had its build status changed: failing to not available
• uint.1.1.1 on 4.04 had its build status changed: failing to not available
• uint.1.1.1 on 4.05 had its build status changed: failing to not available
• uint.1.1.4 on 4.03 had its build status changed: failing to not available
• uint.1.1.4 on 4.04 had its build status changed: failing to not available
• uint.1.1.4 on 4.05 had its build status changed: failing to not available

Packages now failing with an internal failure:

• KaSim.3.5.150925 on 4.02 had its build status changed: failing to internal failure
• KaSim.3.5.150925 on 4.03 had its build status changed: failing to internal failure
• KaSim.3.5.150925 on 4.04 had its build status changed: failing to internal failure
• KaSim.3.5.150925 on 4.05 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.02 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.03 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.04 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.05 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.06 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.07 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.08 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.09 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.10 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.11 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.12 had its build status changed: failing to internal failure
• KaSim.4.0.0 on 4.13 is now installable. Current state is: internal failure
• aacplus.0.2.1 on 4.13 is now installable. Current state is: internal failure
• aacplus.0.2.2 on 4.13 is now installable. Current state is: internal failure
• ahrocksdb.0.2.0 on 4.13 is now installable. Current state is: internal failure
• ahrocksdb.0.2.1 on 4.13 is now installable. Current state is: internal failure
• ancient.0.9.0 on 4.02 had its build status changed: failing to internal failure
• bap-primus-symbolic-executor.2.2.0 on 4.08 had its build status changed: passing to internal failure
• bap-primus.1.3.0 on 4.04 had its build status changed: passing to internal failure
• bap-primus.2.2.0 on 4.08 had its build status changed: passing to internal failure
• bap-raw.2.1.0 on 4.08 had its build status changed: passing to internal failure
• bap-relocatable.1.4.0 on 4.04 had its build status changed: passing to internal failure
• bap-report.1.6.0 on 4.04 had its build status changed: passing to internal failure
• bap-signatures.2.1.0 on 4.12 had its build status changed: passing to internal failure
• bap-ssa.1.4.0 on 4.06 had its build status changed: not available to internal failure
• bap-std.1.5.0 on 4.04 had its build status changed: passing to internal failure
• bitvec-order.2.0.0 on 4.04 had its build status changed: passing to internal failure
• bsbnative.1.9.4 on 4.02 had its build status changed: failing to internal failure
• build_path_prefix_map.0.2 on 4.04 had its build status changed: passing to internal failure
• cairo.1.2.0 on 4.02 had its build status changed: failing to internal failure
• cairo.1.2.0 on 4.03 had its build status changed: failing to internal failure
• cairo.1.2.0 on 4.04 had its build status changed: failing to internal failure
• cairo.1.2.0 on 4.05 had its build status changed: failing to internal failure
• camlimages.4.1.2 on 4.02 had its build status changed: failing to internal failure
• camlimages.4.1.2 on 4.03 had its build status changed: failing to internal failure
• camlimages.4.1.2 on 4.04 had its build status changed: failing to internal failure
• camlimages.4.1.2 on 4.05 had its build status changed: failing to internal failure
• camlimages.4.2.0 on 4.02 had its build status changed: failing to internal failure
• camlimages.4.2.0 on 4.03 had its build status changed: failing to internal failure
• camlimages.4.2.0 on 4.04 had its build status changed: failing to internal failure
• camlimages.4.2.0 on 4.05 had its build status changed: failing to internal failure
• camlimages.4.2.1 on 4.02 had its build status changed: failing to internal failure
• camlimages.4.2.2 on 4.02 had its build status changed: failing to internal failure
• camlimages.4.2.2 on 4.03 had its build status changed: failing to internal failure
• camlimages.4.2.2 on 4.04 had its build status changed: failing to internal failure
• camlimages.4.2.2 on 4.05 had its build status changed: failing to internal failure
• camlimages.4.2.3 on 4.02 had its build status changed: failing to internal failure
• camlimages.4.2.3 on 4.03 had its build status changed: failing to internal failure
• camlimages.4.2.3 on 4.04 had its build status changed: failing to internal failure
• camlimages.4.2.3 on 4.05 had its build status changed: failing to internal failure
• camlimages.4.2.4 on 4.02 had its build status changed: failing to internal failure
• camlimages.4.2.4 on 4.03 had its build status changed: failing to internal failure
• camlimages.4.2.4 on 4.04 had its build status changed: failing to internal failure
• camlimages.4.2.4 on 4.05 had its build status changed: failing to internal failure
• camlimages.4.2.5 on 4.06 had its build status changed: failing to internal failure
• camlimages.4.2.6 on 4.06 had its build status changed: failing to internal failure
• camlimages.5.0.0 on 4.06 had its build status changed: failing to internal failure
• camlimages.5.0.0 on 4.07 had its build status changed: failing to internal failure
• camlimages.5.0.0 on 4.08 had its build status changed: failing to internal failure
• camlimages.5.0.0 on 4.09 had its build status changed: failing to internal failure
• camlimages.5.0.0 on 4.10 had its build status changed: failing to internal failure
• camlimages.5.0.0 on 4.11 had its build status changed: failing to internal failure
• camlon.1.0.0 on 4.03 had its build status changed: failing to internal failure
• camlon.1.0.0 on 4.04 had its build status changed: failing to internal failure
• camlon.1.0.0 on 4.05 had its build status changed: failing to internal failure
• camlon.1.0.1 on 4.03 had its build status changed: failing to internal failure
• camlon.1.0.1 on 4.04 had its build status changed: failing to internal failure
• camlon.1.0.1 on 4.05 had its build status changed: failing to internal failure
• camlon.1.0.2 on 4.03 had its build status changed: failing to internal failure
• camlon.1.0.2 on 4.04 had its build status changed: failing to internal failure
• camlon.1.0.2 on 4.05 had its build status changed: failing to internal failure
• camlon.2.0.0 on 4.03 had its build status changed: failing to internal failure
• camlon.2.0.0 on 4.04 had its build status changed: failing to internal failure
• camlon.2.0.0 on 4.05 had its build status changed: failing to internal failure
• camlon.2.0.0 on 4.06 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.03 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.04 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.05 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.06 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.07 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.08 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.09 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.10 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.11 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.12 had its build status changed: failing to internal failure
• camlon.2.0.1 on 4.13 is now installable. Current state is: internal failure
• caradoc.0.3 on 4.02 had its build status changed: failing to internal failure
• caradoc.0.3 on 4.03 had its build status changed: failing to internal failure
• caradoc.0.3 on 4.04 had its build status changed: failing to internal failure
• caradoc.0.3 on 4.05 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.02 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.03 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.04 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.05 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.06 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.07 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.08 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.09 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.10 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.11 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.12 had its build status changed: failing to internal failure
• charInfo_width.0.1.0 on 4.13 is now installable. Current state is: internal failure
• charInfo_width.1.0.0 on 4.02 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.03 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.04 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.05 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.06 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.07 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.08 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.09 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.10 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.11 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.12 had its build status changed: failing to internal failure
• charInfo_width.1.0.0 on 4.13 is now installable. Current state is: internal failure
• coccinelle.1.0.0-rc21 on 4.02 had its build status changed: failing to internal failure
• coccinelle.1.0.0-rc21 on 4.03 had its build status changed: failing to internal failure
• coccinelle.1.0.0-rc21 on 4.04 had its build status changed: failing to internal failure
• coccinelle.1.0.0-rc21 on 4.05 had its build status changed: failing to internal failure
• coccinelle.1.0.0-rc22 on 4.02 had its build status changed: failing to internal failure
• coccinelle.1.0.0-rc22 on 4.03 had its build status changed: failing to internal failure
• coccinelle.1.0.0-rc22 on 4.04 had its build status changed: failing to internal failure
• coccinelle.1.0.0-rc22 on 4.05 had its build status changed: failing to internal failure
• coccinelle.1.0.0.1 on 4.02 had its build status changed: failing to internal failure
• coccinelle.1.0.0.1 on 4.03 had its build status changed: not available to internal failure
• conf-ida.0.1 on 4.13 is now installable. Current state is: internal failure
• conf-ida.0.2 on 4.13 is now installable. Current state is: internal failure
• conf-ida.0.3 on 4.13 is now installable. Current state is: internal failure
• conf-lua.1 on 4.13 is now installable. Current state is: internal failure
• conf-openbabel.0.1 on 4.13 is now installable. Current state is: internal failure
• crypt.1.2 on 4.13 is now installable. Current state is: internal failure
• cstruct.1.6.0 on 4.02 had its build status changed: failing to internal failure
• cubicle.1.0 on 4.02 had its build status changed: failing to internal failure
• cubicle.1.0.1 on 4.02 had its build status changed: failing to internal failure
• curses.1.0.3 on 4.13 is now installable. Current state is: internal failure
• dbforge.2.0 on 4.02 had its build status changed: passing to internal failure
• dbforge.2.0 on 4.03 had its build status changed: passing to internal failure
• dbforge.2.0 on 4.04 had its build status changed: passing to internal failure
• dbforge.2.0 on 4.05 had its build status changed: passing to internal failure
• dbforge.2.0.1 on 4.02 had its build status changed: passing to internal failure
• dbforge.2.0.1 on 4.03 had its build status changed: passing to internal failure
• dbforge.2.0.1 on 4.04 had its build status changed: passing to internal failure
• dbforge.2.0.1 on 4.05 had its build status changed: passing to internal failure
• dssi.0.1.1 on 4.13 is now installable. Current state is: internal failure
• dune_watch.0.0.1 on 4.04 had its build status changed: failing to internal failure
• dune_watch.0.0.1 on 4.05 had its build status changed: failing to internal failure
• dune_watch.0.0.1 on 4.06 had its build status changed: failing to internal failure
• dune_watch.0.0.1 on 4.07 had its build status changed: failing to internal failure
• dune_watch.0.1.0 on 4.04 had its build status changed: partially failing to internal failure
• dune_watch.0.1.0 on 4.05 had its build status changed: partially failing to internal failure
• dune_watch.0.1.0 on 4.06 had its build status changed: partially failing to internal failure
• dune_watch.0.1.0 on 4.07 had its build status changed: failing to internal failure
• dune_watch.0.2.0 on 4.04 had its build status changed: partially failing to internal failure
• dune_watch.0.2.0 on 4.05 had its build status changed: partially failing to internal failure
• dune_watch.0.2.0 on 4.06 had its build status changed: partially failing to internal failure
• dune_watch.0.2.0 on 4.07 had its build status changed: partially failing to internal failure
• dyntype.0.8.3 on 4.02 had its build status changed: failing to internal failure
• dyntype.0.8.4 on 4.02 had its build status changed: failing to internal failure
• dyntype.0.8.5 on 4.02 had its build status changed: failing to internal failure
• ezjs_extension.0.1 on 4.06 had its build status changed: passing to internal failure
• ezjs_fetch.0.1 on 4.05 had its build status changed: failing to internal failure
• ezjs_fetch.0.1 on 4.06 had its build status changed: failing to internal failure
• ezjs_fetch.0.1 on 4.07 had its build status changed: failing to internal failure
• ezjs_fetch.0.1 on 4.08 had its build status changed: failing to internal failure
• ezjs_fetch.0.1 on 4.09 had its build status changed: failing to internal failure
• ezjs_fetch.0.1 on 4.10 had its build status changed: failing to internal failure
• ezjs_fetch.0.1 on 4.11 had its build status changed: failing to internal failure
• ezjs_fetch.0.1 on 4.12 had its build status changed: failing to internal failure
• facebook-sdk.0.3.1 on 4.02 had its build status changed: partially failing to internal failure
• facebook-sdk.0.3.3 on 4.02 had its build status changed: partially failing to internal failure
• facebook-sdk.0.3.4 on 4.02 had its build status changed: partially failing to internal failure
• facebook-sdk.0.3.5 on 4.02 had its build status changed: partially failing to internal failure
• fat-filesystem.0.6.0 on 4.02 had its build status changed: partially failing to internal failure
• fat-filesystem.0.6.2 on 4.02 had its build status changed: partially failing to internal failure
• fat-filesystem.0.7.0 on 4.02 had its build status changed: partially failing to internal failure
• fat-filesystem.0.8.0 on 4.02 had its build status changed: partially failing to internal failure
• fat-filesystem.0.9.0 on 4.02 had its build status changed: partially failing to internal failure
• ffmpeg.0.1.0 on 4.13 is now installable. Current state is: internal failure
• ffmpeg.0.1.1 on 4.13 is now installable. Current state is: internal failure
• ffmpeg.0.2.0 on 4.13 is now installable. Current state is: internal failure
• ffmpeg.0.2.1 on 4.13 is now installable. Current state is: internal failure
• ffmpeg.0.3.0 on 4.13 is now installable. Current state is: internal failure
• ffmpeg.0.4.0 on 4.13 is now installable. Current state is: internal failure
• ffmpeg.0.4.1 on 4.13 is now installable. Current state is: internal failure
• freetennis.0.4.8 on 4.02 had its build status changed: partially failing to internal failure
• freetennis.0.4.8 on 4.03 had its build status changed: partially failing to internal failure
• freetennis.0.4.8 on 4.04 had its build status changed: partially failing to internal failure
• freetennis.0.4.8 on 4.05 had its build status changed: partially failing to internal failure
• genet.0.6 on 4.02 had its build status changed: partially failing to internal failure
• genet.0.6 on 4.03 had its build status changed: failing to internal failure
• genet.0.6 on 4.04 had its build status changed: failing to internal failure
• genet.0.6 on 4.05 had its build status changed: failing to internal failure
• git-mirage.1.10.0 on 4.03 had its build status changed: partially failing to internal failure
• git-mirage.1.10.0 on 4.04 had its build status changed: partially failing to internal failure
• git-mirage.1.10.0 on 4.05 had its build status changed: partially failing to internal failure
• git-mirage.1.11.0 on 4.03 had its build status changed: partially failing to internal failure
• git-mirage.1.11.0 on 4.04 had its build status changed: partially failing to internal failure
• git-mirage.1.11.0 on 4.05 had its build status changed: partially failing to internal failure
• glMLite.0.03.51 on 4.02 had its build status changed: failing to internal failure
• glMLite.0.03.51 on 4.03 had its build status changed: failing to internal failure
• gles3.20160307.alpha on 4.13 is now installable. Current state is: internal failure
• glpk.0.1.6 on 4.13 is now installable. Current state is: internal failure
• glsurf.3.3 on 4.02 had its build status changed: partially failing to internal failure
• glsurf.3.3 on 4.03 had its build status changed: partially failing to internal failure
• glsurf.3.3 on 4.04 had its build status changed: partially failing to internal failure
• glsurf.3.3 on 4.05 had its build status changed: partially failing to internal failure
• glsurf.3.3.1 on 4.02 had its build status changed: partially failing to internal failure
• glsurf.3.3.1 on 4.03 had its build status changed: partially failing to internal failure
• glsurf.3.3.1 on 4.04 had its build status changed: partially failing to internal failure
• glsurf.3.3.1 on 4.05 had its build status changed: partially failing to internal failure
• goblint.1.0.0 on 4.04 had its build status changed: partially failing to internal failure
• goblint.1.0.0 on 4.05 had its build status changed: partially failing to internal failure
• goblint.1.0.0 on 4.06 had its build status changed: partially failing to internal failure
• gsl.1.18.5 on 4.13 is now installable. Current state is: internal failure
• gtktop.2.0 on 4.02 had its build status changed: passing to internal failure
• gtktop.2.0 on 4.03 had its build status changed: passing to internal failure
• gtktop.2.0 on 4.04 had its build status changed: passing to internal failure
• gtktop.2.0 on 4.05 had its build status changed: passing to internal failure
• hdfs.0.1 on 4.13 is now installable. Current state is: internal failure
• hdfs.0.3 on 4.13 is now installable. Current state is: internal failure
• higlo.0.1 on 4.02 had its build status changed: passing to internal failure
• higlo.0.1 on 4.03 had its build status changed: passing to internal failure
• higlo.0.1 on 4.04 had its build status changed: passing to internal failure
• higlo.0.1 on 4.05 had its build status changed: passing to internal failure
• higlo.0.1 on 4.06 had its build status changed: passing to internal failure
• higlo.0.1 on 4.08 had its build status changed: passing to internal failure
• higlo.0.1 on 4.11 had its build status changed: passing to internal failure
• higlo.0.1 on 4.12 had its build status changed: passing to internal failure
• higlo.0.2 on 4.02 had its build status changed: passing to internal failure
• higlo.0.2 on 4.03 had its build status changed: passing to internal failure
• higlo.0.2 on 4.04 had its build status changed: passing to internal failure
• higlo.0.2 on 4.05 had its build status changed: passing to internal failure
• higlo.0.2 on 4.09 had its build status changed: passing to internal failure
• higlo.0.2 on 4.10 had its build status changed: passing to internal failure
• higlo.0.3 on 4.02 had its build status changed: passing to internal failure
• higlo.0.3 on 4.03 had its build status changed: passing to internal failure
• higlo.0.3 on 4.04 had its build status changed: passing to internal failure
• higlo.0.3 on 4.05 had its build status changed: passing to internal failure
• higlo.0.4 on 4.02 had its build status changed: passing to internal failure
• higlo.0.4 on 4.06 had its build status changed: passing to internal failure
• higlo.0.4 on 4.11 had its build status changed: passing to internal failure
• higlo.0.5 on 4.02 had its build status changed: partially failing to internal failure
• higlo.0.5 on 4.03 had its build status changed: passing to internal failure
• higlo.0.5 on 4.04 had its build status changed: passing to internal failure
• higlo.0.5 on 4.05 had its build status changed: passing to internal failure
• higlo.0.5 on 4.06 had its build status changed: passing to internal failure
• higlo.0.5 on 4.07 had its build status changed: passing to internal failure
• higlo.0.6 on 4.02 had its build status changed: partially failing to internal failure
• imagemagick.0.34 on 4.02 had its build status changed: failing to internal failure
• imagemagick.0.34 on 4.03 had its build status changed: failing to internal failure
• imagemagick.0.34 on 4.04 had its build status changed: failing to internal failure
• imagemagick.0.34 on 4.05 had its build status changed: failing to internal failure
• imagemagick.0.34-1 on 4.02 had its build status changed: failing to internal failure
• imagemagick.0.34-1 on 4.03 had its build status changed: failing to internal failure
• imagemagick.0.34-1 on 4.04 had its build status changed: failing to internal failure
• imagemagick.0.34-1 on 4.05 had its build status changed: failing to internal failure
• irmin-mirage.1.0.0 on 4.03 had its build status changed: partially failing to internal failure
• irmin-mirage.1.0.0 on 4.04 had its build status changed: partially failing to internal failure
• irmin-mirage.1.0.0 on 4.05 had its build status changed: partially failing to internal failure
• irmin-mirage.1.2.0 on 4.03 had its build status changed: partially failing to internal failure
• irmin-mirage.1.3.0 on 4.03 had its build status changed: partially failing to internal failure
• ivy.1.2.2 on 4.02 had its build status changed: failing to internal failure
• ivy.1.2.2 on 4.03 had its build status changed: failing to internal failure
• ivy.1.2.2 on 4.04 had its build status changed: failing to internal failure
• ivy.1.2.2 on 4.05 had its build status changed: failing to internal failure
• ivy.1.3.1 on 4.02 had its build status changed: failing to internal failure
• ivy.1.3.1 on 4.03 had its build status changed: failing to internal failure
• ivy.1.3.1 on 4.04 had its build status changed: failing to internal failure
• ivy.1.3.1 on 4.05 had its build status changed: failing to internal failure
• kappa-agents.4.1.0 on 4.05 had its build status changed: failing to internal failure
• kappa-agents.4.1.0 on 4.06 had its build status changed: failing to internal failure
• kappa-agents.4.1.0 on 4.07 had its build status changed: failing to internal failure
• kappa-agents.4.1.0 on 4.08 had its build status changed: failing to internal failure
• kappa-agents.4.1.0 on 4.09 had its build status changed: failing to internal failure
• kappa-agents.4.1.0 on 4.10 had its build status changed: failing to internal failure
• kappa-agents.4.1.0 on 4.11 had its build status changed: failing to internal failure
• kappa-agents.4.1.0 on 4.12 had its build status changed: failing to internal failure
• kappa-agents.4.1.0 on 4.13 is now installable. Current state is: internal failure
• kappa-binaries.4.1.0 on 4.05 had its build status changed: failing to internal failure
• kappa-binaries.4.1.0 on 4.06 had its build status changed: failing to internal failure
• kappa-binaries.4.1.0 on 4.07 had its build status changed: failing to internal failure
• kappa-binaries.4.1.0 on 4.08 had its build status changed: failing to internal failure
• kappa-binaries.4.1.0 on 4.09 had its build status changed: failing to internal failure
• kappa-binaries.4.1.0 on 4.10 had its build status changed: failing to internal failure
• kappa-binaries.4.1.0 on 4.11 had its build status changed: failing to internal failure
• kappa-binaries.4.1.0 on 4.12 had its build status changed: failing to internal failure
• kappa-binaries.4.1.0 on 4.13 is now installable. Current state is: internal failure
• kappa-library.4.1.0 on 4.05 had its build status changed: failing to internal failure
• kappa-library.4.1.0 on 4.06 had its build status changed: failing to internal failure
• kappa-library.4.1.0 on 4.07 had its build status changed: failing to internal failure
• kappa-library.4.1.0 on 4.08 had its build status changed: failing to internal failure
• kappa-library.4.1.0 on 4.09 had its build status changed: failing to internal failure
• kappa-library.4.1.0 on 4.10 had its build status changed: failing to internal failure
• kappa-library.4.1.0 on 4.11 had its build status changed: failing to internal failure
• kappa-library.4.1.0 on 4.12 had its build status changed: failing to internal failure
• kappa-library.4.1.0 on 4.13 is now installable. Current state is: internal failure
• kappa-server.4.1.0 on 4.05 had its build status changed: failing to internal failure
• kappa-server.4.1.0 on 4.06 had its build status changed: failing to internal failure
• kappa-server.4.1.0 on 4.07 had its build status changed: failing to internal failure
• kappa-server.4.1.0 on 4.08 had its build status changed: failing to internal failure
• kappa-server.4.1.0 on 4.09 had its build status changed: failing to internal failure
• kappa-server.4.1.0 on 4.10 had its build status changed: failing to internal failure
• kappa-server.4.1.0 on 4.11 had its build status changed: failing to internal failure
• kappa-server.4.1.0 on 4.12 had its build status changed: failing to internal failure
• lablgtk.2.18.10 on 4.13 is now installable. Current state is: internal failure
• labltk.8.06.6 on 4.13 is now installable. Current state is: internal failure
• levenshtein.1.0.0 on 4.02 had its build status changed: failing to internal failure
• levenshtein.1.1.0 on 4.02 had its build status changed: failing to internal failure
• levenshtein.1.1.0 on 4.03 had its build status changed: failing to internal failure
• levenshtein.1.1.0 on 4.04 had its build status changed: failing to internal failure
• levenshtein.1.1.0 on 4.05 had its build status changed: failing to internal failure
• levenshtein.1.1.0 on 4.06 had its build status changed: failing to internal failure
• levenshtein.1.1.1 on 4.02 had its build status changed: failing to internal failure
• levenshtein.1.1.1 on 4.03 had its build status changed: failing to internal failure
• levenshtein.1.1.1 on 4.04 had its build status changed: failing to internal failure
• levenshtein.1.1.1 on 4.05 had its build status changed: failing to internal failure
• levenshtein.1.1.1 on 4.06 had its build status changed: failing to internal failure
• levenshtein.1.1.2 on 4.02 had its build status changed: failing to internal failure
• levenshtein.1.1.2 on 4.03 had its build status changed: failing to internal failure
• levenshtein.1.1.2 on 4.04 had its build status changed: failing to internal failure
• levenshtein.1.1.2 on 4.05 had its build status changed: failing to internal failure
• levenshtein.1.1.2 on 4.06 had its build status changed: failing to internal failure
• levenshtein.1.1.3 on 4.04 had its build status changed: partially failing to internal failure
• levenshtein.1.1.3 on 4.05 had its build status changed: partially failing to internal failure
• levenshtein.1.1.3 on 4.06 had its build status changed: partially failing to internal failure
• libres3.0.1 on 4.02 had its build status changed: partially failing to internal failure
• libres3.0.2 on 4.02 had its build status changed: partially failing to internal failure
• libres3.0.3 on 4.02 had its build status changed: partially failing to internal failure
• libres3.0.9 on 4.02 had its build status changed: partially failing to internal failure
• libres3.1.0 on 4.02 had its build status changed: partially failing to internal failure
• libres3.1.1 on 4.02 had its build status changed: partially failing to internal failure
• libres3.1.2 on 4.02 had its build status changed: partially failing to internal failure
• libres3.1.3 on 4.02 had its build status changed: partially failing to internal failure
• lustre-v6.1.737 on 4.02 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.03 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.04 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.05 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.06 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.07 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.08 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.09 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.10 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.11 had its build status changed: failing to internal failure
• lustre-v6.1.737 on 4.12 had its build status changed: failing to internal failure
• lustre-v6.6.101.7 on 4.06 had its build status changed: partially failing to internal failure
• lustre-v6.6.101.7 on 4.09 had its build status changed: passing to internal failure
• lustre-v6.6.101.7 on 4.10 had its build status changed: partially failing to internal failure
• lustre-v6.6.101.7 on 4.11 had its build status changed: partially failing to internal failure
• lustre-v6.6.101.7 on 4.12 had its build status changed: partially failing to internal failure
• lustre-v6.6.101.7 on 4.13 is now installable. Current state is: internal failure
• lutils.1.44 on 4.02 had its build status changed: failing to internal failure
• lutils.1.44 on 4.03 had its build status changed: failing to internal failure
• lutils.1.44 on 4.04 had its build status changed: failing to internal failure
• lutils.1.44 on 4.05 had its build status changed: failing to internal failure
• lutils.1.44 on 4.06 had its build status changed: failing to internal failure
• lutils.1.44 on 4.07 had its build status changed: failing to internal failure
• lutils.1.44 on 4.08 had its build status changed: failing to internal failure
• lutils.1.44 on 4.09 had its build status changed: failing to internal failure
• lutils.1.44 on 4.10 had its build status changed: failing to internal failure
• lutils.1.44 on 4.11 had its build status changed: failing to internal failure
• lutils.1.44 on 4.12 had its build status changed: failing to internal failure
• lutils.1.49.5 on 4.02 had its build status changed: failing to internal failure
• lutils.1.49.5 on 4.04 had its build status changed: failing to internal failure
• lutils.1.49.5 on 4.06 had its build status changed: passing to internal failure
• lutils.1.49.5 on 4.09 had its build status changed: failing to internal failure
• lutils.1.49.5 on 4.10 had its build status changed: passing to internal failure
• lutils.1.49.5 on 4.11 had its build status changed: failing to internal failure
• lutils.1.49.5 on 4.12 had its build status changed: failing to internal failure
• lutils.1.49.5 on 4.13 is now installable. Current state is: internal failure
• lutin.2.56 on 4.02 had its build status changed: failing to internal failure
• lutin.2.56 on 4.03 had its build status changed: failing to internal failure
• lutin.2.56 on 4.04 had its build status changed: failing to internal failure
• lutin.2.56 on 4.05 had its build status changed: failing to internal failure
• lutin.2.56 on 4.06 had its build status changed: failing to internal failure
• lutin.2.56 on 4.07 had its build status changed: failing to internal failure
• lutin.2.56 on 4.08 had its build status changed: failing to internal failure
• lutin.2.56 on 4.09 had its build status changed: failing to internal failure
• lutin.2.56 on 4.10 had its build status changed: failing to internal failure
• lutin.2.56 on 4.11 had its build status changed: failing to internal failure
• lutin.2.70.4 on 4.05 had its build status changed: partially failing to internal failure
• lutin.2.70.4 on 4.08 had its build status changed: partially failing to internal failure
• lutin.2.70.4 on 4.09 had its build status changed: partially failing to internal failure
• lutin.2.70.4 on 4.10 had its build status changed: partially failing to internal failure
• lutin.2.70.4 on 4.11 had its build status changed: passing to internal failure
• melt.1.4.0 on 4.02 had its build status changed: partially failing to internal failure
• melt.1.4.0 on 4.04 had its build status changed: partially failing to internal failure
• melt.1.4.0 on 4.05 had its build status changed: partially failing to internal failure
• meta_conv.1.1.5 on 4.02 had its build status changed: failing to internal failure
• minimal.1.1.0 on 4.05 had its build status changed: failing to internal failure
• minimal.1.1.0 on 4.06 had its build status changed: failing to internal failure
• minimal.1.1.0 on 4.07 had its build status changed: failing to internal failure
• mirage-git.1.6.0 on 4.02 had its build status changed: partially failing to internal failure
• mirage-git.1.6.0 on 4.03 had its build status changed: partially failing to internal failure
• mirage-git.1.6.0 on 4.04 had its build status changed: partially failing to internal failure
• mirage-git.1.6.0 on 4.05 had its build status changed: partially failing to internal failure
• mirage-http-unix.1.0.0 on 4.02 had its build status changed: partially failing to internal failure
• mirage-http.1.1.0 on 4.02 had its build status changed: failing to internal failure
• mirage-http.2.3.0 on 4.02 had its build status changed: failing to internal failure
• mirage-http.2.4.0 on 4.02 had its build status changed: failing to internal failure
• mirage-http.2.5.0 on 4.02 had its build status changed: failing to internal failure
• mirage-http.2.5.0 on 4.03 had its build status changed: failing to internal failure
• mirage-http.2.5.0 on 4.04 had its build status changed: failing to internal failure
• mirage-http.2.5.0 on 4.05 had its build status changed: failing to internal failure
• mirage-http.2.5.1 on 4.02 had its build status changed: failing to internal failure
• mirage-http.2.5.1 on 4.03 had its build status changed: failing to internal failure
• mirage-http.2.5.1 on 4.04 had its build status changed: failing to internal failure
• mirage-http.2.5.1 on 4.05 had its build status changed: failing to internal failure
• mirage-http.2.5.2 on 4.02 had its build status changed: failing to internal failure
• mirage-http.2.5.2 on 4.03 had its build status changed: failing to internal failure
• mirage-http.2.5.2 on 4.04 had its build status changed: failing to internal failure
• mirage-http.2.5.2 on 4.05 had its build status changed: failing to internal failure
• mirage-http.2.5.3 on 4.02 had its build status changed: failing to internal failure
• mirage-http.2.5.3 on 4.03 had its build status changed: failing to internal failure
• mirage-http.2.5.3 on 4.04 had its build status changed: failing to internal failure
• mirage-http.2.5.3 on 4.05 had its build status changed: failing to internal failure
• mirage-http.3.0.0 on 4.03 had its build status changed: failing to internal failure
• mirage-http.3.0.0 on 4.04 had its build status changed: failing to internal failure
• mirage-http.3.0.0 on 4.05 had its build status changed: failing to internal failure
• mirage-http.3.1.0 on 4.03 had its build status changed: failing to internal failure
• mirage-http.3.1.0 on 4.04 had its build status changed: failing to internal failure
• mirage-http.3.1.0 on 4.05 had its build status changed: failing to internal failure
• mirage-irmin.0.9.8 on 4.02 had its build status changed: partially failing to internal failure
• mirage-www.1.0.0 on 4.02 had its build status changed: partially failing to internal failure
• mirage-www.1.1.0 on 4.02 had its build status changed: partially failing to internal failure
• mlgmpidl.1.2.6 on 4.02 had its build status changed: passing to internal failure
• mlmpfr.3.1.6 on 4.13 is now installable. Current state is: internal failure
• mlmpfr.4.0.0 on 4.13 is now installable. Current state is: internal failure
• mlmpfr.4.0.1 on 4.13 is now installable. Current state is: internal failure
• mlmpfr.4.0.2 on 4.13 is now installable. Current state is: internal failure
• mlmpfr.4.0.2+dune on 4.13 is now installable. Current state is: internal failure
• mlpost.0.8.1 on 4.02 had its build status changed: partially failing to internal failure
• mlpost.0.8.2 on 4.04 had its build status changed: partially failing to internal failure
• mlpost.0.8.2 on 4.05 had its build status changed: partially failing to internal failure
• mmseg.0.1.1 on 4.02 had its build status changed: failing to internal failure
• mmseg.0.1.1 on 4.03 had its build status changed: failing to internal failure
• mmseg.0.1.1 on 4.04 had its build status changed: failing to internal failure
• mmseg.0.1.1 on 4.05 had its build status changed: failing to internal failure
• mmseg.0.1.1 on 4.06 had its build status changed: failing to internal failure
• mmseg.0.1.1 on 4.07 had its build status changed: failing to internal failure
• mmseg.0.1.1 on 4.08 had its build status changed: failing to internal failure
• mmseg.0.1.1 on 4.09 had its build status changed: failing to internal failure
• mpi.1.03 on 4.13 is now installable. Current state is: internal failure
• nebula.0.2.1 on 4.02 had its build status changed: failing to internal failure
• nebula.0.2.1 on 4.03 had its build status changed: failing to internal failure
• nebula.0.2.1 on 4.04 had its build status changed: failing to internal failure
• nebula.0.2.1 on 4.05 had its build status changed: failing to internal failure
• ocaml-r.0.0.1 on 4.02 had its build status changed: failing to internal failure
• ocaml-r.0.0.1 on 4.03 had its build status changed: failing to internal failure
• ocaml-r.0.0.1 on 4.04 had its build status changed: failing to internal failure
• ocaml-r.0.0.1 on 4.05 had its build status changed: failing to internal failure
• ocaml-top.1.1.1 on 4.02 had its build status changed: partially failing to internal failure
• ocaml-top.1.1.2 on 4.02 had its build status changed: partially failing to internal failure
• ocaml_at_p.1.0 on 4.03 had its build status changed: partially failing to internal failure
• ocaml_at_p.1.0.1 on 4.03 had its build status changed: partially failing to internal failure
• ocaml_at_p.1.1.0 on 4.03 had its build status changed: partially failing to internal failure
• ocamldiff.1.0 on 4.02 had its build status changed: passing to internal failure
• ocamldiff.1.0 on 4.03 had its build status changed: passing to internal failure
• ocamldiff.1.0 on 4.04 had its build status changed: passing to internal failure
• ocamldiff.1.0 on 4.05 had its build status changed: passing to internal failure
• ocamldot.1.0 on 4.02 had its build status changed: passing to internal failure
• ocamldot.1.0 on 4.03 had its build status changed: passing to internal failure
• ocamldot.1.0 on 4.04 had its build status changed: passing to internal failure
• ocamldot.1.0 on 4.05 had its build status changed: passing to internal failure
• ocamlrss.2.1.0 on 4.09 had its build status changed: passing to internal failure
• ocamlspot.4.02.1.2.3.0 on 4.02 had its build status changed: failing to internal failure
• ocamlspot.4.03.0.2.3.1 on 4.03 had its build status changed: failing to internal failure
• ocamlspot.4.04.0.2.3.2 on 4.04 had its build status changed: failing to internal failure
• ocamlspot.4.05.0.2.3.2 on 4.05 had its build status changed: failing to internal failure
• ocamlspot.4.06.0.2.3.2 on 4.06 had its build status changed: failing to internal failure
• ocamltter.2.1.1 on 4.02 had its build status changed: failing to internal failure
• ocamltter.2.1.2 on 4.02 had its build status changed: partially failing to internal failure
• ocamltter.3.0.0 on 4.02 had its build status changed: partially failing to internal failure
• ocamltter.4.0.2 on 4.02 had its build status changed: partially failing to internal failure
• ocamltter.4.1.0 on 4.03 had its build status changed: partially failing to internal failure
• ocamltter.4.1.0 on 4.04 had its build status changed: partially failing to internal failure
• ocamltter.4.1.1 on 4.03 had its build status changed: partially failing to internal failure
• ocamltter.4.1.1 on 4.04 had its build status changed: partially failing to internal failure
• ocamlviz.1.01 on 4.02 had its build status changed: failing to internal failure
• ocamlviz.1.01 on 4.03 had its build status changed: failing to internal failure
• ocamlviz.1.01 on 4.04 had its build status changed: failing to internal failure
• ocamlviz.1.01 on 4.05 had its build status changed: failing to internal failure
• ocamlyices.0.7.0 on 4.13 is now installable. Current state is: internal failure
• ocamlyices.0.7.1 on 4.13 is now installable. Current state is: internal failure
• ocf.0.1.0 on 4.02 had its build status changed: failing to internal failure
• ocf.0.2.0 on 4.02 had its build status changed: failing to internal failure
• ocf.0.3.0 on 4.02 had its build status changed: failing to internal failure
• ocf.0.4.0 on 4.02 had its build status changed: failing to internal failure
• ocp-build.1.99.13-beta on 4.02 had its build status changed: failing to internal failure
• ocp-build.1.99.14-beta on 4.02 had its build status changed: failing to internal failure
• ocp-build.1.99.14-beta on 4.03 had its build status changed: failing to internal failure
• ocp-build.1.99.15-beta on 4.02 had its build status changed: failing to internal failure
• ocp-build.1.99.16-beta on 4.02 had its build status changed: failing to internal failure
• ocp-build.1.99.16-beta on 4.03 had its build status changed: failing to internal failure
• ocp-build.1.99.9-beta on 4.02 had its build status changed: passing to internal failure
• ocp-manager.0.1.2 on 4.02 had its build status changed: partially failing to internal failure
• ocp-manager.0.1.3 on 4.02 had its build status changed: partially failing to internal failure
• ocsfml.2.0 on 4.13 is now installable. Current state is: internal failure
• odoc-depgraph.1.0 on 4.04 had its build status changed: passing to internal failure
• odoc-depgraph.1.0 on 4.05 had its build status changed: passing to internal failure
• ojs-base.0.1.0 on 4.02 had its build status changed: partially failing to internal failure
• ojs-base.0.3.0 on 4.02 had its build status changed: partially failing to internal failure
• ojs-base.0.4.0 on 4.02 had its build status changed: partially failing to internal failure
• oni.1.0.11 on 4.02 had its build status changed: failing to internal failure
• oni.1.0.12 on 4.03 had its build status changed: failing to internal failure
• opamfind.1.0.0 on 4.03 had its build status changed: failing to internal failure
• opamfind.1.0.0 on 4.04 had its build status changed: failing to internal failure
• opamfind.1.1.0 on 4.04 had its build status changed: failing to internal failure
• opamfind.1.1.1 on 4.04 had its build status changed: failing to internal failure
• opamfind.1.1.2 on 4.04 had its build status changed: failing to internal failure
• opamfind.1.1.3 on 4.04 had its build status changed: failing to internal failure
• opamfind.1.2.0 on 4.04 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.02 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.03 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.04 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.05 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.06 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.07 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.08 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.09 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.10 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.11 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.12 had its build status changed: failing to internal failure
• opencc.0.4.3-0.1.1 on 4.13 is now installable. Current state is: internal failure
• optint.0.0.1 on 4.10 had its build status changed: passing to internal failure
• orakuda.1.0.1 on 4.02 had its build status changed: failing to internal failure
• orakuda.1.0.1 on 4.03 had its build status changed: failing to internal failure
• orakuda.1.0.1 on 4.04 had its build status changed: partially failing to internal failure
• orakuda.1.0.1 on 4.05 had its build status changed: partially failing to internal failure
• orakuda.1.0.2 on 4.02 had its build status changed: failing to internal failure
• orakuda.1.0.2 on 4.03 had its build status changed: failing to internal failure
• orakuda.1.0.2 on 4.04 had its build status changed: partially failing to internal failure
• orakuda.1.0.2 on 4.05 had its build status changed: partially failing to internal failure
• orakuda.1.1.0 on 4.02 had its build status changed: failing to internal failure
• orakuda.1.1.0 on 4.03 had its build status changed: failing to internal failure
• orakuda.1.1.0 on 4.04 had its build status changed: partially failing to internal failure
• orakuda.1.1.0 on 4.05 had its build status changed: partially failing to internal failure
• orakuda.1.1.1 on 4.02 had its build status changed: failing to internal failure
• orakuda.1.1.1 on 4.03 had its build status changed: failing to internal failure
• orakuda.1.1.1 on 4.04 had its build status changed: partially failing to internal failure
• orakuda.1.1.1 on 4.05 had its build status changed: partially failing to internal failure
• orakuda.1.2.0 on 4.02 had its build status changed: failing to internal failure
• orakuda.1.2.0 on 4.03 had its build status changed: failing to internal failure
• orakuda.1.2.0 on 4.04 had its build status changed: failing to internal failure
• orakuda.1.2.0 on 4.05 had its build status changed: failing to internal failure
• orakuda.1.2.1 on 4.02 had its build status changed: failing to internal failure
• orakuda.1.2.1 on 4.03 had its build status changed: failing to internal failure
• orakuda.1.2.1 on 4.04 had its build status changed: failing to internal failure
• orakuda.1.2.1 on 4.05 had its build status changed: failing to internal failure
• orakuda.1.2.2 on 4.02 had its build status changed: failing to internal failure
• orakuda.1.2.2 on 4.03 had its build status changed: failing to internal failure
• orakuda.1.2.2 on 4.04 had its build status changed: failing to internal failure
• orakuda.1.2.2 on 4.05 had its build status changed: failing to internal failure
• orakuda.2.0.0 on 4.02 had its build status changed: failing to internal failure
• orocksdb.0.2.2 on 4.13 is now installable. Current state is: internal failure
• orrandomForest.1.0.0 on 4.13 is now installable. Current state is: internal failure
• orrandomForest.2.0.1 on 4.13 is now installable. Current state is: internal failure
• orsetto.1.0.1 on 4.06 had its build status changed: failing to internal failure
• orsetto.1.0.1 on 4.07 had its build status changed: failing to internal failure
• orsetto.1.0.1 on 4.08 had its build status changed: failing to internal failure
• orsvm_e1071.2.0.0 on 4.13 is now installable. Current state is: internal failure
• orsvm_e1071.3.0.0 on 4.13 is now installable. Current state is: internal failure
• orxgboost.1.0.1 on 4.13 is now installable. Current state is: internal failure
• orxgboost.1.1.0 on 4.13 is now installable. Current state is: internal failure
• p4pp.0.1.6 on 4.09 is now installable. Current state is: internal failure
• p4pp.0.1.6 on 4.10 is now installable. Current state is: internal failure
• p4pp.0.1.6 on 4.11 is now installable. Current state is: internal failure
• p4pp.0.1.6 on 4.12 is now installable. Current state is: internal failure
• pa_monad_custom.v6.0.0 on 4.02 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.03 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.04 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.05 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.06 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.07 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.08 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.09 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.10 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.11 had its build status changed: failing to internal failure
• pa_monad_custom.v6.0.0 on 4.12 had its build status changed: failing to internal failure
• pa_ovisitor.1.0.0 on 4.02 had its build status changed: failing to internal failure
• pa_ovisitor.1.0.0 on 4.03 had its build status changed: failing to internal failure
• pa_ovisitor.1.0.0 on 4.04 had its build status changed: failing to internal failure
• pa_ovisitor.1.0.0 on 4.05 had its build status changed: failing to internal failure
• patoline.0.1 on 4.02 had its build status changed: failing to internal failure
• patoline.0.1 on 4.03 had its build status changed: failing to internal failure
• patoline.0.1 on 4.04 had its build status changed: failing to internal failure
• patoline.0.1 on 4.05 had its build status changed: failing to internal failure
• planck.2.0.1 on 4.02 had its build status changed: failing to internal failure
• planck.2.1.0 on 4.02 had its build status changed: failing to internal failure
• planck.2.1.1 on 4.02 had its build status changed: failing to internal failure
• planck.2.2.0 on 4.02 had its build status changed: failing to internal failure
• planck.2.2.0 on 4.03 had its build status changed: failing to internal failure
• planck.2.2.0 on 4.04 had its build status changed: failing to internal failure
• planck.2.2.0 on 4.05 had its build status changed: failing to internal failure
• posix-bindings.2.0.0 on 4.03 had its build status changed: passing to internal failure
• ppx_curried_constr.1.0.0 on 4.02 had its build status changed: failing to internal failure
• ppx_deriving_jsoo.0.1 on 4.10 had its build status changed: passing to internal failure
• ppx_dotbracket.1.0.0 on 4.04 had its build status changed: failing to internal failure
• ppx_dotbracket.1.0.0 on 4.05 had its build status changed: failing to internal failure
• ppx_dotbracket.1.0.0 on 4.06 had its build status changed: failing to internal failure
• ppx_implicits.0.1.0 on 4.02 had its build status changed: failing to internal failure
• ppx_implicits.0.2.0 on 4.04 had its build status changed: failing to internal failure
• ppx_implicits.0.3.0 on 4.04 had its build status changed: failing to internal failure
• ppx_integer.0.1.0 on 4.04 had its build status changed: failing to internal failure
• ppx_integer.0.1.0 on 4.05 had its build status changed: failing to internal failure
• ppx_integer.0.1.0 on 4.06 had its build status changed: failing to internal failure
• ppx_integer.0.1.0 on 4.07 had its build status changed: failing to internal failure
• ppx_meta_conv.2.1.0 on 4.02 had its build status changed: failing to internal failure
• ppx_meta_conv.2.2.0 on 4.02 had its build status changed: failing to internal failure
• ppx_meta_conv.2.3.0 on 4.02 had its build status changed: failing to internal failure
• ppx_meta_conv.2.4.0 on 4.03 had its build status changed: failing to internal failure
• ppx_meta_conv.2.4.1 on 4.03 had its build status changed: failing to internal failure
• ppx_meta_conv.2.5.0 on 4.04 had its build status changed: failing to internal failure
• ppx_meta_conv.2.5.1 on 4.04 had its build status changed: failing to internal failure
• ppx_meta_conv.2.6.0 on 4.04 had its build status changed: failing to internal failure
• ppx_meta_conv.2.7.0 on 4.04 had its build status changed: failing to internal failure
• ppx_meta_conv.2.8.0 on 4.04 had its build status changed: partially failing to internal failure
• ppx_meta_conv.3.0.0 on 4.04 had its build status changed: partially failing to internal failure
• ppx_meta_conv.4.0.0 on 4.04 had its build status changed: partially failing to internal failure
• ppx_meta_conv.4.0.0 on 4.05 had its build status changed: partially failing to internal failure
• ppx_meta_conv.4.0.0 on 4.06 had its build status changed: partially failing to internal failure
• ppx_monadic.1.0.3 on 4.02 had its build status changed: failing to internal failure
• ppx_monadic.1.0.4 on 4.03 had its build status changed: failing to internal failure
• ppx_monadic.1.0.4 on 4.04 had its build status changed: failing to internal failure
• ppx_monadic.1.0.4 on 4.05 had its build status changed: failing to internal failure
• ppx_monadic.1.0.4 on 4.06 had its build status changed: failing to internal failure
• ppx_monadic.1.0.5 on 4.03 had its build status changed: failing to internal failure
• ppx_monadic.1.0.5 on 4.04 had its build status changed: failing to internal failure
• ppx_monadic.1.0.6 on 4.04 had its build status changed: failing to internal failure
• ppx_monadic.1.1.0 on 4.04 had its build status changed: failing to internal failure
• ppx_monadic.1.1.0 on 4.05 had its build status changed: failing to internal failure
• ppx_monadic.1.1.0 on 4.06 had its build status changed: failing to internal failure
• ppx_monadic.2.2.1 on 4.04 had its build status changed: failing to internal failure
• ppx_monadic.2.2.1 on 4.05 had its build status changed: failing to internal failure
• ppx_monadic.2.2.1 on 4.06 had its build status changed: failing to internal failure
• ppx_monadic.2.2.2 on 4.04 had its build status changed: failing to internal failure
• ppx_monadic.2.2.2 on 4.05 had its build status changed: failing to internal failure
• ppx_monadic.2.2.2 on 4.06 had its build status changed: failing to internal failure
• ppx_monadic.2.3.0 on 4.04 had its build status changed: failing to internal failure
• ppx_monadic.2.3.0 on 4.05 had its build status changed: failing to internal failure
• ppx_monadic.2.3.0 on 4.06 had its build status changed: failing to internal failure
• ppx_monadic.2.3.0 on 4.07 had its build status changed: failing to internal failure
• ppx_orakuda.2.0.1 on 4.02 had its build status changed: failing to internal failure
• ppx_orakuda.3.0.0 on 4.03 had its build status changed: failing to internal failure
• ppx_orakuda.3.0.1 on 4.03 had its build status changed: failing to internal failure
• ppx_orakuda.3.0.1 on 4.04 had its build status changed: failing to internal failure
• ppx_orakuda.3.0.2 on 4.04 had its build status changed: failing to internal failure
• ppx_orakuda.3.0.3 on 4.04 had its build status changed: failing to internal failure
• ppx_orakuda.3.1.0 on 4.04 had its build status changed: failing to internal failure
• ppx_orakuda.3.1.1 on 4.04 had its build status changed: failing to internal failure
• ppx_orakuda.3.1.1 on 4.05 had its build status changed: failing to internal failure
• ppx_orakuda.3.2.0 on 4.04 had its build status changed: partially failing to internal failure
• ppx_orakuda.3.2.0 on 4.05 had its build status changed: partially failing to internal failure
• ppx_orakuda.3.3.0 on 4.04 had its build status changed: partially failing to internal failure
• ppx_orakuda.3.3.0 on 4.05 had its build status changed: partially failing to internal failure
• ppx_orakuda.3.3.0 on 4.06 had its build status changed: partially failing to internal failure
• ppx_orakuda.3.3.0 on 4.07 had its build status changed: failing to internal failure
• ppx_overload.1.0.0 on 4.02 had its build status changed: failing to internal failure
• ppx_overload.1.0.1 on 4.02 had its build status changed: failing to internal failure
• ppx_overload.1.4 on 4.05 had its build status changed: partially failing to internal failure
• ppx_overload.1.4 on 4.06 had its build status changed: partially failing to internal failure
• ppx_poly_record.1.0.1 on 4.02 had its build status changed: failing to internal failure
• ppx_poly_record.1.1.0 on 4.02 had its build status changed: failing to internal failure
• ppx_poly_record.1.1.1 on 4.03 had its build status changed: failing to internal failure
• ppx_poly_record.1.1.1 on 4.04 had its build status changed: failing to internal failure
• ppx_poly_record.1.1.1 on 4.05 had its build status changed: failing to internal failure
• ppx_poly_record.1.1.1 on 4.06 had its build status changed: failing to internal failure
• ppx_poly_record.1.1.2 on 4.03 had its build status changed: failing to internal failure
• ppx_poly_record.1.1.2 on 4.04 had its build status changed: failing to internal failure
• ppx_poly_record.1.1.3 on 4.04 had its build status changed: failing to internal failure
• ppx_poly_record.1.2.0 on 4.04 had its build status changed: failing to internal failure
• ppx_poly_record.1.2.0 on 4.05 had its build status changed: failing to internal failure
• ppx_poly_record.1.2.0 on 4.06 had its build status changed: failing to internal failure
• ppx_poly_record.1.2.1 on 4.04 had its build status changed: failing to internal failure
• ppx_poly_record.1.2.1 on 4.05 had its build status changed: failing to internal failure
• ppx_poly_record.1.2.1 on 4.06 had its build status changed: failing to internal failure
• ppx_poly_record.1.2.2 on 4.04 had its build status changed: failing to internal failure
• ppx_poly_record.1.2.2 on 4.05 had its build status changed: failing to internal failure
• ppx_poly_record.1.2.2 on 4.06 had its build status changed: failing to internal failure
• ppx_poly_record.1.3.0 on 4.04 had its build status changed: failing to internal failure
• ppx_poly_record.1.3.0 on 4.05 had its build status changed: failing to internal failure
• ppx_poly_record.1.3.0 on 4.06 had its build status changed: failing to internal failure
• ppx_poly_record.1.3.0 on 4.07 had its build status changed: failing to internal failure
• ppx_sexp.0.3.0 on 4.02 had its build status changed: failing to internal failure
• ppx_test.0.0.1 on 4.02 had its build status changed: failing to internal failure
• ppx_test.1.0.1 on 4.02 had its build status changed: failing to internal failure
• ppx_test.1.1.0 on 4.02 had its build status changed: failing to internal failure
• ppx_test.1.2.0 on 4.02 had its build status changed: failing to internal failure
• ppx_test.1.2.1 on 4.02 had its build status changed: failing to internal failure
• ppx_test.1.3.0 on 4.02 had its build status changed: failing to internal failure
• ppx_test.1.3.1 on 4.02 had its build status changed: failing to internal failure
• ppx_test.1.4.0 on 4.03 had its build status changed: failing to internal failure
• ppx_test.1.4.0 on 4.04 had its build status changed: failing to internal failure
• ppx_test.1.4.1 on 4.03 had its build status changed: failing to internal failure
• ppx_test.1.4.1 on 4.04 had its build status changed: failing to internal failure
• ppx_test.1.4.2 on 4.04 had its build status changed: failing to internal failure
• ppx_test.1.5.0 on 4.04 had its build status changed: failing to internal failure
• ppx_test.1.5.0 on 4.05 had its build status changed: failing to internal failure
• ppx_test.1.5.0 on 4.06 had its build status changed: failing to internal failure
• ppx_test.1.5.1 on 4.04 had its build status changed: failing to internal failure
• ppx_test.1.5.1 on 4.05 had its build status changed: failing to internal failure
• ppx_test.1.5.1 on 4.06 had its build status changed: failing to internal failure
• ppx_test.1.5.2 on 4.04 had its build status changed: failing to internal failure
• ppx_test.1.5.2 on 4.05 had its build status changed: failing to internal failure
• ppx_test.1.5.2 on 4.06 had its build status changed: failing to internal failure
• ppx_test.1.6.0 on 4.04 had its build status changed: partially failing to internal failure
• ppx_test.1.6.0 on 4.05 had its build status changed: partially failing to internal failure
• ppx_test.1.6.0 on 4.06 had its build status changed: partially failing to internal failure
• ppxx.1.0.0 on 4.02 had its build status changed: failing to internal failure
• ppxx.1.1.0 on 4.02 had its build status changed: failing to internal failure
• ppxx.1.2.0 on 4.02 had its build status changed: failing to internal failure
• ppxx.1.2.1 on 4.02 had its build status changed: failing to internal failure
• ppxx.1.3.0 on 4.03 had its build status changed: failing to internal failure
• ppxx.1.3.1 on 4.04 had its build status changed: failing to internal failure
• ppxx.1.3.2 on 4.04 had its build status changed: failing to internal failure
• ppxx.1.4.0 on 4.04 had its build status changed: failing to internal failure
• ppxx.2.0.0 on 4.04 had its build status changed: failing to internal failure
• ppxx.2.1.0 on 4.04 had its build status changed: failing to internal failure
• ppxx.2.1.0 on 4.05 had its build status changed: failing to internal failure
• ppxx.2.1.0 on 4.06 had its build status changed: failing to internal failure
• ppxx.2.2.0 on 4.04 had its build status changed: failing to internal failure
• ppxx.2.2.0 on 4.05 had its build status changed: failing to internal failure
• ppxx.2.2.0 on 4.06 had its build status changed: failing to internal failure
• ppxx.2.3.0 on 4.04 had its build status changed: failing to internal failure
• ppxx.2.3.0 on 4.05 had its build status changed: failing to internal failure
• ppxx.2.3.0 on 4.06 had its build status changed: failing to internal failure
• ppxx.2.3.1 on 4.04 had its build status changed: failing to internal failure
• ppxx.2.3.1 on 4.05 had its build status changed: failing to internal failure
• ppxx.2.3.1 on 4.06 had its build status changed: failing to internal failure
• proj4.0.9.2 on 4.13 is now installable. Current state is: internal failure
• psyche.0.0.1 on 4.04 had its build status changed: failing to internal failure
• psyche.0.0.1 on 4.05 had its build status changed: failing to internal failure
• psyche.0.0.1 on 4.06 had its build status changed: failing to internal failure
• psyche.0.0.1 on 4.07 had its build status changed: failing to internal failure
• psyche.0.0.1 on 4.08 had its build status changed: failing to internal failure
• psyche.0.0.1 on 4.09 had its build status changed: failing to internal failure
• psyche.0.0.1 on 4.10 had its build status changed: failing to internal failure
• psyche.0.0.1 on 4.11 had its build status changed: failing to internal failure
• psyche.0.0.1 on 4.12 had its build status changed: failing to internal failure
• psyche.0.0.1 on 4.13 is now installable. Current state is: internal failure
• ptmap.2.0.5 on 4.02 had its build status changed: passing to internal failure
• qcheck.0.2 on 4.02 had its build status changed: failing to internal failure
• qcheck.0.2 on 4.03 had its build status changed: failing to internal failure
• qcheck.0.2 on 4.04 had its build status changed: failing to internal failure
• qcheck.0.2 on 4.05 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.02 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.03 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.04 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.05 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.06 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.07 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.08 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.09 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.10 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.11 had its build status changed: failing to internal failure
• rdbg.1.175 on 4.12 had its build status changed: failing to internal failure
• rdbg.1.184.1 on 4.05 had its build status changed: passing to internal failure
• rdbg.1.184.1 on 4.08 had its build status changed: passing to internal failure
• rdbg.1.184.1 on 4.09 had its build status changed: partially failing to internal failure
• rdbg.1.184.1 on 4.11 had its build status changed: passing to internal failure
• rdbg.1.184.1 on 4.12 had its build status changed: partially failing to internal failure
• rdbg.1.184.1 on 4.13 is now installable. Current state is: internal failure
• rdbg.1.65 on 4.02 had its build status changed: failing to internal failure
• rdbg.1.65 on 4.03 had its build status changed: failing to internal failure
• rdbg.1.70 on 4.02 had its build status changed: failing to internal failure
• rdbg.1.70 on 4.03 had its build status changed: failing to internal failure
• rdbg.1.70 on 4.04 had its build status changed: failing to internal failure
• resource-pooling.0.5 on 4.06 had its build status changed: passing to internal failure
• rotor.0.1 on 4.04 had its build status changed: failing to internal failure
• rotor.0.1 on 4.05 had its build status changed: failing to internal failure
• rotor.0.1 on 4.06 had its build status changed: failing to internal failure
• rotor.0.1 on 4.07 had its build status changed: failing to internal failure
• rotor.0.1 on 4.08 had its build status changed: failing to internal failure
• sibylfs-lem.0.4.0 on 4.02 had its build status changed: failing to internal failure
• sibylfs-lem.0.4.0 on 4.03 had its build status changed: failing to internal failure
• sibylfs-lem.0.4.0 on 4.04 had its build status changed: failing to internal failure
• sibylfs-lem.0.4.0 on 4.05 had its build status changed: failing to internal failure
• sibylfs.0.5.0 on 4.02 had its build status changed: partially failing to internal failure
• sill.1.3 on 4.02 had its build status changed: partially failing to internal failure
• sill.1.3.1 on 4.02 had its build status changed: partially failing to internal failure
• sill.1.4 on 4.02 had its build status changed: partially failing to internal failure
• sociaml-facebook-api.0.4.0 on 4.02 had its build status changed: partially failing to internal failure
• sociaml-tumblr-api.0.2.0 on 4.02 had its build status changed: partially failing to internal failure
• solo5-bindings-hvt.0.4.0 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-hvt.0.4.1 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-hvt.0.6.2 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-hvt.0.6.3 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-hvt.0.6.4 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-muen.0.4.0 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-muen.0.4.1 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-muen.0.6.2 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-muen.0.6.3 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-muen.0.6.4 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-spt.0.6.2 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-spt.0.6.3 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-spt.0.6.4 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-virtio.0.4.0 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-virtio.0.4.1 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-virtio.0.6.2 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-virtio.0.6.3 on 4.13 is now installable. Current state is: internal failure
• solo5-bindings-virtio.0.6.4 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-muen.0.3.0 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-muen.0.3.1 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-ukvm.0.1.1 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-ukvm.0.2.1 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-ukvm.0.2.2 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-ukvm.0.3.0 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-ukvm.0.3.1 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-virtio.0.1.1 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-virtio.0.2.1 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-virtio.0.2.2 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-virtio.0.3.0 on 4.13 is now installable. Current state is: internal failure
• solo5-kernel-virtio.0.3.1 on 4.13 is now installable. Current state is: internal failure
• spotinstall.1.0.0 on 4.02 had its build status changed: failing to internal failure
• spotinstall.1.0.1 on 4.02 had its build status changed: failing to internal failure
• spotinstall.1.1.0 on 4.02 had its build status changed: failing to internal failure
• spotinstall.1.1.1 on 4.02 had its build status changed: failing to internal failure
• spotinstall.1.2.0 on 4.02 had its build status changed: failing to internal failure
• spotinstall.1.2.0 on 4.03 had its build status changed: failing to internal failure
• spotinstall.1.2.0 on 4.04 had its build status changed: failing to internal failure
• spotinstall.1.2.0 on 4.05 had its build status changed: failing to internal failure
• spotinstall.1.2.1 on 4.03 had its build status changed: failing to internal failure
• spotinstall.1.2.1 on 4.04 had its build status changed: partially failing to internal failure
• spotinstall.1.2.1 on 4.05 had its build status changed: partially failing to internal failure
• spotlib.2.0.1 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.1.0 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.1.1 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.1.2 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.2.0 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.3.0 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.4.0 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.4.1 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.4.1 on 4.03 had its build status changed: failing to internal failure
• spotlib.2.4.1 on 4.04 had its build status changed: failing to internal failure
• spotlib.2.4.1 on 4.05 had its build status changed: failing to internal failure
• spotlib.2.5.0 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.5.0 on 4.03 had its build status changed: failing to internal failure
• spotlib.2.5.0 on 4.04 had its build status changed: failing to internal failure
• spotlib.2.5.0 on 4.05 had its build status changed: failing to internal failure
• spotlib.2.5.1 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.5.1 on 4.03 had its build status changed: failing to internal failure
• spotlib.2.5.1 on 4.04 had its build status changed: failing to internal failure
• spotlib.2.5.1 on 4.05 had its build status changed: failing to internal failure
• spotlib.2.5.2 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.5.2 on 4.03 had its build status changed: failing to internal failure
• spotlib.2.5.2 on 4.04 had its build status changed: failing to internal failure
• spotlib.2.5.2 on 4.05 had its build status changed: failing to internal failure
• spotlib.2.5.3 on 4.02 had its build status changed: failing to internal failure
• spotlib.2.5.3 on 4.03 had its build status changed: failing to internal failure
• spotlib.2.5.3 on 4.04 had its build status changed: failing to internal failure
• spotlib.2.5.3 on 4.05 had its build status changed: failing to internal failure
• spotlib.3.0.0 on 4.02 had its build status changed: failing to internal failure
• spotlib.3.0.0 on 4.03 had its build status changed: failing to internal failure
• spotlib.3.0.0 on 4.04 had its build status changed: failing to internal failure
• spotlib.3.0.0 on 4.05 had its build status changed: failing to internal failure
• spotlib.3.1.0 on 4.02 had its build status changed: failing to internal failure
• spotlib.3.1.0 on 4.03 had its build status changed: failing to internal failure
• spotlib.3.1.0 on 4.04 had its build status changed: failing to internal failure
• spotlib.3.1.0 on 4.05 had its build status changed: failing to internal failure
• spotlib.3.1.2 on 4.03 had its build status changed: failing to internal failure
• spotlib.3.1.2 on 4.04 had its build status changed: failing to internal failure
• spotlib.3.1.2 on 4.05 had its build status changed: failing to internal failure
• spotlib.4.0.0 on 4.04 had its build status changed: failing to internal failure
• spotlib.4.0.0 on 4.05 had its build status changed: failing to internal failure
• spotlib.4.0.1 on 4.04 had its build status changed: failing to internal failure
• spotlib.4.0.1 on 4.05 had its build status changed: failing to internal failure
• spotlib.4.0.2 on 4.04 had its build status changed: failing to internal failure
• spotlib.4.0.2 on 4.05 had its build status changed: failing to internal failure
• spotlib.4.0.2 on 4.06 had its build status changed: failing to internal failure
• spotlib.4.0.3 on 4.04 had its build status changed: partially failing to internal failure
• spotlib.4.0.3 on 4.05 had its build status changed: partially failing to internal failure
• spotlib.4.0.3 on 4.06 had its build status changed: partially failing to internal failure
• sqlgg.20200521 on 4.04 had its build status changed: passing to internal failure
• srs.2.0.0 on 4.13 is now installable. Current state is: internal failure
• stog-rdf.0.11.0 on 4.02 had its build status changed: passing to internal failure
• stog-rdf.0.15.0 on 4.02 had its build status changed: partially failing to internal failure
• stog-rdf.0.16.0 on 4.02 had its build status changed: partially failing to internal failure
• stog-rdf.0.16.1 on 4.02 had its build status changed: partially failing to internal failure
• stog-rdf.0.16.1 on 4.03 had its build status changed: partially failing to internal failure
• stog-rdf.0.16.1 on 4.04 had its build status changed: partially failing to internal failure
• stog-rdf.0.16.1 on 4.05 had its build status changed: partially failing to internal failure
• stog-rdf.0.16.1 on 4.06 had its build status changed: partially failing to internal failure
• stog-rdf.0.16.1 on 4.07 had its build status changed: partially failing to internal failure
• stog-writing.0.11.0 on 4.02 had its build status changed: passing to internal failure
• stog-writing.0.11.0 on 4.03 had its build status changed: passing to internal failure
• stog-writing.0.11.0 on 4.04 had its build status changed: passing to internal failure
• stog-writing.0.11.0 on 4.05 had its build status changed: passing to internal failure
• stog-writing.0.13.0 on 4.02 had its build status changed: passing to internal failure
• stog-writing.0.13.0 on 4.03 had its build status changed: passing to internal failure
• stog-writing.0.13.0 on 4.04 had its build status changed: passing to internal failure
• stog-writing.0.13.0 on 4.05 had its build status changed: passing to internal failure
• stog-writing.0.15.0 on 4.02 had its build status changed: partially failing to internal failure
• stog-writing.0.16.0 on 4.02 had its build status changed: partially failing to internal failure
• stog-writing.0.16.0 on 4.03 had its build status changed: partially failing to internal failure
• stog-writing.0.16.0 on 4.04 had its build status changed: partially failing to internal failure
• stog-writing.0.16.0 on 4.05 had its build status changed: partially failing to internal failure
• stog-writing.0.16.0 on 4.06 had its build status changed: partially failing to internal failure
• stog-writing.0.16.0 on 4.07 had its build status changed: partially failing to internal failure
• stog.0.11.1 on 4.02 had its build status changed: passing to internal failure
• stog.0.11.1 on 4.03 had its build status changed: passing to internal failure
• stog.0.11.1 on 4.04 had its build status changed: passing to internal failure
• stog.0.11.1 on 4.05 had its build status changed: passing to internal failure
• stog.0.13.0 on 4.02 had its build status changed: passing to internal failure
• stog.0.13.0 on 4.03 had its build status changed: passing to internal failure
• stog.0.13.0 on 4.04 had its build status changed: passing to internal failure
• stog.0.13.0 on 4.05 had its build status changed: passing to internal failure
• stog.0.14.0 on 4.02 had its build status changed: passing to internal failure
• stog.0.14.0 on 4.03 had its build status changed: passing to internal failure
• stog.0.14.0 on 4.04 had its build status changed: passing to internal failure
• stog.0.14.0 on 4.05 had its build status changed: passing to internal failure
• stog.0.15.0 on 4.02 had its build status changed: partially failing to internal failure
• stog.0.16.0 on 4.02 had its build status changed: partially failing to internal failure
• stog.0.16.0 on 4.03 had its build status changed: partially failing to internal failure
• stog.0.16.0 on 4.04 had its build status changed: failing to internal failure
• stog.0.16.0 on 4.05 had its build status changed: failing to internal failure
• stog.0.16.0 on 4.06 had its build status changed: failing to internal failure
• stog.0.16.0 on 4.07 had its build status changed: failing to internal failure
• taglog.0.1.0 on 4.02 had its build status changed: partially failing to internal failure
• taglog.0.2.0 on 4.02 had its build status changed: partially failing to internal failure
• taglog.0.2.0 on 4.03 had its build status changed: passing to internal failure
• taglog.0.2.0 on 4.04 had its build status changed: passing to internal failure
• taglog.0.2.0 on 4.05 had its build status changed: passing to internal failure
• taglog.0.2.0 on 4.06 had its build status changed: passing to internal failure
• taglog.0.2.0 on 4.07 had its build status changed: passing to internal failure
• taglog.0.3.0 on 4.02 had its build status changed: partially failing to internal failure
• tcx.0.25.0 on 4.02 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.03 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.04 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.05 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.06 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.07 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.08 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.09 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.10 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.11 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.12 had its build status changed: failing to internal failure
• tcx.0.25.0 on 4.13 is now installable. Current state is: internal failure
• tidy.0-2009-0.1.1 on 4.02 had its build status changed: failing to internal failure
• tidy.0-2009-0.1.1 on 4.03 had its build status changed: failing to internal failure
• tidy.0-2009-0.1.1 on 4.04 had its build status changed: failing to internal failure
• tidy.0-2009-0.1.1 on 4.05 had its build status changed: failing to internal failure
• tidy.0-2009-0.1.1 on 4.06 had its build status changed: failing to internal failure
• tidy.1-4.9.30-0.1.1 on 4.02 had its build status changed: failing to internal failure
• tidy.1-4.9.30-0.1.1 on 4.03 had its build status changed: failing to internal failure
• tidy.1-4.9.30-0.1.1 on 4.04 had its build status changed: failing to internal failure
• tidy.1-4.9.30-0.1.1 on 4.05 had its build status changed: failing to internal failure
• tidy.1-4.9.30-0.1.1 on 4.06 had its build status changed: failing to internal failure
• tidy.1-4.9.30-0.1.1 on 4.07 had its build status changed: failing to internal failure
• tidy.1-4.9.30-0.1.1 on 4.08 had its build status changed: failing to internal failure
• tidy.1-4.9.30-0.1.1 on 4.09 had its build status changed: failing to internal failure
• tidy.5-0.2 on 4.04 had its build status changed: failing to internal failure
• tidy.5-0.2 on 4.05 had its build status changed: failing to internal failure
• tidy.5-0.2 on 4.06 had its build status changed: failing to internal failure
• tidy.5-0.2 on 4.07 had its build status changed: failing to internal failure
• tidy.5-0.2 on 4.08 had its build status changed: failing to internal failure
• tidy.5-0.2 on 4.09 had its build status changed: failing to internal failure
• tiny_json.1.0.0 on 4.02 had its build status changed: failing to internal failure
• tiny_json.1.0.0 on 4.03 had its build status changed: failing to internal failure
• tiny_json.1.0.0 on 4.04 had its build status changed: failing to internal failure
• tiny_json.1.0.0 on 4.05 had its build status changed: failing to internal failure
• tiny_json.1.0.1 on 4.02 had its build status changed: failing to internal failure
• tiny_json.1.0.1 on 4.03 had its build status changed: failing to internal failure
• tiny_json.1.0.1 on 4.04 had its build status changed: failing to internal failure
• tiny_json.1.0.1 on 4.05 had its build status changed: failing to internal failure
• tiny_json.1.1.0 on 4.02 had its build status changed: failing to internal failure
• tiny_json.1.1.0 on 4.03 had its build status changed: failing to internal failure
• tiny_json.1.1.0 on 4.04 had its build status changed: failing to internal failure
• tiny_json.1.1.0 on 4.05 had its build status changed: failing to internal failure
• tiny_json.1.1.1 on 4.02 had its build status changed: failing to internal failure
• tiny_json.1.1.1 on 4.03 had its build status changed: failing to internal failure
• tiny_json.1.1.1 on 4.04 had its build status changed: failing to internal failure
• tiny_json.1.1.1 on 4.05 had its build status changed: failing to internal failure
• tiny_json.1.1.2 on 4.02 had its build status changed: failing to internal failure
• tiny_json.1.1.2 on 4.03 had its build status changed: failing to internal failure
• tiny_json.1.1.2 on 4.04 had its build status changed: failing to internal failure
• tiny_json.1.1.2 on 4.05 had its build status changed: failing to internal failure
• tiny_json.1.1.3 on 4.02 had its build status changed: failing to internal failure
• tiny_json.1.1.3 on 4.03 had its build status changed: failing to internal failure
• tiny_json.1.1.3 on 4.04 had its build status changed: failing to internal failure
• tiny_json.1.1.3 on 4.05 had its build status changed: failing to internal failure
• tiny_json.1.1.4 on 4.02 had its build status changed: failing to internal failure
• tiny_json.1.1.4 on 4.03 had its build status changed: failing to internal failure
• tiny_json.1.1.4 on 4.04 had its build status changed: failing to internal failure
• tiny_json.1.1.4 on 4.05 had its build status changed: failing to internal failure
• tiny_json.1.1.5 on 4.05 had its build status changed: failing to internal failure
• tiny_json.1.1.5 on 4.06 had its build status changed: failing to internal failure
• tiny_json.1.1.5 on 4.07 had its build status changed: failing to internal failure
• tiny_json.1.1.5 on 4.08 had its build status changed: failing to internal failure
• tiny_json.1.1.5 on 4.09 had its build status changed: failing to internal failure
• tiny_json.1.1.5 on 4.10 had its build status changed: failing to internal failure
• tiny_json.1.1.5 on 4.11 had its build status changed: failing to internal failure
• tiny_json.1.1.5 on 4.12 had its build status changed: failing to internal failure
• tiny_json.1.1.5 on 4.13 is now installable. Current state is: internal failure
• tiny_json_conv.1.3.0 on 4.02 had its build status changed: failing to internal failure
• tiny_json_conv.1.4.0 on 4.02 had its build status changed: failing to internal failure
• tiny_json_conv.1.4.1 on 4.02 had its build status changed: failing to internal failure
• tls.0.5.0 on 4.02 had its build status changed: failing to internal failure
• tlstunnel.0.1.0 on 4.02 had its build status changed: failing to internal failure
• tlstunnel.0.1.1 on 4.02 had its build status changed: failing to internal failure
• tlstunnel.0.1.2 on 4.02 had its build status changed: failing to internal failure
• treeprint.1.0.2 on 4.02 had its build status changed: failing to internal failure
• treeprint.1.0.3 on 4.02 had its build status changed: failing to internal failure
• treeprint.2.0.0 on 4.02 had its build status changed: failing to internal failure
• treeprint.2.1.0 on 4.02 had its build status changed: failing to internal failure
• treeprint.2.1.1 on 4.02 had its build status changed: failing to internal failure
• treeprint.2.1.1 on 4.03 had its build status changed: failing to internal failure
• treeprint.2.1.1 on 4.04 had its build status changed: partially failing to internal failure
• treeprint.2.1.1 on 4.05 had its build status changed: partially failing to internal failure
• treeprint.2.1.1 on 4.06 had its build status changed: partially failing to internal failure
• treeprint.2.1.1 on 4.07 had its build status changed: failing to internal failure
• treeprint.2.1.1 on 4.08 had its build status changed: failing to internal failure
• treeprint.2.1.1 on 4.09 had its build status changed: failing to internal failure
• treeprint.2.1.1 on 4.10 had its build status changed: failing to internal failure
• treeprint.2.1.1 on 4.11 had its build status changed: failing to internal failure
• treeprint.2.2.0 on 4.04 had its build status changed: partially failing to internal failure
• treeprint.2.2.0 on 4.05 had its build status changed: partially failing to internal failure
• treeprint.2.2.0 on 4.06 had its build status changed: partially failing to internal failure
• trie.0.1.1 on 4.02 had its build status changed: failing to internal failure
• trie.0.1.1 on 4.03 had its build status changed: failing to internal failure
• trie.0.1.1 on 4.04 had its build status changed: failing to internal failure
• trie.0.1.1 on 4.05 had its build status changed: failing to internal failure
• trie.0.1.1 on 4.06 had its build status changed: failing to internal failure
• typerex-attic.1.0.0 on 4.02 had its build status changed: partially failing to internal failure
• typerex-attic.1.0.2 on 4.02 had its build status changed: partially failing to internal failure
• typerex-attic.1.0.2 on 4.03 had its build status changed: partially failing to internal failure
• typpx.1.0.2 on 4.02 had its build status changed: failing to internal failure
• typpx.1.1.1 on 4.02 had its build status changed: failing to internal failure
• typpx.1.1.2 on 4.02 had its build status changed: failing to internal failure
• typpx.1.1.3 on 4.03 had its build status changed: failing to internal failure
• typpx.1.2.0 on 4.04 had its build status changed: failing to internal failure
• typpx.1.2.1 on 4.04 had its build status changed: failing to internal failure
• typpx.1.2.2 on 4.04 had its build status changed: failing to internal failure
• typpx.1.3.0 on 4.05 had its build status changed: failing to internal failure
• typpx.1.4.0 on 4.04 had its build status changed: failing to internal failure
• typpx.1.4.1 on 4.05 had its build status changed: failing to internal failure
• typpx.1.4.2 on 4.06 had its build status changed: failing to internal failure
• typpx.1.4.3 on 4.06 had its build status changed: failing to internal failure
• unmagic.0.9.0 on 4.03 had its build status changed: failing to internal failure
• unmagic.0.9.0 on 4.04 had its build status changed: partially failing to internal failure
• unmagic.0.9.0 on 4.05 had its build status changed: partially failing to internal failure
• unmagic.0.9.0 on 4.06 had its build status changed: partially failing to internal failure
• unmagic.1.0.0 on 4.03 had its build status changed: failing to internal failure
• unmagic.1.0.0 on 4.04 had its build status changed: partially failing to internal failure
• unmagic.1.0.0 on 4.05 had its build status changed: partially failing to internal failure
• unmagic.1.0.0 on 4.06 had its build status changed: partially failing to internal failure
• unmagic.1.0.1 on 4.03 had its build status changed: failing to internal failure
• unmagic.1.0.1 on 4.04 had its build status changed: partially failing to internal failure
• unmagic.1.0.1 on 4.05 had its build status changed: partially failing to internal failure
• unmagic.1.0.1 on 4.06 had its build status changed: partially failing to internal failure
• unmagic.1.0.2 on 4.03 had its build status changed: failing to internal failure
• unmagic.1.0.2 on 4.04 had its build status changed: partially failing to internal failure
• unmagic.1.0.3 on 4.06 had its build status changed: partially failing to internal failure
• unmagic.1.0.4 on 4.06 had its build status changed: partially failing to internal failure
• vpnkit.0.2.0 on 4.05 had its build status changed: partially failing to internal failure
• wiringpi.0.0.1 on 4.13 is now installable. Current state is: internal failure
• xen-gnt.2.2.1 on 4.03 had its build status changed: failing to internal failure
• xen-gnt.2.2.1 on 4.04 had its build status changed: failing to internal failure
• xmldiff.0.1 on 4.02 had its build status changed: passing to internal failure
• xmldiff.0.1 on 4.03 had its build status changed: passing to internal failure
• xmldiff.0.1 on 4.04 had its build status changed: passing to internal failure
• xmldiff.0.2 on 4.02 had its build status changed: passing to internal failure
• xmldiff.0.2 on 4.03 had its build status changed: passing to internal failure
• xmldiff.0.2 on 4.04 had its build status changed: passing to internal failure
• xmldiff.0.2 on 4.05 had its build status changed: passing to internal failure
• xmldiff.0.3.0 on 4.02 had its build status changed: passing to internal failure
• xmldiff.0.3.0 on 4.03 had its build status changed: passing to internal failure
• xmldiff.0.3.0 on 4.04 had its build status changed: passing to internal failure
• xmldiff.0.3.0 on 4.05 had its build status changed: passing to internal failure
• xmldiff.0.4.0 on 4.02 had its build status changed: passing to internal failure
• xmldiff.0.4.0 on 4.03 had its build status changed: passing to internal failure
• xmldiff.0.4.0 on 4.04 had its build status changed: passing to internal failure
• xmldiff.0.4.0 on 4.05 had its build status changed: passing to internal failure
• xmldiff.0.5.0 on 4.02 had its build status changed: passing to internal failure
• xmldiff.0.5.0 on 4.04 had its build status changed: passing to internal failure
• xmldiff.0.5.0 on 4.05 had its build status changed: passing to internal failure
• xtmpl.0.11 on 4.02 had its build status changed: passing to internal failure
• xtmpl.0.12 on 4.02 had its build status changed: passing to internal failure
• xtmpl.0.13.0 on 4.02 had its build status changed: failing to internal failure
• xtmpl.0.14.0 on 4.03 had its build status changed: failing to internal failure
• xtmpl.0.14.0 on 4.04 had its build status changed: failing to internal failure
• z3.4.6 on 4.13 is now installable. Current state is: internal failure
• zarith.1.9.1 on 4.04 had its build status changed: passing to internal failure
• zarith_stubs_js.v0.13.0 on 4.07 had its build status changed: passing to internal failure
• zarith_stubs_js.v0.13.0 on 4.13 is now installable. Current state is: internal failure
• zarith_stubs_js.v0.14.0 on 4.06 had its build status changed: passing to internal failure
• zarith_stubs_js.v0.14.0 on 4.11 had its build status changed: passing to internal failure
• zbar.0.9 on 4.04 had its build status changed: passing to internal failure
• zbar.0.9 on 4.07 had its build status changed: passing to internal failure
• zbar.0.9 on 4.09 had its build status changed: passing to internal failure
• zbar.0.9 on 4.11 had its build status changed: passing to internal failure
• zed.1.3 on 4.02 had its build status changed: passing to internal failure