Packages in experimental/amd64 which failed to build from source

63 (15.4%) 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.)

exiv2 icu daq kmetronome openjdk-7 linbox deja-dup maliit-framework gnokii radicale# python-django# llvm-toolchain-5.0 gnucash## ssh-askpass-fullscreen ceph+# libnb-platform18-java# ants# libatteanx-store-memorytriplestore-perl# pynn# freedict-swa-eng# blcr# libtirpc banshee critterding gnutls28 json4s sbt-test-interface scopt openjdk-7-jre-dcevm insighttoolkit4 dbus yamcha sump-logicanalyzer socat lucene-net# ruby-nmatrix pybliographer# dvidvi+ mariadb-10.3 jawn sbt-template-resolver libcdio phonetisaurus tomboy# gcc-cross-support insserv arduino clipperP certmaster libkf5kface# forge# sbt-serialization sbt-launcher-interface scala-pickling kcm-ufw php-sabre-vobject# php-phpdocumentor-reflection## php-hamcrest# php-sabre-event# php-sabredav## ruby-influxdb netbeans pond

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.