[Syslog-ng-maintainers] Bug#848786: syslog-ng: FTBFS: build-dependency not installable: libmongoc-dev

[Lucas Nussbaum]

Source: syslog-ng
Version: 3.8.1-8
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +------------------------------------------------------------------------------+
> | Install package build dependencies                                           |
> +------------------------------------------------------------------------------+
> 
> 
> Setup apt archive
> -----------------
> 
> Merged Build-Depends: debhelper (>= 9~), dh-autoreconf, automake (>= 1:1.11.1), tzdata, pkg-config, flex, bison, xsltproc, docbook-xsl, libevtlog-dev (>= 0.2.12-5~), libesmtp-dev, libivykis-dev (>= 0.36.1~), libnet1-dev, libglib2.0-dev, libdbi-dev | libdbi0-dev, libssl1.0-dev, libmongoc-dev, libbson-dev, libjson-c-dev | libjson0-dev, libwrap0-dev, libpcre3-dev, libcap-dev, dh-systemd (>= 1.3), libsystemd-dev (>= 209), libgeoip-dev, libhiredis-dev, libriemann-client-dev (>= 1.6.0~), librabbitmq-dev, python, python-dev, pep8, pylint, dh-python, dh-exec (>= 0.13~), python-nose, python-ply, libxml2-utils, geoip-database
> Merged Build-Conflicts: autoconf2.13
> Filtered Build-Depends: debhelper (>= 9~), dh-autoreconf, automake (>= 1:1.11.1), tzdata, pkg-config, flex, bison, xsltproc, docbook-xsl, libevtlog-dev (>= 0.2.12-5~), libesmtp-dev, libivykis-dev (>= 0.36.1~), libnet1-dev, libglib2.0-dev, libdbi-dev, libssl1.0-dev, libmongoc-dev, libbson-dev, libjson-c-dev, libwrap0-dev, libpcre3-dev, libcap-dev, dh-systemd (>= 1.3), libsystemd-dev (>= 209), libgeoip-dev, libhiredis-dev, libriemann-client-dev (>= 1.6.0~), librabbitmq-dev, python, python-dev, pep8, pylint, dh-python, dh-exec (>= 0.13~), python-nose, python-ply, libxml2-utils, geoip-database
> Filtered Build-Conflicts: autoconf2.13
> dpkg-deb: building package 'sbuild-build-depends-syslog-ng-dummy' in '/<<BUILDDIR>>/resolver-GggcSn/apt_archive/sbuild-build-depends-syslog-ng-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy sbuild-build-depends-syslog-ng-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<<BUILDDIR>>/resolver-GggcSn/apt_archive ./ InRelease
> Get:2 copy:/<<BUILDDIR>>/resolver-GggcSn/apt_archive ./ Release [963 B]
> Ign:3 copy:/<<BUILDDIR>>/resolver-GggcSn/apt_archive ./ Release.gpg
> Get:4 copy:/<<BUILDDIR>>/resolver-GggcSn/apt_archive ./ Sources [798 B]
> Get:5 copy:/<<BUILDDIR>>/resolver-GggcSn/apt_archive ./ Packages [844 B]
> Fetched 2605 B in 0s (251 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install syslog-ng build dependencies (apt-based resolver)
> ---------------------------------------------------------
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-syslog-ng-dummy : Depends: libmongoc-dev but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/12/19/syslog-ng_3.8.1-8_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.