Packages in experimental/i386 which failed to build from source

122 (20.3%) packages which failed to build from source in experimental/i386: (this list is filtered and only shows unexpected ftbfs issues - see the list below for expected failures.)

virtuoso-opensource libaio-ocaml emacs+ botan socklog tuxpaint plasma-workspace node-autoprefixer cyrus-imapd polkit-kde-agent-1 boinc libreoffice cups# etesync-dav qtdeclarative-opensource-src-gles blcr# fluxbox xfce4-sensors-plugin runit php-timer meson osmo-bts osmo-bsc node-diff brian# vitrage-dashboard libgnatcoll-db zaqar-ui libgmpada arriero groestlcoin pluto-sat-code pluto-find-orb sundials qtlocation-opensource-src symfony wpa freedroidrpg mini-buildd llvm-toolchain-snapshot xen mediagoblin cargo librandomx gnutls28 gnokii nvidia-texture-tools musescore-snapshot qtquickcontrols-opensource-src sawfish qtdeclarative-opensource-src spamassassin ssh-askpass-fullscreen libewf php-sabredav# enhanceio phonetisaurus ruby3.0 osmo-msc osmo-sgsn mariadb-10.4 xalan garcon# ants# pyfeed simtools sump-logicanalyzer python-firehose gcc-cross-support openhft-chronicle-wire# e2fsprogs node-rollup-plugin-node-resolve ruby-faraday vault fprintd xmlelements yamcha php-sabre-event# openhft-chronicle-network blt rocr-runtime nodejs qtwebkit-opensource-src libxfce4ui plexus-archiver rust-cfg-if audit jbig2-imageio spyder-kernels ruby-faraday-middleware vdr-plugin-markad ruby-sentry-raven ruby-elasticsearch hiredis fcl android-platform-external-doclava libsass node-trust-jwa xavs2+ bcachefs-tools ldh-client davs2 python-gphoto2 mupen64plus-video-z64 debrequest colord-kde ruby-nmatrix socat openhft-chronicle-threads openhft-chronicle-bytes mmh golang-golang-x-debug dvdisaster glew diaspora xpdf arduino golang-github-golang-geo python-django node-solid-jose zeek netsniff-ng

1 (0.2%) packages which failed to build from source in experimental/i386 due to our changes in the toolchain or due to our setup. This list includes packages tagged or ffile_prefix_map_passed_to_clang.

chromium

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.