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

65 (10.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.

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

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.