Packages in experimental/arm64 which failed to build from source
71 (10.8%) 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.)
openhft-chronicle-network
openhft-chronicle-threads
octave-instrument-control
gnunet-fuse
gnunet-gtk
php-finder-facade
sawfish
libaio-ocaml
nvidia-texture-tools
gnokii
musescore-snapshot
enhanceio
php-sabredav#
pyfeed
mmh
spamassassin
golang-github-xenolf-lego
mediagoblin
gromacs
lensfun
wpa
icu
freedroidrpg
tuxpaint
sunpy
qpdf
ruby-uglifier#
node-liftoff
node-webpack
golang-github-containers-common
openhft-chronicle-bytes
openhft-chronicle-wire#
rocr-runtime
pluto-sat-code
vault
nodejs
simtools
vkd3d
vitrage-dashboard
xmlelements
golang-golang-x-debug
python-django
ssh-askpass-fullscreen
gcc-cross-support
golang-github-golang-geo
arriero
davs2+
gtk+4.0
matrix-construct
ruby-jaeger-client
ruby3.0
glew
diaspora
libewf
xavs2+
zaqar-ui
fluxbox
yamcha
socat
php-sabre-event#
xmbmon
ruby-nmatrix
sump-logicanalyzer
tinc
glib2.0
openhft-affinity
kopete
blt
dvdisaster
git+
phonetisaurus
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.