Packages in stretch/i386 which failed to build from source

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

ruby2.3 c-icap-modules xapian-core sagemath# txfixtures python-apt cups# node-grunt-contrib-copy python-django strace+ scilab botch icu tap.py watcher subversion# cadabra libtemplate-plugin-calendar-simple-perl zookeeper llvm-toolchain-3.9 x264 libbusiness-hours-perl kmer ipywidgets libio-socket-ssl-perl node-yargs dnssecjava translate-toolkit yadifa libio-socket-multicast6-perl node-marked-man gridengine# debci python-kdcproxy elixir-lang refind# prometheus mpqc3 custodia dico crash quantlib-swig zeroc-ice 0ad neovim sra-sdk traverso galera-3 android-platform-external-doclava ecere-sdk ncbi-vdb ruby-eventmachine## ants# the+ sword mkosi python-arrayfire okio user-mode-linux openmsx wiredtiger tcc yade python-biplist xpp python-babel openbsc urwid soundscaperenderer validator.js regina-rexx+ sbcl nuitka saga sketch ri-li# python-gammu python-argcomplete+ jetty9 ryu sslsplit qbs php-sabre-vobject-3 zfs-fuse openbios pbbam# python-formencode polygen nodejs argyll libffado nbd handbrake meson latrace# libpqtypes golang-github-boltdb-bolt natbraille kvmtool htsjdk scilab-ann kbuild ruby-diaspora-vines mlton pyliblo ocrmypdf llvm-toolchain-3.8 gammu llvm-toolchain-4.0 cross-toolchain-base-ports bcftools### jnr-posix# dc-qt git-build-recipe bagelP blockdiag checkinstall neon27 gatos gnucash# scilab-plotlib exec-maven-plugin cinder scilab-celestlab 3270font snap-aligner cvc3 trilinos iodine# tiptop jruby#

2 (0.0%) packages which failed to build from source in stretch/i386 due to our changes in the toolchain or due to our setup. This list includes packages tagged or ffile_prefix_map_passed_to_clang.

llvm-toolchain-7 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.