Packages in stretch/amd64 which failed to build from source

100 (0.4%) packages which failed to build from source in stretch/amd64: (this list is filtered and only shows unexpected ftbfs issues - see the list below for expected failures.)

neovim qbs icu gammu botch dico sslsplit python-gammu yorick llvm-toolchain-3.9 heimdal llvm-toolchain-3.8 soundscaperenderer libanyevent-perl vdirsyncer nbd restic custodia asyncpg jruby## python-glanceclient# xpp haskell-parsers ola libanyevent-gearman-perl grub2# gnome-keyring# libbusiness-hours-perl libotr haskell-sendfile haskell-sha dumbster# ruby-influxdb php-sabre-vobject-3P gnucash## openbsc## nodejs ruby2.3# armci-mpi gnote locket strongswan libio-socket-multicast6-perl# libevent-rpc-perl libmessage-passing-perl# devscripts gobgp# ipywidgets xapian-core golang-github-elithrar-simple-scrypt mariadb-10.1 node-marked-man# ruby-neovim python-kdcproxy watcher# txfixtures# reel# tendermint-go-flowrate# debci# ruby-prof sword golang-github-prometheus-client-golang golang-1.7# tap.py openhft-chronicle-bytes# datalad validator.js# ruby-certificate-authority commons-pool2 git-build-recipe ruby-sshkit# golang-github-hashicorp-yamux# cram golang-gopkg-eapache-go-resiliency.v1 strace+ cross-toolchain-base ruby-encryptor# python-django# ri-li# rsyslog ruby-httpclient# ruby-eventmachineP python-passlib reptyr ruby-connection-pool python-eventlet libpqtypes python-formencode# python-argcomplete+ glib2.0 python-babel mitmproxy natbraille# iodine# checkinstall diodon autopkgtest golang-github-mxk-go-flowrate# umockdev# elixir-lang#

4 (0.0%) packages which failed to build from source in stretch/amd64 due to our changes in the toolchain or due to our setup. This list includes packages tagged ftbfs_in_jenkins_setup or ftbfs_build_depends_not_available_on_amd64 or ftbfs_build-indep_not_build_on_some_archs.

freedict debian-installer-netboot-images libreoffice debian-installer#

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.