Packages in experimental/amd64 tested in the last 24h for build reproducibility
37 packages (5.9% of 625) failed to build reproducibly in total, 2 (4.5% of 44) of them in the last 24h in experimental/amd64:
92 packages (14.7% of 625) failed to build from source in total, 10 (22.7% of 44) of them in the last 24h in experimental/amd64:
ruby-omniauth-salesforce
ruby-gitlab-pg-query
kworkflow
kata-containers
scap-workbench
polyml
darkice
nvidia-texture-tools
tracker-miners
thrift
42 packages (6.7% of 625) failed to satisfy their build-dependencies, 6 (13.6% of 44) of them in the last 24h in experimental/amd64:
opensnitch
liblsl
golang-github-google-cel-spec
rust-nitrokey
node-solid-jose
etesync-dav
443 packages (70.9% of 625) successfully built reproducibly in total, 25 (56.8% of 44) of them in the last 24h in experimental/amd64:
ruby-console
go-gir-generator
maven-jflex-plugin
libvirt-tck
libtaverna2-server-java
m2m-aligner
libmarpa
subethasmtp
zarr
libgpiod
ppp
fuse3
bind9#
libosmo-sccp
libsodium
node-d3-color
inkscape-textext
badger
spamassassin
cgreen
libsdl3-mixer
tinysparql
gnome-shell
apt
mutter
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
A # sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a P means a
pending bug while # indicates a
closed bug. In cases of several bugs, the symbol is repeated.