Source: syslog-ng Version: 3.11.1-2 Severity: serious Tags: buster sid User: [email protected] Usertags: qa-ftbfs-20171030 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): > /bin/bash ./libtool --tag=CC --mode=link gcc -g -O2 > -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -pthread -avoid-version -module -no-undefined > -Wl,-z,relro -o modules/systemd-journal/libsdjournal.la -rpath > /usr/lib/syslog-ng/3.11 > modules/systemd-journal/modules_systemd_journal_libsdjournal_la-systemd-journal.lo > > modules/systemd-journal/modules_systemd_journal_libsdjournal_la-systemd-journal-grammar.lo > > modules/systemd-journal/modules_systemd_journal_libsdjournal_la-systemd-journal-parser.lo > > modules/systemd-journal/modules_systemd_journal_libsdjournal_la-systemd-journal-plugin.lo > > modules/systemd-journal/modules_systemd_journal_libsdjournal_la-journal-reader.lo > > modules/systemd-journal/modules_systemd_journal_libsdjournal_la-journald-subsystem.lo > > modules/systemd-journal/modules_systemd_journal_libsdjournal_la-journald-helper.lo > ./lib/libsyslog-ng.la -lsystemd > /usr/bin/ld: cannot find -lsnappy > collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/2017/10/30/syslog-ng_3.11.1-2_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.
