Packages in unstable/amd64 where the build dependencies failed to be satisfied
67 (0.2%) packages where the build dependencies failed to be satisfied. Note that temporary failures (eg. due to network problems) are automatically rescheduled every 4 hours.
cambalache
perlnavigator
gcc-11-cross-mipsen
ypy
python-cryptography
rust-sequoia-octopus-librnp
rust-cargo-test-support
haskell-misfortune
python-ocp
pygccjit
rust-czkawka-gui
debian-installer###
vuls
wasix-libc
python-opencascade-pywrap
ecere-sdk
rust-rav1e
python-es-client
kraft
rust-ouroboros
python-pysnmp-lextudio
python-fastparquet
unicrypto
python-aioraven
libt3window
python-certbot-dns-gandi
libpsml
python-adb-shell
breezy
prads
php-fxsl
scrcpy
ruby-arbre
python-feather-format
rust-sequoia-chameleon-gnupg
gensim
rust-debian-repro-status
pyemd
rust-sequoia-sq
fretboard
ghc
cross-toolchain-base
tree-style-tab
unburden-home-dir
php-fdomdocument
trafficserver
libt3widget
watchman
syrthes
sagetex
sagemath
hyperspy
user-mode-linux
cross-toolchain-base-mipsen
tilde
rust-utmp-classic
synfigstudio
python-oauth2client
phpdox
pymia
gimp-plugin-registry
node-y-protocols
prelude-correlator
grok
setools
shc
cross-toolchain-base-ports
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.