Your message dated Sat, 17 Dec 2011 00:23:21 +0100
with message-id <20111216232321.ga2...@glenfiddich.mraw.org>
and subject line Re: Bug#643414: jfsutils: FTBFS: fscklog.c:255:2: error:
format not a string literal and no format arguments [-Werror=format-security]
has caused the Debian Bug report #643414,
regarding jfsutils: FTBFS: fscklog.c:255:2: 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 ow...@bugs.debian.org
immediately.)
--
643414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jfsutils
Version: 1.1.15-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
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:
> gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../libfs -I../fsck -Wall
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security
> -Werror=format-security -Wall -c fscklog.c
> fscklog.c: In function 'v_send_msg':
> fscklog.c:255:2: error: format not a string literal and no format arguments
> [-Werror=format-security]
> fscklog.c:256:2: error: format not a string literal and no format arguments
> [-Werror=format-security]
> cc1: some warnings being treated as errors
>
> make[3]: *** [fscklog.o] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2011/09/23/jfsutils_1.1.15-1_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.
--- End Message ---
--- Begin Message ---
Version: 1.1.15-2
On Tue, Sep 27, 2011 at 02:31:40PM +0200, Didier Raboud wrote:
> Source: jfsutils
> Version: 1.1.15-1
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening
> Justification: FTBFS on amd64
[..]
> > fscklog.c: In function 'v_send_msg':
> > fscklog.c:255:2: error: format not a string literal and no format arguments
> > [-Werror=format-security]
> > fscklog.c:256:2: error: format not a string literal and no format arguments
> > [-Werror=format-security]
This has been fixed already, please don't forget to close bugs (with *version*
information).
http://www.debian.org/Bugs/Developer#closing
http://www.debian.org/Bugs/server-control#fixed
jfsutils (1.1.15-2) unstable; urgency=low
* Include patchsys-quilt.mk and add new patch format-security-errors to fix
FTBFS with -Werror=format-security (thanks to Loïc Minier
<loic.min...@ubuntu.com> for the patch)
-- Stefan Hornburg (Racke) <ra...@linuxia.de> Fri, 02 Dec 2011 11:03:10 +0100
--
Simon Paillard
--- End Message ---
