Source: rrdtool
Version: 1.4.7-1
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: [email protected]
Usertags: default19
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/bindings/ruby'
> compiling main.c
> main.c: In function 'string_arr_new':
> main.c:60:22: warning: format '%s' expects argument of type 'char *', but 
> argument 3 has type 'long int' [-Wformat]
> main.c:60:22: warning: format '%ld' expects argument of type 'long int', but 
> argument 4 has type 'int' [-Wformat]
> main.c: In function 'rrd_call':
> main.c:102:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_infocall':
> main.c:170:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_fetch':
> main.c:246:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_graph':
> main.c:291:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_last':
> main.c:319:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_xport':
> main.c:340:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> make[1]: *** [main.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/rrdtool_1.4.7-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.



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

Reply via email to