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

59 (8.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.

groestlcoin enhanceio php-sabre-vobject# reiser4progs rust-indieweb osmo-iuh linphone grpc r-bioc-alabaster.base r-bioc-alabaster.matrix llvmlite r-cran-ggm osmo-hlr cnvkit deal.ii node-jsonld insighttoolkit5 xorgxrdp rust-glycin rust-nitrokey esdm golang-github-google-cel-spec node-solid-jose vault zeekctl etesync-dav code-saturne libewf eccodes-python vuls imip-agent tensorflow daq dart opensnitch libosmo-sccp gromacs tepl unicycler rust-futures-rustls symfony r-cran-mutoss r-cran-alakazam ovito# pizzly r-bioc-densvis rocm-llvm macromoleculebuilder node-trust-jwa rust-nitrokey-sys go-cpe-dictionary freebayes critterding urjtag mpich libapache2-mod-tile phonetisaurus inotifyrecursive ruby-nmatrix

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.