Source: gnats Version: 4.1.0-4 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170805 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): > gcc -c -I. -I. -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -W -Wall -ansi > -pedantic -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings > -Wno-format -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H > -DGNATSD_USER_ACCESS_FILE=\"/etc/gnats/gnatsd.user_access\" > -DGNATSD_HOST_ACCESS_FILE=\"/etc/gnats/gnatsd.host_access\" > -DDEFAULT_GNATS_SERVICE=\"gnats\" > -DGLOBAL_DB_LIST_FILE=\"/etc/gnats/databases\" -DGNATS_USER=\"gnats\" edit.c > cc1: error: -Wformat-security ignored without -Wformat > [-Werror=format-security] > edit.c: In function 'rewrite_pr': > edit.c:440:7: warning: ignoring return value of 'asprintf', declared with > attribute warn_unused_result [-Wunused-result] > asprintf (&dirPath, "%s/%s", databaseDir (database), > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > field_value (new_pr, CATEGORY (database))); > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > edit.c:473:3: warning: ignoring return value of 'asprintf', declared with > attribute warn_unused_result [-Wunused-result] > asprintf (&bkup_path, "%s.old", old_path); > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > edit.c: In function 'lock_pr': > edit.c:927:7: warning: ignoring return value of 'fgets', declared with > attribute warn_unused_result [-Wunused-result] > fgets (buf, sizeof (buf) - 1, fp); > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > cc1: some warnings being treated as errors > Makefile:174: recipe for target 'edit.o' failed > make[2]: *** [edit.o] Error 1 The full build log is available from: http://aws-logs.debian.net/2017/08/05/gnats_4.1.0-4_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.
