Packages in unstable/amd64 where the build dependencies failed to be satisfied

68 (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.

lua-nginx-redis lintex loadwatch flightgear node-rollup-plugin-alias haskell-hmt ovito#+ urweb sambamba rust-gumdrop zorp+ boinc-app-eah-brp haskell-simple haskell-cabal-helper haskell-blogliterately ppx-sexp-conv shim-signed kubernetes# ppx-driver hdbc-odbc ppx-optcomp berkshelf# lambda-term dafny# ppx-type-conv boogie janest-core-kernel# utop containerd# janest-core-extended# ocaml-re2 pa-structural-sexp ocaml-textutils ruby-carrierwave golang-github-bradfitz-http2 xcffib# pluginhook typerep utopia-documents### rng-tools nanoc python-sponge# ploticus# pycaptcha python-googlecloudapis psychopyP polyorb monotone+ ocsigenserver libswe-doc# libgnome-keyring# ocaml-ipaddr nurpawiki netpipe mlton eliom tpm2-pk11 guacamole-server fceux# janest-core### libg15render ghc-mod doc-linux-fr+ aboot++# coinst clips bugs-everywhere+ uima-as

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.