Source: mailutils
Version: 1:2.2+dfsg1-3
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../.. -I../.. -I../../include  -I../../include -I../../mailbox 
> -I../../libproto/include -I../../libproto/include   -DSYSCONFDIR=\"/etc\"  -g 
> -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat 
> -Wformat-security -Werror=format-security -Wall -c -o pop3_sendline.lo 
> pop3_sendline.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include 
> -I../../include -I../../mailbox -I../../libproto/include 
> -I../../libproto/include -DSYSCONFDIR=\"/etc\" -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security 
> -Werror=format-security -Wall -c pop3_sendline.c  -fPIC -DPIC -o 
> .libs/pop3_sendline.o
> pop3_sendline.c: In function 'mu_pop3_sendline':
> pop3_sendline.c:115:7: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> cc1: some warnings being treated as errors
> 
> make[4]: *** [pop3_sendline.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/mailutils_1:2.2+dfsg1-3_lsid64.buildlog

This happened because since dpkg 1.16.0 [0], hardening flags are enabled 
under various conditions.

[0] http://lists.debian.org/debian-devel-announce/2011/09/msg00001.html

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to