Packages in experimental/armhf which failed to build from source

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

mesa pluto-find-orb pluto-sat-code git llvm-toolchain-snapshot boinc golang-google-grpc ruby-eventmachine# virtuoso-opensource kicad opencv geary heaptrack starpu exiv2 urjtag thunderbird daq nvidia-texture-tools critterding marble embree pocl gnokii xavs2 davs2 ruby-celluloid# vite# gstreamer-vaapi quassel-irssi xmbmon sump-logicanalyzer ssh-askpass-fullscreen socat pynn# dvidvi+ ruby-nmatrix php-sabre-event# phonetisaurus kcm-ufw gcc-cross-support arduino yamcha poti+ php-sabre-vobject# php-sabredav# blcr# python-django cups# gnome-todo libewf libvigraimpex# gnunet-gtk python-clamav havp cairosvg ruby-influxdb openhft-chronicle-core# openhft-chronicle-wire# openhft-affinity kopete openhft-chronicle-bytes# colmap software-properties golang-golang-x-debug golang-github-golang-geo

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.