Packages in experimental/arm64 where the build dependencies failed to be satisfied

62 (6.5%) packages where the build dependencies failed to be satisfied. Note that temporary failures (eg. due to network problems) are automatically rescheduled every 4 hours.

urjtag critterding inotifyrecursive libewf enhanceio tensorflow reiser4progs ruby-nmatrix calendarsupport incidenceeditor merkuro akonadi-calendar-tools messagelib kdepim-addons kmail zanshin akonadiconsole kaddressbook libksieve libgravatar mailcommon etesync-dav node-solid-jose pim-sieve-editor groestlcoin akregator eventviews mbox-importer daq r-bioc-beachmat r-bioc-bluster r-bioc-glmgampoi r-bioc-dropletutils r-bioc-singler node-jsonld r-bioc-biocsingular imip-agent zeekctl php-sabre-vobject# linphone-desktop go-cpe-dictionary belcard golang-github-google-cel-spec rust-nitrokey phonetisaurus gcc-mingw-w64 q2-phylogeny vuls r-bioc-biocneighbors vault bcachefs-tools opensnitch rust-futures-rustls llvmlite rust-indieweb rocthrust ovito# unicycler janitor node-trust-jwa rust-nitrokey-sys linphone

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.