Packages in experimental/i386 where the build dependencies failed to be satisfied

58 (12.1%) packages where the build dependencies failed to be satisfied. Note that temporary failures (eg. due to network problems) are automatically rescheduled every 4 hours.

rust-piet-cairo opensnitch odc fckit xorgxrdp rust-nitrokey esdm procdump liblsl golang-github-google-cel-spec zeekctl node-solid-jose vault etesync-dav eckit meson code-saturne ruby-devise-i18n libewf node-trust-jwa bcachefs-tools freebayes go-cpe-dictionary phonetisaurus daq php-sabre-vobject# mediagoblin critterding groestlcoin android-cuttlefish osmo-iuh grpc osmo-hlr r-bioc-alabaster.matrix r-cran-alakazam r-cran-mutoss libosmo-sccp node-jsonld r-cran-ggm r-bioc-densvis pizzly grok llama.cpp rocm-llvm qtdeclarative-opensource-src python-dynasor onnxscript ectrans r-bioc-alabaster.base sccache janitor rust-nitrokey-sys eccodes-python imip-agent tensorflow reiser4progs vuls tinysvm

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.