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

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

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

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.