Packages in experimental/amd64 which failed to build from source
130 (13.0%) 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.)
gst-plugins-base1.0
falkon
pcl
rust-gobject-sys
rust-glib-sys
rust-pango-sys
rust-atk-sys
rust-pangocairo-sys
vowpal-wabbit##
rust-graphene-sys
ros-ros-comm
stdgpu
ncl
safeclib
sssd
silo-llnl
ntirpc
polymake
ros-image-common
notmuch
snacc
wpewebkit
wxwidgets3.2
osmo-iuh
s6
singular
st
ros-bond-core
stellarsolver
gcc-14-cross-ports
qbs
hdf-eos5
qgis
consolekit2
ovito#
t4kcommon
thrift
mrtdreader
m4api
libvformat
librnd
libspf2
qtcharts-opensource-src
qtwayland-opensource-src
budgie-desktop
qtquickcontrols-opensource-src
qtlocation-opensource-src
php-codecoverage
qtdeclarative-opensource-src
php-monolog
golang-github-protonmail-go-crypto
mutter
tracker-miners
reprepro
qt6-base
sleef
phpunit-code-unit
clamav
nvidia-texture-tools
libkqueue
h2o
fuse
broker
highway
fmtlib
sqlalchemy
mediagoblin
autogen
polyml
daq
musescore-snapshot
darkice
kopete
poco
golang-github-spiffe-go-spiffe
python-kubernetes
sawfish
scap-workbench
puppet
openimageio
gnome-shell
git
python-urllib3
ruby-omniauth-salesforce
wmbusmeters
webrtc-audio-processing
ruby-uglifier#
diaspora
sasview
iem-plugin-suite
lcms2
glyphslib
gnome-shell-pomodoro
ruby-serverengine
abseil
qtdeclarative-opensource-src-gles
openhft-chronicle-wire
node-d3-time
sump-logicanalyzer
rg-el
bali-phy
libstreamvbyte
vimix
node-d3-hierarchy
qwt
tools-deps-alpha-clojure
kpatch
liblsl
kworkflow
mu-editor
android-platform-external-doclava
monkeysphere
mediasoup
openhft-chronicle-threads
openhft-chronicle-network
openhft-chronicle-bytes
php-sabre-event#
pluto-sat-code
ruby-nmatrix
janitor
gnome-photos
yamcha
dtc
node-readable-stream
cmark
kata-containers
pg-cron
simtools
jbig2-imageio
vorta
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.