Packages in stretch/amd64 which failed to build from source

117 (0.5%) 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.)

subversion rustc icu heimdal abinit llvm-toolchain-3.8 dico llvm-toolchain-3.9 gammu neovim sslsplit qbs soundscaperenderer user-mode-linux python-gammu yorick toxiproxy llvm-toolchain-4.0 strongswan xapian-core python-django openldap trove-dashboard libmediainfo ruby-http neon27 form golang-gopkg-alexcesaro-statsd.v1 strace ipywidgets translate-toolkit python-cotyledon shc ycmd golang-github-gogits-cron node-merge-stream botch libanyevent-perl vdirsyncer nbd restic custodia asyncpg 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-3 gnucash openbsc nodejs ruby2.3 armci-mpi gnote locket libio-socket-multicast6-perl libmessage-passing-perl libevent-rpc-perl gobgp golang-github-elithrar-simple-scrypt mariadb-10.1 node-marked-man ruby-neovim python-kdcproxy txfixtures watcher reel tendermint-go-flowrate debci ruby-prof sword golang-github-prometheus-client-golang golang-1.7 tap.py openhft-chronicle-bytes datalad ruby-certificate-authority validator.js git-build-recipe commons-pool2 ruby-sshkit golang-github-hashicorp-yamux cram golang-gopkg-eapache-go-resiliency.v1 cross-toolchain-base ruby-encryptor ri-li rsyslog ruby-httpclient ruby-eventmachine python-passlib ruby-connection-pool reptyr libpqtypes python-eventlet python-formencode glib2.0 python-argcomplete python-babel mitmproxy natbraille iodine diodon checkinstall autopkgtest golang-github-mxk-go-flowrate elixir-lang umockdev

2 (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 or ftbfs_build-indep_not_build_on_some_archs.

debian-installer-netboot-images 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.