Packages in experimental/i386 where the build dependencies failed to be satisfied
55 (3.3%) packages where the build dependencies failed to be satisfied. Note that temporary failures (eg. due to network problems) are automatically rescheduled every 4 hours.
freedombox
vuls
libjogl2-java
davmail
golang-opentelemetry-contrib
gazebo
pynormaliz
gitlab
rust-nitrokey
golang-github-grpc-ecosystem-grpc-gateway.v2
faumachine
rust-sequoia-octopus-librnp
ruby-webauthn
esdm
edk2
gitaly
gnome-shell
tracker-miners
rust-gstreamer
q2-quality-control
rust-microformats
rust-isahc
node-solid-jose
golang-opentelemetry-proto
emperor
q2-metadata
tycho
golang-github-google-cel-go
parmed
golang-google-grpc
golang-github-google-cel-spec
golang-google-genproto
vault
zeekctl
etesync-dav
node-trust-jwa
freebayes
fastqc
libewf
imip-agent
phonetisaurus
rust-nitrokey-sys
sequitur-g2p
tensorflow
freedict-swa-eng#
keysafe
cura
urjtag
enhanceio
critterding
rust-gstreamer-audio
rust-gstreamer-base
rust-gstreamer-video
ipywidgets
python-pdbfixer
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.