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

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

heat reiser4progs rust-nitrokey golang-github-google-cel-spec esdm libapache2-mod-tile mediagoblin zeekctl node-solid-jose etesync-dav libosmo-sccp vault vuls code-saturne ovito# libewf symfony r-cran-mutoss osmo-hlr imip-agent networking-baremetal daq tensorflow neutron-tempest-plugin pizzly r-cran-alakazam eccodes-python opensnitch python-os-vif osmo-iuh r-bioc-densvis python-neutron-lib node-jsonld deal.ii grpc python-ovsdbapp python-os-ken android-cuttlefish rust-indieweb r-bioc-alabaster.base networking-bagpipe r-cran-ggm qtdeclarative-opensource-src r-bioc-alabaster.matrix llvmlite rocm-llvm xorgxrdp rust-nitrokey-sys freebayes node-trust-jwa groestlcoin go-cpe-dictionary inotifyrecursive critterding phonetisaurus php-sabre-vobject#

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.