Packages in experimental/i386 which failed to build from source

113 (17.7%) 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.)

python-django php-lcobucci-clock golang-github-protonmail-go-crypto symfony php-codecoverage hdf5 python-mrcfile qemu openmpi openstructure go-gir-generator libsdl3 iem-plugin-suite rapmap libcgns nvidia-texture-tools puppet musescore-snapshot python-urllib3 appstream astc-encoder tracker kopete node-corepack darkice polyml sawfish lensfun mediagoblin daq xfce4-panel icinga2 clamav dcmtk sasview scap-workbench node-jupyterlab g2clib puma autogen yosys highway node-yarnpkg golang-github-urfave-cli-v2 php-zend-code chatty ruby3.2 linphone-desktop libvigraimpex# phpunit-complexity php-doctrine-dbal php-league-uri-src lib2geom phpunit-lines-of-code php-text-template php-file-iterator phpunit-comparator hiredis scheme-bytestructures vimix liblsl webrtc-audio-processing mu-editor phpunit-global-state phpunit-type php-timer phpunit-code-unit-reverse-lookup phpunit-object-enumerator kworkflow ruby-uglifier# vdr-plugin-markad golang-github-golang-geo monkeysphere golang-golang-x-debug mediasoup ruby-nmatrix simtools node-readable-stream openhft-chronicle-network rust-nitrokey-sys golang-opentelemetry-proto wmbusmeters jbig2-imageio diaspora ants# groestlcoin php-sabre-event# openhft-chronicle-bytes golang-github-ostreedev-ostree-go tools-deps-alpha-clojure ruby-omniauth-salesforce yamcha livi janitor node-d3-hierarchy openhft-chronicle-threads golang-opentelemetry-contrib ruby-google-apis-androidpublisher-v3 glew heudiconv php-http-psr7-integration-tests android-platform-external-doclava blt node-d3-time breezy reprepro php-codesniffer dtc sump-logicanalyzer openhft-chronicle-wire pluto-sat-code qwt bpfcc

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.