Packages in experimental/amd64 which failed to build from source

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

octave-instrument-control gnunet-gtk gnunet-fuse freedroidrpg tuxpaint icu php-finder-facade sawfish wpa mediagoblin libaio-ocaml musescore-snapshot gnokii nvidia-texture-tools golang-github-xenolf-lego sunpy mini-buildd libreoffice zaqar-ui xmlelements fluxbox ssh-askpass-fullscreen ruby-nmatrix socat pyfeed gcc-cross-support vitrage-dashboard ants# pango1.0 simtools gromacs ruby-uglifier# node-liftoff ruby-jaeger-client etesync-dav diaspora ruby3.0 nodejs node-webpack openhft-chronicle-wire# kopete openhft-chronicle-bytes blt openhft-chronicle-threads openhft-chronicle-network pluto-sat-code php-sabre-event# dvdisaster meson nnpack gtk+4.0 vault golang-github-containers-common blcr# gtk4 tinc mmh libewf arriero rocr-runtime php-sabredav# yamcha phonetisaurus sump-logicanalyzer enhanceio glib2.0

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.