Your message dated Sun, 4 Dec 2011 00:31:45 +0100
with message-id <[email protected]>
and subject line Re: Bug#646449: libosip2: FTBFS: osip_message_parse.c:850:5:
error: format not a string literal and no format arguments
[-Werror=format-security]
has caused the Debian Bug report #646449,
regarding libosip2: FTBFS: osip_message_parse.c:850:5: error: format not a
string literal and no format arguments [-Werror=format-security]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
646449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646449
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libosip2
Version: 3.3.0-1
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20111022 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -Wall -Wcast-align
> -Wchar-subscripts -Wformat -Winline -Wmissing-declarations
> -Wmissing-prototypes -Wnested-externs -Wpointer-arith -g -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security
> -Wall -DUSE_GPERF -pedantic -g -DENABLE_TRACE -g -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security
> -Wall -c osip_message_parse.c -fPIC -DPIC -o .libs/osip_message_parse.o
> osip_message_parse.c: In function 'msg_osip_body_parse':
> osip_message_parse.c:800:15: warning: format '%i' expects argument of type
> 'int', but argument 3 has type 'size_t' [-Wformat]
> osip_message_parse.c:850:5: error: format not a string literal and no format
> arguments [-Werror=format-security]
> cc1: some warnings being treated as errors
>
> make[4]: *** [osip_message_parse.lo] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2011/10/22/libosip2_3.3.0-1_lsid64.buildlog
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.
--- End Message ---
--- Begin Message ---
Version: 3.6.0-1
On Mon, Oct 24, 2011 at 01:08:24PM +0200, Mònica Ramírez Arceda wrote:
> Source: libosip2
> Version: 3.3.0-1
> Severity: serious
> Tags: wheezy sid
> User: [email protected]
> Usertags: qa-ftbfs-20111022 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part:
> > gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -Wall -Wcast-align
> > -Wchar-subscripts -Wformat -Winline -Wmissing-declarations
> > -Wmissing-prototypes -Wnested-externs -Wpointer-arith -g -fstack-protector
> > --param=ssp-buffer-size=4 -Wformat -Wformat-security
> > -Werror=format-security -Wall -DUSE_GPERF -pedantic -g -DENABLE_TRACE -g
> > -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security
> > -Werror=format-security -Wall -c osip_message_parse.c -fPIC -DPIC -o
> > .libs/osip_message_parse.o
> > osip_message_parse.c: In function 'msg_osip_body_parse':
> > osip_message_parse.c:800:15: warning: format '%i' expects argument of type
> > 'int', but argument 3 has type 'size_t' [-Wformat]
> > osip_message_parse.c:850:5: error: format not a string literal and no
> > format arguments [-Werror=format-security]
> > cc1: some warnings being treated as errors
> >
> > make[4]: *** [osip_message_parse.lo] Error 1
>
This was fixed already in version 3.6.0-1 uploaded to unstable
about the same time the archive rebuild was done.
--- End Message ---
