Home
|
Differences with the last checks
|
Previous runs
Differences between
9b339ea
and
232a37e
(
git diff
)
Packages now
failing
:
afl.2.52b
on
4.08
had its build status changed:
passing
to
failing
afl.2.52b
on
4.09
had its build status changed:
passing
to
failing
afl.2.52b
on
4.10
had its build status changed:
passing
to
failing
afl.2.52b
on
4.11
had its build status changed:
passing
to
failing
afl.2.52b
on
4.12
had its build status changed:
passing
to
failing
afl.2.52b
on
4.13
had its build status changed:
passing
to
failing
afl.2.52b
on
4.14
had its build status changed:
passing
to
failing
afl.2.52b
on
5.0
had its build status changed:
passing
to
failing
afl.2.52b
on
5.1
had its build status changed:
passing
to
failing
afl.2.52b
on
5.2
is now installable. Current state is:
failing
afl.2.57b
on
4.08
had its build status changed:
passing
to
failing
afl.2.57b
on
4.09
had its build status changed:
passing
to
failing
afl.2.57b
on
4.10
had its build status changed:
passing
to
failing
afl.2.57b
on
4.11
had its build status changed:
passing
to
failing
afl.2.57b
on
4.12
had its build status changed:
passing
to
failing
afl.2.57b
on
4.13
had its build status changed:
passing
to
failing
afl.2.57b
on
4.14
had its build status changed:
passing
to
failing
afl.2.57b
on
5.0
had its build status changed:
passing
to
failing
afl.2.57b
on
5.1
had its build status changed:
passing
to
failing
afl.2.57b
on
5.2
is now installable. Current state is:
failing
ahrocksdb.0.2.2
on
4.08
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
4.09
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
4.10
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
4.11
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
4.12
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
4.13
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
4.14
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
5.0
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
5.1
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
5.2
is now installable. Current state is:
failing
alt-ergo.0.95.2
on
4.09
had its build status changed:
partially failing
to
failing
asai.0.1.1
on
5.0
had its build status changed:
partially failing
to
failing
asai.0.1.1
on
5.1
had its build status changed:
partially failing
to
failing
async_ssl.v0.12.0
on
4.08
had its build status changed:
partially failing
to
failing
async_ssl.v0.12.0
on
4.09
had its build status changed:
partially failing
to
failing
async_ssl.v0.13.0
on
4.08
had its build status changed:
partially failing
to
failing
async_ssl.v0.13.0
on
4.09
had its build status changed:
partially failing
to
failing
async_ssl.v0.13.0
on
4.10
had its build status changed:
partially failing
to
failing
async_ssl.v0.13.0
on
4.11
had its build status changed:
partially failing
to
failing
async_ssl.v0.14.0
on
4.08
had its build status changed:
partially failing
to
failing
async_ssl.v0.14.0
on
4.09
had its build status changed:
partially failing
to
failing
async_ssl.v0.14.0
on
4.10
had its build status changed:
partially failing
to
failing
async_ssl.v0.14.0
on
4.11
had its build status changed:
partially failing
to
failing
async_ssl.v0.14.0
on
4.12
had its build status changed:
partially failing
to
failing
async_ssl.v0.14.0
on
4.13
had its build status changed:
partially failing
to
failing
async_ssl.v0.14.0
on
4.14
had its build status changed:
partially failing
to
failing
async_ssl.v0.15.0
on
4.11
had its build status changed:
partially failing
to
failing
async_ssl.v0.15.0
on
4.12
had its build status changed:
partially failing
to
failing
async_ssl.v0.15.0
on
4.13
had its build status changed:
partially failing
to
failing
async_ssl.v0.15.0
on
4.14
had its build status changed:
partially failing
to
failing
async_ssl.v0.15.0
on
5.0
had its build status changed:
partially failing
to
failing
async_ssl.v0.16.0
on
4.14
had its build status changed:
partially failing
to
failing
async_ssl.v0.16.0
on
5.0
had its build status changed:
partially failing
to
failing
async_ssl.v0.16.0
on
5.1
had its build status changed:
partially failing
to
failing
async_ssl.v0.16.0
on
5.2
is now installable. Current state is:
failing
async_ssl.v0.16.1
on
4.14
had its build status changed:
partially failing
to
failing
async_ssl.v0.16.1
on
5.0
had its build status changed:
partially failing
to
failing
async_ssl.v0.16.1
on
5.1
had its build status changed:
partially failing
to
failing
async_ssl.v0.16.1
on
5.2
is now installable. Current state is:
failing
async_ssl.v0.17.0
on
5.1
is now installable. Current state is:
failing
async_ssl.v0.17.0
on
5.2
is now installable. Current state is:
failing
aws-s3-async.4.2.0
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-async.4.2.0
on
4.09
had its build status changed:
partially failing
to
failing
aws-s3-async.4.3.0
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-async.4.3.0
on
4.09
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.0
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.0
on
4.09
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.0
on
4.10
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.0
on
4.11
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.0
on
4.12
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.0
on
4.13
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.0
on
4.14
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.1
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.1
on
4.09
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.1
on
4.10
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.1
on
4.11
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.1
on
4.12
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.1
on
4.13
had its build status changed:
partially failing
to
failing
aws-s3-async.4.4.1
on
4.14
had its build status changed:
partially failing
to
failing
aws-s3-async.4.5.0
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-async.4.5.0
on
4.09
had its build status changed:
partially failing
to
failing
aws-s3-async.4.5.1
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-async.4.5.1
on
4.09
had its build status changed:
partially failing
to
failing
aws-s3-async.4.5.1
on
4.10
had its build status changed:
partially failing
to
failing
aws-s3-async.4.5.1
on
4.11
had its build status changed:
partially failing
to
failing
aws-s3-async.4.5.1
on
4.12
had its build status changed:
partially failing
to
failing
aws-s3-async.4.5.1
on
4.13
had its build status changed:
partially failing
to
failing
aws-s3-async.4.5.1
on
4.14
had its build status changed:
partially failing
to
failing
aws-s3-async.4.6.0
on
4.11
had its build status changed:
partially failing
to
failing
aws-s3-async.4.6.0
on
4.12
had its build status changed:
partially failing
to
failing
aws-s3-async.4.6.0
on
4.13
had its build status changed:
partially failing
to
failing
aws-s3-async.4.7.0
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-async.4.7.0
on
4.09
had its build status changed:
partially failing
to
failing
aws-s3-async.4.7.0
on
4.10
had its build status changed:
partially failing
to
failing
aws-s3-async.4.7.0
on
4.11
had its build status changed:
partially failing
to
failing
aws-s3-async.4.7.0
on
4.12
had its build status changed:
partially failing
to
failing
aws-s3-async.4.7.0
on
4.13
had its build status changed:
partially failing
to
failing
aws-s3-async.4.8.0
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-async.4.8.0
on
4.09
had its build status changed:
partially failing
to
failing
aws-s3-async.4.8.0
on
4.10
had its build status changed:
partially failing
to
failing
aws-s3-async.4.8.0
on
4.11
had its build status changed:
partially failing
to
failing
aws-s3-async.4.8.0
on
4.12
had its build status changed:
partially failing
to
failing
aws-s3-async.4.8.0
on
4.13
had its build status changed:
partially failing
to
failing
aws-s3-lwt.4.2.0
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-lwt.4.2.0
on
4.09
had its build status changed:
partially failing
to
failing
aws-s3-lwt.4.3.0
on
4.08
had its build status changed:
partially failing
to
failing
aws-s3-lwt.4.3.0
on
4.09
had its build status changed:
partially failing
to
failing
bap-core-theory.2.1.0
on
4.08
had its build status changed:
partially failing
to
failing
bap-core-theory.2.1.0
on
4.09
had its build status changed:
partially failing
to
failing
bap-frames.2.1.0
on
4.08
had its build status changed:
partially failing
to
failing
bap-frames.2.1.0
on
4.09
had its build status changed:
partially failing
to
failing
bap-ghidra.2.4.0
on
4.08
had its build status changed:
partially failing
to
failing
bap-ghidra.2.4.0
on
4.09
had its build status changed:
partially failing
to
failing
bap-ghidra.2.4.0
on
4.10
had its build status changed:
partially failing
to
failing
bap-ghidra.2.4.0
on
4.11
had its build status changed:
partially failing
to
failing
bap-ghidra.2.4.0
on
4.12
had its build status changed:
partially failing
to
failing
bap-ghidra.2.4.0
on
4.13
had its build status changed:
partially failing
to
failing
bap-ghidra.2.4.0
on
4.14
had its build status changed:
partially failing
to
failing
bap-ghidra.2.5.0
on
4.08
had its build status changed:
partially failing
to
failing
bap-ghidra.2.5.0
on
4.09
had its build status changed:
partially failing
to
failing
bap-ghidra.2.5.0
on
4.10
had its build status changed:
partially failing
to
failing
bap-ghidra.2.5.0
on
4.11
had its build status changed:
partially failing
to
failing
bap-ghidra.2.5.0
on
4.12
had its build status changed:
partially failing
to
failing
bap-ghidra.2.5.0
on
4.13
had its build status changed:
partially failing
to
failing
bap-ghidra.2.5.0
on
4.14
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
4.08
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
4.09
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
4.10
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
4.11
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
4.12
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
4.13
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
4.14
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
5.1
had its build status changed:
partially failing
to
failing
binaryen.0.1.0
on
5.2
is now installable. Current state is:
failing
binaryen.0.2.1
on
4.08
had its build status changed:
partially failing
to
failing
binaryen.0.2.1
on
4.09
had its build status changed:
partially failing
to
failing
binaryen.0.2.1
on
4.10
had its build status changed:
partially failing
to
failing
binaryen.0.2.1
on
4.11
had its build status changed:
partially failing
to
failing
binaryen.0.2.1
on
4.12
had its build status changed:
partially failing
to
failing
binaryen.0.2.1
on
4.13
had its build status changed:
partially failing
to
failing
binaryen.0.2.1
on
4.14
had its build status changed:
partially failing
to
failing
binaryen.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
binaryen.0.2.1
on
5.1
had its build status changed:
partially failing
to
failing
binaryen.0.2.1
on
5.2
is now installable. Current state is:
failing
binaryen.0.2.2
on
4.08
had its build status changed:
partially failing
to
failing
binaryen.0.2.2
on
4.09
had its build status changed:
partially failing
to
failing
binaryen.0.2.2
on
4.10
had its build status changed:
partially failing
to
failing
binaryen.0.2.2
on
4.11
had its build status changed:
partially failing
to
failing
binaryen.0.2.2
on
4.12
had its build status changed:
partially failing
to
failing
binaryen.0.2.2
on
4.13
had its build status changed:
partially failing
to
failing
binaryen.0.2.2
on
4.14
had its build status changed:
partially failing
to
failing
binaryen.0.2.2
on
5.0
had its build status changed:
partially failing
to
failing
binaryen.0.2.2
on
5.1
had its build status changed:
partially failing
to
failing
binaryen.0.2.2
on
5.2
is now installable. Current state is:
failing
binaryen.0.2.3
on
4.08
had its build status changed:
partially failing
to
failing
binaryen.0.2.3
on
4.09
had its build status changed:
partially failing
to
failing
binaryen.0.2.3
on
4.10
had its build status changed:
partially failing
to
failing
binaryen.0.2.3
on
4.11
had its build status changed:
partially failing
to
failing
binaryen.0.2.3
on
4.12
had its build status changed:
partially failing
to
failing
binaryen.0.2.3
on
4.13
had its build status changed:
partially failing
to
failing
binaryen.0.2.3
on
4.14
had its build status changed:
partially failing
to
failing
binaryen.0.2.3
on
5.0
had its build status changed:
partially failing
to
failing
binaryen.0.2.3
on
5.1
had its build status changed:
partially failing
to
failing
binaryen.0.2.3
on
5.2
is now installable. Current state is:
failing
bitmasks.1.4.0
on
5.1
had its build status changed:
partially failing
to
failing
bitmasks.1.4.0
on
5.2
is now installable. Current state is:
failing
bitwuzla-bin.1.0.0
on
5.2
is now installable. Current state is:
failing
bitwuzla-cxx.0.2.0
on
4.12
had its build status changed:
partially failing
to
failing
bitwuzla-cxx.0.2.0
on
4.13
had its build status changed:
partially failing
to
failing
bitwuzla-cxx.0.2.0
on
4.14
had its build status changed:
partially failing
to
failing
bitwuzla-cxx.0.3.0
on
4.12
is now installable. Current state is:
failing
bitwuzla-cxx.0.3.0
on
4.13
is now installable. Current state is:
failing
bitwuzla-cxx.0.3.0
on
4.14
is now installable. Current state is:
failing
bitwuzla-cxx.0.4.0
on
4.12
is now installable. Current state is:
failing
bitwuzla-cxx.0.4.0
on
4.13
is now installable. Current state is:
failing
bitwuzla-cxx.0.4.0
on
4.14
is now installable. Current state is:
failing
bitwuzla-cxx.0.4.0
on
5.0
is now installable. Current state is:
failing
bitwuzla-cxx.0.4.0
on
5.1
is now installable. Current state is:
failing
bitwuzla-cxx.0.4.0
on
5.2
is now installable. Current state is:
failing
blake3.0.1
on
4.09
had its build status changed:
partially failing
to
failing
blake3.0.1
on
4.10
had its build status changed:
partially failing
to
failing
blake3.0.1
on
4.11
had its build status changed:
partially failing
to
failing
blake3.0.1
on
4.12
had its build status changed:
partially failing
to
failing
blake3.0.1
on
4.13
had its build status changed:
partially failing
to
failing
blake3.0.1
on
4.14
had its build status changed:
partially failing
to
failing
blake3.0.1
on
5.0
had its build status changed:
partially failing
to
failing
blake3.0.1
on
5.1
had its build status changed:
partially failing
to
failing
blake3.0.1
on
5.2
is now installable. Current state is:
failing
boltzgen.0.9
on
5.2
is now installable. Current state is:
failing
boltzgen.0.9.2
on
5.2
is now installable. Current state is:
failing
boltzgen.0.9.3
on
5.2
is now installable. Current state is:
failing
calculon.0.3
on
4.08
had its build status changed:
partially failing
to
failing
calculon.0.3
on
4.09
had its build status changed:
partially failing
to
failing
calculon.0.3
on
4.10
had its build status changed:
partially failing
to
failing
calculon.0.3
on
4.11
had its build status changed:
partially failing
to
failing
calculon.0.4
on
4.08
had its build status changed:
partially failing
to
failing
calculon.0.4
on
4.09
had its build status changed:
partially failing
to
failing
calculon.0.4
on
4.10
had its build status changed:
partially failing
to
failing
calculon.0.4
on
4.11
had its build status changed:
partially failing
to
failing
camlgpc.1.0
on
5.0
had its build status changed:
passing
to
failing
camlgpc.1.0
on
5.1
had its build status changed:
passing
to
failing
camlgpc.1.0
on
5.2
is now installable. Current state is:
failing
camlidl.1.05
on
4.08
had its build status changed:
passing
to
failing
camlidl.1.05
on
4.09
had its build status changed:
passing
to
failing
camlidl.1.05
on
4.10
had its build status changed:
passing
to
failing
camlidl.1.05
on
4.11
had its build status changed:
passing
to
failing
camlidl.1.05
on
4.12
had its build status changed:
passing
to
failing
camlidl.1.05
on
4.13
had its build status changed:
passing
to
failing
camlp4.5.1
on
5.1
is now installable. Current state is:
failing
catala-format.0.1.0
on
4.08
is now installable. Current state is:
failing
catala-format.0.1.0
on
4.09
is now installable. Current state is:
failing
catala-format.0.1.0
on
4.10
is now installable. Current state is:
failing
catala-format.0.1.0
on
4.11
is now installable. Current state is:
failing
catala-format.0.1.0
on
4.12
is now installable. Current state is:
failing
catala-format.0.1.0
on
4.13
is now installable. Current state is:
failing
catala-format.0.1.0
on
4.14
is now installable. Current state is:
failing
catala-format.0.1.0
on
5.0
is now installable. Current state is:
failing
catala-format.0.1.0
on
5.1
is now installable. Current state is:
failing
catala-format.0.1.0
on
5.2
is now installable. Current state is:
failing
cca.0.1
on
4.11
had its build status changed:
partially failing
to
failing
cca.0.1
on
4.12
had its build status changed:
partially failing
to
failing
cca.0.2
on
4.11
had its build status changed:
partially failing
to
failing
cca.0.2
on
4.12
had its build status changed:
partially failing
to
failing
cca.0.2
on
4.13
had its build status changed:
partially failing
to
failing
cca.0.2
on
4.14
had its build status changed:
partially failing
to
failing
cca.0.4
on
4.11
had its build status changed:
partially failing
to
failing
cca.0.4
on
4.12
had its build status changed:
partially failing
to
failing
cca.0.4
on
4.13
had its build status changed:
partially failing
to
failing
cca.0.4
on
4.14
had its build status changed:
partially failing
to
failing
cca.0.5
on
4.11
had its build status changed:
partially failing
to
failing
cca.0.5
on
4.12
had its build status changed:
partially failing
to
failing
cca.0.5
on
4.13
had its build status changed:
partially failing
to
failing
cca.0.5
on
4.14
had its build status changed:
partially failing
to
failing
cca.0.6.2
on
4.14
had its build status changed:
partially failing
to
failing
cca.0.7
on
4.14
had its build status changed:
partially failing
to
failing
charrua-unix.1.0.0
on
4.08
had its build status changed:
partially failing
to
failing
charrua-unix.1.0.0
on
4.09
had its build status changed:
partially failing
to
failing
charrua-unix.1.0.0
on
4.10
had its build status changed:
partially failing
to
failing
charrua-unix.1.0.0
on
4.11
had its build status changed:
partially failing
to
failing
charset.0.1.0
on
5.1
had its build status changed:
partially failing
to
failing
charset.0.1.0
on
5.2
is now installable. Current state is:
failing
clangml.4.0.1
on
4.08
had its build status changed:
partially failing
to
failing
clangml.4.0.1
on
4.09
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
4.08
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
4.09
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
4.10
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
4.11
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
4.12
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
4.13
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
4.14
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
5.0
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
5.1
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.2
on
5.2
is now installable. Current state is:
failing
class_group_vdf.0.0.3
on
4.08
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.3
on
4.09
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.3
on
4.10
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.3
on
4.11
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.3
on
4.12
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.3
on
4.13
had its build status changed:
partially failing
to
failing
class_group_vdf.0.0.3
on
4.14
had its build status changed:
partially failing
to
failing
codept.0.11.0
on
4.08
had its build status changed:
partially failing
to
failing
codept.0.11.0
on
4.09
had its build status changed:
partially failing
to
failing
codept.0.11.0
on
4.10
had its build status changed:
partially failing
to
failing
codept.0.11.0
on
4.11
had its build status changed:
partially failing
to
failing
codept.0.11.0
on
4.12
had its build status changed:
partially failing
to
failing
codept.0.11.0
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.2.1.1
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.1.1
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.1.3
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.1.3
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.2.0
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.2.0
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.3.0
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.3.0
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.4.0
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.4.0
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.0
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.0
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.0
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.0
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.1
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.1
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.1
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.1
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.2-1
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.2-1
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.2-1
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.2-1
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.4
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.4
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.4
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.4
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.4
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.4
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.4
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.5
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.5
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.5
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.5
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.5
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.5
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.5
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.6
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.6
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.6
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.6
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.6
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.6
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.6
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.6
on
5.0
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.7
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.7
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.7
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.7
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.7
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.7
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.7
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.7
on
5.0
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.8
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.8
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.8
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.8
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.8
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.2.5.8
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.4.0.0
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.4.0.0
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.4.0.0
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.4.0.0
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.4.0.0
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.4.0.0
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.4.0.0
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.1
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.1
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.1
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.1
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.1
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.1
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.1
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.2
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.2
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.2
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.2
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.2
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.2
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.4.1.2
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.5.0.0
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.5.0.0
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.5.0.0
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.5.0.0
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.5.0.0
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.5.0.0
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.5.0.0
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.5.0.0
on
5.0
had its build status changed:
partially failing
to
failing
cohttp-async.5.1.0
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.5.1.0
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.5.1.0
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.5.1.0
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.5.1.0
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.5.1.0
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.5.1.0
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.5.1.0
on
5.0
had its build status changed:
partially failing
to
failing
cohttp-async.5.2.0
on
4.08
had its build status changed:
partially failing
to
failing
cohttp-async.5.2.0
on
4.09
had its build status changed:
partially failing
to
failing
cohttp-async.5.2.0
on
4.10
had its build status changed:
partially failing
to
failing
cohttp-async.5.2.0
on
4.11
had its build status changed:
partially failing
to
failing
cohttp-async.5.2.0
on
4.12
had its build status changed:
partially failing
to
failing
cohttp-async.5.2.0
on
4.13
had its build status changed:
partially failing
to
failing
cohttp-async.5.2.0
on
4.14
had its build status changed:
partially failing
to
failing
cohttp-async.5.2.0
on
5.0
had its build status changed:
partially failing
to
failing
cohttp-lwt.1.0.0
on
4.12
had its build status changed:
partially failing
to
failing
cohttp_async_websocket.v0.17.0
on
5.1
is now installable. Current state is:
failing
cohttp_async_websocket.v0.17.0
on
5.2
is now installable. Current state is:
failing
coin.0.1.0
on
4.08
had its build status changed:
partially failing
to
failing
coin.0.1.1
on
4.08
had its build status changed:
partially failing
to
failing
comby.1.2.2
on
4.08
had its build status changed:
partially failing
to
failing
comby.1.2.2
on
4.09
had its build status changed:
partially failing
to
failing
comby.1.2.2
on
4.10
had its build status changed:
partially failing
to
failing
comby.1.2.2
on
4.11
had its build status changed:
partially failing
to
failing
comby.1.2.2
on
4.12
had its build status changed:
partially failing
to
failing
comby.1.2.2
on
4.13
had its build status changed:
partially failing
to
failing
comby.1.2.2
on
4.14
had its build status changed:
partially failing
to
failing
comby.1.3.0
on
4.08
had its build status changed:
partially failing
to
failing
comby.1.3.0
on
4.09
had its build status changed:
partially failing
to
failing
comby.1.3.0
on
4.10
had its build status changed:
partially failing
to
failing
comby.1.3.0
on
4.11
had its build status changed:
partially failing
to
failing
comby.1.3.0
on
4.12
had its build status changed:
partially failing
to
failing
comby.1.3.0
on
4.13
had its build status changed:
partially failing
to
failing
comby.1.3.0
on
4.14
had its build status changed:
partially failing
to
failing
comby.1.4.0
on
4.08
had its build status changed:
partially failing
to
failing
comby.1.4.0
on
4.09
had its build status changed:
partially failing
to
failing
comby.1.4.0
on
4.10
had its build status changed:
partially failing
to
failing
comby.1.4.0
on
4.11
had its build status changed:
partially failing
to
failing
comby.1.4.0
on
4.12
had its build status changed:
partially failing
to
failing
comby.1.4.0
on
4.13
had its build status changed:
partially failing
to
failing
comby.1.4.0
on
4.14
had its build status changed:
partially failing
to
failing
comby.1.4.1
on
4.08
had its build status changed:
partially failing
to
failing
comby.1.4.1
on
4.09
had its build status changed:
partially failing
to
failing
comby.1.4.1
on
4.10
had its build status changed:
partially failing
to
failing
comby.1.4.1
on
4.11
had its build status changed:
partially failing
to
failing
comby.1.4.1
on
4.12
had its build status changed:
partially failing
to
failing
comby.1.4.1
on
4.13
had its build status changed:
partially failing
to
failing
comby.1.4.1
on
4.14
had its build status changed:
partially failing
to
failing
comby.1.7.0
on
4.08
had its build status changed:
partially failing
to
failing
comby.1.7.0
on
4.09
had its build status changed:
partially failing
to
failing
comby.1.7.0
on
4.10
had its build status changed:
partially failing
to
failing
comby.1.7.0
on
4.11
had its build status changed:
partially failing
to
failing
comby.1.7.0
on
4.12
had its build status changed:
partially failing
to
failing
comby.1.7.0
on
4.13
had its build status changed:
partially failing
to
failing
comby.1.7.0
on
4.14
had its build status changed:
partially failing
to
failing
conf-cuda.1
on
4.08
is now installable. Current state is:
failing
conf-cuda.1
on
4.09
is now installable. Current state is:
failing
conf-cuda.1
on
4.10
is now installable. Current state is:
failing
conf-cuda.1
on
4.11
is now installable. Current state is:
failing
conf-cuda.1
on
4.12
is now installable. Current state is:
failing
conf-cuda.1
on
4.13
is now installable. Current state is:
failing
conf-cuda.1
on
4.14
is now installable. Current state is:
failing
conf-cuda.1
on
5.0
is now installable. Current state is:
failing
conf-cuda.1
on
5.1
is now installable. Current state is:
failing
conf-cuda.1
on
5.2
is now installable. Current state is:
failing
conf-gmp-powm-sec.1
on
4.08
had its build status changed:
passing
to
failing
conf-gmp-powm-sec.1
on
4.09
had its build status changed:
passing
to
failing
conf-gmp-powm-sec.1
on
4.10
had its build status changed:
passing
to
failing
conf-gmp-powm-sec.1
on
4.11
had its build status changed:
passing
to
failing
conf-gmp-powm-sec.1
on
4.12
had its build status changed:
passing
to
failing
conf-gmp-powm-sec.1
on
4.13
had its build status changed:
passing
to
failing
conf-gmp-powm-sec.1
on
4.14
had its build status changed:
passing
to
failing
conf-gmp-powm-sec.1
on
5.0
had its build status changed:
passing
to
failing
conf-gmp-powm-sec.1
on
5.1
had its build status changed:
passing
to
failing
conf-gmp-powm-sec.1
on
5.2
is now installable. Current state is:
failing
conf-gmp.1
on
4.08
had its build status changed:
passing
to
failing
conf-gmp.1
on
4.09
had its build status changed:
passing
to
failing
conf-gmp.1
on
4.10
had its build status changed:
passing
to
failing
conf-gmp.1
on
4.11
had its build status changed:
passing
to
failing
conf-gmp.1
on
4.12
had its build status changed:
passing
to
failing
conf-gmp.1
on
4.13
had its build status changed:
passing
to
failing
conf-gmp.1
on
4.14
had its build status changed:
passing
to
failing
conf-gmp.1
on
5.0
had its build status changed:
passing
to
failing
conf-gmp.1
on
5.1
had its build status changed:
passing
to
failing
conf-gmp.1
on
5.2
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
4.08
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
4.09
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
4.10
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
4.11
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
4.12
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
4.13
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
4.14
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
5.0
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
5.1
is now installable. Current state is:
failing
conf-libblake3.1.5.1
on
5.2
is now installable. Current state is:
failing
conf-libclang.12
on
5.2
is now installable. Current state is:
failing
conf-libclang.15
on
5.2
is now installable. Current state is:
failing
conf-libgccjit.1
on
4.08
is now installable. Current state is:
failing
conf-libgccjit.1
on
4.09
is now installable. Current state is:
failing
conf-libgccjit.1
on
4.10
is now installable. Current state is:
failing
conf-libgccjit.1
on
4.11
is now installable. Current state is:
failing
conf-libgccjit.1
on
4.12
is now installable. Current state is:
failing
conf-libgccjit.1
on
4.13
is now installable. Current state is:
failing
conf-libgccjit.1
on
4.14
is now installable. Current state is:
failing
conf-libgccjit.1
on
5.0
is now installable. Current state is:
failing
conf-libgccjit.1
on
5.1
is now installable. Current state is:
failing
conf-libgccjit.1
on
5.2
is now installable. Current state is:
failing
conf-trexio.0.1
on
5.2
is now installable. Current state is:
failing
core_profiler.v0.12.0
on
4.08
had its build status changed:
partially failing
to
failing
core_profiler.v0.12.0
on
4.09
had its build status changed:
partially failing
to
failing
core_profiler.v0.13.0
on
4.08
had its build status changed:
partially failing
to
failing
core_profiler.v0.13.0
on
4.09
had its build status changed:
partially failing
to
failing
core_profiler.v0.13.0
on
4.10
had its build status changed:
partially failing
to
failing
core_profiler.v0.13.0
on
4.11
had its build status changed:
partially failing
to
failing
core_profiler.v0.14.0
on
4.08
had its build status changed:
partially failing
to
failing
core_profiler.v0.14.0
on
4.09
had its build status changed:
partially failing
to
failing
core_profiler.v0.14.0
on
4.10
had its build status changed:
partially failing
to
failing
core_profiler.v0.14.0
on
4.11
had its build status changed:
partially failing
to
failing
core_profiler.v0.14.0
on
4.12
had its build status changed:
partially failing
to
failing
core_profiler.v0.14.0
on
4.13
had its build status changed:
partially failing
to
failing
core_profiler.v0.14.0
on
4.14
had its build status changed:
partially failing
to
failing
core_profiler.v0.15.0
on
4.11
had its build status changed:
partially failing
to
failing
core_profiler.v0.15.0
on
4.12
had its build status changed:
partially failing
to
failing
core_profiler.v0.15.0
on
4.13
had its build status changed:
partially failing
to
failing
core_profiler.v0.15.0
on
4.14
had its build status changed:
partially failing
to
failing
core_profiler.v0.15.0
on
5.0
had its build status changed:
partially failing
to
failing
crypt.1.3
on
4.08
had its build status changed:
passing
to
failing
crypt.1.3
on
4.09
had its build status changed:
passing
to
failing
crypt.1.3
on
4.10
had its build status changed:
passing
to
failing
crypt.1.3
on
4.11
had its build status changed:
passing
to
failing
crypt.1.3
on
4.12
had its build status changed:
passing
to
failing
crypt.1.3
on
4.13
had its build status changed:
passing
to
failing
crypt.1.3
on
4.14
had its build status changed:
passing
to
failing
crypt.1.3
on
5.0
had its build status changed:
passing
to
failing
crypt.1.3
on
5.1
had its build status changed:
passing
to
failing
crypt.1.3
on
5.2
is now installable. Current state is:
failing
datakit-client-9p.0.12.0
on
4.12
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.0
on
4.13
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.2
on
4.08
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.2
on
4.09
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.2
on
4.10
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.2
on
4.11
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.2
on
4.12
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.2
on
4.13
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.3
on
4.08
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.3
on
4.09
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.3
on
4.10
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.3
on
4.11
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.3
on
4.12
had its build status changed:
partially failing
to
failing
datakit-client-9p.0.12.3
on
4.13
had its build status changed:
partially failing
to
failing
datakit-client-9p.1.0.0
on
4.08
had its build status changed:
partially failing
to
failing
datakit-client-9p.1.0.0
on
4.09
had its build status changed:
partially failing
to
failing
datakit-client-9p.1.0.0
on
4.10
had its build status changed:
partially failing
to
failing
datakit-client-9p.1.0.0
on
4.11
had its build status changed:
partially failing
to
failing
datakit-client-9p.1.0.0
on
4.12
had its build status changed:
partially failing
to
failing
datakit-client-9p.1.0.0
on
4.13
had its build status changed:
partially failing
to
failing
devkit.0.6
on
4.08
had its build status changed:
partially failing
to
failing
devkit.0.6
on
4.09
had its build status changed:
partially failing
to
failing
devkit.0.6
on
4.10
had its build status changed:
partially failing
to
failing
devkit.0.6
on
4.11
had its build status changed:
partially failing
to
failing
devkit.0.7
on
4.08
had its build status changed:
partially failing
to
failing
devkit.0.7
on
4.09
had its build status changed:
partially failing
to
failing
devkit.0.7
on
4.10
had its build status changed:
partially failing
to
failing
devkit.0.7
on
4.11
had its build status changed:
partially failing
to
failing
devkit.1.0
on
4.08
had its build status changed:
partially failing
to
failing
devkit.1.0
on
4.09
had its build status changed:
partially failing
to
failing
devkit.1.0
on
4.10
had its build status changed:
partially failing
to
failing
devkit.1.0
on
4.11
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
4.08
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
4.09
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
4.10
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
4.11
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
4.12
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
4.13
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
4.14
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
5.0
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
5.1
had its build status changed:
partially failing
to
failing
dssi.0.1.3
on
5.2
is now installable. Current state is:
failing
dssi.0.1.4
on
4.08
had its build status changed:
partially failing
to
failing
dssi.0.1.4
on
4.09
had its build status changed:
partially failing
to
failing
dssi.0.1.4
on
4.10
had its build status changed:
partially failing
to
failing
dssi.0.1.4
on
4.11
had its build status changed:
partially failing
to
failing
dssi.0.1.4
on
4.12
had its build status changed:
partially failing
to
failing
dssi.0.1.4
on
4.13
had its build status changed:
partially failing
to
failing
dssi.0.1.4
on
4.14
had its build status changed:
partially failing
to
failing
dssi.0.1.4
on
5.0
had its build status changed:
partially failing
to
failing
dssi.0.1.4
on
5.1
had its build status changed:
partially failing
to
failing
dssi.0.1.4
on
5.2
is now installable. Current state is:
failing
easy_logging_yojson.0.4
on
4.08
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.4
on
4.09
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.4
on
4.10
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.4
on
4.11
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.4
on
4.12
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.08
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.09
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.10
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.11
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.12
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5.2
on
4.08
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5.2
on
4.09
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5.2
on
4.10
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5.2
on
4.11
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5.2
on
4.12
had its build status changed:
partially failing
to
failing
efl.1.12.0
on
4.08
is now installable. Current state is:
failing
efl.1.12.0
on
4.09
is now installable. Current state is:
failing
efl.1.12.0
on
4.10
is now installable. Current state is:
failing
efl.1.12.0
on
4.11
is now installable. Current state is:
failing
efl.1.12.0
on
4.12
is now installable. Current state is:
failing
efl.1.12.0
on
4.13
is now installable. Current state is:
failing
efl.1.12.0
on
4.14
is now installable. Current state is:
failing
efl.1.12.0
on
5.0
is now installable. Current state is:
failing
efl.1.12.0
on
5.1
is now installable. Current state is:
failing
efl.1.12.0
on
5.2
is now installable. Current state is:
failing
efl.1.13.0
on
4.08
is now installable. Current state is:
failing
efl.1.13.0
on
4.09
is now installable. Current state is:
failing
efl.1.13.0
on
4.10
is now installable. Current state is:
failing
efl.1.13.0
on
4.11
is now installable. Current state is:
failing
efl.1.13.0
on
4.12
is now installable. Current state is:
failing
efl.1.13.0
on
4.13
is now installable. Current state is:
failing
efl.1.13.0
on
4.14
is now installable. Current state is:
failing
efl.1.13.0
on
5.0
is now installable. Current state is:
failing
efl.1.13.0
on
5.1
is now installable. Current state is:
failing
efl.1.13.0
on
5.2
is now installable. Current state is:
failing
efl.1.17.0
on
4.08
is now installable. Current state is:
failing
efl.1.17.0
on
4.09
is now installable. Current state is:
failing
efl.1.17.0
on
4.10
is now installable. Current state is:
failing
efl.1.17.0
on
4.11
is now installable. Current state is:
failing
efl.1.17.0
on
4.12
is now installable. Current state is:
failing
efl.1.17.0
on
4.13
is now installable. Current state is:
failing
efl.1.17.0
on
4.14
is now installable. Current state is:
failing
efl.1.17.0
on
5.0
is now installable. Current state is:
failing
efl.1.17.0
on
5.1
is now installable. Current state is:
failing
efl.1.17.0
on
5.2
is now installable. Current state is:
failing
efl.1.18.0
on
4.08
is now installable. Current state is:
failing
efl.1.18.0
on
4.09
is now installable. Current state is:
failing
efl.1.18.0
on
4.10
is now installable. Current state is:
failing
efl.1.18.0
on
4.11
is now installable. Current state is:
failing
efl.1.18.0
on
4.12
is now installable. Current state is:
failing
efl.1.18.0
on
4.13
is now installable. Current state is:
failing
efl.1.18.0
on
4.14
is now installable. Current state is:
failing
efl.1.18.0
on
5.0
is now installable. Current state is:
failing
efl.1.18.0
on
5.1
is now installable. Current state is:
failing
efl.1.18.0
on
5.2
is now installable. Current state is:
failing
efl.1.19.0
on
4.08
is now installable. Current state is:
failing
efl.1.19.0
on
4.09
is now installable. Current state is:
failing
efl.1.19.0
on
4.10
is now installable. Current state is:
failing
efl.1.19.0
on
4.11
is now installable. Current state is:
failing
efl.1.19.0
on
4.12
is now installable. Current state is:
failing
efl.1.19.0
on
4.13
is now installable. Current state is:
failing
efl.1.19.0
on
4.14
is now installable. Current state is:
failing
efl.1.19.0
on
5.0
is now installable. Current state is:
failing
efl.1.19.0
on
5.1
is now installable. Current state is:
failing
efl.1.19.0
on
5.2
is now installable. Current state is:
failing
efl.1.20.0
on
4.08
is now installable. Current state is:
failing
efl.1.20.0
on
4.09
is now installable. Current state is:
failing
efl.1.20.0
on
4.10
is now installable. Current state is:
failing
efl.1.20.0
on
4.11
is now installable. Current state is:
failing
efl.1.20.0
on
4.12
is now installable. Current state is:
failing
efl.1.20.0
on
4.13
is now installable. Current state is:
failing
efl.1.20.0
on
4.14
is now installable. Current state is:
failing
efl.1.20.0
on
5.0
is now installable. Current state is:
failing
efl.1.20.0
on
5.1
is now installable. Current state is:
failing
efl.1.20.0
on
5.2
is now installable. Current state is:
failing
efl.1.22.0
on
4.08
is now installable. Current state is:
failing
efl.1.22.0
on
4.09
is now installable. Current state is:
failing
efl.1.22.0
on
4.10
is now installable. Current state is:
failing
efl.1.22.0
on
4.11
is now installable. Current state is:
failing
efl.1.22.0
on
4.12
is now installable. Current state is:
failing
efl.1.22.0
on
4.13
is now installable. Current state is:
failing
efl.1.22.0
on
4.14
is now installable. Current state is:
failing
efl.1.22.0
on
5.0
is now installable. Current state is:
failing
efl.1.22.0
on
5.1
is now installable. Current state is:
failing
efl.1.22.0
on
5.2
is now installable. Current state is:
failing
efl.1.24.0
on
4.08
is now installable. Current state is:
failing
efl.1.24.0
on
4.09
is now installable. Current state is:
failing
efl.1.24.0
on
4.10
is now installable. Current state is:
failing
efl.1.24.0
on
4.11
is now installable. Current state is:
failing
efl.1.24.0
on
4.12
is now installable. Current state is:
failing
efl.1.24.0
on
4.13
is now installable. Current state is:
failing
efl.1.24.0
on
4.14
is now installable. Current state is:
failing
efl.1.24.0
on
5.0
is now installable. Current state is:
failing
efl.1.24.0
on
5.1
is now installable. Current state is:
failing
efl.1.24.0
on
5.2
is now installable. Current state is:
failing
eigen.0.1.4
on
5.1
had its build status changed:
partially failing
to
failing
eigen.0.1.4
on
5.2
is now installable. Current state is:
failing
eigen.0.1.5
on
5.1
had its build status changed:
partially failing
to
failing
eigen.0.1.5
on
5.2
is now installable. Current state is:
failing
elina.1.0
on
4.08
had its build status changed:
partially failing
to
failing
elina.1.0
on
4.09
had its build status changed:
partially failing
to
failing
elina.1.0
on
4.10
had its build status changed:
partially failing
to
failing
elina.1.0
on
4.11
had its build status changed:
partially failing
to
failing
elina.1.0
on
4.12
had its build status changed:
partially failing
to
failing
elina.1.0
on
4.13
had its build status changed:
partially failing
to
failing
elina.1.0
on
4.14
had its build status changed:
partially failing
to
failing
elina.1.0
on
5.0
had its build status changed:
partially failing
to
failing
elina.1.0
on
5.1
had its build status changed:
partially failing
to
failing
elina.1.0
on
5.2
is now installable. Current state is:
failing
elina.1.1
on
4.08
had its build status changed:
partially failing
to
failing
elina.1.1
on
4.09
had its build status changed:
partially failing
to
failing
elina.1.1
on
4.10
had its build status changed:
partially failing
to
failing
elina.1.1
on
4.11
had its build status changed:
partially failing
to
failing
elina.1.1
on
4.12
had its build status changed:
partially failing
to
failing
elina.1.1
on
4.13
had its build status changed:
partially failing
to
failing
elina.1.1
on
4.14
had its build status changed:
partially failing
to
failing
elina.1.1
on
5.0
had its build status changed:
partially failing
to
failing
elina.1.1
on
5.1
had its build status changed:
partially failing
to
failing
elina.1.1
on
5.2
is now installable. Current state is:
failing
elina.1.3
on
4.08
had its build status changed:
internal failure
to
failing
elina.1.3
on
4.09
had its build status changed:
internal failure
to
failing
elina.1.3
on
4.10
had its build status changed:
internal failure
to
failing
elina.1.3
on
4.11
had its build status changed:
internal failure
to
failing
elina.1.3
on
4.12
had its build status changed:
internal failure
to
failing
elina.1.3
on
4.13
had its build status changed:
internal failure
to
failing
elina.1.3
on
4.14
had its build status changed:
internal failure
to
failing
elina.1.3
on
5.0
had its build status changed:
internal failure
to
failing
elina.1.3
on
5.1
had its build status changed:
internal failure
to
failing
elina.1.3
on
5.2
is now installable. Current state is:
failing
elina.1.3.1
on
4.08
had its build status changed:
partially failing
to
failing
elina.1.3.1
on
4.09
had its build status changed:
partially failing
to
failing
elina.1.3.1
on
4.10
had its build status changed:
partially failing
to
failing
elina.1.3.1
on
4.11
had its build status changed:
partially failing
to
failing
elina.1.3.1
on
4.12
had its build status changed:
partially failing
to
failing
elina.1.3.1
on
4.13
had its build status changed:
partially failing
to
failing
elina.1.3.1
on
4.14
had its build status changed:
partially failing
to
failing
elina.1.3.1
on
5.0
had its build status changed:
partially failing
to
failing
elina.1.3.1
on
5.1
had its build status changed:
partially failing
to
failing
elina.1.3.1
on
5.2
is now installable. Current state is:
failing
elina.1.3.2
on
4.08
had its build status changed:
partially failing
to
failing
elina.1.3.2
on
4.09
had its build status changed:
partially failing
to
failing
elina.1.3.2
on
4.10
had its build status changed:
partially failing
to
failing
elina.1.3.2
on
4.11
had its build status changed:
partially failing
to
failing
elina.1.3.2
on
4.12
had its build status changed:
partially failing
to
failing
elina.1.3.2
on
4.13
had its build status changed:
partially failing
to
failing
elina.1.3.2
on
4.14
had its build status changed:
partially failing
to
failing
elina.1.3.2
on
5.0
had its build status changed:
partially failing
to
failing
elina.1.3.2
on
5.1
had its build status changed:
partially failing
to
failing
elina.1.3.2
on
5.2
is now installable. Current state is:
failing
eliom.6.11.0
on
4.08
had its build status changed:
partially failing
to
failing
eliom.6.11.0
on
4.09
had its build status changed:
partially failing
to
failing
eliom.6.11.0
on
4.10
had its build status changed:
partially failing
to
failing
eliom.6.12.0
on
4.08
had its build status changed:
partially failing
to
failing
eliom.6.12.0
on
4.09
had its build status changed:
partially failing
to
failing
eliom.6.12.0
on
4.10
had its build status changed:
partially failing
to
failing
eliom.6.12.1
on
4.08
had its build status changed:
partially failing
to
failing
eliom.6.12.1
on
4.09
had its build status changed:
partially failing
to
failing
eliom.6.12.1
on
4.10
had its build status changed:
partially failing
to
failing
eliom.6.12.1
on
4.11
had its build status changed:
partially failing
to
failing
eliom.6.12.4
on
4.08
had its build status changed:
partially failing
to
failing
eliom.6.12.4
on
4.09
had its build status changed:
partially failing
to
failing
eliom.6.12.4
on
4.10
had its build status changed:
partially failing
to
failing
eliom.6.12.4
on
4.11
had its build status changed:
partially failing
to
failing
eliom.6.13.1
on
4.08
had its build status changed:
partially failing
to
failing
eliom.6.13.1
on
4.09
had its build status changed:
partially failing
to
failing
eliom.6.13.1
on
4.10
had its build status changed:
partially failing
to
failing
eliom.6.13.1
on
4.11
had its build status changed:
partially failing
to
failing
eliom.7.0.0
on
4.08
had its build status changed:
partially failing
to
failing
eliom.7.0.0
on
4.09
had its build status changed:
partially failing
to
failing
eliom.7.0.0
on
4.10
had its build status changed:
partially failing
to
failing
eliom.7.0.0
on
4.11
had its build status changed:
partially failing
to
failing
eliom.7.0.0
on
4.12
had its build status changed:
partially failing
to
failing
eliom.8.4.8
on
4.08
had its build status changed:
partially failing
to
failing
eliom.8.4.8
on
4.09
had its build status changed:
partially failing
to
failing
eliom.8.4.8
on
4.10
had its build status changed:
partially failing
to
failing
eliom.8.4.8
on
4.11
had its build status changed:
partially failing
to
failing
eliom.8.4.8
on
4.12
had its build status changed:
partially failing
to
failing
eliom.8.6.0
on
4.08
had its build status changed:
partially failing
to
failing
eliom.8.6.0
on
4.09
had its build status changed:
partially failing
to
failing
eliom.8.6.0
on
4.10
had its build status changed:
partially failing
to
failing
eliom.8.6.0
on
4.11
had its build status changed:
partially failing
to
failing
eliom.8.6.0
on
4.12
had its build status changed:
partially failing
to
failing
eliom.8.8.0
on
4.08
had its build status changed:
partially failing
to
failing
eliom.8.8.0
on
4.09
had its build status changed:
partially failing
to
failing
eliom.8.8.0
on
4.10
had its build status changed:
partially failing
to
failing
eliom.8.8.0
on
4.11
had its build status changed:
partially failing
to
failing
eliom.8.8.0
on
4.12
had its build status changed:
partially failing
to
failing
eliom.8.8.1
on
4.08
had its build status changed:
partially failing
to
failing
eliom.8.8.1
on
4.09
had its build status changed:
partially failing
to
failing
eliom.8.8.1
on
4.10
had its build status changed:
partially failing
to
failing
eliom.8.8.1
on
4.11
had its build status changed:
partially failing
to
failing
eliom.8.8.1
on
4.12
had its build status changed:
partially failing
to
failing
elpi.1.14.3
on
4.10
had its build status changed:
partially failing
to
failing
elpi.1.14.3
on
4.11
had its build status changed:
partially failing
to
failing
elpi.1.14.3
on
4.12
had its build status changed:
partially failing
to
failing
elpi.1.14.3
on
4.13
had its build status changed:
partially failing
to
failing
errpy.0.0.10
on
5.2
is now installable. Current state is:
failing
errpy.0.0.7
on
5.1
had its build status changed:
partially failing
to
failing
errpy.0.0.8
on
5.1
had its build status changed:
partially failing
to
failing
errpy.0.0.9
on
5.1
had its build status changed:
partially failing
to
failing
esperanto.0.0.1
on
4.13
had its build status changed:
passing
to
failing
esperanto.0.0.2
on
4.13
had its build status changed:
passing
to
failing
esperanto.0.0.2
on
4.14
had its build status changed:
passing
to
failing
esperanto.0.0.3
on
4.13
had its build status changed:
passing
to
failing
esperanto.0.0.3
on
4.14
had its build status changed:
passing
to
failing
esperanto.0.0.4
on
4.13
had its build status changed:
passing
to
failing
esperanto.0.0.4
on
4.14
had its build status changed:
passing
to
failing
extprot.1.7.0
on
5.0
had its build status changed:
partially failing
to
failing
ezdl.2.71.10
on
5.0
had its build status changed:
partially failing
to
failing
ezdl.2.71.10
on
5.1
had its build status changed:
partially failing
to
failing
ezdl.2.71.10
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.0.0
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.0.0~beta1
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta1
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta1
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta1
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta1
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta1
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta1
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta1
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta1
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta1
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.0.0~beta2
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta2
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta2
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta2
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta2
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta2
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta2
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta2
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta2
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~beta2
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.0.0~rc1
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~rc1
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~rc1
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~rc1
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~rc1
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~rc1
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~rc1
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~rc1
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~rc1
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.0~rc1
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.0.1
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.1
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.1
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.1
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.1
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.1
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.1
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.1
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.1
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.0.1
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.0
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.0
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.0
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.0
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.0
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.0
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.0
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.0
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.0
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.0
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.1
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.1
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.1
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.1
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.1
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.1
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.1
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.1
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.1
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.1
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
4.08
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
4.09
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
4.10
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
4.11
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
4.12
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
4.13
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
4.14
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
5.0
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
5.1
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.10
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
4.08
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
4.09
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
4.10
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
4.11
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
4.12
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
4.13
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
4.14
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
5.0
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
5.1
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.11
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.2
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.2
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.2
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.2
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.2
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.2
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.2
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.2
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.2
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.2
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.3
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.3
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.3
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.3
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.3
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.3
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.3
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.3
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.3
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.3
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.4
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.4
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.4
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.4
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.4
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.4
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.4
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.4
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.4
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.4
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.5
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.5
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.5
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.5
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.5
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.5
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.5
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.5
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.5
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.5
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.6
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.6
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.6
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.6
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.6
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.6
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.6
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.6
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.6
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.6
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.7
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.7
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.7
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.7
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.7
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.7
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.7
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.7
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.7
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.7
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.8
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.8
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.8
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.8
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.8
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.8
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.8
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.8
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.8
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.8
on
5.2
is now installable. Current state is:
failing
ffmpeg-avutil.1.1.9
on
4.08
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.9
on
4.09
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.9
on
4.10
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.9
on
4.11
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.9
on
4.12
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.9
on
4.13
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.9
on
4.14
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.9
on
5.0
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.9
on
5.1
had its build status changed:
partially failing
to
failing
ffmpeg-avutil.1.1.9
on
5.2
is now installable. Current state is:
failing
ffmpeg.0.4.2
on
4.08
had its build status changed:
passing
to
failing
ffmpeg.0.4.2
on
4.09
had its build status changed:
passing
to
failing
ffmpeg.0.4.2
on
4.10
had its build status changed:
passing
to
failing
ffmpeg.0.4.2
on
4.11
had its build status changed:
passing
to
failing
ffmpeg.0.4.2
on
4.12
had its build status changed:
passing
to
failing
ffmpeg.0.4.2
on
4.13
had its build status changed:
passing
to
failing
ffmpeg.0.4.2
on
4.14
had its build status changed:
passing
to
failing
ffmpeg.0.4.3
on
4.08
had its build status changed:
passing
to
failing
ffmpeg.0.4.3
on
4.09
had its build status changed:
passing
to
failing
ffmpeg.0.4.3
on
4.10
had its build status changed:
passing
to
failing
ffmpeg.0.4.3
on
4.11
had its build status changed:
passing
to
failing
ffmpeg.0.4.3
on
4.12
had its build status changed:
passing
to
failing
ffmpeg.0.4.3
on
4.13
had its build status changed:
passing
to
failing
ffmpeg.0.4.3
on
4.14
had its build status changed:
passing
to
failing
frama-c.22.0
on
4.08
had its build status changed:
partially failing
to
failing
frama-c.22.0
on
4.09
had its build status changed:
partially failing
to
failing
frama-c.22.0
on
4.10
had its build status changed:
partially failing
to
failing
frama-c.22.0
on
4.11
had its build status changed:
partially failing
to
failing
frama-c.22.0
on
4.12
had its build status changed:
partially failing
to
failing
frama-c.22.0
on
4.13
had its build status changed:
partially failing
to
failing
frama-c.22.0
on
4.14
had its build status changed:
partially failing
to
failing
freetds.0.4
on
5.0
had its build status changed:
passing
to
failing
freetds.0.4
on
5.1
had its build status changed:
passing
to
failing
freetds.0.4
on
5.2
is now installable. Current state is:
failing
freetds.0.4.1
on
5.0
had its build status changed:
passing
to
failing
freetds.0.4.1
on
5.1
had its build status changed:
passing
to
failing
freetds.0.4.1
on
5.2
is now installable. Current state is:
failing
freetds.0.4.2
on
5.0
had its build status changed:
passing
to
failing
freetds.0.4.2
on
5.1
had its build status changed:
passing
to
failing
freetds.0.4.2
on
5.2
is now installable. Current state is:
failing
freetds.0.5
on
5.0
had its build status changed:
passing
to
failing
freetds.0.5
on
5.1
had its build status changed:
passing
to
failing
freetds.0.5
on
5.2
is now installable. Current state is:
failing
freetds.0.5.1
on
5.0
had its build status changed:
passing
to
failing
freetds.0.5.1
on
5.1
had its build status changed:
passing
to
failing
freetds.0.5.1
on
5.2
is now installable. Current state is:
failing
frei0r.0.1.0
on
4.08
had its build status changed:
passing
to
failing
frei0r.0.1.0
on
4.09
had its build status changed:
passing
to
failing
frei0r.0.1.0
on
4.10
had its build status changed:
passing
to
failing
frei0r.0.1.0
on
4.11
had its build status changed:
passing
to
failing
frei0r.0.1.0
on
4.12
had its build status changed:
passing
to
failing
frei0r.0.1.0
on
4.13
had its build status changed:
passing
to
failing
frei0r.0.1.0
on
4.14
had its build status changed:
passing
to
failing
frei0r.0.1.0
on
5.0
had its build status changed:
passing
to
failing
frei0r.0.1.0
on
5.1
had its build status changed:
passing
to
failing
frei0r.0.1.0
on
5.2
is now installable. Current state is:
failing
frenetic.5.0.5
on
4.11
had its build status changed:
partially failing
to
failing
frenetic.5.0.5
on
4.12
had its build status changed:
partially failing
to
failing
frenetic.5.0.5
on
4.13
had its build status changed:
partially failing
to
failing
frenetic.5.0.5
on
4.14
had its build status changed:
partially failing
to
failing
gadelac.0.6
on
5.0
had its build status changed:
partially failing
to
failing
gadelac.0.6
on
5.1
had its build status changed:
partially failing
to
failing
gadelac.0.6
on
5.2
is now installable. Current state is:
failing
gdbprofiler.0.3
on
4.12
had its build status changed:
partially failing
to
failing
genprint.0.3
on
4.08
had its build status changed:
partially failing
to
failing
genprint.0.3
on
4.09
had its build status changed:
partially failing
to
failing
genprint.0.3
on
4.10
had its build status changed:
partially failing
to
failing
git-unix.3.2.0
on
4.08
had its build status changed:
partially failing
to
failing
git-unix.3.2.0
on
4.09
had its build status changed:
partially failing
to
failing
git-unix.3.2.0
on
4.10
had its build status changed:
partially failing
to
failing
git-unix.3.2.0
on
4.11
had its build status changed:
partially failing
to
failing
git-unix.3.2.0
on
4.12
had its build status changed:
partially failing
to
failing
git-unix.3.3.0
on
4.08
had its build status changed:
partially failing
to
failing
git-unix.3.3.0
on
4.09
had its build status changed:
partially failing
to
failing
git-unix.3.3.0
on
4.10
had its build status changed:
partially failing
to
failing
git-unix.3.3.0
on
4.11
had its build status changed:
partially failing
to
failing
git-unix.3.3.0
on
4.12
had its build status changed:
partially failing
to
failing
git-unix.3.3.1
on
4.08
had its build status changed:
partially failing
to
failing
git-unix.3.3.1
on
4.09
had its build status changed:
partially failing
to
failing
git-unix.3.3.1
on
4.10
had its build status changed:
partially failing
to
failing
git-unix.3.3.1
on
4.11
had its build status changed:
partially failing
to
failing
git-unix.3.3.1
on
4.12
had its build status changed:
partially failing
to
failing
git-unix.3.3.2
on
4.08
had its build status changed:
partially failing
to
failing
git-unix.3.3.2
on
4.09
had its build status changed:
partially failing
to
failing
git-unix.3.3.2
on
4.10
had its build status changed:
partially failing
to
failing
git-unix.3.3.2
on
4.11
had its build status changed:
partially failing
to
failing
git-unix.3.3.2
on
4.12
had its build status changed:
partially failing
to
failing
git-unix.3.3.3
on
4.08
had its build status changed:
partially failing
to
failing
git-unix.3.3.3
on
4.09
had its build status changed:
partially failing
to
failing
git-unix.3.3.3
on
4.10
had its build status changed:
partially failing
to
failing
git-unix.3.3.3
on
4.11
had its build status changed:
partially failing
to
failing
git-unix.3.3.3
on
4.12
had its build status changed:
partially failing
to
failing
glMLite.0.03.53
on
4.08
had its build status changed:
passing
to
failing
glMLite.0.03.53
on
4.09
had its build status changed:
passing
to
failing
glMLite.0.03.53
on
4.10
had its build status changed:
passing
to
failing
glMLite.0.03.53
on
4.11
had its build status changed:
passing
to
failing
glMLite.0.03.53
on
4.12
had its build status changed:
passing
to
failing
glMLite.0.03.53
on
4.13
had its build status changed:
passing
to
failing
glMLite.0.03.53
on
4.14
had its build status changed:
passing
to
failing
gluon.0.0.8
on
5.2
is now installable. Current state is:
failing
gluon.0.0.9
on
5.2
is now installable. Current state is:
failing
gmp-xen.6.0.0
on
4.08
had its build status changed:
passing
to
failing
gmp-xen.6.0.0
on
4.09
had its build status changed:
passing
to
failing
gmp-xen.6.0.0
on
4.10
had its build status changed:
passing
to
failing
gmp-xen.6.0.0
on
4.11
had its build status changed:
passing
to
failing
gmp-xen.6.0.0
on
4.12
had its build status changed:
passing
to
failing
gmp-xen.6.0.0
on
4.13
had its build status changed:
passing
to
failing
gmp-xen.6.0.0
on
4.14
had its build status changed:
passing
to
failing
gmp-xen.6.0.0
on
5.0
had its build status changed:
passing
to
failing
gmp-xen.6.0.0
on
5.1
had its build status changed:
passing
to
failing
gmp-xen.6.0.0
on
5.2
is now installable. Current state is:
failing
gmp-xen.6.0.0-1
on
4.08
had its build status changed:
passing
to
failing
gmp-xen.6.0.0-1
on
4.09
had its build status changed:
passing
to
failing
gmp-xen.6.0.0-1
on
4.10
had its build status changed:
passing
to
failing
gmp-xen.6.0.0-1
on
4.11
had its build status changed:
passing
to
failing
gmp-xen.6.0.0-1
on
4.12
had its build status changed:
passing
to
failing
gmp-xen.6.0.0-1
on
4.13
had its build status changed:
passing
to
failing
gmp-xen.6.0.0-1
on
4.14
had its build status changed:
passing
to
failing
gmp-xen.6.0.0-1
on
5.0
had its build status changed:
passing
to
failing
gmp-xen.6.0.0-1
on
5.1
had its build status changed:
passing
to
failing
gmp-xen.6.0.0-1
on
5.2
is now installable. Current state is:
failing
graphql.0.1.0
on
4.12
had its build status changed:
partially failing
to
failing
graphql.0.2.0
on
4.12
had its build status changed:
partially failing
to
failing
graphql.0.4.0
on
4.12
had its build status changed:
partially failing
to
failing
graphql.0.5.0
on
4.12
had its build status changed:
partially failing
to
failing
graphql.0.6.0
on
4.12
had its build status changed:
partially failing
to
failing
graphql.0.7.0
on
4.12
had its build status changed:
partially failing
to
failing
graphql.0.8.0
on
4.08
had its build status changed:
partially failing
to
failing
graphql.0.8.0
on
4.09
had its build status changed:
partially failing
to
failing
graphql.0.8.0
on
4.10
had its build status changed:
partially failing
to
failing
graphql.0.8.0
on
4.11
had its build status changed:
partially failing
to
failing
graphql.0.8.0
on
4.12
had its build status changed:
partially failing
to
failing
gsl.1.19.1
on
4.08
had its build status changed:
passing
to
failing
gsl.1.19.1
on
4.09
had its build status changed:
passing
to
failing
gsl.1.19.1
on
4.10
had its build status changed:
passing
to
failing
gsl.1.19.1
on
4.11
had its build status changed:
passing
to
failing
gsl.1.19.1
on
4.12
had its build status changed:
passing
to
failing
gsl.1.19.1
on
4.13
had its build status changed:
passing
to
failing
gsl.1.19.1
on
4.14
had its build status changed:
passing
to
failing
gsl.1.19.3
on
4.08
had its build status changed:
passing
to
failing
gsl.1.19.3
on
4.09
had its build status changed:
passing
to
failing
gsl.1.19.3
on
4.10
had its build status changed:
passing
to
failing
gsl.1.19.3
on
4.11
had its build status changed:
passing
to
failing
gsl.1.19.3
on
4.12
had its build status changed:
passing
to
failing
gsl.1.19.3
on
4.13
had its build status changed:
passing
to
failing
gsl.1.19.3
on
4.14
had its build status changed:
passing
to
failing
guile.1.0
on
4.08
had its build status changed:
partially failing
to
failing
guile.1.0
on
4.09
had its build status changed:
partially failing
to
failing
guile.1.0
on
4.10
had its build status changed:
partially failing
to
failing
guile.1.0
on
4.11
had its build status changed:
partially failing
to
failing
guile.1.0
on
4.12
had its build status changed:
partially failing
to
failing
guile.1.0
on
4.13
had its build status changed:
partially failing
to
failing
guile.1.0
on
4.14
had its build status changed:
partially failing
to
failing
guile.1.0
on
5.0
had its build status changed:
partially failing
to
failing
guile.1.0
on
5.1
had its build status changed:
partially failing
to
failing
guile.1.0
on
5.2
is now installable. Current state is:
failing
hack_parallel.0.1.1
on
4.08
had its build status changed:
partially failing
to
failing
hack_parallel.0.1.1
on
4.09
had its build status changed:
partially failing
to
failing
hardcaml_waveterm.v0.15.0
on
4.11
had its build status changed:
partially failing
to
failing
hardcaml_waveterm.v0.15.0
on
4.12
had its build status changed:
partially failing
to
failing
hardcaml_waveterm.v0.15.0
on
4.13
had its build status changed:
partially failing
to
failing
hardcaml_waveterm.v0.15.0
on
4.14
had its build status changed:
partially failing
to
failing
hardcaml_waveterm.v0.15.0
on
5.0
had its build status changed:
partially failing
to
failing
haxe.4.1.1
on
4.08
had its build status changed:
partially failing
to
failing
haxe.4.1.1
on
4.09
had its build status changed:
partially failing
to
failing
haxe.4.1.1
on
4.10
had its build status changed:
partially failing
to
failing
haxe.4.1.1
on
4.11
had its build status changed:
partially failing
to
failing
haxe.4.1.1
on
4.12
had its build status changed:
partially failing
to
failing
haxe.4.1.1
on
4.13
had its build status changed:
partially failing
to
failing
haxe.4.1.1
on
4.14
had its build status changed:
partially failing
to
failing
index.1.2.1
on
4.08
had its build status changed:
partially failing
to
failing
index.1.2.1
on
4.09
had its build status changed:
partially failing
to
failing
index.1.2.1
on
4.10
had its build status changed:
partially failing
to
failing
index.1.2.1
on
4.11
had its build status changed:
partially failing
to
failing
inquire.0.3.1
on
5.0
had its build status changed:
partially failing
to
failing
inquire.0.3.1
on
5.1
had its build status changed:
partially failing
to
failing
inquire.0.3.1
on
5.2
is now installable. Current state is:
failing
irmin-test.2.0.0
on
4.08
had its build status changed:
partially failing
to
failing
irmin-test.2.0.0
on
4.09
had its build status changed:
partially failing
to
failing
irmin-test.2.0.0
on
4.10
had its build status changed:
partially failing
to
failing
irmin-test.2.0.0
on
4.11
had its build status changed:
partially failing
to
failing
irmin-test.2.0.0
on
4.12
had its build status changed:
partially failing
to
failing
irmin-test.2.0.0
on
4.13
had its build status changed:
partially failing
to
failing
janestreet_cpuid.v0.17.0
on
5.1
is now installable. Current state is:
failing
janestreet_cpuid.v0.17.0
on
5.2
is now installable. Current state is:
failing
jhupllib.0.1
on
4.08
had its build status changed:
partially failing
to
failing
jhupllib.0.1
on
4.09
had its build status changed:
partially failing
to
failing
jhupllib.0.1.1
on
4.08
had its build status changed:
partially failing
to
failing
jhupllib.0.1.1
on
4.09
had its build status changed:
partially failing
to
failing
jhupllib.0.2.1
on
4.08
had its build status changed:
partially failing
to
failing
jhupllib.0.2.1
on
4.09
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.1
on
4.08
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.1
on
4.09
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.1
on
4.10
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.1
on
4.11
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.1
on
4.12
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.1
on
4.13
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.1
on
4.14
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.2
on
4.08
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.2
on
4.09
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.2
on
4.10
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.2
on
4.11
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.2
on
4.12
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.2
on
4.13
had its build status changed:
partially failing
to
failing
js_of_ocaml-webidl.0.2
on
4.14
had its build status changed:
partially failing
to
failing
jupyter-kernel.0.4
on
4.08
had its build status changed:
partially failing
to
failing
jupyter-kernel.0.4
on
4.09
had its build status changed:
partially failing
to
failing
jupyter-kernel.0.4
on
4.10
had its build status changed:
partially failing
to
failing
jupyter-kernel.0.4
on
4.11
had its build status changed:
partially failing
to
failing
jupyter.2.6.0
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.6.1
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.6.1
on
4.09
had its build status changed:
partially failing
to
failing
jupyter.2.7.0
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.7.0
on
4.09
had its build status changed:
partially failing
to
failing
jupyter.2.7.0
on
4.10
had its build status changed:
partially failing
to
failing
jupyter.2.7.1
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.7.1
on
4.09
had its build status changed:
partially failing
to
failing
jupyter.2.7.1
on
4.10
had its build status changed:
partially failing
to
failing
jupyter.2.7.2
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.7.2
on
4.09
had its build status changed:
partially failing
to
failing
jupyter.2.7.2
on
4.10
had its build status changed:
partially failing
to
failing
jupyter.2.7.2
on
4.11
had its build status changed:
partially failing
to
failing
jupyter.2.7.3
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.7.3
on
4.09
had its build status changed:
partially failing
to
failing
jupyter.2.7.3
on
4.10
had its build status changed:
partially failing
to
failing
jupyter.2.7.3
on
4.11
had its build status changed:
partially failing
to
failing
jupyter.2.7.4
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.7.4
on
4.09
had its build status changed:
partially failing
to
failing
jupyter.2.7.4
on
4.10
had its build status changed:
partially failing
to
failing
jupyter.2.7.4
on
4.11
had its build status changed:
partially failing
to
failing
jupyter.2.7.4
on
4.12
had its build status changed:
partially failing
to
failing
jupyter.2.7.5
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.7.5
on
4.09
had its build status changed:
partially failing
to
failing
jupyter.2.7.5
on
4.10
had its build status changed:
partially failing
to
failing
jupyter.2.7.5
on
4.11
had its build status changed:
partially failing
to
failing
jupyter.2.7.5
on
4.12
had its build status changed:
partially failing
to
failing
jupyter.2.7.6
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.7.6
on
4.09
had its build status changed:
partially failing
to
failing
jupyter.2.7.6
on
4.10
had its build status changed:
partially failing
to
failing
jupyter.2.7.6
on
4.11
had its build status changed:
partially failing
to
failing
jupyter.2.7.6
on
4.12
had its build status changed:
partially failing
to
failing
jupyter.2.7.6
on
4.13
had its build status changed:
partially failing
to
failing
jupyter.2.7.7
on
4.08
had its build status changed:
partially failing
to
failing
jupyter.2.7.7
on
4.09
had its build status changed:
partially failing
to
failing
jupyter.2.7.7
on
4.10
had its build status changed:
partially failing
to
failing
jupyter.2.7.7
on
4.11
had its build status changed:
partially failing
to
failing
jupyter.2.7.7
on
4.12
had its build status changed:
partially failing
to
failing
jupyter.2.7.7
on
4.13
had its build status changed:
partially failing
to
failing
jupyter.2.7.8
on
4.10
had its build status changed:
partially failing
to
failing
jupyter.2.7.8
on
4.11
had its build status changed:
partially failing
to
failing
jupyter.2.7.8
on
4.12
had its build status changed:
partially failing
to
failing
jupyter.2.7.8
on
4.13
had its build status changed:
partially failing
to
failing
kafka_async.0.5
on
4.08
had its build status changed:
partially failing
to
failing
kafka_async.0.5
on
4.09
had its build status changed:
partially failing
to
failing
kafka_async.0.5
on
4.10
had its build status changed:
partially failing
to
failing
kafka_async.0.5
on
4.11
had its build status changed:
partially failing
to
failing
kafka_async.0.5
on
4.12
had its build status changed:
partially failing
to
failing
kafka_async.0.5
on
4.13
had its build status changed:
partially failing
to
failing
kafka_async.0.5
on
4.14
had its build status changed:
partially failing
to
failing
kappa-library.4.1.0
on
4.08
had its build status changed:
partially failing
to
failing
kappa-library.4.1.0
on
4.09
had its build status changed:
partially failing
to
failing
kappa-library.4.1.0
on
4.10
had its build status changed:
partially failing
to
failing
kappa-library.4.1.0
on
4.11
had its build status changed:
partially failing
to
failing
key-parsers.0.9.2
on
4.08
had its build status changed:
partially failing
to
failing
key-parsers.0.9.2
on
4.09
had its build status changed:
partially failing
to
failing
key-parsers.0.9.2
on
4.10
had its build status changed:
partially failing
to
failing
key-parsers.0.9.2
on
4.11
had its build status changed:
partially failing
to
failing
key-parsers.0.9.2
on
4.12
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.1
on
4.08
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.1
on
4.09
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.1
on
4.10
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.1
on
4.11
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.1
on
4.12
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.1
on
4.13
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.1
on
4.14
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.9
on
4.08
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.9
on
4.09
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.9
on
4.10
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.9
on
4.11
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.9
on
4.12
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.9
on
4.13
had its build status changed:
partially failing
to
failing
kinetic-client.0.0.9
on
4.14
had its build status changed:
partially failing
to
failing
lablgtk3-sourceview3.3.0.beta4
on
4.08
had its build status changed:
partially failing
to
failing
lablgtk3-sourceview3.3.0.beta5
on
4.08
had its build status changed:
partially failing
to
failing
lablgtk3-sourceview3.3.0.beta6
on
4.08
had its build status changed:
partially failing
to
failing
lablgtk3-sourceview3.3.0.beta7
on
4.08
had its build status changed:
partially failing
to
failing
lablgtk3-sourceview3.3.0.beta8
on
4.08
had its build status changed:
partially failing
to
failing
labltk.8.06.10
on
4.08
had its build status changed:
passing
to
failing
labltk.8.06.10
on
4.09
had its build status changed:
passing
to
failing
labltk.8.06.10
on
4.10
had its build status changed:
passing
to
failing
labltk.8.06.10
on
4.11
had its build status changed:
passing
to
failing
labltk.8.06.10
on
4.12
had its build status changed:
passing
to
failing
labltk.8.06.11
on
4.08
had its build status changed:
passing
to
failing
labltk.8.06.11
on
4.09
had its build status changed:
passing
to
failing
labltk.8.06.11
on
4.10
had its build status changed:
passing
to
failing
labltk.8.06.11
on
4.11
had its build status changed:
passing
to
failing
labltk.8.06.11
on
4.12
had its build status changed:
passing
to
failing
labltk.8.06.11
on
4.13
had its build status changed:
passing
to
failing
labltk.8.06.11
on
5.2
is now installable. Current state is:
failing
labltk.8.06.12
on
4.08
had its build status changed:
passing
to
failing
labltk.8.06.12
on
4.09
had its build status changed:
passing
to
failing
labltk.8.06.12
on
4.10
had its build status changed:
passing
to
failing
labltk.8.06.12
on
4.11
had its build status changed:
passing
to
failing
labltk.8.06.12
on
4.12
had its build status changed:
passing
to
failing
labltk.8.06.12
on
4.13
had its build status changed:
passing
to
failing
labltk.8.06.12
on
5.2
is now installable. Current state is:
failing
labltk.8.06.13
on
4.08
had its build status changed:
passing
to
failing
labltk.8.06.13
on
4.09
had its build status changed:
passing
to
failing
labltk.8.06.13
on
4.10
had its build status changed:
passing
to
failing
labltk.8.06.13
on
4.11
had its build status changed:
passing
to
failing
labltk.8.06.13
on
4.12
had its build status changed:
passing
to
failing
labltk.8.06.13
on
4.13
had its build status changed:
passing
to
failing
labltk.8.06.13
on
4.14
had its build status changed:
passing
to
failing
labltk.8.06.13
on
5.0
had its build status changed:
passing
to
failing
labltk.8.06.13
on
5.1
had its build status changed:
passing
to
failing
labltk.8.06.13
on
5.2
is now installable. Current state is:
failing
labltk.8.06.7
on
4.08
had its build status changed:
passing
to
failing
labltk.8.06.7
on
4.09
had its build status changed:
passing
to
failing
labltk.8.06.7
on
4.10
had its build status changed:
passing
to
failing
labltk.8.06.7
on
4.11
had its build status changed:
passing
to
failing
labltk.8.06.7
on
4.12
had its build status changed:
passing
to
failing
labltk.8.06.8
on
4.08
had its build status changed:
passing
to
failing
labltk.8.06.8
on
4.09
had its build status changed:
passing
to
failing
labltk.8.06.8
on
4.10
had its build status changed:
passing
to
failing
labltk.8.06.8
on
4.11
had its build status changed:
passing
to
failing
labltk.8.06.8
on
4.12
had its build status changed:
passing
to
failing
labltk.8.06.9
on
4.08
had its build status changed:
passing
to
failing
labltk.8.06.9
on
4.09
had its build status changed:
passing
to
failing
labltk.8.06.9
on
4.10
had its build status changed:
passing
to
failing
labltk.8.06.9
on
4.11
had its build status changed:
passing
to
failing
labltk.8.06.9
on
4.12
had its build status changed:
passing
to
failing
lbfgs.0.9.1
on
5.0
had its build status changed:
partially failing
to
failing
lbfgs.0.9.1
on
5.2
is now installable. Current state is:
failing
lbfgs.0.9.2
on
5.0
had its build status changed:
partially failing
to
failing
lbfgs.0.9.2
on
5.2
is now installable. Current state is:
failing
lbfgs.0.9.3
on
5.0
had its build status changed:
partially failing
to
failing
lbfgs.0.9.3
on
5.1
had its build status changed:
partially failing
to
failing
lbfgs.0.9.3
on
5.2
is now installable. Current state is:
failing
ldp_curl.0.2.0
on
4.14
is now installable. Current state is:
failing
ldp_curl.0.2.0
on
5.0
is now installable. Current state is:
failing
ldp_curl.0.2.0
on
5.1
is now installable. Current state is:
failing
ldp_curl.0.2.0
on
5.2
is now installable. Current state is:
failing
ldp_curl.0.3.0
on
4.14
is now installable. Current state is:
failing
ldp_curl.0.3.0
on
5.0
is now installable. Current state is:
failing
ldp_curl.0.3.0
on
5.1
is now installable. Current state is:
failing
ldp_curl.0.3.0
on
5.2
is now installable. Current state is:
failing
ldp_tls.0.2.0
on
4.14
is now installable. Current state is:
failing
ldp_tls.0.2.0
on
5.0
is now installable. Current state is:
failing
ldp_tls.0.2.0
on
5.1
is now installable. Current state is:
failing
ldp_tls.0.2.0
on
5.2
is now installable. Current state is:
failing
ldp_tls.0.3.0
on
4.14
is now installable. Current state is:
failing
ldp_tls.0.3.0
on
5.0
is now installable. Current state is:
failing
ldp_tls.0.3.0
on
5.1
is now installable. Current state is:
failing
ldp_tls.0.3.0
on
5.2
is now installable. Current state is:
failing
libbinaryen.109.0.0
on
4.12
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.0
on
4.13
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.0
on
4.14
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.0
on
5.0
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.0
on
5.1
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.0
on
5.2
is now installable. Current state is:
failing
libbinaryen.109.0.1
on
4.12
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.1
on
4.13
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.1
on
4.14
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.1
on
5.0
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.1
on
5.1
had its build status changed:
partially failing
to
failing
libbinaryen.109.0.1
on
5.2
is now installable. Current state is:
failing
libbinaryen.110.0.0
on
4.12
had its build status changed:
partially failing
to
failing
libbinaryen.110.0.0
on
4.13
had its build status changed:
partially failing
to
failing
libbinaryen.110.0.0
on
4.14
had its build status changed:
partially failing
to
failing
libbinaryen.110.0.0
on
5.0
had its build status changed:
partially failing
to
failing
libbinaryen.110.0.0
on
5.1
had its build status changed:
partially failing
to
failing
libbinaryen.110.0.0
on
5.2
is now installable. Current state is:
failing
libbinaryen.111.0.0
on
4.12
had its build status changed:
partially failing
to
failing
libbinaryen.111.0.0
on
4.13
had its build status changed:
partially failing
to
failing
libbinaryen.111.0.0
on
4.14
had its build status changed:
partially failing
to
failing
libbinaryen.111.0.0
on
5.0
had its build status changed:
partially failing
to
failing
libbinaryen.111.0.0
on
5.1
had its build status changed:
partially failing
to
failing
libbinaryen.111.0.0
on
5.2
is now installable. Current state is:
failing
libbinaryen.111.1.0
on
4.12
had its build status changed:
partially failing
to
failing
libbinaryen.111.1.0
on
4.13
had its build status changed:
partially failing
to
failing
libbinaryen.111.1.0
on
4.14
had its build status changed:
partially failing
to
failing
libbinaryen.111.1.0
on
5.0
had its build status changed:
partially failing
to
failing
libbinaryen.111.1.0
on
5.1
had its build status changed:
partially failing
to
failing
libbinaryen.111.1.0
on
5.2
is now installable. Current state is:
failing
linenoise.0.9.0
on
4.08
had its build status changed:
passing
to
failing
linenoise.0.9.0
on
4.09
had its build status changed:
passing
to
failing
linenoise.0.9.0
on
4.10
had its build status changed:
passing
to
failing
linenoise.0.9.0
on
4.11
had its build status changed:
passing
to
failing
linenoise.0.9.0
on
4.12
had its build status changed:
passing
to
failing
linenoise.0.9.0
on
4.13
had its build status changed:
passing
to
failing
linenoise.0.9.0
on
4.14
had its build status changed:
passing
to
failing
llama-cpp-ocaml.0.0.1
on
4.14
had its build status changed:
partially failing
to
failing
llama-cpp-ocaml.0.0.1
on
5.0
had its build status changed:
partially failing
to
failing
llama-cpp-ocaml.0.0.1
on
5.1
had its build status changed:
partially failing
to
failing
llama-cpp-ocaml.0.0.1
on
5.2
is now installable. Current state is:
failing
lmdb.0.1
on
4.08
had its build status changed:
partially failing
to
failing
lmdb.0.1
on
4.09
had its build status changed:
partially failing
to
failing
lmdb.0.1
on
4.10
had its build status changed:
partially failing
to
failing
lmdb.0.1
on
4.11
had its build status changed:
partially failing
to
failing
lmdb.0.1
on
4.12
had its build status changed:
partially failing
to
failing
lmdb.0.1
on
4.13
had its build status changed:
partially failing
to
failing
lmdb.0.1
on
4.14
had its build status changed:
partially failing
to
failing
lo.0.1.0
on
4.08
had its build status changed:
passing
to
failing
lo.0.1.0
on
4.09
had its build status changed:
passing
to
failing
lo.0.1.0
on
4.10
had its build status changed:
passing
to
failing
lo.0.1.0
on
4.11
had its build status changed:
passing
to
failing
lo.0.1.0
on
4.12
had its build status changed:
passing
to
failing
lo.0.1.0
on
4.13
had its build status changed:
passing
to
failing
lo.0.1.0
on
4.14
had its build status changed:
passing
to
failing
lo.0.1.0
on
5.0
had its build status changed:
passing
to
failing
lo.0.1.0
on
5.1
had its build status changed:
passing
to
failing
lo.0.1.0
on
5.2
is now installable. Current state is:
failing
lo.0.1.1
on
4.08
had its build status changed:
passing
to
failing
lo.0.1.1
on
4.09
had its build status changed:
passing
to
failing
lo.0.1.1
on
4.10
had its build status changed:
passing
to
failing
lo.0.1.1
on
4.11
had its build status changed:
passing
to
failing
lo.0.1.1
on
4.12
had its build status changed:
passing
to
failing
lo.0.1.1
on
4.13
had its build status changed:
passing
to
failing
lo.0.1.1
on
4.14
had its build status changed:
passing
to
failing
lo.0.1.1
on
5.0
had its build status changed:
passing
to
failing
lo.0.1.1
on
5.1
had its build status changed:
passing
to
failing
lo.0.1.1
on
5.2
is now installable. Current state is:
failing
lo.0.1.2
on
4.08
had its build status changed:
passing
to
failing
lo.0.1.2
on
4.09
had its build status changed:
passing
to
failing
lo.0.1.2
on
4.10
had its build status changed:
passing
to
failing
lo.0.1.2
on
4.11
had its build status changed:
passing
to
failing
lo.0.1.2
on
4.12
had its build status changed:
passing
to
failing
lo.0.1.2
on
4.13
had its build status changed:
passing
to
failing
lo.0.1.2
on
4.14
had its build status changed:
passing
to
failing
lo.0.1.2
on
5.0
had its build status changed:
passing
to
failing
lo.0.1.2
on
5.1
had its build status changed:
passing
to
failing
lo.0.1.2
on
5.2
is now installable. Current state is:
failing
lo.0.2.0
on
4.08
had its build status changed:
partially failing
to
failing
lo.0.2.0
on
4.09
had its build status changed:
partially failing
to
failing
lo.0.2.0
on
4.10
had its build status changed:
partially failing
to
failing
lo.0.2.0
on
4.11
had its build status changed:
partially failing
to
failing
lo.0.2.0
on
4.12
had its build status changed:
partially failing
to
failing
lo.0.2.0
on
4.13
had its build status changed:
partially failing
to
failing
lo.0.2.0
on
4.14
had its build status changed:
partially failing
to
failing
lo.0.2.0
on
5.0
had its build status changed:
partially failing
to
failing
lo.0.2.0
on
5.1
had its build status changed:
partially failing
to
failing
lo.0.2.0
on
5.2
is now installable. Current state is:
failing
lutin.2.56
on
4.08
had its build status changed:
partially failing
to
failing
lutin.2.56
on
4.09
had its build status changed:
partially failing
to
failing
lutin.2.56
on
4.10
had its build status changed:
partially failing
to
failing
lutin.2.56
on
4.11
had its build status changed:
partially failing
to
failing
lutin.2.70.4
on
4.08
had its build status changed:
partially failing
to
failing
lutin.2.70.4
on
4.09
had its build status changed:
partially failing
to
failing
lutin.2.70.4
on
4.10
had its build status changed:
partially failing
to
failing
lutin.2.70.4
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
5.2
is now installable. Current state is:
failing
luv.0.5.1
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.1
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.1
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.1
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.1
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.1
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.1
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.1
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.1
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.1
on
5.2
is now installable. Current state is:
failing
luv.0.5.10
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.10
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.10
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.10
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.10
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.10
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.10
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.10
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.10
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.10
on
5.2
is now installable. Current state is:
failing
luv.0.5.11
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.11
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.11
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.11
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.11
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.11
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.11
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.11
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.11
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.11
on
5.2
is now installable. Current state is:
failing
luv.0.5.12
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.12
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.12
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.12
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.12
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.12
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.12
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.12
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.12
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.12
on
5.2
is now installable. Current state is:
failing
luv.0.5.13
on
4.08
is now installable. Current state is:
failing
luv.0.5.13
on
4.09
is now installable. Current state is:
failing
luv.0.5.13
on
4.10
is now installable. Current state is:
failing
luv.0.5.13
on
4.11
is now installable. Current state is:
failing
luv.0.5.13
on
4.12
is now installable. Current state is:
failing
luv.0.5.13
on
4.13
is now installable. Current state is:
failing
luv.0.5.13
on
4.14
is now installable. Current state is:
failing
luv.0.5.13
on
5.0
is now installable. Current state is:
failing
luv.0.5.13
on
5.1
is now installable. Current state is:
failing
luv.0.5.13
on
5.2
is now installable. Current state is:
failing
luv.0.5.2
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.2
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.2
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.2
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.2
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.2
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.2
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.2
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.2
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.2
on
5.2
is now installable. Current state is:
failing
luv.0.5.3
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.3
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.3
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.3
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.3
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.3
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.3
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.3
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.3
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.3
on
5.2
is now installable. Current state is:
failing
luv.0.5.4
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.4
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.4
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.4
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.4
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.4
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.4
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.4
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.4
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.4
on
5.2
is now installable. Current state is:
failing
luv.0.5.5
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.5
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.5
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.5
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.5
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.5
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.5
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.5
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.5
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.5
on
5.2
is now installable. Current state is:
failing
luv.0.5.6
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.6
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.6
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.6
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.6
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.6
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.6
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.6
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.6
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.6
on
5.2
is now installable. Current state is:
failing
luv.0.5.7
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.7
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.7
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.7
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.7
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.7
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.7
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.7
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.7
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.7
on
5.2
is now installable. Current state is:
failing
luv.0.5.8
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.8
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.8
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.8
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.8
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.8
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.8
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.8
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.8
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.8
on
5.2
is now installable. Current state is:
failing
luv.0.5.9
on
4.08
had its build status changed:
partially failing
to
failing
luv.0.5.9
on
4.09
had its build status changed:
partially failing
to
failing
luv.0.5.9
on
4.10
had its build status changed:
partially failing
to
failing
luv.0.5.9
on
4.11
had its build status changed:
partially failing
to
failing
luv.0.5.9
on
4.12
had its build status changed:
partially failing
to
failing
luv.0.5.9
on
4.13
had its build status changed:
partially failing
to
failing
luv.0.5.9
on
4.14
had its build status changed:
partially failing
to
failing
luv.0.5.9
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.9
on
5.1
had its build status changed:
partially failing
to
failing
luv.0.5.9
on
5.2
is now installable. Current state is:
failing
magic-trace.1.0.1
on
4.12
had its build status changed:
partially failing
to
failing
magic-trace.1.0.1
on
4.13
had its build status changed:
partially failing
to
failing
magic-trace.1.0.1
on
4.14
had its build status changed:
partially failing
to
failing
magic-trace.1.0.1
on
5.0
had its build status changed:
partially failing
to
failing
mariadb.1.1.4
on
4.08
had its build status changed:
partially failing
to
failing
mariadb.1.1.4
on
4.09
had its build status changed:
partially failing
to
failing
mariadb.1.1.4
on
4.10
had its build status changed:
partially failing
to
failing
mariadb.1.1.4
on
4.11
had its build status changed:
partially failing
to
failing
mariadb.1.1.4
on
4.12
had its build status changed:
partially failing
to
failing
mariadb.1.1.4
on
4.13
had its build status changed:
partially failing
to
failing
maxminddb.0.3
on
4.08
had its build status changed:
passing
to
failing
maxminddb.0.3
on
4.09
had its build status changed:
passing
to
failing
maxminddb.0.3
on
4.10
had its build status changed:
passing
to
failing
maxminddb.0.3
on
4.11
had its build status changed:
passing
to
failing
maxminddb.0.3
on
4.12
had its build status changed:
passing
to
failing
maxminddb.0.3
on
4.13
had its build status changed:
passing
to
failing
maxminddb.0.3
on
4.14
had its build status changed:
passing
to
failing
maxminddb.0.4
on
4.08
had its build status changed:
passing
to
failing
maxminddb.0.4
on
4.09
had its build status changed:
passing
to
failing
maxminddb.0.4
on
4.10
had its build status changed:
passing
to
failing
maxminddb.0.4
on
4.11
had its build status changed:
passing
to
failing
maxminddb.0.4
on
4.12
had its build status changed:
passing
to
failing
maxminddb.0.4
on
4.13
had its build status changed:
passing
to
failing
maxminddb.0.4
on
4.14
had its build status changed:
passing
to
failing
maxminddb.0.5
on
4.08
had its build status changed:
passing
to
failing
maxminddb.0.5
on
4.09
had its build status changed:
passing
to
failing
maxminddb.0.5
on
4.10
had its build status changed:
passing
to
failing
maxminddb.0.5
on
4.11
had its build status changed:
passing
to
failing
maxminddb.0.5
on
4.12
had its build status changed:
passing
to
failing
maxminddb.0.5
on
4.13
had its build status changed:
passing
to
failing
maxminddb.0.5
on
4.14
had its build status changed:
passing
to
failing
maxminddb.0.6
on
4.08
had its build status changed:
passing
to
failing
maxminddb.0.6
on
4.09
had its build status changed:
passing
to
failing
maxminddb.0.6
on
4.10
had its build status changed:
passing
to
failing
maxminddb.0.6
on
4.11
had its build status changed:
passing
to
failing
maxminddb.0.6
on
4.12
had its build status changed:
passing
to
failing
maxminddb.0.6
on
4.13
had its build status changed:
passing
to
failing
maxminddb.0.6
on
4.14
had its build status changed:
passing
to
failing
mccs.1.1+10
on
4.08
had its build status changed:
partially failing
to
failing
mccs.1.1+10
on
4.09
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
4.08
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
4.09
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
4.10
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
4.11
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
4.12
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
4.13
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
4.14
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
5.0
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
5.1
had its build status changed:
partially failing
to
failing
mccs.1.1+11
on
5.2
is now installable. Current state is:
failing
mdx.1.7.0
on
4.08
had its build status changed:
partially failing
to
failing
mdx.1.7.0
on
4.09
had its build status changed:
partially failing
to
failing
mdx.1.7.0
on
4.10
had its build status changed:
partially failing
to
failing
mdx.1.7.0
on
4.11
had its build status changed:
partially failing
to
failing
melange.3.0.0-51
on
5.1
is now installable. Current state is:
failing
memtrace.0.1
on
5.0
had its build status changed:
partially failing
to
failing
memtrace.0.1
on
5.1
had its build status changed:
partially failing
to
failing
memtrace.0.1
on
5.2
is now installable. Current state is:
failing
memtrace_viewer.v0.14.0
on
4.11
had its build status changed:
partially failing
to
failing
memtrace_viewer.v0.14.1
on
4.11
had its build status changed:
partially failing
to
failing
menhir-secondary.20231231
on
5.2
is now installable. Current state is:
failing
metapp.0.4.4
on
4.08
had its build status changed:
partially failing
to
failing
metapp.0.4.4
on
4.09
had its build status changed:
partially failing
to
failing
metapp.0.4.4
on
4.10
had its build status changed:
partially failing
to
failing
metapp.0.4.4
on
4.11
had its build status changed:
partially failing
to
failing
metapp.0.4.4
on
4.12
had its build status changed:
partially failing
to
failing
metapp.0.4.4
on
4.13
had its build status changed:
partially failing
to
failing
metapp.0.4.4
on
4.14
had its build status changed:
partially failing
to
failing
metapp.0.4.4
on
5.0
had its build status changed:
partially failing
to
failing
metapp.0.4.4
on
5.1
had its build status changed:
partially failing
to
failing
minios-xen.0.7
on
5.2
is now installable. Current state is:
failing
mirage-block-xen.1.7.0
on
4.08
had its build status changed:
partially failing
to
failing
mirage-block-xen.1.7.0
on
4.09
had its build status changed:
partially failing
to
failing
mirage-block-xen.1.7.0
on
4.10
had its build status changed:
partially failing
to
failing
mirage-block-xen.1.7.0
on
4.11
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.0
on
4.08
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.0
on
4.09
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.0
on
4.10
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.0
on
4.11
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.1
on
4.08
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.1
on
4.09
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.1
on
4.10
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.1
on
4.11
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.2
on
4.08
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.2
on
4.09
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.2
on
4.10
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.2
on
4.11
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.3
on
4.08
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.3
on
4.09
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.3
on
4.10
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.3
on
4.11
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.3.0.2
on
4.08
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.3.0.2
on
4.09
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.3.0.2
on
4.10
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.3.0.2
on
4.11
had its build status changed:
partially failing
to
failing
mirage-console-xen.2.4.2
on
4.08
had its build status changed:
partially failing
to
failing
mirage-console-xen.2.4.2
on
4.09
had its build status changed:
partially failing
to
failing
mirage-console-xen.2.4.2
on
4.10
had its build status changed:
partially failing
to
failing
mirage-console-xen.2.4.2
on
4.11
had its build status changed:
partially failing
to
failing
mirage-console-xen.2.4.3
on
4.08
had its build status changed:
partially failing
to
failing
mirage-console-xen.2.4.3
on
4.09
had its build status changed:
partially failing
to
failing
mirage-console-xen.2.4.3
on
4.10
had its build status changed:
partially failing
to
failing
mirage-console-xen.2.4.3
on
4.11
had its build status changed:
partially failing
to
failing
mirage-console-xen.3.0.2
on
4.08
had its build status changed:
partially failing
to
failing
mirage-console-xen.3.0.2
on
4.09
had its build status changed:
partially failing
to
failing
mirage-console-xen.3.0.2
on
4.10
had its build status changed:
partially failing
to
failing
mirage-console-xen.3.0.2
on
4.11
had its build status changed:
partially failing
to
failing
mirage-fs-unix.1.6.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-fs-unix.1.6.0
on
5.1
had its build status changed:
partially failing
to
failing
mirage-fs-unix.1.6.0
on
5.2
is now installable. Current state is:
failing
mirage-xen-minios.0.2
on
5.2
is now installable. Current state is:
failing
mirage-xen-minios.0.3
on
5.2
is now installable. Current state is:
failing
mirage-xen-minios.0.4
on
5.2
is now installable. Current state is:
failing
mirage-xen-minios.0.4.1
on
5.2
is now installable. Current state is:
failing
mirage-xen-minios.0.4.2
on
5.2
is now installable. Current state is:
failing
mirage-xen-minios.0.5.0
on
5.2
is now installable. Current state is:
failing
mirage-xen-minios.0.6.0
on
5.2
is now installable. Current state is:
failing
mirage-xen-minios.0.7.0
on
5.2
is now installable. Current state is:
failing
mirage-xen-posix.2.3.0
on
4.08
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.0
on
4.09
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.0
on
4.10
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.0
on
4.11
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.0
on
4.12
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.0
on
4.13
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.0
on
4.14
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.0
on
5.0
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.0
on
5.1
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.0
on
5.2
is now installable. Current state is:
failing
mirage-xen-posix.2.3.1
on
4.08
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.1
on
4.09
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.1
on
4.10
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.1
on
4.11
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.1
on
4.12
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.1
on
4.13
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.1
on
4.14
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.1
on
5.0
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.1
on
5.1
had its build status changed:
passing
to
failing
mirage-xen-posix.2.3.1
on
5.2
is now installable. Current state is:
failing
misuja.0.0.0
on
5.0
had its build status changed:
passing
to
failing
misuja.0.0.0
on
5.1
had its build status changed:
passing
to
failing
misuja.0.0.0
on
5.2
is now installable. Current state is:
failing
mlcuddidl.3.0.2
on
4.08
had its build status changed:
passing
to
failing
mlcuddidl.3.0.3
on
4.08
had its build status changed:
passing
to
failing
mlcuddidl.3.0.4
on
4.08
had its build status changed:
passing
to
failing
mlcuddidl.3.0.4
on
4.09
had its build status changed:
passing
to
failing
mlcuddidl.3.0.5
on
4.08
had its build status changed:
passing
to
failing
mlcuddidl.3.0.5
on
4.09
had its build status changed:
passing
to
failing
mlcuddidl.3.0.6
on
4.08
had its build status changed:
passing
to
failing
mlcuddidl.3.0.6
on
4.09
had its build status changed:
passing
to
failing
mlcuddidl.3.0.6
on
4.10
had its build status changed:
passing
to
failing
mlcuddidl.3.0.6
on
4.11
had its build status changed:
passing
to
failing
mlcuddidl.3.0.6
on
4.12
had its build status changed:
passing
to
failing
mlcuddidl.3.0.6
on
4.13
had its build status changed:
passing
to
failing
mlcuddidl.3.0.6
on
4.14
had its build status changed:
passing
to
failing
mlcuddidl.3.0.7
on
4.08
had its build status changed:
passing
to
failing
mlcuddidl.3.0.7
on
4.09
had its build status changed:
passing
to
failing
mlcuddidl.3.0.7
on
4.10
had its build status changed:
passing
to
failing
mlcuddidl.3.0.7
on
4.11
had its build status changed:
passing
to
failing
mlcuddidl.3.0.7
on
4.12
had its build status changed:
passing
to
failing
mlcuddidl.3.0.7
on
4.13
had its build status changed:
passing
to
failing
mlcuddidl.3.0.7
on
4.14
had its build status changed:
passing
to
failing
mlcuddidl.3.0.8
on
4.08
is now installable. Current state is:
failing
mlcuddidl.3.0.8
on
4.09
is now installable. Current state is:
failing
mlcuddidl.3.0.8
on
4.10
is now installable. Current state is:
failing
mlcuddidl.3.0.8
on
4.11
is now installable. Current state is:
failing
mlcuddidl.3.0.8
on
4.12
is now installable. Current state is:
failing
mlcuddidl.3.0.8
on
4.13
is now installable. Current state is:
failing
mlcuddidl.3.0.8
on
4.14
is now installable. Current state is:
failing
mldonkey.3.1.7-2
on
4.08
had its build status changed:
partially failing
to
failing
mldonkey.3.1.7-2
on
4.09
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
4.08
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
4.09
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
4.10
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
4.11
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
4.12
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
4.13
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
4.14
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
5.1
had its build status changed:
partially failing
to
failing
mmdb.0.1.0
on
5.2
is now installable. Current state is:
failing
mmdb.0.2.1
on
4.08
had its build status changed:
partially failing
to
failing
mmdb.0.2.1
on
4.09
had its build status changed:
partially failing
to
failing
mmdb.0.2.1
on
4.10
had its build status changed:
partially failing
to
failing
mmdb.0.2.1
on
4.11
had its build status changed:
partially failing
to
failing
mmdb.0.2.1
on
4.12
had its build status changed:
partially failing
to
failing
mmdb.0.2.1
on
4.13
had its build status changed:
partially failing
to
failing
mmdb.0.2.1
on
4.14
had its build status changed:
partially failing
to
failing
mmdb.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
mmdb.0.2.1
on
5.1
had its build status changed:
partially failing
to
failing
mmdb.0.2.1
on
5.2
is now installable. Current state is:
failing
mmdb.0.3.0
on
4.08
had its build status changed:
partially failing
to
failing
mmdb.0.3.0
on
4.09
had its build status changed:
partially failing
to
failing
mmdb.0.3.0
on
4.10
had its build status changed:
partially failing
to
failing
mmdb.0.3.0
on
4.11
had its build status changed:
partially failing
to
failing
mmdb.0.3.0
on
4.12
had its build status changed:
partially failing
to
failing
mmdb.0.3.0
on
4.13
had its build status changed:
partially failing
to
failing
mmdb.0.3.0
on
4.14
had its build status changed:
partially failing
to
failing
mmdb.0.3.0
on
5.0
had its build status changed:
partially failing
to
failing
mmdb.0.3.0
on
5.1
had its build status changed:
partially failing
to
failing
mmdb.0.3.0
on
5.2
is now installable. Current state is:
failing
mopsa.1.0
on
4.12
is now installable. Current state is:
failing
mopsa.1.0
on
4.13
is now installable. Current state is:
failing
mopsa.1.0
on
4.14
is now installable. Current state is:
failing
mopsa.1.0
on
5.0
is now installable. Current state is:
failing
mopsa.1.0
on
5.1
is now installable. Current state is:
failing
mopsa.1.0
on
5.2
is now installable. Current state is:
failing
morbig.0.9
on
5.0
had its build status changed:
partially failing
to
failing
morbig.0.9
on
5.1
had its build status changed:
partially failing
to
failing
morbig.0.9
on
5.2
is now installable. Current state is:
failing
mpg123.0.1
on
4.08
had its build status changed:
partially failing
to
failing
mpg123.0.1
on
4.09
had its build status changed:
partially failing
to
failing
mpg123.0.1
on
4.10
had its build status changed:
partially failing
to
failing
mpg123.0.1
on
4.11
had its build status changed:
partially failing
to
failing
mpg123.0.1
on
4.12
had its build status changed:
partially failing
to
failing
mpg123.0.1
on
4.13
had its build status changed:
partially failing
to
failing
mpg123.0.1
on
4.14
had its build status changed:
partially failing
to
failing
mpg123.0.1
on
5.0
had its build status changed:
partially failing
to
failing
mpg123.0.1
on
5.1
had its build status changed:
partially failing
to
failing
mpg123.0.1
on
5.2
is now installable. Current state is:
failing
mpg123.0.2
on
4.08
had its build status changed:
partially failing
to
failing
mpg123.0.2
on
4.09
had its build status changed:
partially failing
to
failing
mpg123.0.2
on
4.10
had its build status changed:
partially failing
to
failing
mpg123.0.2
on
4.11
had its build status changed:
partially failing
to
failing
mpg123.0.2
on
4.12
had its build status changed:
partially failing
to
failing
mpg123.0.2
on
4.13
had its build status changed:
partially failing
to
failing
mpg123.0.2
on
4.14
had its build status changed:
partially failing
to
failing
mpg123.0.2
on
5.0
had its build status changed:
partially failing
to
failing
mpg123.0.2
on
5.1
had its build status changed:
partially failing
to
failing
mpg123.0.2
on
5.2
is now installable. Current state is:
failing
mpg123.0.3
on
4.08
had its build status changed:
partially failing
to
failing
mpg123.0.3
on
4.09
had its build status changed:
partially failing
to
failing
mpg123.0.3
on
4.10
had its build status changed:
partially failing
to
failing
mpg123.0.3
on
4.11
had its build status changed:
partially failing
to
failing
mpg123.0.3
on
4.12
had its build status changed:
partially failing
to
failing
mpg123.0.3
on
4.13
had its build status changed:
partially failing
to
failing
mpg123.0.3
on
4.14
had its build status changed:
partially failing
to
failing
mpg123.0.3
on
5.0
had its build status changed:
partially failing
to
failing
mpg123.0.3
on
5.1
had its build status changed:
partially failing
to
failing
mpg123.0.3
on
5.2
is now installable. Current state is:
failing
multicont.1.0.2
on
5.0
is now installable. Current state is:
failing
mysql8.1.0
on
4.08
had its build status changed:
partially failing
to
failing
mysql8.1.0
on
4.09
had its build status changed:
partially failing
to
failing
mysql8.1.0
on
4.10
had its build status changed:
partially failing
to
failing
mysql8.1.0
on
4.11
had its build status changed:
partially failing
to
failing
mysql8.1.0
on
4.12
had its build status changed:
partially failing
to
failing
mysql8.1.0
on
4.13
had its build status changed:
partially failing
to
failing
mysql8.1.0
on
4.14
had its build status changed:
partially failing
to
failing
mysql8.1.0
on
5.0
had its build status changed:
partially failing
to
failing
mysql8.1.0
on
5.1
had its build status changed:
partially failing
to
failing
mysql8.1.0
on
5.2
is now installable. Current state is:
failing
named-pipe.0.4.0
on
4.08
had its build status changed:
partially failing
to
failing
named-pipe.0.4.0
on
4.09
had its build status changed:
partially failing
to
failing
named-pipe.0.4.0
on
4.10
had its build status changed:
partially failing
to
failing
named-pipe.0.4.0
on
4.11
had its build status changed:
partially failing
to
failing
netchannel.1.10.2
on
4.08
had its build status changed:
partially failing
to
failing
netchannel.1.10.2
on
4.09
had its build status changed:
partially failing
to
failing
netchannel.1.10.2
on
4.10
had its build status changed:
partially failing
to
failing
netchannel.1.10.2
on
4.11
had its build status changed:
partially failing
to
failing
netchannel.1.11.0
on
4.08
had its build status changed:
partially failing
to
failing
netchannel.1.11.0
on
4.09
had its build status changed:
partially failing
to
failing
netchannel.1.11.0
on
4.10
had its build status changed:
partially failing
to
failing
netchannel.1.11.0
on
4.11
had its build status changed:
partially failing
to
failing
netchannel.1.12.0
on
4.08
had its build status changed:
partially failing
to
failing
netchannel.1.12.0
on
4.09
had its build status changed:
partially failing
to
failing
netchannel.1.12.0
on
4.10
had its build status changed:
partially failing
to
failing
netchannel.1.12.0
on
4.11
had its build status changed:
partially failing
to
failing
netchannel.1.13.0
on
4.08
had its build status changed:
partially failing
to
failing
netchannel.1.13.0
on
4.09
had its build status changed:
partially failing
to
failing
netchannel.1.13.0
on
4.10
had its build status changed:
partially failing
to
failing
netchannel.1.13.0
on
4.11
had its build status changed:
partially failing
to
failing
netchannel.1.13.1
on
4.08
had its build status changed:
partially failing
to
failing
netchannel.1.13.1
on
4.09
had its build status changed:
partially failing
to
failing
netchannel.1.13.1
on
4.10
had its build status changed:
partially failing
to
failing
netchannel.1.13.1
on
4.11
had its build status changed:
partially failing
to
failing
netkat.0.1
on
4.08
had its build status changed:
partially failing
to
failing
netkat.0.1
on
4.09
had its build status changed:
partially failing
to
failing
netkat.0.1
on
4.10
had its build status changed:
partially failing
to
failing
netkat.0.1
on
4.11
had its build status changed:
partially failing
to
failing
noCanren.0.3.0
on
4.13
had its build status changed:
partially failing
to
failing
noCanren.0.3.0~alpha1
on
4.13
had its build status changed:
partially failing
to
failing
nuscr.1.0.0
on
4.08
had its build status changed:
partially failing
to
failing
nuscr.1.0.0
on
4.09
had its build status changed:
partially failing
to
failing
nuscr.1.1.0
on
4.08
had its build status changed:
partially failing
to
failing
nuscr.1.1.0
on
4.09
had its build status changed:
partially failing
to
failing
nuscr.1.1.0
on
4.10
had its build status changed:
partially failing
to
failing
nuscr.1.1.0
on
4.11
had its build status changed:
partially failing
to
failing
nuscr.1.1.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-buddy.0.6.1
on
4.08
had its build status changed:
passing
to
failing
ocaml-buddy.0.6.1
on
4.09
had its build status changed:
passing
to
failing
ocaml-buddy.0.6.1
on
4.10
had its build status changed:
passing
to
failing
ocaml-buddy.0.6.1
on
4.11
had its build status changed:
passing
to
failing
ocaml-buddy.0.6.1
on
4.12
had its build status changed:
passing
to
failing
ocaml-buddy.0.6.1
on
4.13
had its build status changed:
passing
to
failing
ocaml-buddy.0.6.1
on
4.14
had its build status changed:
passing
to
failing
ocaml-buddy.0.6.1
on
5.0
had its build status changed:
passing
to
failing
ocaml-buddy.0.6.1
on
5.1
had its build status changed:
passing
to
failing
ocaml-buddy.0.6.1
on
5.2
is now installable. Current state is:
failing
ocaml-embed-file.v0.15.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-embed-file.v0.15.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-embed-file.v0.15.0
on
4.13
had its build status changed:
partially failing
to
failing
ocaml-embed-file.v0.15.0
on
4.14
had its build status changed:
partially failing
to
failing
ocaml-embed-file.v0.15.0
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-expat.0.9.1
on
5.0
had its build status changed:
passing
to
failing
ocaml-expat.0.9.1
on
5.1
had its build status changed:
passing
to
failing
ocaml-expat.0.9.1
on
5.2
is now installable. Current state is:
failing
ocaml-expat.1.0.0
on
5.0
had its build status changed:
passing
to
failing
ocaml-expat.1.0.0
on
5.1
had its build status changed:
passing
to
failing
ocaml-expat.1.0.0
on
5.2
is now installable. Current state is:
failing
ocaml-expat.1.1.0
on
5.0
had its build status changed:
passing
to
failing
ocaml-expat.1.1.0
on
5.1
had its build status changed:
passing
to
failing
ocaml-expat.1.1.0
on
5.2
is now installable. Current state is:
failing
ocaml-lsp-server.1.1.0
on
4.08
had its build status changed:
passing
to
failing
ocaml-lsp-server.1.1.0
on
4.09
had its build status changed:
passing
to
failing
ocaml-lsp-server.1.1.0
on
4.10
had its build status changed:
passing
to
failing
ocaml-lsp-server.1.1.0
on
4.11
had its build status changed:
passing
to
failing
ocaml-lsp-server.1.10.0
on
4.13
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.10.1
on
4.13
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.10.2
on
4.13
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.10.3
on
4.13
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.2.0
on
4.08
had its build status changed:
passing
to
failing
ocaml-lsp-server.1.2.0
on
4.09
had its build status changed:
passing
to
failing
ocaml-lsp-server.1.2.0
on
4.10
had its build status changed:
passing
to
failing
ocaml-lsp-server.1.2.0
on
4.11
had its build status changed:
passing
to
failing
ocaml-lsp-server.1.3.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.3.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.3.0
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.3.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.4.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.4.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.4.0
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.4.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.4.1
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.4.1
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.4.1
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.4.1
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.5.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.6.1
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.7.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.8.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.8.2
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.8.3
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.9.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-lsp-server.1.9.1
on
4.13
had its build status changed:
partially failing
to
failing
ocaml-makefile.6.37.0
on
5.2
is now installable. Current state is:
failing
ocaml-makefile.6.38.0
on
5.2
is now installable. Current state is:
failing
ocaml-makefile.6.39.0
on
5.2
is now installable. Current state is:
failing
ocaml-protoc-plugin.0.9
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-protoc-plugin.0.9
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-protoc-plugin.0.9
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-protoc-plugin.0.9
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-r.0.1.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-r.0.1.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-r.0.1.0
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-r.0.1.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-r.0.1.1
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-r.0.1.1
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-r.0.1.1
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-r.0.1.1
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-r.0.2.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-r.0.2.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-r.0.2.0
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-r.0.2.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.0
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
4.13
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
4.14
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
5.1
had its build status changed:
partially failing
to
failing
ocaml-r.0.3.1
on
5.2
is now installable. Current state is:
failing
ocaml-r.0.4.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-r.0.4.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-r.0.4.0
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-r.0.4.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-r.0.4.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-r.0.4.0
on
4.13
had its build status changed:
partially failing
to
failing
ocaml-r.0.4.0
on
4.14
had its build status changed:
partially failing
to
failing
ocaml-r.0.4.0
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-r.0.4.0
on
5.1
had its build status changed:
partially failing
to
failing
ocaml-r.0.4.0
on
5.2
is now installable. Current state is:
failing
ocaml-r.0.5.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml-r.0.5.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml-r.0.5.0
on
4.10
had its build status changed:
partially failing
to
failing
ocaml-r.0.5.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml-r.0.5.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml-r.0.5.0
on
4.13
had its build status changed:
partially failing
to
failing
ocaml-r.0.5.0
on
4.14
had its build status changed:
partially failing
to
failing
ocaml-r.0.5.0
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-r.0.5.0
on
5.1
had its build status changed:
partially failing
to
failing
ocaml-r.0.5.0
on
5.2
is now installable. Current state is:
failing
ocaml_plugin.v0.12.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.12.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.13.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.13.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.13.0
on
4.10
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.13.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.14.0
on
4.08
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.14.0
on
4.09
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.14.0
on
4.10
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.14.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.14.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.14.0
on
4.13
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.14.0
on
4.14
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.15.0
on
4.11
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.15.0
on
4.12
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.15.0
on
4.13
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.15.0
on
4.14
had its build status changed:
partially failing
to
failing
ocaml_plugin.v0.15.0
on
5.0
had its build status changed:
partially failing
to
failing
ocamlbrowser.5.0.0
on
5.0
had its build status changed:
passing
to
failing
ocamldiff.1.1
on
5.2
is now installable. Current state is:
failing
ocamlfuse.2.7.1-cvs
on
4.08
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs
on
4.09
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs
on
4.10
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs
on
4.11
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs
on
4.12
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs
on
4.13
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs
on
4.14
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs2
on
4.08
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs2
on
4.09
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs2
on
4.10
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs2
on
4.11
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs2
on
4.12
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs2
on
4.13
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs2
on
4.14
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs3
on
4.08
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs3
on
4.09
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs3
on
4.10
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs3
on
4.11
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs3
on
4.12
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs3
on
4.13
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs3
on
4.14
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs4
on
4.08
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs4
on
4.09
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs4
on
4.10
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs4
on
4.11
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs4
on
4.12
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs4
on
4.13
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs4
on
4.14
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs5
on
4.08
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs5
on
4.09
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs5
on
4.10
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs5
on
4.11
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs5
on
4.12
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs5
on
4.13
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs5
on
4.14
had its build status changed:
passing
to
failing
ocamlfuse.2.7.1-cvs6
on
4.08
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs6
on
4.09
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs6
on
4.10
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs6
on
4.11
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs6
on
4.12
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs6
on
4.13
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs6
on
4.14
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs7
on
4.08
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs7
on
4.09
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs7
on
4.10
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs7
on
4.11
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs7
on
4.12
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs7
on
4.13
had its build status changed:
partially failing
to
failing
ocamlfuse.2.7.1-cvs7
on
4.14
had its build status changed:
partially failing
to
failing
ocamlmerlin-mlx.0.9
on
5.1
is now installable. Current state is:
failing
ocamlsdl2.0.02
on
4.08
had its build status changed:
passing
to
failing
ocamlsdl2.0.02
on
4.09
had its build status changed:
passing
to
failing
ocamlsdl2.0.02
on
4.10
had its build status changed:
passing
to
failing
ocamlsdl2.0.02
on
4.11
had its build status changed:
passing
to
failing
ocamlsdl2.0.02
on
4.12
had its build status changed:
passing
to
failing
ocamlsdl2.0.02
on
4.13
had its build status changed:
passing
to
failing
ocamlsdl2.0.02
on
4.14
had its build status changed:
passing
to
failing
ocamlsdl2.0.02
on
5.0
had its build status changed:
passing
to
failing
ocamlsdl2.0.02
on
5.1
had its build status changed:
passing
to
failing
ocamlsdl2.0.02
on
5.2
is now installable. Current state is:
failing
ocamlsdl2.0.03
on
4.08
had its build status changed:
passing
to
failing
ocamlsdl2.0.03
on
4.09
had its build status changed:
passing
to
failing
ocamlsdl2.0.03
on
4.10
had its build status changed:
passing
to
failing
ocamlsdl2.0.03
on
4.11
had its build status changed:
passing
to
failing
ocamlsdl2.0.03
on
4.12
had its build status changed:
passing
to
failing
ocamlsdl2.0.03
on
4.13
had its build status changed:
passing
to
failing
ocamlsdl2.0.03
on
4.14
had its build status changed:
passing
to
failing
ocamlsdl2.0.03
on
5.0
had its build status changed:
passing
to
failing
ocamlsdl2.0.03
on
5.1
had its build status changed:
passing
to
failing
ocamlsdl2.0.03
on
5.2
is now installable. Current state is:
failing
oclock.0.3.0
on
5.0
had its build status changed:
passing
to
failing
oclock.0.3.0
on
5.1
had its build status changed:
passing
to
failing
oclock.0.3.0
on
5.2
is now installable. Current state is:
failing
oclock.0.4.0
on
5.0
had its build status changed:
passing
to
failing
oclock.0.4.0
on
5.1
had its build status changed:
passing
to
failing
oclock.0.4.0
on
5.2
is now installable. Current state is:
failing
ocp-index-top.0.4.1
on
4.08
had its build status changed:
partially failing
to
failing
ocp-index-top.0.4.1
on
4.09
had its build status changed:
partially failing
to
failing
ocp-index-top.0.4.3
on
4.08
had its build status changed:
partially failing
to
failing
ocp-index-top.0.4.3
on
4.09
had its build status changed:
partially failing
to
failing
ocp-index-top.0.5.0
on
4.08
had its build status changed:
partially failing
to
failing
ocp-index-top.0.5.0
on
4.09
had its build status changed:
partially failing
to
failing
ocplib-simplex.0.3
on
5.2
is now installable. Current state is:
failing
ocsigen-start.2.15.1
on
4.08
had its build status changed:
partially failing
to
failing
ocsigen-start.2.15.1
on
4.09
had its build status changed:
partially failing
to
failing
ocsigen-start.2.15.1
on
4.10
had its build status changed:
partially failing
to
failing
ocsigen-start.2.16.0
on
4.08
had its build status changed:
partially failing
to
failing
ocsigen-start.2.16.0
on
4.09
had its build status changed:
partially failing
to
failing
ocsigen-start.2.16.0
on
4.10
had its build status changed:
partially failing
to
failing
ocsigen-start.2.16.1
on
4.08
had its build status changed:
partially failing
to
failing
ocsigen-start.2.16.1
on
4.09
had its build status changed:
partially failing
to
failing
ocsigen-start.2.16.1
on
4.10
had its build status changed:
partially failing
to
failing
odbc.3.0
on
5.0
had its build status changed:
passing
to
failing
odbc.3.0
on
5.1
had its build status changed:
passing
to
failing
odbc.3.0
on
5.2
is now installable. Current state is:
failing
odepack.0.6.9
on
4.08
had its build status changed:
partially failing
to
failing
odepack.0.6.9
on
4.09
had its build status changed:
partially failing
to
failing
odepack.0.6.9
on
4.10
had its build status changed:
partially failing
to
failing
odepack.0.6.9
on
4.11
had its build status changed:
partially failing
to
failing
odepack.0.6.9
on
4.12
had its build status changed:
partially failing
to
failing
odepack.0.6.9
on
4.13
had its build status changed:
partially failing
to
failing
odepack.0.6.9
on
4.14
had its build status changed:
partially failing
to
failing
odepack.0.6.9
on
5.0
had its build status changed:
partially failing
to
failing
odepack.0.6.9
on
5.1
had its build status changed:
partially failing
to
failing
odepack.0.6.9
on
5.2
is now installable. Current state is:
failing
odepack.0.7
on
4.08
had its build status changed:
partially failing
to
failing
odepack.0.7
on
4.09
had its build status changed:
partially failing
to
failing
odepack.0.7
on
4.10
had its build status changed:
partially failing
to
failing
odepack.0.7
on
4.11
had its build status changed:
partially failing
to
failing
odepack.0.7
on
4.12
had its build status changed:
partially failing
to
failing
odepack.0.7
on
4.13
had its build status changed:
partially failing
to
failing
odepack.0.7
on
4.14
had its build status changed:
partially failing
to
failing
odepack.0.7
on
5.0
had its build status changed:
partially failing
to
failing
odepack.0.7
on
5.1
had its build status changed:
partially failing
to
failing
odepack.0.7
on
5.2
is now installable. Current state is:
failing
odig.0.0.3
on
4.08
had its build status changed:
partially failing
to
failing
odig.0.0.3
on
4.09
had its build status changed:
partially failing
to
failing
odig.0.0.3
on
4.10
had its build status changed:
partially failing
to
failing
odig.0.0.3
on
4.11
had its build status changed:
partially failing
to
failing
ojs-base.0.6.0
on
4.12
had its build status changed:
partially failing
to
failing
ojs-base.0.6.0
on
4.13
had its build status changed:
partially failing
to
failing
ojs-base.0.6.0
on
4.14
had its build status changed:
partially failing
to
failing
ojs-base.0.6.0
on
5.0
had its build status changed:
partially failing
to
failing
ollvm-tapir.0.99.1
on
4.08
had its build status changed:
partially failing
to
failing
ollvm-tapir.0.99.1
on
4.09
had its build status changed:
partially failing
to
failing
ollvm-tapir.0.99.1
on
5.0
had its build status changed:
partially failing
to
failing
ollvm-tapir.0.99.1
on
5.1
had its build status changed:
partially failing
to
failing
ollvm.0.99
on
4.08
had its build status changed:
partially failing
to
failing
openai-gym.0.01
on
4.08
had its build status changed:
partially failing
to
failing
openai-gym.0.01
on
4.09
had its build status changed:
partially failing
to
failing
openai-gym.0.01
on
4.10
had its build status changed:
partially failing
to
failing
openai-gym.0.01
on
4.11
had its build status changed:
partially failing
to
failing
openai-gym.0.01
on
4.12
had its build status changed:
partially failing
to
failing
opentelemetry-cohttp-lwt.0.10
on
4.08
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.10
on
4.09
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.10
on
4.10
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.10
on
4.11
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.10
on
4.12
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.10
on
4.13
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.10
on
4.14
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.10
on
5.0
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.10
on
5.1
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.10
on
5.2
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
4.08
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
4.09
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
4.10
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
4.11
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
4.12
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
4.13
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
4.14
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
5.0
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
5.1
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.7
on
5.2
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
4.08
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
4.09
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
4.10
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
4.11
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
4.12
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
4.13
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
4.14
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
5.0
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
5.1
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.8
on
5.2
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
4.08
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
4.09
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
4.10
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
4.11
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
4.12
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
4.13
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
4.14
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
5.0
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
5.1
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.9
on
5.2
is now installable. Current state is:
failing
oplsr.8.0.1
on
4.08
had its build status changed:
partially failing
to
failing
oplsr.8.0.1
on
4.09
had its build status changed:
partially failing
to
failing
oplsr.8.0.1
on
4.10
had its build status changed:
partially failing
to
failing
oplsr.8.0.1
on
4.11
had its build status changed:
partially failing
to
failing
oplsr.8.0.1
on
4.12
had its build status changed:
partially failing
to
failing
oplsr.8.0.1
on
4.13
had its build status changed:
partially failing
to
failing
oplsr.8.0.1
on
4.14
had its build status changed:
partially failing
to
failing
oplsr.8.0.1
on
5.0
had its build status changed:
partially failing
to
failing
oplsr.8.0.1
on
5.1
had its build status changed:
partially failing
to
failing
oplsr.8.0.1
on
5.2
is now installable. Current state is:
failing
opsian.0.1
on
5.0
had its build status changed:
partially failing
to
failing
opsian.0.1
on
5.1
had its build status changed:
partially failing
to
failing
opsian.0.1
on
5.2
is now installable. Current state is:
failing
override.0.2.2
on
4.08
had its build status changed:
partially failing
to
failing
override.0.2.2
on
4.09
had its build status changed:
partially failing
to
failing
owi.0.2
on
5.1
is now installable. Current state is:
failing
owl-symbolic.0.1.0
on
4.08
had its build status changed:
partially failing
to
failing
owl-symbolic.0.1.0
on
4.09
had its build status changed:
partially failing
to
failing
owl-symbolic.0.1.0
on
4.10
had its build status changed:
partially failing
to
failing
owl-symbolic.0.1.0
on
4.11
had its build status changed:
partially failing
to
failing
owl-symbolic.0.1.0
on
4.12
had its build status changed:
partially failing
to
failing
owl-symbolic.0.2.0
on
4.08
had its build status changed:
partially failing
to
failing
owl-symbolic.0.2.0
on
4.09
had its build status changed:
partially failing
to
failing
owl-symbolic.0.2.0
on
4.10
had its build status changed:
partially failing
to
failing
owl-symbolic.0.2.0
on
4.11
had its build status changed:
partially failing
to
failing
owl-symbolic.0.2.0
on
4.12
had its build status changed:
partially failing
to
failing
owl-zoo.1.0.2
on
4.10
had its build status changed:
partially failing
to
failing
owl-zoo.1.0.2
on
4.11
had its build status changed:
partially failing
to
failing
owl-zoo.1.0.2
on
4.12
had its build status changed:
partially failing
to
failing
owl-zoo.1.0.2
on
4.13
had its build status changed:
partially failing
to
failing
pa_ppx.0.03
on
4.10
had its build status changed:
partially failing
to
failing
pa_ppx_ag.0.07.02
on
4.10
had its build status changed:
partially failing
to
failing
pa_ppx_ag.0.07.02
on
4.11
had its build status changed:
partially failing
to
failing
pa_ppx_ag.0.07.02
on
4.12
had its build status changed:
partially failing
to
failing
pa_ppx_hashcons.0.07.02
on
4.10
had its build status changed:
partially failing
to
failing
pa_ppx_hashcons.0.07.02
on
4.11
had its build status changed:
partially failing
to
failing
pa_ppx_hashcons.0.07.02
on
4.12
had its build status changed:
partially failing
to
failing
pa_ppx_migrate.0.07.02
on
4.10
had its build status changed:
partially failing
to
failing
pa_ppx_migrate.0.07.02
on
4.11
had its build status changed:
partially failing
to
failing
pa_ppx_migrate.0.07.02
on
4.12
had its build status changed:
partially failing
to
failing
pa_ppx_unique.0.07.02
on
4.10
had its build status changed:
partially failing
to
failing
pa_ppx_unique.0.07.02
on
4.11
had its build status changed:
partially failing
to
failing
pa_ppx_unique.0.07.02
on
4.12
had its build status changed:
partially failing
to
failing
pari-bindings.0.1
on
4.10
had its build status changed:
partially failing
to
failing
pari-bindings.0.1
on
4.11
had its build status changed:
partially failing
to
failing
pari-bindings.0.1
on
4.12
had its build status changed:
partially failing
to
failing
pari-bindings.0.1
on
4.13
had its build status changed:
partially failing
to
failing
pari-bindings.0.1
on
4.14
had its build status changed:
partially failing
to
failing
pari-bindings.0.1
on
5.0
had its build status changed:
partially failing
to
failing
pari-bindings.0.1
on
5.1
had its build status changed:
partially failing
to
failing
pari-bindings.0.1
on
5.2
is now installable. Current state is:
failing
patdiff.v0.12.0
on
4.08
had its build status changed:
passing
to
failing
patdiff.v0.12.0
on
4.09
had its build status changed:
passing
to
failing
patdiff.v0.12.1
on
4.08
had its build status changed:
partially failing
to
failing
patdiff.v0.12.1
on
4.09
had its build status changed:
partially failing
to
failing
patdiff.v0.13.0
on
4.08
had its build status changed:
partially failing
to
failing
patdiff.v0.13.0
on
4.09
had its build status changed:
partially failing
to
failing
patdiff.v0.13.0
on
4.10
had its build status changed:
partially failing
to
failing
patdiff.v0.13.0
on
4.11
had its build status changed:
partially failing
to
failing
patdiff.v0.14.0
on
4.08
had its build status changed:
partially failing
to
failing
patdiff.v0.14.0
on
4.09
had its build status changed:
partially failing
to
failing
patdiff.v0.14.0
on
4.10
had its build status changed:
partially failing
to
failing
patdiff.v0.14.0
on
4.11
had its build status changed:
partially failing
to
failing
patdiff.v0.14.0
on
4.12
had its build status changed:
partially failing
to
failing
patdiff.v0.14.0
on
4.13
had its build status changed:
partially failing
to
failing
patdiff.v0.14.0
on
4.14
had its build status changed:
partially failing
to
failing
patdiff.v0.15.0
on
4.11
had its build status changed:
partially failing
to
failing
patdiff.v0.15.0
on
4.12
had its build status changed:
partially failing
to
failing
patdiff.v0.15.0
on
4.13
had its build status changed:
partially failing
to
failing
patdiff.v0.15.0
on
4.14
had its build status changed:
partially failing
to
failing
patdiff.v0.15.0
on
5.0
had its build status changed:
partially failing
to
failing
petr4.0.1
on
4.08
had its build status changed:
partially failing
to
failing
petr4.0.1
on
4.09
had its build status changed:
partially failing
to
failing
petr4.0.1.1
on
4.08
had its build status changed:
partially failing
to
failing
petr4.0.1.1
on
4.09
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
4.08
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
4.09
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
4.10
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
4.11
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
4.12
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
4.13
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
4.14
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
5.0
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
5.1
had its build status changed:
partially failing
to
failing
pg_query.0.9.7
on
5.2
is now installable. Current state is:
failing
picos.0.1.0
on
4.12
is now installable. Current state is:
failing
picos.0.2.0
on
4.12
is now installable. Current state is:
failing
picos.0.3.0
on
4.12
is now installable. Current state is:
failing
picos_std.0.5.0
on
4.12
is now installable. Current state is:
failing
plplot.5.11.0
on
4.08
had its build status changed:
passing
to
failing
plplot.5.11.0
on
4.09
had its build status changed:
passing
to
failing
plplot.5.11.0
on
4.10
had its build status changed:
passing
to
failing
plplot.5.11.0
on
4.11
had its build status changed:
passing
to
failing
plplot.5.11.0
on
4.12
had its build status changed:
passing
to
failing
plplot.5.11.0
on
4.13
had its build status changed:
passing
to
failing
plplot.5.11.0
on
4.14
had its build status changed:
passing
to
failing
plplot.5.11.0-1
on
4.08
had its build status changed:
partially failing
to
failing
plplot.5.11.0-1
on
4.09
had its build status changed:
partially failing
to
failing
plplot.5.11.0-1
on
4.10
had its build status changed:
partially failing
to
failing
plplot.5.11.0-1
on
4.11
had its build status changed:
partially failing
to
failing
plplot.5.11.0-1
on
4.12
had its build status changed:
partially failing
to
failing
plplot.5.11.0-1
on
4.13
had its build status changed:
partially failing
to
failing
plplot.5.11.0-1
on
4.14
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
4.08
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
4.09
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
4.10
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
4.11
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
4.12
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
4.13
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
4.14
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
5.0
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
5.1
had its build status changed:
partially failing
to
failing
plplot.5.12.0
on
5.2
is now installable. Current state is:
failing
polka.2.71.10
on
4.08
had its build status changed:
partially failing
to
failing
polka.2.71.10
on
4.09
had its build status changed:
partially failing
to
failing
polka.2.71.10
on
4.10
had its build status changed:
partially failing
to
failing
polka.2.71.10
on
4.11
had its build status changed:
partially failing
to
failing
polka.2.71.10
on
4.12
had its build status changed:
partially failing
to
failing
polka.2.71.10
on
4.13
had its build status changed:
partially failing
to
failing
polka.2.71.10
on
4.14
had its build status changed:
partially failing
to
failing
polka.2.71.10
on
5.0
had its build status changed:
partially failing
to
failing
polka.2.71.10
on
5.1
had its build status changed:
partially failing
to
failing
polka.2.71.10
on
5.2
is now installable. Current state is:
failing
polka.2.71.15
on
4.08
had its build status changed:
partially failing
to
failing
polka.2.71.15
on
4.09
had its build status changed:
partially failing
to
failing
polka.2.71.15
on
4.10
had its build status changed:
partially failing
to
failing
polka.2.71.15
on
4.11
had its build status changed:
partially failing
to
failing
polka.2.71.15
on
4.12
had its build status changed:
partially failing
to
failing
polka.2.71.15
on
4.13
had its build status changed:
partially failing
to
failing
polka.2.71.15
on
4.14
had its build status changed:
partially failing
to
failing
polka.2.71.15
on
5.0
had its build status changed:
partially failing
to
failing
polka.2.71.15
on
5.1
had its build status changed:
partially failing
to
failing
polka.2.71.15
on
5.2
is now installable. Current state is:
failing
portaudio.0.2.1
on
4.08
had its build status changed:
passing
to
failing
portaudio.0.2.1
on
4.09
had its build status changed:
passing
to
failing
portaudio.0.2.1
on
4.10
had its build status changed:
passing
to
failing
portaudio.0.2.1
on
4.11
had its build status changed:
passing
to
failing
portaudio.0.2.1
on
4.12
had its build status changed:
passing
to
failing
portaudio.0.2.1
on
4.13
had its build status changed:
passing
to
failing
portaudio.0.2.1
on
4.14
had its build status changed:
passing
to
failing
portaudio.0.2.1
on
5.0
had its build status changed:
passing
to
failing
portaudio.0.2.1
on
5.1
had its build status changed:
passing
to
failing
portaudio.0.2.1
on
5.2
is now installable. Current state is:
failing
portaudio_c_bindings.19.6.0
on
4.08
had its build status changed:
partially failing
to
failing
portaudio_c_bindings.19.6.0
on
4.09
had its build status changed:
partially failing
to
failing
portaudio_c_bindings.19.6.0
on
4.10
had its build status changed:
partially failing
to
failing
portaudio_c_bindings.19.6.0
on
4.11
had its build status changed:
partially failing
to
failing
portaudio_c_bindings.19.6.0
on
4.12
had its build status changed:
partially failing
to
failing
portaudio_c_bindings.19.6.0
on
4.13
had its build status changed:
partially failing
to
failing
portaudio_c_bindings.19.6.0
on
4.14
had its build status changed:
partially failing
to
failing
portaudio_c_bindings.19.6.0
on
5.0
had its build status changed:
partially failing
to
failing
portaudio_c_bindings.19.6.0
on
5.1
had its build status changed:
partially failing
to
failing
portaudio_c_bindings.19.6.0
on
5.2
is now installable. Current state is:
failing
portia.1.1
on
4.10
had its build status changed:
partially failing
to
failing
portia.1.1
on
5.0
had its build status changed:
partially failing
to
failing
portia.1.1
on
5.1
had its build status changed:
partially failing
to
failing
portia.1.1
on
5.2
is now installable. Current state is:
failing
portia.1.3
on
4.11
had its build status changed:
partially failing
to
failing
portia.1.3
on
5.0
had its build status changed:
partially failing
to
failing
portia.1.3
on
5.1
had its build status changed:
partially failing
to
failing
portia.1.3
on
5.2
is now installable. Current state is:
failing
portia.1.5
on
5.0
had its build status changed:
partially failing
to
failing
portia.1.5
on
5.1
had its build status changed:
partially failing
to
failing
portia.1.5
on
5.2
is now installable. Current state is:
failing
posix-getopt.2.0.0
on
4.08
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.0
on
4.09
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.0
on
4.10
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.0
on
4.11
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.0
on
4.12
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.0
on
4.13
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.0
on
4.14
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.0
on
5.0
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.0
on
5.1
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.0
on
5.2
is now installable. Current state is:
failing
posix-getopt.2.0.1
on
4.08
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.1
on
4.09
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.1
on
4.10
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.1
on
4.11
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.1
on
4.12
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.1
on
4.13
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.1
on
4.14
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.1
on
5.0
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.1
on
5.1
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.1
on
5.2
is now installable. Current state is:
failing
posix-getopt.2.0.2
on
4.08
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.2
on
4.09
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.2
on
4.10
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.2
on
4.11
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.2
on
4.12
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.2
on
4.13
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.2
on
4.14
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.2
on
5.0
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.2
on
5.1
had its build status changed:
partially failing
to
failing
posix-getopt.2.0.2
on
5.2
is now installable. Current state is:
failing
posix-time2.2.0.0
on
4.08
had its build status changed:
partially failing
to
failing
posix-time2.2.0.0
on
4.09
had its build status changed:
partially failing
to
failing
posix-time2.2.0.0
on
4.10
had its build status changed:
partially failing
to
failing
posix-time2.2.0.0
on
4.11
had its build status changed:
partially failing
to
failing
posix-time2.2.0.0
on
4.12
had its build status changed:
partially failing
to
failing
posix-time2.2.0.0
on
4.13
had its build status changed:
partially failing
to
failing
posix-time2.2.0.0
on
4.14
had its build status changed:
partially failing
to
failing
posix-time2.2.0.0
on
5.0
had its build status changed:
partially failing
to
failing
posix-time2.2.0.0
on
5.1
had its build status changed:
partially failing
to
failing
posix-time2.2.0.0
on
5.2
is now installable. Current state is:
failing
posix-time2.2.0.1
on
4.08
had its build status changed:
partially failing
to
failing
posix-time2.2.0.1
on
4.09
had its build status changed:
partially failing
to
failing
posix-time2.2.0.1
on
4.10
had its build status changed:
partially failing
to
failing
posix-time2.2.0.1
on
4.11
had its build status changed:
partially failing
to
failing
posix-time2.2.0.1
on
4.12
had its build status changed:
partially failing
to
failing
posix-time2.2.0.1
on
4.13
had its build status changed:
partially failing
to
failing
posix-time2.2.0.1
on
4.14
had its build status changed:
partially failing
to
failing
posix-time2.2.0.1
on
5.0
had its build status changed:
partially failing
to
failing
posix-time2.2.0.1
on
5.1
had its build status changed:
partially failing
to
failing
posix-time2.2.0.1
on
5.2
is now installable. Current state is:
failing
ppx_deriving_encoding.0.2.3
on
4.08
had its build status changed:
partially failing
to
failing
ppx_deriving_encoding.0.2.3
on
4.09
had its build status changed:
partially failing
to
failing
ppx_deriving_encoding.0.2.3
on
4.10
had its build status changed:
partially failing
to
failing
ppx_deriving_encoding.0.2.3
on
4.11
had its build status changed:
partially failing
to
failing
ppx_deriving_encoding.0.2.3
on
4.12
had its build status changed:
partially failing
to
failing
ppx_deriving_encoding.0.2.3
on
4.13
had its build status changed:
partially failing
to
failing
ppx_deriving_encoding.0.2.3
on
4.14
had its build status changed:
partially failing
to
failing
ppx_deriving_encoding.0.2.3
on
5.0
had its build status changed:
partially failing
to
failing
ppx_deriving_encoding.0.2.3
on
5.1
had its build status changed:
partially failing
to
failing
ppx_deriving_encoding.0.2.3
on
5.2
is now installable. Current state is:
failing
ppx_factory.0.1.0
on
4.08
had its build status changed:
partially failing
to
failing
ppx_pbt.0.2.1
on
4.10
had its build status changed:
partially failing
to
failing
ppx_pbt.0.2.1
on
4.11
had its build status changed:
partially failing
to
failing
ppx_pbt.0.2.1
on
4.12
had its build status changed:
partially failing
to
failing
ppx_pbt.0.2.1
on
4.13
had its build status changed:
partially failing
to
failing
prof_spacetime.0.3.0
on
4.08
had its build status changed:
partially failing
to
failing
prof_spacetime.0.3.0
on
4.09
had its build status changed:
partially failing
to
failing
prof_spacetime.0.3.0
on
4.10
had its build status changed:
partially failing
to
failing
prof_spacetime.0.3.0
on
4.11
had its build status changed:
partially failing
to
failing
protocol-9p.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
protocol-9p.1.0.0
on
5.1
had its build status changed:
partially failing
to
failing
protocol-9p.1.0.0
on
5.2
is now installable. Current state is:
failing
protocol-9p.1.0.1
on
5.0
had its build status changed:
partially failing
to
failing
protocol-9p.1.0.1
on
5.1
had its build status changed:
partially failing
to
failing
protocol-9p.1.0.1
on
5.2
is now installable. Current state is:
failing
proverif.1.98
on
5.0
had its build status changed:
partially failing
to
failing
proverif.1.98
on
5.1
had its build status changed:
partially failing
to
failing
proverif.1.98
on
5.2
is now installable. Current state is:
failing
proverif.1.98pl1
on
5.0
had its build status changed:
partially failing
to
failing
proverif.1.98pl1
on
5.1
had its build status changed:
partially failing
to
failing
proverif.1.98pl1
on
5.2
is now installable. Current state is:
failing
proverif.2.00
on
5.0
had its build status changed:
partially failing
to
failing
proverif.2.00
on
5.1
had its build status changed:
partially failing
to
failing
proverif.2.00
on
5.2
is now installable. Current state is:
failing
pythonlib.v0.15.1
on
5.1
had its build status changed:
partially failing
to
failing
qcow.0.10.0
on
4.08
had its build status changed:
partially failing
to
failing
qcow.0.10.0
on
4.09
had its build status changed:
partially failing
to
failing
qcow.0.10.2
on
4.08
had its build status changed:
partially failing
to
failing
qcow.0.10.2
on
4.09
had its build status changed:
partially failing
to
failing
qcow.0.10.3
on
4.08
had its build status changed:
partially failing
to
failing
qcow.0.10.3
on
4.09
had its build status changed:
partially failing
to
failing
qcow.0.10.4
on
4.08
had its build status changed:
partially failing
to
failing
qcow.0.10.4
on
4.09
had its build status changed:
partially failing
to
failing
qrencode.0.2
on
5.0
had its build status changed:
partially failing
to
failing
qrencode.0.2
on
5.1
had its build status changed:
partially failing
to
failing
qrencode.0.2
on
5.2
is now installable. Current state is:
failing
radare2.0.0.2
on
4.12
had its build status changed:
partially failing
to
failing
radare2.0.0.2
on
4.13
had its build status changed:
partially failing
to
failing
radare2.0.0.2
on
4.14
had its build status changed:
partially failing
to
failing
randoml.0.1.5
on
5.0
had its build status changed:
partially failing
to
failing
randoml.0.1.5
on
5.1
had its build status changed:
partially failing
to
failing
randoml.0.1.5
on
5.2
is now installable. Current state is:
failing
raygui.1.3.0
on
4.08
is now installable. Current state is:
failing
raygui.1.3.0
on
4.09
is now installable. Current state is:
failing
raygui.1.3.0
on
4.10
is now installable. Current state is:
failing
raygui.1.3.0
on
4.11
is now installable. Current state is:
failing
raygui.1.3.0
on
4.12
is now installable. Current state is:
failing
raygui.1.3.0
on
4.13
is now installable. Current state is:
failing
raygui.1.3.0
on
4.14
is now installable. Current state is:
failing
raygui.1.3.0
on
5.0
is now installable. Current state is:
failing
raygui.1.3.0
on
5.1
is now installable. Current state is:
failing
raygui.1.3.0
on
5.2
is now installable. Current state is:
failing
raylib.0.1.0
on
4.08
had its build status changed:
partially failing
to
failing
raylib.0.1.0
on
4.09
had its build status changed:
partially failing
to
failing
raylib.0.1.0
on
4.10
had its build status changed:
partially failing
to
failing
raylib.0.1.0
on
4.11
had its build status changed:
partially failing
to
failing
raylib.0.1.0
on
4.12
had its build status changed:
partially failing
to
failing
raylib.0.1.0
on
4.13
had its build status changed:
partially failing
to
failing
raylib.0.1.0
on
4.14
had its build status changed:
partially failing
to
failing
raylib.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
raylib.0.2.2
on
4.08
had its build status changed:
partially failing
to
failing
raylib.0.2.2
on
4.09
had its build status changed:
partially failing
to
failing
raylib.0.2.2
on
4.10
had its build status changed:
partially failing
to
failing
raylib.0.2.2
on
4.11
had its build status changed:
partially failing
to
failing
raylib.0.2.2
on
4.12
had its build status changed:
partially failing
to
failing
raylib.0.2.2
on
4.13
had its build status changed:
partially failing
to
failing
raylib.0.2.2
on
4.14
had its build status changed:
partially failing
to
failing
raylib.0.2.2
on
5.0
had its build status changed:
partially failing
to
failing
raylib.0.3.1
on
4.08
had its build status changed:
partially failing
to
failing
raylib.0.3.1
on
4.09
had its build status changed:
partially failing
to
failing
raylib.0.3.1
on
4.10
had its build status changed:
partially failing
to
failing
raylib.0.3.1
on
4.11
had its build status changed:
partially failing
to
failing
raylib.0.3.1
on
4.12
had its build status changed:
partially failing
to
failing
raylib.0.3.1
on
4.13
had its build status changed:
partially failing
to
failing
raylib.0.3.1
on
4.14
had its build status changed:
partially failing
to
failing
raylib.0.3.1
on
5.0
had its build status changed:
partially failing
to
failing
raylib.0.3.2
on
4.08
had its build status changed:
partially failing
to
failing
raylib.0.3.2
on
4.09
had its build status changed:
partially failing
to
failing
raylib.0.3.2
on
4.10
had its build status changed:
partially failing
to
failing
raylib.0.3.2
on
4.11
had its build status changed:
partially failing
to
failing
raylib.0.3.2
on
4.12
had its build status changed:
partially failing
to
failing
raylib.0.3.2
on
4.13
had its build status changed:
partially failing
to
failing
raylib.0.3.2
on
4.14
had its build status changed:
partially failing
to
failing
raylib.0.3.2
on
5.0
had its build status changed:
partially failing
to
failing
raylib.0.4.0
on
4.08
had its build status changed:
partially failing
to
failing
raylib.0.4.0
on
4.09
had its build status changed:
partially failing
to
failing
raylib.0.4.0
on
4.10
had its build status changed:
partially failing
to
failing
raylib.0.4.0
on
4.11
had its build status changed:
partially failing
to
failing
raylib.0.4.0
on
4.12
had its build status changed:
partially failing
to
failing
raylib.0.4.0
on
4.13
had its build status changed:
partially failing
to
failing
raylib.0.4.0
on
4.14
had its build status changed:
partially failing
to
failing
raylib.0.4.0
on
5.0
had its build status changed:
partially failing
to
failing
raylib.0.5.1
on
4.08
had its build status changed:
partially failing
to
failing
raylib.0.5.1
on
4.09
had its build status changed:
partially failing
to
failing
raylib.0.5.1
on
4.10
had its build status changed:
partially failing
to
failing
raylib.0.5.1
on
4.11
had its build status changed:
partially failing
to
failing
raylib.0.5.1
on
4.12
had its build status changed:
partially failing
to
failing
raylib.0.5.1
on
4.13
had its build status changed:
partially failing
to
failing
raylib.0.5.1
on
4.14
had its build status changed:
partially failing
to
failing
raylib.0.5.1
on
5.0
had its build status changed:
partially failing
to
failing
rdf.0.11.0
on
4.08
had its build status changed:
partially failing
to
failing
rdf.0.11.0
on
4.09
had its build status changed:
partially failing
to
failing
rdf.0.11.0
on
4.10
had its build status changed:
partially failing
to
failing
rdf.0.12.0
on
4.12
had its build status changed:
partially failing
to
failing
reason.3.5.0
on
4.08
had its build status changed:
partially failing
to
failing
reason.3.5.2
on
4.08
had its build status changed:
partially failing
to
failing
reason.3.5.2
on
4.09
had its build status changed:
partially failing
to
failing
records.0.6.0
on
4.08
had its build status changed:
partially failing
to
failing
rotor.0.1
on
4.08
had its build status changed:
internal failure
to
failing
rtop.3.5.2
on
4.08
had its build status changed:
partially failing
to
failing
rtop.3.5.2
on
4.09
had its build status changed:
partially failing
to
failing
rtop.3.6.0
on
4.08
had its build status changed:
partially failing
to
failing
rtop.3.6.0
on
4.09
had its build status changed:
partially failing
to
failing
rtop.3.6.0
on
4.10
had its build status changed:
partially failing
to
failing
rtop.3.6.2
on
4.08
had its build status changed:
partially failing
to
failing
rtop.3.6.2
on
4.09
had its build status changed:
partially failing
to
failing
rtop.3.6.2
on
4.10
had its build status changed:
partially failing
to
failing
rtop.3.6.2
on
4.11
had its build status changed:
partially failing
to
failing
rtop.3.7.0
on
4.08
had its build status changed:
partially failing
to
failing
rtop.3.7.0
on
4.09
had its build status changed:
partially failing
to
failing
rtop.3.7.0
on
4.10
had its build status changed:
partially failing
to
failing
rtop.3.7.0
on
4.11
had its build status changed:
partially failing
to
failing
rtop.3.7.0
on
4.12
had its build status changed:
partially failing
to
failing
sanlock.0.0.9
on
4.08
had its build status changed:
partially failing
to
failing
sanlock.0.0.9
on
4.09
had its build status changed:
partially failing
to
failing
sanlock.0.0.9
on
4.10
had its build status changed:
partially failing
to
failing
sanlock.0.0.9
on
4.11
had its build status changed:
partially failing
to
failing
sanlock.0.0.9
on
4.12
had its build status changed:
partially failing
to
failing
secp256k1.0.1.5
on
4.08
is now installable. Current state is:
failing
secp256k1.0.1.5
on
4.09
is now installable. Current state is:
failing
secp256k1.0.1.5
on
4.10
is now installable. Current state is:
failing
secp256k1.0.1.5
on
4.11
is now installable. Current state is:
failing
secp256k1.0.1.5
on
4.12
is now installable. Current state is:
failing
secp256k1.0.1.5
on
4.13
is now installable. Current state is:
failing
secp256k1.0.1.5
on
4.14
is now installable. Current state is:
failing
sexp.v0.12.0
on
4.08
had its build status changed:
partially failing
to
failing
sexp.v0.12.0
on
4.09
had its build status changed:
partially failing
to
failing
sexp.v0.13.0
on
4.08
had its build status changed:
partially failing
to
failing
sexp.v0.13.0
on
4.09
had its build status changed:
partially failing
to
failing
sexp.v0.13.0
on
4.10
had its build status changed:
partially failing
to
failing
sexp.v0.13.0
on
4.11
had its build status changed:
partially failing
to
failing
sexp.v0.14.0
on
4.08
had its build status changed:
partially failing
to
failing
sexp.v0.14.0
on
4.09
had its build status changed:
partially failing
to
failing
sexp.v0.14.0
on
4.10
had its build status changed:
partially failing
to
failing
sexp.v0.14.0
on
4.11
had its build status changed:
partially failing
to
failing
sexp.v0.14.0
on
4.12
had its build status changed:
partially failing
to
failing
sexp.v0.14.0
on
4.13
had its build status changed:
partially failing
to
failing
sexp.v0.14.0
on
4.14
had its build status changed:
partially failing
to
failing
sexp.v0.15.0
on
4.11
had its build status changed:
partially failing
to
failing
sexp.v0.15.0
on
4.12
had its build status changed:
partially failing
to
failing
sexp.v0.15.0
on
4.13
had its build status changed:
partially failing
to
failing
sexp.v0.15.0
on
4.14
had its build status changed:
partially failing
to
failing
sexp.v0.15.0
on
5.0
had its build status changed:
partially failing
to
failing
sha.1.10
on
4.08
had its build status changed:
passing
to
failing
sha.1.10
on
4.09
had its build status changed:
passing
to
failing
sha.1.10
on
4.10
had its build status changed:
passing
to
failing
sha.1.10
on
4.11
had its build status changed:
passing
to
failing
sha.1.10
on
4.12
had its build status changed:
passing
to
failing
sha.1.10
on
4.13
had its build status changed:
passing
to
failing
sha.1.10
on
4.14
had its build status changed:
passing
to
failing
sha.1.11
on
4.08
had its build status changed:
passing
to
failing
sha.1.11
on
4.09
had its build status changed:
passing
to
failing
sha.1.11
on
4.10
had its build status changed:
passing
to
failing
sha.1.11
on
4.11
had its build status changed:
passing
to
failing
sha.1.11
on
4.12
had its build status changed:
passing
to
failing
sha.1.11
on
4.13
had its build status changed:
passing
to
failing
sha.1.11
on
4.14
had its build status changed:
passing
to
failing
solo5-bindings-hvt.0.6.5
on
5.2
is now installable. Current state is:
failing
solo5-bindings-hvt.0.6.6
on
5.2
is now installable. Current state is:
failing
solo5-bindings-hvt.0.6.7
on
5.2
is now installable. Current state is:
failing
solo5-bindings-hvt.0.6.8
on
5.2
is now installable. Current state is:
failing
solo5-bindings-hvt.0.6.9
on
5.2
is now installable. Current state is:
failing
solo5-bindings-muen.0.6.5
on
5.2
is now installable. Current state is:
failing
solo5-bindings-muen.0.6.6
on
5.2
is now installable. Current state is:
failing
solo5-bindings-muen.0.6.7
on
5.2
is now installable. Current state is:
failing
solo5-bindings-muen.0.6.8
on
5.2
is now installable. Current state is:
failing
solo5-bindings-muen.0.6.9
on
5.2
is now installable. Current state is:
failing
solo5-bindings-spt.0.6.5
on
5.2
is now installable. Current state is:
failing
solo5-bindings-spt.0.6.6
on
5.2
is now installable. Current state is:
failing
solo5-bindings-spt.0.6.7
on
5.2
is now installable. Current state is:
failing
solo5-bindings-spt.0.6.8
on
5.2
is now installable. Current state is:
failing
solo5-bindings-spt.0.6.9
on
5.2
is now installable. Current state is:
failing
solo5-bindings-virtio.0.6.5
on
5.2
is now installable. Current state is:
failing
solo5-bindings-virtio.0.6.6
on
5.2
is now installable. Current state is:
failing
solo5-bindings-virtio.0.6.7
on
5.2
is now installable. Current state is:
failing
solo5-bindings-virtio.0.6.8
on
5.2
is now installable. Current state is:
failing
solo5-bindings-virtio.0.6.9
on
5.2
is now installable. Current state is:
failing
solo5-bindings-xen.0.6.6
on
5.2
is now installable. Current state is:
failing
solo5-bindings-xen.0.6.7
on
5.2
is now installable. Current state is:
failing
solo5-bindings-xen.0.6.8
on
5.2
is now installable. Current state is:
failing
solo5-bindings-xen.0.6.9
on
5.2
is now installable. Current state is:
failing
solo5.0.7.0
on
5.2
is now installable. Current state is:
failing
solo5.0.7.1
on
5.2
is now installable. Current state is:
failing
stdcompat.0
on
5.0
had its build status changed:
partially failing
to
failing
stdcompat.0
on
5.1
had its build status changed:
partially failing
to
failing
stdcompat.1
on
5.0
had its build status changed:
partially failing
to
failing
stdcompat.1
on
5.1
had its build status changed:
partially failing
to
failing
stog.0.19.0
on
4.12
had its build status changed:
partially failing
to
failing
stog_rdf.0.20.0
on
4.12
had its build status changed:
partially failing
to
failing
stog_server.0.20.0
on
4.12
had its build status changed:
partially failing
to
failing
systemverilog.0.0.1
on
5.1
had its build status changed:
partially failing
to
failing
systemverilog.0.0.1
on
5.2
is now installable. Current state is:
failing
tcpip.4.0.0
on
4.08
had its build status changed:
partially failing
to
failing
tcpip.4.0.0
on
4.09
had its build status changed:
partially failing
to
failing
tcpip.4.0.0
on
4.10
had its build status changed:
partially failing
to
failing
tcpip.4.0.0
on
4.11
had its build status changed:
partially failing
to
failing
tensorflow.0.0.11
on
4.08
had its build status changed:
passing
to
failing
tensorflow.0.0.11
on
4.09
had its build status changed:
passing
to
failing
tensorflow.0.0.11
on
4.10
had its build status changed:
passing
to
failing
tensorflow.0.0.11
on
4.11
had its build status changed:
passing
to
failing
tidy.1-4.9.30-0.1.1
on
4.08
had its build status changed:
partially failing
to
failing
tidy.1-4.9.30-0.1.1
on
4.09
had its build status changed:
partially failing
to
failing
tidy.5-0.2
on
4.08
had its build status changed:
partially failing
to
failing
tidy.5-0.2
on
4.09
had its build status changed:
partially failing
to
failing
tldr.0.1
on
4.08
had its build status changed:
partially failing
to
failing
tldr.0.1
on
4.09
had its build status changed:
partially failing
to
failing
tldr.0.2
on
4.08
had its build status changed:
partially failing
to
failing
tldr.0.2
on
4.09
had its build status changed:
partially failing
to
failing
toplevel_expect_test.v0.12.2
on
4.08
had its build status changed:
partially failing
to
failing
toplevel_expect_test.v0.12.2
on
4.09
had its build status changed:
partially failing
to
failing
toplevel_expect_test.v0.13.0
on
4.08
had its build status changed:
partially failing
to
failing
toplevel_expect_test.v0.13.0
on
4.09
had its build status changed:
partially failing
to
failing
toplevel_expect_test.v0.13.0
on
4.10
had its build status changed:
partially failing
to
failing
toplevel_expect_test.v0.13.0
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.10
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.10
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.10
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.10
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.10
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.10
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.10
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.10
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.10
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.10
on
5.2
is now installable. Current state is:
failing
torch.0.11
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.11
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.11
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.11
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.11
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.11
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.11
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.11
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.11
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.11
on
5.2
is now installable. Current state is:
failing
torch.0.12
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.12
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.12
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.12
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.12
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.12
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.12
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.12
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.12
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.12
on
5.2
is now installable. Current state is:
failing
torch.0.13
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.13
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.13
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.13
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.13
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.13
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.13
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.13
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.13
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.13
on
5.2
is now installable. Current state is:
failing
torch.0.14
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.14
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.14
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.14
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.14
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.14
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.14
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.14
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.14
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.14
on
5.2
is now installable. Current state is:
failing
torch.0.15
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.15
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.15
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.15
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.15
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.15
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.15
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.15
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.15
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.15
on
5.2
is now installable. Current state is:
failing
torch.0.16
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.16
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.16
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.16
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.16
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.16
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.16
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.16
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.16
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.16
on
5.2
is now installable. Current state is:
failing
torch.0.17
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.17
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.17
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.17
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.17
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.17
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.17
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.17
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.17
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.17
on
5.2
is now installable. Current state is:
failing
torch.0.4
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.4
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.4
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.4
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.4
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.4
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.4
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.5
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.5
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.5
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.5
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.5
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.5
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.5
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.6
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.6
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.6
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.6
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.6
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.6
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.6
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.6
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.6
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.6
on
5.2
is now installable. Current state is:
failing
torch.0.7
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.7
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.7
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.7
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.7
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.7
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.7
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.7
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.7
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.7
on
5.2
is now installable. Current state is:
failing
torch.0.8
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.8
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.8
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.8
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.8
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.8
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.8
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.8
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.8
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.8
on
5.2
is now installable. Current state is:
failing
torch.0.9
on
4.08
had its build status changed:
partially failing
to
failing
torch.0.9
on
4.09
had its build status changed:
partially failing
to
failing
torch.0.9
on
4.10
had its build status changed:
partially failing
to
failing
torch.0.9
on
4.11
had its build status changed:
partially failing
to
failing
torch.0.9
on
4.12
had its build status changed:
partially failing
to
failing
torch.0.9
on
4.13
had its build status changed:
partially failing
to
failing
torch.0.9
on
4.14
had its build status changed:
partially failing
to
failing
torch.0.9
on
5.0
had its build status changed:
partially failing
to
failing
torch.0.9
on
5.1
had its build status changed:
partially failing
to
failing
torch.0.9
on
5.2
is now installable. Current state is:
failing
torch.v0.16.0
on
4.14
had its build status changed:
partially failing
to
failing
torch.v0.16.0
on
5.0
had its build status changed:
partially failing
to
failing
torch.v0.16.0
on
5.1
had its build status changed:
partially failing
to
failing
torch.v0.16.0
on
5.2
is now installable. Current state is:
failing
torch.v0.17.0
on
5.1
is now installable. Current state is:
failing
torch.v0.17.0
on
5.2
is now installable. Current state is:
failing
tplib.1.3
on
5.2
is now installable. Current state is:
failing
tuareg.2.0.10
on
5.2
is now installable. Current state is:
failing
tuareg.2.0.7
on
5.2
is now installable. Current state is:
failing
tuareg.2.1.0
on
4.09
had its build status changed:
passing
to
failing
tuareg.2.1.0
on
4.12
had its build status changed:
passing
to
failing
tuareg.2.1.0
on
4.14
had its build status changed:
passing
to
failing
tuareg.2.1.0
on
5.1
had its build status changed:
passing
to
failing
uri-bench.4.4.0
on
4.08
had its build status changed:
partially failing
to
failing
uri-bench.4.4.0
on
4.09
had its build status changed:
partially failing
to
failing
uri-bench.4.4.0
on
4.10
had its build status changed:
partially failing
to
failing
uri-bench.4.4.0
on
4.11
had its build status changed:
partially failing
to
failing
uri-bench.4.4.0
on
4.12
had its build status changed:
partially failing
to
failing
uri-bench.4.4.0
on
4.13
had its build status changed:
partially failing
to
failing
uri.1.9.7
on
4.12
had its build status changed:
partially failing
to
failing
uuuu.0.1.0
on
4.08
had its build status changed:
partially failing
to
failing
uuuu.0.1.1
on
4.08
had its build status changed:
partially failing
to
failing
uwt.0.3.0
on
4.08
had its build status changed:
partially failing
to
failing
uwt.0.3.0
on
4.09
had its build status changed:
partially failing
to
failing
uwt.0.3.0
on
4.10
had its build status changed:
partially failing
to
failing
uwt.0.3.0
on
4.11
had its build status changed:
partially failing
to
failing
uwt.0.3.0.2
on
4.08
had its build status changed:
partially failing
to
failing
uwt.0.3.0.2
on
4.09
had its build status changed:
partially failing
to
failing
uwt.0.3.0.2
on
4.10
had its build status changed:
partially failing
to
failing
uwt.0.3.0.2
on
4.11
had its build status changed:
partially failing
to
failing
uwt.0.3.2
on
4.08
had its build status changed:
partially failing
to
failing
uwt.0.3.2
on
4.09
had its build status changed:
partially failing
to
failing
uwt.0.3.2
on
4.10
had its build status changed:
partially failing
to
failing
uwt.0.3.2
on
4.11
had its build status changed:
partially failing
to
failing
uwt.0.3.3
on
4.08
had its build status changed:
partially failing
to
failing
uwt.0.3.3
on
4.09
had its build status changed:
partially failing
to
failing
uwt.0.3.3
on
4.10
had its build status changed:
partially failing
to
failing
uwt.0.3.3
on
4.11
had its build status changed:
partially failing
to
failing
vcaml.v0.16.0
on
5.1
had its build status changed:
partially failing
to
failing
vcaml.v0.16.0
on
5.2
is now installable. Current state is:
failing
vhd-format.0.12.0
on
4.08
had its build status changed:
partially failing
to
failing
vhd-format.0.12.0
on
4.09
had its build status changed:
partially failing
to
failing
vhd-format.0.12.0
on
4.10
had its build status changed:
partially failing
to
failing
vhd-format.0.12.0
on
4.11
had its build status changed:
partially failing
to
failing
vhd-format.0.12.0
on
4.12
had its build status changed:
partially failing
to
failing
vhd-format.0.12.1
on
4.08
had its build status changed:
partially failing
to
failing
vhd-format.0.12.1
on
4.09
had its build status changed:
partially failing
to
failing
vhd-format.0.12.1
on
4.10
had its build status changed:
partially failing
to
failing
vhd-format.0.12.1
on
4.11
had its build status changed:
partially failing
to
failing
vhd-format.0.12.1
on
4.12
had its build status changed:
partially failing
to
failing
wall.0.3
on
4.08
had its build status changed:
passing
to
failing
wall.0.3
on
4.09
had its build status changed:
passing
to
failing
wasmtime.0.0.1
on
4.10
had its build status changed:
partially failing
to
failing
wasmtime.0.0.1
on
4.11
had its build status changed:
partially failing
to
failing
wasmtime.0.0.1
on
4.12
had its build status changed:
partially failing
to
failing
wasmtime.0.0.1
on
4.13
had its build status changed:
partially failing
to
failing
wasmtime.0.0.1
on
4.14
had its build status changed:
partially failing
to
failing
wasmtime.0.0.1
on
5.0
had its build status changed:
partially failing
to
failing
wasmtime.0.0.1
on
5.1
had its build status changed:
partially failing
to
failing
wasmtime.0.0.1
on
5.2
is now installable. Current state is:
failing
wasmtime.0.0.2
on
4.10
had its build status changed:
partially failing
to
failing
wasmtime.0.0.2
on
4.11
had its build status changed:
partially failing
to
failing
wasmtime.0.0.2
on
4.12
had its build status changed:
partially failing
to
failing
wasmtime.0.0.2
on
4.13
had its build status changed:
partially failing
to
failing
wasmtime.0.0.2
on
4.14
had its build status changed:
partially failing
to
failing
wasmtime.0.0.2
on
5.0
had its build status changed:
partially failing
to
failing
wasmtime.0.0.2
on
5.1
had its build status changed:
partially failing
to
failing
wasmtime.0.0.2
on
5.2
is now installable. Current state is:
failing
wasmtime.0.0.3
on
4.10
had its build status changed:
partially failing
to
failing
wasmtime.0.0.3
on
4.11
had its build status changed:
partially failing
to
failing
wasmtime.0.0.3
on
4.12
had its build status changed:
partially failing
to
failing
wasmtime.0.0.3
on
4.13
had its build status changed:
partially failing
to
failing
wasmtime.0.0.3
on
4.14
had its build status changed:
partially failing
to
failing
wasmtime.0.0.3
on
5.0
had its build status changed:
partially failing
to
failing
wasmtime.0.0.3
on
5.1
had its build status changed:
partially failing
to
failing
wasmtime.0.0.3
on
5.2
is now installable. Current state is:
failing
websocket-async.2.17
on
5.1
is now installable. Current state is:
failing
websocket-async.2.17
on
5.2
is now installable. Current state is:
failing
why3.1.1.1
on
4.08
had its build status changed:
passing
to
failing
why3.1.2.1
on
4.08
had its build status changed:
passing
to
failing
why3.1.2.1
on
4.09
had its build status changed:
passing
to
failing
win-eventlog.0.3
on
5.0
had its build status changed:
partially failing
to
failing
win-eventlog.0.3
on
5.1
had its build status changed:
partially failing
to
failing
win-eventlog.0.3
on
5.2
is now installable. Current state is:
failing
xen-evtchn-unix.2.0.0
on
4.08
had its build status changed:
passing
to
failing
xen-evtchn-unix.2.0.0
on
4.09
had its build status changed:
passing
to
failing
xen-evtchn-unix.2.0.0
on
4.10
had its build status changed:
passing
to
failing
xen-evtchn-unix.2.0.0
on
4.11
had its build status changed:
passing
to
failing
xen-evtchn-unix.2.0.0
on
4.12
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.0.0
on
4.13
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.0.0
on
4.14
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
4.08
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
4.09
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
4.10
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
4.11
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
4.12
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
4.13
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
4.14
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
5.0
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
5.1
had its build status changed:
partially failing
to
failing
xen-evtchn-unix.2.1.0
on
5.2
is now installable. Current state is:
failing
xen-evtchn.1.0.7
on
4.08
had its build status changed:
partially failing
to
failing
xen-evtchn.1.0.7
on
4.09
had its build status changed:
partially failing
to
failing
xen-evtchn.1.0.7
on
4.10
had its build status changed:
partially failing
to
failing
xen-evtchn.1.0.7
on
4.11
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.0.0
on
4.08
had its build status changed:
passing
to
failing
xen-gnt-unix.3.0.0
on
4.09
had its build status changed:
passing
to
failing
xen-gnt-unix.3.0.0
on
4.10
had its build status changed:
passing
to
failing
xen-gnt-unix.3.0.0
on
4.11
had its build status changed:
passing
to
failing
xen-gnt-unix.3.0.0
on
4.12
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.0.0
on
4.13
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.0.0
on
4.14
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.0.1
on
4.08
had its build status changed:
passing
to
failing
xen-gnt-unix.3.0.1
on
4.09
had its build status changed:
passing
to
failing
xen-gnt-unix.3.0.1
on
4.10
had its build status changed:
passing
to
failing
xen-gnt-unix.3.0.1
on
4.11
had its build status changed:
passing
to
failing
xen-gnt-unix.3.0.1
on
4.12
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.0.1
on
4.13
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.0.1
on
4.14
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.1.0
on
4.08
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.1.0
on
4.09
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.1.0
on
4.10
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.1.0
on
4.11
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.1.0
on
4.12
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.1.0
on
4.13
had its build status changed:
partially failing
to
failing
xen-gnt-unix.3.1.0
on
4.14
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.0
on
4.08
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.0
on
4.09
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.0
on
4.10
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.0
on
4.11
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.0
on
4.12
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.0
on
4.13
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.0
on
4.14
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.1
on
4.08
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.1
on
4.09
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.1
on
4.10
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.1
on
4.11
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.1
on
4.12
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.1
on
4.13
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.1
on
4.14
had its build status changed:
partially failing
to
failing
xen-gnt-unix.4.0.2
on
4.08
is now installable. Current state is:
failing
xen-gnt-unix.4.0.2
on
4.09
is now installable. Current state is:
failing
xen-gnt-unix.4.0.2
on
4.10
is now installable. Current state is:
failing
xen-gnt-unix.4.0.2
on
4.11
is now installable. Current state is:
failing
xen-gnt-unix.4.0.2
on
4.12
is now installable. Current state is:
failing
xen-gnt-unix.4.0.2
on
4.13
is now installable. Current state is:
failing
xen-gnt-unix.4.0.2
on
4.14
is now installable. Current state is:
failing
yices2.0.0.2
on
4.08
had its build status changed:
passing
to
failing
yices2.0.0.2
on
4.09
had its build status changed:
passing
to
failing
yices2.0.0.2
on
4.10
had its build status changed:
passing
to
failing
yices2.0.0.2
on
4.11
had its build status changed:
passing
to
failing
yices2.0.0.2
on
4.12
had its build status changed:
passing
to
failing
yices2.0.0.2
on
4.13
had its build status changed:
passing
to
failing
yices2.0.0.2
on
4.14
had its build status changed:
passing
to
failing
yices2.0.0.2
on
5.0
had its build status changed:
passing
to
failing
yices2.0.0.2
on
5.1
had its build status changed:
passing
to
failing
yices2.0.0.3
on
4.08
had its build status changed:
passing
to
failing
yices2.0.0.3
on
4.09
had its build status changed:
passing
to
failing
yices2.0.0.3
on
4.10
had its build status changed:
passing
to
failing
yices2.0.0.3
on
4.11
had its build status changed:
passing
to
failing
yices2.0.0.3
on
4.12
had its build status changed:
passing
to
failing
yices2.0.0.3
on
4.13
had its build status changed:
passing
to
failing
yices2.0.0.3
on
4.14
had its build status changed:
passing
to
failing
yices2.0.0.3
on
5.0
had its build status changed:
passing
to
failing
yices2.0.0.3
on
5.1
had its build status changed:
passing
to
failing
yojson-bench.2.0.0
on
4.08
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.0
on
4.09
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.0
on
4.10
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.0
on
4.11
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.0
on
4.12
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.0
on
4.13
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.1
on
4.08
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.1
on
4.09
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.1
on
4.10
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.1
on
4.11
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.1
on
4.12
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.1
on
4.13
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.2
on
4.08
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.2
on
4.09
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.2
on
4.10
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.2
on
4.11
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.2
on
4.12
had its build status changed:
partially failing
to
failing
yojson-bench.2.0.2
on
4.13
had its build status changed:
partially failing
to
failing
zlib.0.6
on
4.08
had its build status changed:
partially failing
to
failing
zlib.0.6
on
4.09
had its build status changed:
partially failing
to
failing
zlib.0.6
on
4.10
had its build status changed:
partially failing
to
failing
zlib.0.6
on
4.11
had its build status changed:
partially failing
to
failing
zlib.0.6
on
4.12
had its build status changed:
partially failing
to
failing
zlib.0.6
on
4.13
had its build status changed:
partially failing
to
failing
zlib.0.6
on
4.14
had its build status changed:
partially failing
to
failing
zlib.0.6
on
5.0
had its build status changed:
partially failing
to
failing
zlib.0.6
on
5.1
had its build status changed:
partially failing
to
failing
zlib.0.6
on
5.2
is now installable. Current state is:
failing
zxcvbn.2.3+2
on
4.08
had its build status changed:
partially failing
to
failing
zxcvbn.2.3+2
on
4.09
had its build status changed:
partially failing
to
failing
zxcvbn.2.3+2
on
4.10
had its build status changed:
partially failing
to
failing
zxcvbn.2.3+2
on
4.11
had its build status changed:
partially failing
to
failing
zxcvbn.2.3+2
on
4.12
had its build status changed:
partially failing
to
failing
Packages now
partially failing
:
arrayjit.0.3.3
on
5.1
is now installable. Current state is:
partially failing
arrayjit.0.3.3
on
5.2
is now installable. Current state is:
partially failing
async_rpc_websocket.v0.17.0
on
5.1
is now installable. Current state is:
partially failing
async_rpc_websocket.v0.17.0
on
5.2
is now installable. Current state is:
partially failing
atacama.0.0.5
on
5.2
is now installable. Current state is:
partially failing
bddapron.2.3.2
on
4.08
had its build status changed:
internal failure
to
partially failing
bddrand.2.71.10
on
5.2
is now installable. Current state is:
partially failing
bddrand.2.71.15
on
5.2
is now installable. Current state is:
partially failing
binaryen.0.19.0
on
5.2
is now installable. Current state is:
partially failing
binaryen.0.21.0
on
5.2
is now installable. Current state is:
partially failing
bonsai.v0.17.0
on
5.1
is now installable. Current state is:
partially failing
bun.0.3
on
4.08
had its build status changed:
passing
to
partially failing
bun.0.3
on
4.09
had its build status changed:
passing
to
partially failing
bun.0.3
on
4.10
had its build status changed:
passing
to
partially failing
bun.0.3
on
4.11
had its build status changed:
passing
to
partially failing
bun.0.3
on
4.12
had its build status changed:
passing
to
partially failing
bun.0.3
on
4.13
had its build status changed:
passing
to
partially failing
bun.0.3
on
4.14
had its build status changed:
passing
to
partially failing
bun.0.3.1
on
4.08
had its build status changed:
passing
to
partially failing
bun.0.3.1
on
4.09
had its build status changed:
passing
to
partially failing
bun.0.3.1
on
4.10
had its build status changed:
passing
to
partially failing
bun.0.3.1
on
4.11
had its build status changed:
passing
to
partially failing
bun.0.3.1
on
4.12
had its build status changed:
passing
to
partially failing
bun.0.3.1
on
4.13
had its build status changed:
passing
to
partially failing
bun.0.3.1
on
4.14
had its build status changed:
passing
to
partially failing
bun.0.3.2
on
4.08
had its build status changed:
passing
to
partially failing
bun.0.3.2
on
4.09
had its build status changed:
passing
to
partially failing
bun.0.3.2
on
4.10
had its build status changed:
passing
to
partially failing
bun.0.3.2
on
4.11
had its build status changed:
passing
to
partially failing
bun.0.3.3
on
4.08
had its build status changed:
passing
to
partially failing
bun.0.3.3
on
4.09
had its build status changed:
passing
to
partially failing
bun.0.3.3
on
4.10
had its build status changed:
passing
to
partially failing
bun.0.3.3
on
4.11
had its build status changed:
passing
to
partially failing
cudajit.0.4.0
on
4.08
is now installable. Current state is:
partially failing
cudajit.0.4.0
on
4.09
is now installable. Current state is:
partially failing
cudajit.0.4.0
on
4.10
is now installable. Current state is:
partially failing
cudajit.0.4.0
on
4.11
is now installable. Current state is:
partially failing
cudajit.0.4.0
on
4.12
is now installable. Current state is:
partially failing
cudajit.0.4.0
on
4.13
is now installable. Current state is:
partially failing
cudajit.0.4.0
on
4.14
is now installable. Current state is:
partially failing
cudajit.0.4.0
on
5.0
is now installable. Current state is:
partially failing
cudajit.0.4.0
on
5.1
is now installable. Current state is:
partially failing
cudajit.0.4.0
on
5.2
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
4.08
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
4.09
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
4.10
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
4.11
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
4.12
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
4.13
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
4.14
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
5.0
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
5.1
is now installable. Current state is:
partially failing
cudajit.0.4.1
on
5.2
is now installable. Current state is:
partially failing
cudajit.0.5.0
on
4.12
is now installable. Current state is:
partially failing
cudajit.0.5.0
on
4.13
is now installable. Current state is:
partially failing
cudajit.0.5.0
on
4.14
is now installable. Current state is:
partially failing
cudajit.0.5.0
on
5.0
is now installable. Current state is:
partially failing
cudajit.0.5.0
on
5.1
is now installable. Current state is:
partially failing
cudajit.0.5.0
on
5.2
is now installable. Current state is:
partially failing
duppy.0.7.0
on
5.1
had its build status changed:
not available
to
partially failing
duppy.0.7.1
on
5.1
had its build status changed:
not available
to
partially failing
duppy.0.7.3
on
5.1
had its build status changed:
not available
to
partially failing
extprot.1.7.0
on
5.1
had its build status changed:
not available
to
partially failing
ffmpeg-av.1.0.0
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.0.0~beta1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.0.0~beta2
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.0.0~rc1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.0.1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.0
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
4.08
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
4.09
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
4.10
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
4.11
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
4.12
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
4.13
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
4.14
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
5.0
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
5.1
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.10
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
4.08
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
4.09
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
4.10
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
4.11
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
4.12
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
4.13
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
4.14
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
5.0
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
5.1
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.11
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.2
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.3
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.4
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.5
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.6
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.7
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.8
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-av.1.1.9
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.0.0
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.0.0~beta1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.0.0~beta2
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.0.0~rc1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.0.1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.0
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
4.08
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
4.09
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
4.10
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
4.11
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
4.12
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
4.13
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
4.14
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
5.0
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
5.1
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.10
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
4.08
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
4.09
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
4.10
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
4.11
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
4.12
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
4.13
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
4.14
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
5.0
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
5.1
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.11
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.2
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.3
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.4
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.5
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.6
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.7
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.8
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avcodec.1.1.9
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.0.0
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.0.0~beta1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.0.0~beta2
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.0.0~rc1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.0.1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.0
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
4.08
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
4.09
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
4.10
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
4.11
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
4.12
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
4.13
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
4.14
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
5.0
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
5.1
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.10
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
4.08
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
4.09
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
4.10
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
4.11
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
4.12
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
4.13
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
4.14
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
5.0
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
5.1
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.11
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.2
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.3
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.4
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.5
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.6
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.7
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.8
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avdevice.1.1.9
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.0.0
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.0.0~beta1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.0.0~beta2
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.0.0~rc1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.0.1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.0
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.1
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
4.08
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
4.09
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
4.10
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
4.11
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
4.12
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
4.13
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
4.14
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
5.0
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
5.1
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.10
on
5.2
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.11
on
4.08
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.11
on
4.09
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.11
on
4.10
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.11
on
4.11
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.11
on
4.12
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.11
on
4.13
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.11
on
4.14
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.11
on
5.0
is now installable. Current state is:
partially failing
ffmpeg-avfilter.1.1.11
on
5.1
is now installable. Current state is:
partially failing</
Home|Differences with the last checks|Previous runs Home|Differences with the last checks|Previous runs