Your message dated Tue, 25 Oct 2011 18:02:18 +0000
with message-id <e1rilkm-0001zs...@franck.debian.org>
and subject line Bug#643430: fixed in libmimedir-gnome 0.4.2-3
has caused the Debian Bug report #643430,
regarding libmimedir-gnome: FTBFS: mimedir-profile.c:583:3: 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.)


-- 
643430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmimedir-gnome
Version: 0.4.2-2
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.. -I.. -DG_DISABLE_DEPRECATED -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
> -DLOCALEDIR=\"/usr/share/locale\" -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security 
> -Werror=format-security -Wall -c mimedir-profile.c  -fPIC -DPIC -o 
> .libs/mimedir-profile.o
> mimedir-profile.c: In function 'mimedir_profile_write_to_string':
> mimedir-profile.c:583:3: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> mimedir-profile.c:593:3: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> mimedir-profile.c:602:3: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> mimedir-profile.c:607:2: warning: implicit declaration of function 'g_unlink' 
> [-Wimplicit-function-declaration]
> cc1: some warnings being treated as errors
> 
> make[3]: *** [mimedir-profile.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/libmimedir-gnome_0.4.2-2_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 ---
Source: libmimedir-gnome
Source-Version: 0.4.2-3

We believe that the bug you reported is fixed in the latest version of
libmimedir-gnome, which is due to be installed in the Debian FTP archive:

libmimedir-gnome-dev_0.4.2-3_amd64.deb
  to main/libm/libmimedir-gnome/libmimedir-gnome-dev_0.4.2-3_amd64.deb
libmimedir-gnome0.4_0.4.2-3_amd64.deb
  to main/libm/libmimedir-gnome/libmimedir-gnome0.4_0.4.2-3_amd64.deb
libmimedir-gnome_0.4.2-3.diff.gz
  to main/libm/libmimedir-gnome/libmimedir-gnome_0.4.2-3.diff.gz
libmimedir-gnome_0.4.2-3.dsc
  to main/libm/libmimedir-gnome/libmimedir-gnome_0.4.2-3.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 643...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Moray Allan <mo...@debian.org> (supplier of updated libmimedir-gnome package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Tue, 25 Oct 2011 18:28:08 +0100
Source: libmimedir-gnome
Binary: libmimedir-gnome-dev libmimedir-gnome0.4
Architecture: source amd64
Version: 0.4.2-3
Distribution: unstable
Urgency: low
Maintainer: Moray Allan <mo...@debian.org>
Changed-By: Moray Allan <mo...@debian.org>
Description: 
 libmimedir-gnome-dev - MIME Directory Profile implementation [development]
 libmimedir-gnome0.4 - MIME Directory Profile implementation [runtime]
Closes: 643430
Changes: 
 libmimedir-gnome (0.4.2-3) unstable; urgency=low
 .
   * Add explicit string format specifiers to calls to g_warning in
     mimedir-profile.c.  Closes: #643430.
Checksums-Sha1: 
 a5ab23acfaa109d71c52998bf26800cf07c37468 1126 libmimedir-gnome_0.4.2-3.dsc
 fc0c0404a24472eca4843a3ba19012bb6c4216cd 72220 libmimedir-gnome_0.4.2-3.diff.gz
 b1310819fc81aab7c5820c3b7e058430a109e5cb 146532 
libmimedir-gnome-dev_0.4.2-3_amd64.deb
 26450caf1e5b8650696d02ece03ba1d8c433e493 111080 
libmimedir-gnome0.4_0.4.2-3_amd64.deb
Checksums-Sha256: 
 a86b1d9397d05236ea446971e1a6baa92966f189b8fcb37a59614c4e24da037d 1126 
libmimedir-gnome_0.4.2-3.dsc
 2edb41463d67e6677495f5d68142f8e1d55f12f8d32b1cb9214669716150f0ce 72220 
libmimedir-gnome_0.4.2-3.diff.gz
 65d527e01e2c1a03a9889ba6294b2831bab2ec22668063b11a394e247d498f6e 146532 
libmimedir-gnome-dev_0.4.2-3_amd64.deb
 48575b35ced7cbfb92676a6177efb91bf8db375a44611231a2bacfa80ca63205 111080 
libmimedir-gnome0.4_0.4.2-3_amd64.deb
Files: 
 a53c1b8af5d760e7301a10a83f33b08c 1126 libs optional 
libmimedir-gnome_0.4.2-3.dsc
 2bc9965d3a71110bbc5a0de29d000938 72220 libs optional 
libmimedir-gnome_0.4.2-3.diff.gz
 ee532672ba53daa92712a3e6a1441fb8 146532 libdevel optional 
libmimedir-gnome-dev_0.4.2-3_amd64.deb
 fbad00fa8bf9b3984feb563bdcea0623 111080 libs optional 
libmimedir-gnome0.4_0.4.2-3_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk6m90UACgkQ500puCvhbQHmbACeIeZ5h5an8w4ieNy3f0bP1r6v
7TkAn1IHQ5MhvP69tfjRpZ4rIie+UR8d
=mJo8
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to