Packages in experimental/arm64 which failed to build from source

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

golang-github-golang-geo openstructure gcc-15 phpcpd hipcub clojure-cli markdown tinc mediasoup node-d3-time featherpad mruby linux musescore-snapshot nvidia-texture-tools metview qtwebengine-opensource-src scap-workbench gnutls28 rocprim rustc gmerlin-avdecoder macromoleculebuilder highway llvm-toolchain-snapshot symfony libqtxdg qgis qt6-languageserver icinga2 php-parser gcc-15-cross nodejs khmer libkryo-java cmor sphinxsearch graph-tool sfcgal seqan2 libgpiv vim ecflow esdm scipy opm-simulators polyml libcgns sawfish qtquickcontrols-opensource-src freebayes stopt iem-plugin-suite qtlocation-opensource-src curl harp code-saturne sdl2-compat php-sabre-event# persalys libreoffice# qtdeclarative-opensource-src-gles gst-python1.0 gst-plugins-base1.0 open-infrastructure-service-tools llvm-toolchain-20 rocblas python3.14 strawberry slcfitsio neochat gmerlin rocsparse golang-golang-x-debug sump-logicanalyzer dtc thrift golang-github-protonmail-gopenpgp php-twig pkg-rocm-tools sphinx hipsparse meson golang-github-kurin-blazer openhft-chronicle-bytes php-getid3 node-d3-hierarchy tools-deps-alpha-clojure node-readable-stream ruby-omniauth-salesforce lios wmbusmeters kworkflow ruby-gitlab-pg-query pluto-sat-code openhft-chronicle-network openhft-chronicle-threads mypy kata-containers grads roman-numerals hasl reprepro gcc-14 ruby-rack-livereload jami php-pcov openhft-chronicle-wire ucx icu-ext syncthingtray gmerlin-encoders miopen android-platform-external-doclava yamcha monkeysphere gcc-15-cross-ports rocm-llvm opensnitch khal ford

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.