Source: munin-c
Version: 0.0.9-1
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 -DPACKAGE_NAME=\"munin-c\" -DPACKAGE_TARNAME=\"munin-c\"
> -DPACKAGE_VERSION=\"0.0.9\" -DPACKAGE_STRING=\"munin-c\ 0.0.9\"
> -DPACKAGE_BUGREPORT=\"https://github.com/munin-monitoring/munin-c/issues\";
> -DPACKAGE_URL=\"https://github.com/munin-monitoring/munin-c\";
> -DPACKAGE=\"munin-c\" -DVERSION=\"0.0.9\" -DSTDC_HEADERS=1
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
> -DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1
> -DHAVE_WORKING_FORK=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wall -Wextra -Werror -pedantic -c -o threads.o
> threads.c
> threads.c: In function 'threads':
> threads.c:62:30: error: '%s' directive output may be truncated writing up to
> 255 bytes into a region of size 250 [-Werror=format-truncation=]
>snprintf(buff, 256, "/proc/%s/status", e->d_name);
> ^~
> In file included from /usr/include/stdio.h:938:0,
> from threads.c:13:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note:
> '__builtin___snprintf_chk' output between 14 and 269 bytes into a destination
> of size 256
>return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
> ^~~~
> __bos (__s), __fmt, __va_arg_pack ());
> ~
> cc1: all warnings being treated as errors
> Makefile:432: recipe for target 'threads.o' failed
> make[2]: *** [threads.o] Error 1
The full build log is available from:
http://aws-logs.debian.net/2017/08/05/munin-c_0.0.9-1_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.