Packages in experimental/i386 which failed to build from source

56 (14.0%) 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.)

insighttoolkit4 kicad boinc mesa marble thunderbird exiv2 daq heaptrack nvidia-texture-tools critterding gnokii gcc-9-cross llvm-toolchain-snapshot webkit2gtk virtuoso-opensource xavs2 davs2 golang-github-golang-geo gcc-cross-support arduino pocl python-django libreoffice gnome-todo cairosvg cups# quassel-irssi gnome-desktop3 libvigraimpex# libewf ants# yamcha ssh-askpass-fullscreen php-sabre-vobject# php-sabre-event# kopete gstreamer-vaapi gnunet-gtk php-sabredav# openhft-chronicle-bytes# openhft-chronicle-wire# openhft-chronicle-core# phonetisaurus ruby-nmatrix socat sump-logicanalyzer kcm-ufw dvidvi+ ruby-influxdb golang-golang-x-debug pynn# blcr# pluto-sat-code pluto-find-orb ruby-eventmachine#

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.