Bug#643304: python-awn-extras: can't install: unable to open '/usr/share/pyshared/awn/extras/__init__.py.dpkg-new'
Package: python-awn-extras
Version: 0.4.0-3.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I attempted to upgrade to AWN 4.0.4 in sid. All my other packages are
up to date. python-awn-extras fails to install with the following
message:
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
(Reading database ... 336028 files and directories currently installed.)
Unpacking python-awn-extras (from .../python-awn-extras_0.4.0-4_amd64.deb) ...
dpkg: error processing
/var/cache/apt/archives/python-awn-extras_0.4.0-4_amd64.deb (--unpack):
unable to open '/usr/share/pyshared/awn/extras/__init__.py.dpkg-new': No such
file or directory
configured to not write apport reports
The package, and thus awn-python-applets-{core, extras}, cannot be installed.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.4 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-awn-extras depends on:
ii python 2.6.7-3
ii python-support 1.0.14
python-awn-extras recommends no packages.
python-awn-extras suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632494: Different error...
Le 26/09/2011 23:46, Iain Lane a écrit : That's fixed in darcs (darcs' darcs repo? hah) and is #642710. You can just hack the .cabal file to accept 0.95.1 which is in sid and it should work for you. I tried after applying patch: http://anonscm.debian.org/cgi-bin/darcsweb.cgi?r=pkg-haskell/darcs;a=commitdiff;h=20110924200400-ce43c-85b0eece832349b09f3852a1c2a7109cc7e5dfcb.gz and it fails with the error: Running unrevert-replace-moved.sh ...passed. Running unrevert.sh ... passed. Running unrevert_cancel.sh ... passed. Running utf8.sh ... skipped. Running what_sl.sh ... passed. Running whatsnew-file.sh ... passed. Running whatsnew-pending.sh ... passed. Running whatsnew.sh ... passed. Running workingdir.sh ...passed. Some tests failed: printer.sh Setup: Tests failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory `/tmp/darcs-2.5.2' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 debuild: fatal error at line 1348: dpkg-buildpackage -rfakeroot -D -us -uc failed before and after applying the patch from #642922 to dash. Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642162: problem with closures on kfreebsd-amd64
On Mon, Sep 26, 2011 at 10:33:19PM +0200, Petr Salinger wrote: user debian-...@lists.debian.org usertag 642928 + kfreebsd usertag 642162 + kfreebsd -- Could be this related to CPU ? My is Intel(R) Core(TM)2 Duo CPU E6750 asdfasdf's AMD Sempron(tm) Processor 3000+ After changing configure.ac and propagating it into configure, the testsuite of 3.0.11~rc1-2 succeeds also on asdfasdf.d.n === libffi Summary === # of expected passes1649 # of unsupported tests 15 --- configure.ac +++ configure.ac @@ -345,7 +345,7 @@ [Cannot use PROT_EXEC on this target, so, we revert to alternative means]) ;; - *-apple-darwin10* | *-*-freebsd* | *-*-openbsd* | *-pc-solaris*) + *-apple-darwin10* | *-*-freebsd* | *-*-kfreebsd* | *-*-openbsd* | *-pc-solaris*) AC_DEFINE(FFI_MMAP_EXEC_WRIT, 1, [Cannot use malloc on this target, so, we revert to alternative means]) IMHO, similar change might help to solve gcj fails under fash.d.o, but not fano.d.o. I confirm it also fixes gcj. Yay \o/ -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643310: mpqc cannot be started
Package: mpqc Version: 2.3.1-7 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Whenever I try to start mpqc, whatever parameters I submit, mpqc 2.3.1-7 crashes with the same output to std.err: [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 357 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 230 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../orte/runtime/orte_init.c at line 132 -- Sorry! You were supposed to get help about: orte_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-orte-runtime: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: mpi_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime: No such file or directory. Sorry! -- *** The MPI_Init_thread() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [cohg:3330] Abort before MPI_INIT completed successfully; not able to guarantee that all other processes were killed! I tried it on this amd64/testing-system, on an amd64/sid-system, and on an i386 /testing-system. Greetings, Georg -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpqc depends on: ii libblas3gf [libblas.so.3gf] 1.2.20110419-2 ii libc62.13-21 ii libgcc1 1:4.6.1-4 ii libgfortran3 4.6.1-4 ii liblapack3gf [liblapack.so.3gf] 3.3.1-1 ii libopenmpi1.31.4.3-2.1 ii libquadmath0 4.6.1-4 ii libsc-data 2.3.1-7 ii libsc7 2.3.1-7 ii libstdc++6 4.6.1-4 mpqc recommends no packages. Versions of packages mpqc suggests: ii mpqc-support 2.3.1-7 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557103: uw-imapd occasionally corrupts /var/spool/mail/[user] and ~/mbox
Same problem here, and since more than a year now. I wasn't aware eiither that UW-Imapd was deprecated, so removing the daemons might help others not fall in the same trap. The problem (first couple lines of the mbox file corrupted) happened with several email clients I tried : - roundcube - thunderbird (several versions) - android mail - android K9-mail from what I read I deduct that at some point these clients either accessed the file while new email was being written to it, and that maybe some of these clients attempted to 'multithread' and accessed the file concurrently during the same session (Only one client connected, several concurrent accesses). I'll give Dovecott a try, thanks for the tip. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643310: [Debichem-devel] Bug#643310: mpqc cannot be started
Hi, On Tue, Sep 27, 2011 at 09:02:50AM +0200, Georg wrote: Package: mpqc Version: 2.3.1-7 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Whenever I try to start mpqc, whatever parameters I submit, mpqc 2.3.1-7 crashes with the same output to std.err: [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 357 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 230 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../orte/runtime/orte_init.c at line 132 -- Sorry! You were supposed to get help about: orte_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-orte-runtime: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: mpi_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime: No such file or directory. Sorry! -- *** The MPI_Init_thread() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [cohg:3330] Abort before MPI_INIT completed successfully; not able to guarantee that all other processes were killed! I tried it on this amd64/testing-system, on an amd64/sid-system, and on an i386 /testing-system. Is that in a chroot? openmpi-bin is known not to work in chroots, see #494046. Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634527: marked as done (libprinterconf: FTBFS: libtool: link: cannot find the library `/usr/lib/libprintsys.la' or unhandled argument `/usr/lib/libprintsys.la')
Your message dated Tue, 27 Sep 2011 08:50:11 +
with message-id e1r8tmh-0004yi...@franck.debian.org
and subject line Bug#634527: fixed in libprinterconf 0.5-12
has caused the Debian Bug report #634527,
regarding libprinterconf: FTBFS: libtool: link: cannot find the library
`/usr/lib/libprintsys.la' or unhandled argument `/usr/lib/libprintsys.la'
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.)
--
634527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libprinterconf
Version: 0.5-11
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110718 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
ar cru .libs/libprinterconf.a printerconf.o snmpinter.o parport.o
ranlib .libs/libprinterconf.a
creating libprinterconf.la
(cd .libs rm -f libprinterconf.la ln -s ../libprinterconf.la
libprinterconf.la)
gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -g -O2 -O2 -g -MT pconf_detect.o -MD -MP
-MF .deps/pconf_detect.Tpo -c -o pconf_detect.o pconf_detect.c
pconf_detect.c: In function 'main':
pconf_detect.c:177:23: warning: incompatible implicit declaration of built-in
function 'strdup' [enabled by default]
mv -f .deps/pconf_detect.Tpo .deps/pconf_detect.Po
/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -O2 -g -lglib-2.0
-ltdb-o pconf_detect pconf_detect.o libprinterconf.la -lstdc++
/usr/lib/libprintsys.la /usr/lib/libsnmpkit.la -lpthread
libtool: link: cannot find the library `/usr/lib/libprintsys.la' or unhandled
argument `/usr/lib/libprintsys.la'
make[4]: *** [pconf_detect] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2011/07/18/libprinterconf_0.5-11_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.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
---End Message---
---BeginMessage---
Source: libprinterconf
Source-Version: 0.5-12
We believe that the bug you reported is fixed in the latest version of
libprinterconf, which is due to be installed in the Debian FTP archive:
libprinterconf-dev_0.5-12_amd64.deb
to main/libp/libprinterconf/libprinterconf-dev_0.5-12_amd64.deb
libprinterconf0c2a_0.5-12_amd64.deb
to main/libp/libprinterconf/libprinterconf0c2a_0.5-12_amd64.deb
libprinterconf_0.5-12.diff.gz
to main/libp/libprinterconf/libprinterconf_0.5-12.diff.gz
libprinterconf_0.5-12.dsc
to main/libp/libprinterconf/libprinterconf_0.5-12.dsc
pconf-detect_0.5-12_amd64.deb
to main/libp/libprinterconf/pconf-detect_0.5-12_amd64.deb
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 634...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
A Mennucc1 mennu...@debian.org (supplier of updated libprinterconf 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: Mon, 26 Sep 2011 13:50:37 +0200
Source: libprinterconf
Binary: libprinterconf-dev pconf-detect libprinterconf0c2a
Architecture: source amd64
Version: 0.5-12
Distribution: unstable
Urgency: low
Maintainer: A Mennucc1 mennu...@debian.org
Changed-By: A Mennucc1 mennu...@debian.org
Description:
libprinterconf-dev - Printer autodetection library
libprinterconf0c2a - Printer autodetection library
pconf-detect - Small printer auto-detect command-line tool
Closes: 558918 634527
Changes:
libprinterconf (0.5-12) unstable; urgency=low
.
* Fixed lintian warnings
- Add build-arch: build-stamp build-indep
- copyright referred to versionless license file GPL
* Bump standard to 3.9.2
* Refreshed autoreconf
* Refresh config.sub and config.guess at each run
* Bumb debhelper to 8 : use ${misc:Depends} ; use dh_prep
*
Bug#639155: marked as done (libprintsys: FTBFS: unsatisfiable build-dependency: tdb-dev (= 1.0.6-4) (versioned dep on a virtual pkg?))
Your message dated Tue, 27 Sep 2011 08:50:26 +
with message-id e1r8tmw-000520...@franck.debian.org
and subject line Bug#639155: fixed in libprintsys 0.6-12
has caused the Debian Bug report #639155,
regarding libprintsys: FTBFS: unsatisfiable build-dependency: tdb-dev (=
1.0.6-4) (versioned dep on a virtual pkg?)
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.)
--
639155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libprintsys
Version: 0.6-11.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110822 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
┌──┐
│ Install libprintsys build dependencies (apt-based resolver)
│
└──┘
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
sbuild-build-depends-libprintsys-dummy : Depends: tdb-dev (= 1.0.6-4)
E: Broken packages
The full build log is available from:
http://people.debian.org/~lucas/logs/2011/08/22/libprintsys_0.6-11.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---
---BeginMessage---
Source: libprintsys
Source-Version: 0.6-12
We believe that the bug you reported is fixed in the latest version of
libprintsys, which is due to be installed in the Debian FTP archive:
libprintsys-dev_0.6-12_amd64.deb
to main/libp/libprintsys/libprintsys-dev_0.6-12_amd64.deb
libprintsys_0.6-12.diff.gz
to main/libp/libprintsys/libprintsys_0.6-12.diff.gz
libprintsys_0.6-12.dsc
to main/libp/libprintsys/libprintsys_0.6-12.dsc
libprintsys_0.6-12_amd64.deb
to main/libp/libprintsys/libprintsys_0.6-12_amd64.deb
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 639...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
A Mennucc1 mennu...@debian.org (supplier of updated libprintsys 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, 27 Sep 2011 09:45:00 +0200
Source: libprintsys
Binary: libprintsys libprintsys-dev
Architecture: source amd64
Version: 0.6-12
Distribution: unstable
Urgency: low
Maintainer: A Mennucc1 mennu...@debian.org
Changed-By: A Mennucc1 mennu...@debian.org
Description:
libprintsys - printcap parser, helper for gnulpr's printfilters
libprintsys-dev - printcap parser, helper for gnulpr's printfilters, dev files
Closes: 639155
Changes:
libprintsys (0.6-12) unstable; urgency=low
.
* Fixed lintian warnings
- Add build-arch: build-stamp build-indep
- copyright referred to versionless license file GPL
* Bumb debhelper to 8 : use dh_prep ; use ${misc:Depends}
* build depends on libtdb-dev , fix: FTBFS
thanks to M. Arceda (Closes: #639155).
Checksums-Sha1:
675929e0945d30e80f5180d2fee8ef52b0873da7 1051 libprintsys_0.6-12.dsc
5acc382f0cbb7ff2afaad3ec68a22ac9ab1086d6 434244 libprintsys_0.6-12.diff.gz
4b83a46d9b09aeeaffd1e4b976eba708f458074b 23374 libprintsys_0.6-12_amd64.deb
34b3ed739acb6ab21e9be3ae4296807a8a2898a3 20530 libprintsys-dev_0.6-12_amd64.deb
Checksums-Sha256:
7ab97ab32ca2a32ac21c5d695c0e029d1eb98cc84d82c2a314d5c2aae8db5ed0 1051
libprintsys_0.6-12.dsc
48dc344a2452359554cef6acbc7862937a26e3577f06cd0f465592012291c560 434244
libprintsys_0.6-12.diff.gz
Bug#643310: [Debichem-devel] Bug#643310: mpqc cannot be started
Hi again, On Tue, Sep 27, 2011 at 09:02:50AM +0200, Georg wrote: Package: mpqc Version: 2.3.1-7 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Whenever I try to start mpqc, whatever parameters I submit, mpqc 2.3.1-7 crashes with the same output to std.err: [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 357 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 230 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../orte/runtime/orte_init.c at line 132 -- Sorry! You were supposed to get help about: orte_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-orte-runtime: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: mpi_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime: No such file or directory. Sorry! -- *** The MPI_Init_thread() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [cohg:3330] Abort before MPI_INIT completed successfully; not able to guarantee that all other processes were killed! I tried it on this amd64/testing-system, on an amd64/sid-system, and on an i386 /testing-system. Erm, can you try installing openmpi-bin, if you have that one not installed, and let me know if that fixes it? Thanks, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642734: java applets don't work in iceweasel; java doesn't terminate
Hi! I have the same problem on Debian Sid AMD64 with Iceweasel+Icedtea. Anybody know if it is possible to work around this problem? Perhaps by configuration changes in /etc/java-6-openjdk/ ? Best regards Torquil Sørensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643310: [Debichem-devel] Bug#643310: Bug#643310: mpqc cannot be started
retitle 64331 mpqc: Missing Depends on mpi-default-bin thanks On Tue, Sep 27, 2011 at 11:09:16AM +0200, Michael Banck wrote: Erm, can you try installing openmpi-bin, if you have that one not installed, and let me know if that fixes it? Yeah, that seems to be the problem, sorry about that. Thanks for your report, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 643310
Processing commands for cont...@bugs.debian.org: tags 643310 + pending Bug #643310 [mpqc] mpqc cannot be started Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 643310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 643310 to mpqc: Missing Depends on mpi-default-bin
Processing commands for cont...@bugs.debian.org: retitle 643310 mpqc: Missing Depends on mpi-default-bin Bug #643310 [mpqc] mpqc cannot be started Changed Bug title to 'mpqc: Missing Depends on mpi-default-bin' from 'mpqc cannot be started' thanks Stopping processing here. Please contact me if you need assistance. -- 643310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Pkg-utopia-maintainers] Bug#642784: network-manager 0.9.0-2 non-functional
Processing commands for cont...@bugs.debian.org: retitle 642784 network-manager 0.9.0 breaks trinity/knetworkmanager Bug #642784 [network-manager] network-manager 0.9.0-2 non-functional Changed Bug title to 'network-manager 0.9.0 breaks trinity/knetworkmanager' from 'network-manager 0.9.0-2 non-functional' thanks Stopping processing here. Please contact me if you need assistance. -- 642784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642784: marked as done (network-manager 0.9.0 breaks trinity/knetworkmanager)
Your message dated Tue, 27 Sep 2011 12:10:02 + with message-id 4e81bd1a.1090...@debian.org and subject line Re: [Pkg-utopia-maintainers] Bug#642784: network-manager 0.9.0-2 non-functional has caused the Debian Bug report #642784, regarding network-manager 0.9.0 breaks trinity/knetworkmanager 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.) -- 642784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: network-manager Version: 0.8.1-6+squeeze1 Severity: grave Justification: renders package unusable Hi there. * What led up to the situation? I ran synaptic and updated my system. * What exactly did you do (or not do) that was effective (or ineffective)? 1. I booted Ubuntu 2. I downloaded network-manager_0.8.1-6+squeeze1_amd64.deb 3. I put in my Debian's /var/cache/apt/archives directory 4. rebooted into Debian 5. ran synaptic 6. forced the version of network-manager to 0.8.1-6+squeeze1 7. updated, thereby downgrading networkmanager to 0.8.1-6+squeeze1 8. locked the version * What was the outcome of this action? My wireless networking works again * What outcome did you expect instead? I expected that upgrading network-manager wouldn't bork my wireless networking -- System Information: Debian Release: wheezy/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager depends on: ii adduser3.113 ii dbus 1.4.14-1 ii isc-dhcp-client4.1.1-P1-17 ii libc6 2.13-21 ii libdbus-1-31.4.14-1 ii libdbus-glib-1-2 0.94-4 ii libgcrypt111.5.0-3 ii libglib2.0-0 2.28.6-1 ii libgnutls262.12.10-2 ii libgudev-1.0-0 172-1 ii libnl1 1.1-7 ii libnm-glib20.8.4.0-2 ii libnm-util10.8.4.0-2 ii libpolkit-gobject-1-0 0.102-1 ii libuuid1 2.19.1-5 ii lsb-base 3.2-28 ii udev 172-1 ii wpasupplicant 0.7.3-3 Versions of packages network-manager recommends: ii dnsmasq-base 2.58-2 ii iptables 1.4.12-1 ii modemmanager none ii policykit-1 0.102-1 ii ppp 2.4.5-5 Versions of packages network-manager suggests: ii avahi-autoipd 0.6.30-5 -- no debconf information ---End Message--- ---BeginMessage--- retitle 642784 network-manager 0.9.0 breaks trinity/knetworkmanager thanks On 27.09.2011 01:24, Philip Ashmore wrote: On 26/09/11 21:41, Michael Biebl wrote: Unless you can provide further information regarding this issue, I don't see another way but closing the bug report. I reported this to Trinity Trinity networking breaks with network-manager 0.9 http://bugs.pearsoncomputing.net/show_bug.cgi?id=521 Closing this bug report. Michael ---End Message---
Processed: downgrade
Processing commands for cont...@bugs.debian.org:
severity 642784 minor
Bug #642784 {Done: Michael Biebl bi...@debian.org} [network-manager]
network-manager 0.9.0 breaks trinity/knetworkmanager
Severity set to 'minor' from 'grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
642784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641991: Problem solved in latest xorg
The problem with kate has vanished with the latest updates to xorg binaries in unstable. Please close this bug. -- Moshe Yudkowsky * mo...@pobox.com * www.pobox.com/~moshe -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643310: [Debichem-devel] Bug#643310: Bug#643310: mpqc cannot be started
Am Dienstag, den 27.09.2011, 11:17 +0200 schrieb Michael Banck: retitle 64331 mpqc: Missing Depends on mpi-default-bin thanks On Tue, Sep 27, 2011 at 11:09:16AM +0200, Michael Banck wrote: Erm, can you try installing openmpi-bin, if you have that one not installed, and let me know if that fixes it? Yeah, that seems to be the problem, sorry about that. Thanks for your report, Michael After installing openmpi-bin, mpqc works! Georg
Bug#625398: fix ftbfs with -Werror
tags 625398 + patch user ubuntu-de...@lists.ubuntu.com usertags 625398 oneiric ubuntu-patch user debian-...@lists.debian.org usertags 625398 ftbfs-gcc-4.6 ftbfs-werror thanks patch at http://launchpadlibrarian.net/81177785/oss4_4.2-build2004-1ubuntu1_4.2-build2004-1ubuntu2.diff.gz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fix ftbfs with -Werror
Processing commands for cont...@bugs.debian.org: tags 625398 + patch Bug #625398 [oss4] oss4: ftbfs with gcc-4.6 -Werror Added tag(s) patch. user ubuntu-de...@lists.ubuntu.com Setting user to ubuntu-de...@lists.ubuntu.com (was d...@ubuntu.com). usertags 625398 oneiric ubuntu-patch Bug#625398: oss4: ftbfs with gcc-4.6 -Werror There were no usertags set. Usertags are now: ubuntu-patch oneiric. user debian-...@lists.debian.org Setting user to debian-...@lists.debian.org (was ubuntu-de...@lists.ubuntu.com). usertags 625398 ftbfs-gcc-4.6 ftbfs-werror Bug#625398: oss4: ftbfs with gcc-4.6 -Werror Usertags were: ftbfs-gcc-4.6 ftbfs-werror. Usertags are now: ftbfs-gcc-4.6 ftbfs-werror. thanks Stopping processing here. Please contact me if you need assistance. -- 625398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642928: problem with closures on kfreebsd-amd64
could you forward/check in this upstream? On 09/26/2011 10:33 PM, Petr Salinger wrote: user debian-...@lists.debian.org usertag 642928 + kfreebsd usertag 642162 + kfreebsd -- Could be this related to CPU ? My is Intel(R) Core(TM)2 Duo CPU E6750 asdfasdf's AMD Sempron(tm) Processor 3000+ After changing configure.ac and propagating it into configure, the testsuite of 3.0.11~rc1-2 succeeds also on asdfasdf.d.n === libffi Summary === # of expected passes1649 # of unsupported tests 15 --- configure.ac +++ configure.ac @@ -345,7 +345,7 @@ [Cannot use PROT_EXEC on this target, so, we revert to alternative means]) ;; - *-apple-darwin10* | *-*-freebsd* | *-*-openbsd* | *-pc-solaris*) + *-apple-darwin10* | *-*-freebsd* | *-*-kfreebsd* | *-*-openbsd* | *-pc-solaris*) AC_DEFINE(FFI_MMAP_EXEC_WRIT, 1, [Cannot use malloc on this target, so, we revert to alternative means]) IMHO, similar change might help to solve gcj fails under fash.d.o, but not fano.d.o. Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633652: how embarrassing that root cannot use X windows on Debian
found 633652 1.2.1-5+lenny1 forwarded 633652 https://bugs.freedesktop.org/show_bug.cgi?id=39720 severity 633652 normal thanks On Fri, 12 Aug 2011 at 07:43:01 +0800, jida...@jidanni.org wrote: I'm raising the severity of this bug. This bug is not a security vulnerability and does not break unrelated applications. The fact that Gtk apps now connect to D-Bus makes them a related application; the reason you've only seen this recently is probably that increasingly many Gtk apps connect to D-Bus. I think this may be caused by upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=39720 which is being worked on. That bug has existed ever since dbus was written, so marking this as found in the oldest version Debian cares about (oldstable). Kenyon Ralph writes: Looking at bug 633652, have you tried running X programs as root with sux or gksu instead of su? http://packages.debian.org/squeeze/sux http://packages.debian.org/squeeze/gksu Yes, this is good advice; any tool that clears most environment variables should work. If you don't clear environment variables, then your ordinary user account is trivially root-equivalent anyway (for instance via LD_PRELOAD, or for Gtk apps, GTK_MODULES) so there's little point in having privilege separation at all. sudoedit is another good way to edit system configuration files (it copies the file to /var/tmp as root, edits that copy of the file as your unprivileged uid, then copies back it into place as root). The emacs TRAMP facility that Kenyon Ralph mentions seems an equally good approach. When run from the (Debian, GNOME, KDE etc.) menu, system administration apps like synaptic either run under su-to-root, which invokes gksu, sux or an assortment of others; or, more commonly in recent applications, act as an unprivileged front-end to a privileged system service. jidanni writes: Root not allowed to use emacs? I'm telling my mom. ... But I suppose that's what the younger generation will use and just mark this bug wontfix. Alas, no family values. Comments like this *reduce* my motivation to fix your pet bugs. If you want people to fix things for you, please be polite. Insulting volunteer developers is not a good way to motivate them to help you. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622583: marked as done (deng: FTBFS everywhere: bsp_main.o: undefined reference to symbol 'ceil@@GLIBC_2.2.5')
Your message dated Tue, 27 Sep 2011 11:32:13 + with message-id e1r8vtv-0008lm...@franck.debian.org and subject line Bug#622583: fixed in deng 1.9.0-beta6.9+dfsg1-2 has caused the Debian Bug report #622583, regarding deng: FTBFS everywhere: bsp_main.o: undefined reference to symbol 'ceil@@GLIBC_2.2.5' 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.) -- 622583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: deng Version: 1.9.0-beta6.9+dfsg1-1 Severity: serious Justification: FTBFS Hi, you seem to be missing (at least) -lm: | Linking C executable doomsday | CMakeFiles/doomsday.dir/external/lzss/unix/src/lzss.o: In function `lzOpenChunk': | /build/buildd-deng_1.9.0-beta6.9+dfsg1-1-amd64-WzHGu7/deng-1.9.0-beta6.9+dfsg1/doomsday/external/lzss/unix/src/lzss.c:1038: warning: the use of `tmpnam' is dangerous, better use `mkstemp' | /usr/bin/ld: CMakeFiles/doomsday.dir/engine/portable/src/bsp_main.o: undefined reference to symbol 'ceil@@GLIBC_2.2.5' | /usr/bin/ld: note: 'ceil@@GLIBC_2.2.5' is defined in DSO //lib64/libm.so.6 so try adding it to the linker command line | //lib64/libm.so.6: could not read symbols: Invalid operation | collect2: ld returned 1 exit status | make[3]: *** [doomsday] Error 1 Full build logs: https://buildd.debian.org/status/package.php?p=deng KiBi. ---End Message--- ---BeginMessage--- Source: deng Source-Version: 1.9.0-beta6.9+dfsg1-2 We believe that the bug you reported is fixed in the latest version of deng, which is due to be installed in the Debian FTP archive: deng_1.9.0-beta6.9+dfsg1-2.diff.gz to main/d/deng/deng_1.9.0-beta6.9+dfsg1-2.diff.gz deng_1.9.0-beta6.9+dfsg1-2.dsc to main/d/deng/deng_1.9.0-beta6.9+dfsg1-2.dsc doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb to main/d/deng/doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb 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 622...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jon Dowland j...@debian.org (supplier of updated deng 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: Mon, 26 Sep 2011 20:13:49 +0100 Source: deng Binary: doomsday Architecture: source i386 Version: 1.9.0-beta6.9+dfsg1-2 Distribution: unstable Urgency: low Maintainer: Kees Meijs p...@keesmeijs.nl Changed-By: Jon Dowland j...@debian.org Description: doomsday - enhanced version of the legendary DOOM game Closes: 622583 Changes: deng (1.9.0-beta6.9+dfsg1-2) unstable; urgency=low . * Add a patch from Jamie Jones to fix a FTBFS. Closes: #622583. * Include the following changes from -1, which were accidentally omitted: * Patched dd_zone.c file as needed * Fixed paths in CMakeLists.txt file in order to reflect Debian policies. * Adjust debian/copyright to not trigger lintian warning about templates. * Split build into build arch/indep (more work to do here) * Bump standards version. * Tweak description to avoid description-synopsis-starts-with-article. Checksums-Sha1: d683af9ed39c4dfec30d38e99541a19351f42583 1336 deng_1.9.0-beta6.9+dfsg1-2.dsc ba3a52a8e4d8b5252e365d8ca7edca10329936d9 4144 deng_1.9.0-beta6.9+dfsg1-2.diff.gz 47ee0260e3b1eaa6c579ae52bcc4bcf1dd4f7899 3185086 doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb Checksums-Sha256: 046183e42d8bf298dda7b6a25dc014fa09300b7e5cbfe9dc48e8fb768a14c22e 1336 deng_1.9.0-beta6.9+dfsg1-2.dsc dd43415e0a675cbf9e284a4593895091a6ccbe141433bdc1079786b848045bc0 4144 deng_1.9.0-beta6.9+dfsg1-2.diff.gz 4c109843ee779830c1467212607ddc1b6e67a585412b3b3b25f4b7ceb0ad32d7 3185086 doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb Files: e252662a2840b18f88569904d492148c 1336 games optional deng_1.9.0-beta6.9+dfsg1-2.dsc 7265d95e029e65c137147bf944e3cdb2 4144 games optional deng_1.9.0-beta6.9+dfsg1-2.diff.gz 46c20bd11465da1332de5e02fe59aaed 3185086 games optional doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6Br2QACgkQFotOcXAy8jgSRwCghiUBAVbVsVQIXKMrno4UBHZU 3gcAn3qn+RPU+4Z06ZGwyzp7SvbXeAuD =lw+u -END PGP SIGNATURE- ---End Message---
Bug#625145: marked as done (deng: FTBFS: libm.so.6: could not read symbols: Invalid operation)
Your message dated Tue, 27 Sep 2011 11:32:13 + with message-id e1r8vtv-0008lm...@franck.debian.org and subject line Bug#622583: fixed in deng 1.9.0-beta6.9+dfsg1-2 has caused the Debian Bug report #622583, regarding deng: FTBFS: libm.so.6: could not read symbols: Invalid operation 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.) -- 622583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: deng Version: 1.9.0-beta6.9+dfsg1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110502 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /usr/bin/ld: note: 'ceil@@GLIBC_2.2.5' is defined in DSO /lib64/libm.so.6 so try adding it to the linker command line /lib64/libm.so.6: could not read symbols: Invalid operation collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2011/05/02/deng_1.9.0-beta6.9+dfsg1-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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: deng Source-Version: 1.9.0-beta6.9+dfsg1-2 We believe that the bug you reported is fixed in the latest version of deng, which is due to be installed in the Debian FTP archive: deng_1.9.0-beta6.9+dfsg1-2.diff.gz to main/d/deng/deng_1.9.0-beta6.9+dfsg1-2.diff.gz deng_1.9.0-beta6.9+dfsg1-2.dsc to main/d/deng/deng_1.9.0-beta6.9+dfsg1-2.dsc doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb to main/d/deng/doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb 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 622...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jon Dowland j...@debian.org (supplier of updated deng 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: Mon, 26 Sep 2011 20:13:49 +0100 Source: deng Binary: doomsday Architecture: source i386 Version: 1.9.0-beta6.9+dfsg1-2 Distribution: unstable Urgency: low Maintainer: Kees Meijs p...@keesmeijs.nl Changed-By: Jon Dowland j...@debian.org Description: doomsday - enhanced version of the legendary DOOM game Closes: 622583 Changes: deng (1.9.0-beta6.9+dfsg1-2) unstable; urgency=low . * Add a patch from Jamie Jones to fix a FTBFS. Closes: #622583. * Include the following changes from -1, which were accidentally omitted: * Patched dd_zone.c file as needed * Fixed paths in CMakeLists.txt file in order to reflect Debian policies. * Adjust debian/copyright to not trigger lintian warning about templates. * Split build into build arch/indep (more work to do here) * Bump standards version. * Tweak description to avoid description-synopsis-starts-with-article. Checksums-Sha1: d683af9ed39c4dfec30d38e99541a19351f42583 1336 deng_1.9.0-beta6.9+dfsg1-2.dsc ba3a52a8e4d8b5252e365d8ca7edca10329936d9 4144 deng_1.9.0-beta6.9+dfsg1-2.diff.gz 47ee0260e3b1eaa6c579ae52bcc4bcf1dd4f7899 3185086 doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb Checksums-Sha256: 046183e42d8bf298dda7b6a25dc014fa09300b7e5cbfe9dc48e8fb768a14c22e 1336 deng_1.9.0-beta6.9+dfsg1-2.dsc dd43415e0a675cbf9e284a4593895091a6ccbe141433bdc1079786b848045bc0 4144 deng_1.9.0-beta6.9+dfsg1-2.diff.gz 4c109843ee779830c1467212607ddc1b6e67a585412b3b3b25f4b7ceb0ad32d7 3185086 doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb Files: e252662a2840b18f88569904d492148c 1336 games optional deng_1.9.0-beta6.9+dfsg1-2.dsc 7265d95e029e65c137147bf944e3cdb2 4144 games optional deng_1.9.0-beta6.9+dfsg1-2.diff.gz 46c20bd11465da1332de5e02fe59aaed 3185086 games optional doomsday_1.9.0-beta6.9+dfsg1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux)
Processed: Re: Bug#642928: problem with closures on kfreebsd-amd64
Processing commands for cont...@bugs.debian.org: forwarded 642928 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50532 Bug #642928 [libffi5] Problem with closures on kfreebsd-amd64 Set Bug forwarded-to-address to 'http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50532'. End of message, stopping processing here. Please contact me if you need assistance. -- 642928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633652: how embarrassing that root cannot use X windows on Debian
OK thanks... all I know is I now use sux and am back in business. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643310: marked as done (mpqc: Missing Depends on mpi-default-bin)
Your message dated Tue, 27 Sep 2011 12:04:22 + with message-id e1r8woc-0004t6...@franck.debian.org and subject line Bug#643310: fixed in mpqc 2.3.1-8 has caused the Debian Bug report #643310, regarding mpqc: Missing Depends on mpi-default-bin 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.) -- 643310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mpqc Version: 2.3.1-7 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Whenever I try to start mpqc, whatever parameters I submit, mpqc 2.3.1-7 crashes with the same output to std.err: [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 357 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 230 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../orte/runtime/orte_init.c at line 132 -- Sorry! You were supposed to get help about: orte_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-orte-runtime: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: mpi_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime: No such file or directory. Sorry! -- *** The MPI_Init_thread() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [cohg:3330] Abort before MPI_INIT completed successfully; not able to guarantee that all other processes were killed! I tried it on this amd64/testing-system, on an amd64/sid-system, and on an i386 /testing-system. Greetings, Georg -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpqc depends on: ii libblas3gf [libblas.so.3gf] 1.2.20110419-2 ii libc62.13-21 ii libgcc1 1:4.6.1-4 ii libgfortran3 4.6.1-4 ii liblapack3gf [liblapack.so.3gf] 3.3.1-1 ii libopenmpi1.31.4.3-2.1 ii libquadmath0 4.6.1-4 ii libsc-data 2.3.1-7 ii libsc7 2.3.1-7 ii libstdc++6 4.6.1-4 mpqc recommends no packages. Versions of packages mpqc suggests: ii mpqc-support 2.3.1-7 -- no debconf information ---End Message--- ---BeginMessage--- Source: mpqc Source-Version: 2.3.1-8 We believe that the bug you reported is fixed in the latest version of mpqc, which is due to be installed in the Debian FTP archive: libsc-data_2.3.1-8_all.deb to main/m/mpqc/libsc-data_2.3.1-8_all.deb libsc-dev_2.3.1-8_i386.deb to main/m/mpqc/libsc-dev_2.3.1-8_i386.deb libsc-doc_2.3.1-8_all.deb to main/m/mpqc/libsc-doc_2.3.1-8_all.deb libsc7_2.3.1-8_i386.deb to main/m/mpqc/libsc7_2.3.1-8_i386.deb mpqc-openmpi_2.3.1-8_all.deb to main/m/mpqc/mpqc-openmpi_2.3.1-8_all.deb mpqc-support_2.3.1-8_i386.deb to main/m/mpqc/mpqc-support_2.3.1-8_i386.deb mpqc_2.3.1-8.debian.tar.gz to main/m/mpqc/mpqc_2.3.1-8.debian.tar.gz mpqc_2.3.1-8.dsc to main/m/mpqc/mpqc_2.3.1-8.dsc mpqc_2.3.1-8_i386.deb to main/m/mpqc/mpqc_2.3.1-8_i386.deb 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. Michael Banck mba...@debian.org (supplier of updated mpqc package) (This message was generated
Bug#642922: proposed upload: dash/0.5.7-2
On Mon, Sep 26, 2011 at 05:09:54PM -0500, Jonathan Nieder wrote: Hi Gerrit, I'd like to propose git://repo.or.cz/dash/debian/jrn.git proposed-updates (commit efa06779) for upload to unstable. It does very little new --- Uploaded. Thanks to Stéphane Glondu for the hints and prodding. Thoughts of all kinds welcome, as always. My thoughts? You do an awesome work on the dash and git packages ;), thanks a lot for your valuable contributions to Debian. Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643039: 3depict: FTBFS: dpkg-buildpackage: error: dpkg-source -b 3depict-0.0.7 gave error exit status 2
severity 643039 normal title 643039 3depict: unclean source package thanks * Didier Raboud o...@debian.org [110926 21:18]: During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: dpkg-source: warning: file 3depict-0.0.7/packaging/mac/main.app/Contents/PkgInfo has no final newline (either original or modified version) dpkg-source: info: local changes detected, the modified files are: 3depict-0.0.7/packaging/debian/patches/debian-naming-desktop.patch 3depict-0.0.7/packaging/debian/patches/disable-assertion-blocking.patch 3depict-0.0.7/packaging/mac/main.app/Contents/Info.plist 3depict-0.0.7/packaging/mac/main.app/Contents/PkgInfo 3depict-0.0.7/src/pngread.c dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/3depict_0.0.7-1.diff.QbDXOW dpkg-source: info: you can integrate the local changes with dpkg-source --commit dpkg-buildpackage: error: dpkg-source -b 3depict-0.0.7 gave error exit status 2 This is a bug in dpkg-source (said to be fixed soon), which makes a relatively minor issue a hard failure. Bernhard R. Link -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#643039: 3depict: FTBFS: dpkg-buildpackage: error: dpkg-source -b 3depict-0.0.7 gave error exit status 2
Processing commands for cont...@bugs.debian.org: severity 643039 normal Bug #643039 [src:3depict] 3depict: FTBFS: dpkg-buildpackage: error: dpkg-source -b 3depict-0.0.7 gave error exit status 2 Severity set to 'normal' from 'serious' title 643039 3depict: unclean source package Unknown command or malformed arguments to command. thanks Stopping processing here. Please contact me if you need assistance. -- 643039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643339: most: build fails on configure-step (couldn't find slang.h)
Package: most Version: 5.0.0a-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, Building most with apt-get source, apt-get build-dep and dpkg-buildpackage fails on configure step: checking for Terminfo... yes checking for the slang library and header files ... no configure: error: unable to find the slang library and header file slang.h make: *** [build-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 libslang2-dev is installed and /usr/include/slang.h does exists here greetings, Michael -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages most depends on: ii libc6 2.13-21 ii libslang2 2.2.4-3 most recommends no packages. most suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643343: abe: FTBFS: Game.c:22:5: error: format not a string literal and no format arguments [-Werror=format-security]
Source: abe Version: 1.1-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 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.. -DHAVE_SDL=1 -DHAVE_SDL_MIXER=1 -DBASE_DIR=/usr/share/games/abe -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -O2 -Wall -fomit-frame-pointer -ffast-math -fexpensive-optimizations -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -c Game.c Game.c: In function 'path_sprintf': Game.c:22:5: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [Game.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/abe_1.1-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643344: abiword: FTBFS: xap_UnixDialogHelper.cpp:833:18: error: format not a string literal and no format arguments [-Werror=format-security]
Source: abiword Version: 2.8.6-0.4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[7]: Entering directory `/build/abiword-OKznWA/abiword-2.8.6/src/af/xap/gtk' CXX xap_UnixDlg_About.o CXX xap_UnixDlg_ClipArt.o CXX xap_GtkComboBoxHelpers.o CXX xap_UnixDlg_DocComparison.o CXX xap_UnixApp.o CXX xap_UnixDlg_Encoding.o CXX xap_UnixAppImpl.o CXX xap_UnixDlg_FileOpenSaveAs.o CXX xap_UnixDialogHelper.o CXX xap_UnixClipboard.o CXX xap_UnixDlg_History.o xap_UnixDlg_About.cpp: In member function 'virtual void XAP_UnixDialog_About::runModal(XAP_Frame*)': xap_UnixDlg_About.cpp:69:21: warning: variable 'dlg' set but not used [-Wunused-but-set-variable] xap_UnixDlg_FileOpenSaveAs.cpp: In member function 'gint XAP_UnixDialog_FileOpenSaveAs::previewPicture()': xap_UnixDlg_FileOpenSaveAs.cpp:953:7: warning: variable 'bLoadFailed' set but not used [-Wunused-but-set-variable] xap_UnixDialogHelper.cpp: In function 'void messageBoxOK(const char*)': xap_UnixDialogHelper.cpp:833:18: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[7]: *** [xap_UnixDialogHelper.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/abiword_2.8.6-0.4_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643345: aee: FTBFS: aee.c:2496:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: aee Version: 2.2.15b-4 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: cc -DSYS5 -DBSD_SELECT -DNCURSE -DHAS_UNISTD -DHAS_STDLIB -DHAS_CTYPE -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c help.c format.c: In function 'Format': format.c:53:6: warning: variable 'temp_pos' set but not used [-Wunused-but-set-variable] format.c:50:15: warning: variable 'start_line' set but not used [-Wunused-but-set-variable] format.c:49:15: warning: variable 'temp_line' set but not used [-Wunused-but-set-variable] control.c: In function 'menu_op': control.c:30:6: warning: variable 'vert_pos' set but not used [-Wunused-but-set-variable] mark.c: In function 'slct_right': mark.c:515:6: warning: variable 'tmpi' set but not used [-Wunused-but-set-variable] motion.c: In function 'next_page': motion.c:779:15: warning: variable 'tmp_line' set but not used [-Wunused-but-set-variable] aee.c: In function 'get_input': aee.c:740:6: warning: variable 'value' set but not used [-Wunused-but-set-variable] motion.c: In function 'prev_page': motion.c:821:15: warning: variable 'tmp_line' set but not used [-Wunused-but-set-variable] control.c: In function 'dump_aee_conf': control.c:2103:7: warning: ignoring return value of 'link', declared with attribute warn_unused_result [-Wunused-result] aee.c: In function 'sh_command': aee.c:2481:4: warning: implicit declaration of function 'wait' [-Wimplicit-function-declaration] aee.c:2496:3: error: format not a string literal and no format arguments [-Werror=format-security] aee.c:2370:7: warning: ignoring return value of 'pipe', declared with attribute warn_unused_result [-Wunused-result] aee.c:2384:7: warning: ignoring return value of 'dup', declared with attribute warn_unused_result [-Wunused-result] aee.c:2390:7: warning: ignoring return value of 'dup', declared with attribute warn_unused_result [-Wunused-result] aee.c:2425:8: warning: ignoring return value of 'pipe', declared with attribute warn_unused_result [-Wunused-result] aee.c:2442:8: warning: ignoring return value of 'dup', declared with attribute warn_unused_result [-Wunused-result] aee.c:2469:12: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] aee.c:2471:57: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] aee.c:2472:12: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] cc1: some warnings being treated as errors make[1]: *** [aee.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/aee_2.2.15b-4_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640334: marked as done ([kfreebsd] dash: faccessat implementation of test -x always returns true for user root)
Your message dated Tue, 27 Sep 2011 12:17:10 +
with message-id e1r8wb0-0005r0...@franck.debian.org
and subject line Bug#640334: fixed in dash 0.5.7-2
has caused the Debian Bug report #640334,
regarding [kfreebsd] dash: faccessat implementation of test -x always returns
true for user root
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.)
--
640334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: dash
Version: 0.5.7-1
Severity: serious
Hi!
dash relies, for it's test builtin that faccessat returns useable
values for X_OK when called from the root user. Unfortunately that's not
true on kfreebsd (and seemingly not required by POSIX, see
#640325). Could you please just use the alternate code path on kfreebsd
which appears to work as wanted.
Thanks
Christoph
---BeginMessage---
Hi!
Petr Salinger petr.salin...@seznam.cz writes:
severity 640325 wishlist
--
The following code (extracted from dash's test builtin) is behaving
differently between linux and kfreebsd, having a 644 `test' file and
running it on linux as root user prints -1 while on kfreebsd it prints
0.
---
#include fcntl.h
#include unistd.h
#include stdio.h
int main () {
printf(%d\n, faccessat(AT_FDCWD, test, X_OK, AT_EACCESS));
}
---
While the behaviour is strange, it is still POSIX conforming:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/access.html
If any access permissions are checked, each shall be checked
individually, as described in XBD File Access Permissions, except that
where that description refers to execute permission for a process with
appropriate privileges, an implementation may indicate success for
X_OK even if execute permission is not granted to any user.
We already wrap access syscall to more intuitive behaviour,
we should try to do the same also for faccessat.
So relying on this is actually a bug in dash? (and there's probably no
easy way to check how faccessat is behaving right?)
Thanks for your information!
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
---End Message---
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
---End Message---
---BeginMessage---
Source: dash
Source-Version: 0.5.7-2
We believe that the bug you reported is fixed in the latest version of
dash, which is due to be installed in the Debian FTP archive:
ash_0.5.7-2_all.deb
to main/d/dash/ash_0.5.7-2_all.deb
dash_0.5.7-2.diff.gz
to main/d/dash/dash_0.5.7-2.diff.gz
dash_0.5.7-2.dsc
to main/d/dash/dash_0.5.7-2.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 640...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonathan Nieder jrnie...@gmail.com (supplier of updated dash 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: Mon, 26 Sep 2011 16:39:38 -0500
Source: dash
Binary: dash ash
Architecture: all source
Version: 0.5.7-2
Distribution: unstable
Urgency: high
Maintainer: Gerrit Pape p...@smarden.org
Changed-By: Jonathan Nieder jrnie...@gmail.com
Description:
ash- compatibility package for dash
dash - POSIX-compliant shell
Closes: 640334 642922
Changes:
dash (0.5.7-2) unstable; urgency=high
.
* debian/diff/:
- 0004-BUILTIN-Fix-test-x-as-root...diff: new; teach test -x
as root not to return true for nonexecutable files on
platforms where faccessat() does return true in this case,
such as glibc-bsd in squeeze (thx Christoph Egger, closes:
#640334).
- 0005-SHELL-Disable-sh-c-...diff: back out the optimization
that makes dash -c script avoid a fork(). It caused
several packages to fail to build from source (thx Stéphane
Glondu, closes: #642922).
Checksums-Sha1:
2f66d96f0c6cc4dc89f6ff6c4f802a3d43603ea0 1083 dash_0.5.7-2.dsc
87d77d2de11dc911938cd93fc17bf1fac2a302e3 40587 dash_0.5.7-2.diff.gz
8cb4c5f4072a1626720d6f87a673fd2321e4cf73 28938 ash_0.5.7-2_all.deb
Checksums-Sha256:
Bug#642922: marked as done (regression: sh -c change causes FTBFS)
Your message dated Tue, 27 Sep 2011 12:17:10 +
with message-id e1r8wb0-0005r6...@franck.debian.org
and subject line Bug#642922: fixed in dash 0.5.7-2
has caused the Debian Bug report #642922,
regarding regression: sh -c change causes FTBFS
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.)
--
642922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: dash
Version: 0.5.7-1
Severity: important
Tags: patch
Hello,
Bugs #642706 (bin-prot FTBFS) and #642835 (sexplib310 FTBFS) can be
fixed by reverting the patch submitted at [1]. I don't understand why.
[1] http://thread.gmane.org/gmane.comp.shells.dash/556
While investigating #642706, in the failing case, I observed that a
cpp process called with sh -c gets SIGPIPE while writing to
stderr. In the succeeding case, the write is successful, and is read
by the ocamlbuild process that started sh -c cpp
Cheers,
--
Stéphane
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dash depends on:
ii debianutils 4.0.2
ii dpkg 1.16.0.3
ii libc62.13-21
dash recommends no packages.
dash suggests no packages.
-- debconf information:
* dash/sh: true
diff -u dash-0.5.7/debian/changelog dash-0.5.7/debian/changelog
--- dash-0.5.7/debian/changelog
+++ dash-0.5.7/debian/changelog
@@ -1,3 +1,10 @@
+dash (0.5.7-1.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Revert http://thread.gmane.org/gmane.comp.shells.dash/556
+
+ -- Stéphane Glondu glo...@debian.org Sun, 25 Sep 2011 19:05:10 +0200
+
dash (0.5.7-1) unstable; urgency=low
* new upstream release.
only in patch2:
unchanged:
--- dash-0.5.7.orig/src/main.c
+++ dash-0.5.7/src/main.c
@@ -171,7 +171,7 @@
state3:
state = 4;
if (minusc)
- evalstring(minusc, sflag ? 0 : EV_EXIT);
+ evalstring(minusc, 0);
if (sflag || minusc == NULL) {
state4: /* XXX ??? - why isn't this before the if statement */
---End Message---
---BeginMessage---
Source: dash
Source-Version: 0.5.7-2
We believe that the bug you reported is fixed in the latest version of
dash, which is due to be installed in the Debian FTP archive:
ash_0.5.7-2_all.deb
to main/d/dash/ash_0.5.7-2_all.deb
dash_0.5.7-2.diff.gz
to main/d/dash/dash_0.5.7-2.diff.gz
dash_0.5.7-2.dsc
to main/d/dash/dash_0.5.7-2.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 642...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonathan Nieder jrnie...@gmail.com (supplier of updated dash 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: Mon, 26 Sep 2011 16:39:38 -0500
Source: dash
Binary: dash ash
Architecture: all source
Version: 0.5.7-2
Distribution: unstable
Urgency: high
Maintainer: Gerrit Pape p...@smarden.org
Changed-By: Jonathan Nieder jrnie...@gmail.com
Description:
ash- compatibility package for dash
dash - POSIX-compliant shell
Closes: 640334 642922
Changes:
dash (0.5.7-2) unstable; urgency=high
.
* debian/diff/:
- 0004-BUILTIN-Fix-test-x-as-root...diff: new; teach test -x
as root not to return true for nonexecutable files on
platforms where faccessat() does return true in this case,
such as glibc-bsd in squeeze (thx Christoph Egger, closes:
#640334).
- 0005-SHELL-Disable-sh-c-...diff: back out the optimization
that makes dash -c script avoid a fork(). It caused
several packages to fail to build from source (thx Stéphane
Glondu, closes: #642922).
Checksums-Sha1:
2f66d96f0c6cc4dc89f6ff6c4f802a3d43603ea0 1083 dash_0.5.7-2.dsc
87d77d2de11dc911938cd93fc17bf1fac2a302e3 40587 dash_0.5.7-2.diff.gz
8cb4c5f4072a1626720d6f87a673fd2321e4cf73 28938 ash_0.5.7-2_all.deb
Checksums-Sha256:
987a50f6f79f854a8caa485d5d4f4b9f5205ce1eba6bc6cda92096ebec2e8107 1083
dash_0.5.7-2.dsc
7ae4ad61bea0849e022dba92b16d46e562ae2dadc7d335a7bce13d5d436d1129 40587
Bug#643347: aegis: FTBFS: libaegis/http.cc:407:43: error: format not a string literal and no format arguments [-Werror=format-security]
Source: aegis Version: 4.24.3-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: g++ -I. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -I/usr/include/libxml2 -c libaegis/http.cc libaegis/http.cc: In function 'void emit_change_href(change::pointer, const char*)': libaegis/http.cc:407:43: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[1]: *** [libaegis/http.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/aegis_4.24.3-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643348: ale: FTBFS: ui/unsupported.h:35:30: error: format not a string literal and no format arguments [-Werror=format-security]
Source: ale Version: 0.9.0.3-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: g++ -DHAVE_CONFIG_H -I. -pthread -DUSE_PTHREAD=1 -DDEBUG -DUSE_UNIX -DUSE_IOCTL -DALE_COORDINATES=SINGLE -DALE_COLORS=SINGLE -DOPTIMIZATIONS=1 -I./lib -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o ui.o `test -f 'ui/ui.cc' || echo './'`ui/ui.cc In file included from ui/../d2/transformation.h:34:0, from ui/../d2/filter.h:29, from ui/../d2/align.h:28, from ui/../d2.h:99, from ui/ui_tty.h:36, from ui/ui.cc:22: ui/../d2/trans_multi.h: In member function 'int d2::trans_multi::multi_coordinate::operator(const d2::trans_multi::multi_coordinate) const': ui/../d2/trans_multi.h:42:38: warning: suggest parentheses around '' within '||' [-Wparentheses] ui/../d2/trans_multi.h:43:51: warning: suggest parentheses around '' within '||' [-Wparentheses] In file included from ui/../d2/align.h:33:0, from ui/../d2.h:99, from ui/ui_tty.h:36, from ui/ui.cc:22: ui/../d2/tfile.h: In function 'd2::transformation d2::tload_next(d2::tload_t*, int, d2::transformation, int*, int)': ui/../d2/tfile.h:525:51: warning: suggest parentheses around '' within '||' [-Wparentheses] ui/../d2/tfile.h:526:69: warning: suggest parentheses around '' within '||' [-Wparentheses] ui/../d2/tfile.h:596:51: warning: suggest parentheses around '' within '||' [-Wparentheses] ui/../d2/tfile.h:597:69: warning: suggest parentheses around '' within '||' [-Wparentheses] In file included from ui/../d2/align.h:34:0, from ui/../d2.h:99, from ui/ui_tty.h:36, from ui/ui.cc:22: ui/../d2/image_rw.h: In static member function 'static d2::image* d2::image_rw::read_image(const char*, d2::exposure*, const char*, unsigned int, int)': ui/../d2/image_rw.h:146:14: warning: unused variable 'warned' [-Wunused-variable] ui/../d2/image_rw.h: In static member function 'static void d2::image_rw::write_image(const char*, const d2::image*, d2::exposure*, int, int)': ui/../d2/image_rw.h:343:14: warning: unused variable 'warned' [-Wunused-variable] In file included from ui/../d2/render/combine.h:31:0, from ui/../d2/render_parse.h:25, from ui/../d2.h:120, from ui/ui_tty.h:36, from ui/ui.cc:22: ui/../d2/render/incremental.h: In member function 'virtual void d2::incremental::merge::subdomain_algorithm(unsigned int, int, int, int, int)': ui/../d2/render/incremental.h:225:10: warning: variable 'offset' set but not used [-Wunused-but-set-variable] In file included from ui/input.h:44:0, from ui/ui.cc:25: ui/unsupported.h: In static member function 'static void unsupported::fornow(const char*)': ui/unsupported.h:35:30: error: format not a string literal and no format arguments [-Werror=format-security] In file included from ui/input.h:45:0, from ui/ui.cc:25: ui/implication.h: In static member function 'static void implication::changed(const char*, const char*, const char*)': ui/implication.h:36:30: error: format not a string literal and no format arguments [-Werror=format-security] ui/implication.h:40:26: error: format not a string literal and no format arguments [-Werror=format-security] ui/implication.h:45:26: error: format not a string literal and no format arguments [-Werror=format-security] In file included from ui/../d3.h:50:0, from ui/input.h:80, from ui/ui.cc:25: ui/../d3/scene.h: In member function 'void d3::scene::wml::increase_capacity()': ui/../d3/scene.h:1134:40: warning: format '%d' expects argument of type 'int', but argument 3 has type 'long unsigned int' [-Wformat] ui/../d2/image_ale_real.h: In member function 'void d2::image_ale_realdisk_support::resident_begin(unsigned int) const [with int disk_support = 1]': ui/../d2/image_ale_real.h:192:3: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] ui/../d2/image_bayer_ale_real.h: In member function 'void d2::image_bayer_ale_realdisk_support::resident_begin(unsigned int) const [with int disk_support = 1]': ui/../d2/image_bayer_ale_real.h:229:3: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] ui/../thread.h: In static member function 'static void thread::try_linux()': ui/../thread.h:57:31: warning: ignoring return value
Bug#643349: alpine: FTBFS: flocklnx.c:60:7: error: format not a string literal and no format arguments [-Werror=format-security]
Source: alpine Version: 2.02-3 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: In file included from osdep.c:56:0: flocklnx.c: In function 'safe_flock': flocklnx.c:60:7: error: format not a string literal and no format arguments [-Werror=format-security] make[5]: *** [osdep.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/alpine_2.02-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643350: alsamixergui: FTBFS: Fl_AM.cxx:154:20: error: format not a string literal and no format arguments [-Werror=format-security]
Source: alsamixergui Version: 0.9.0rc2-1-9 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: g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o Fl_AM.o `test -f 'Fl_AM.cxx' || echo './'`Fl_AM.cxx In file included from Fl_AM.cxx:11:0: images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec0.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] In file included from Fl_AM.cxx:12:0: images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/rec1.xpm:18:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] In file included from Fl_AM.cxx:13:0: images/speakerleft0.xpm:22:19: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/speakerleft0.xpm:22:19: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/speakerleft0.xpm:22:19: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/speakerleft0.xpm:22:19: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/speakerleft0.xpm:22:19: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/speakerleft0.xpm:22:19: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/speakerleft0.xpm:22:19: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] images/speakerleft0.xpm:22:19: warning: deprecated conversion from string constant to 'char*'
Bug#643351: anjuta: FTBFS: am-project.c:1600:7: error: format not a string literal and no format arguments [-Werror=format-security]
Source: anjuta Version: 2:3.0.3.0-3 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: /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare-pthread -DGSEAL_ENABLE -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -DGSEAL_ENABLE -pthread -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libgdl-3.0 -I/usr/include/gtk-3.0 -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include-I../.. -I../../libanjuta -DPACKAGE_PIXMAPS_DIR=\/usr/share/pixmaps/anjuta\ -DPACKAGE_LIB_DIR=\/usr/lib/anjuta\ -DPACKAGE_DATA_DIR=\/usr/share/anjuta\ -DG_LOG_DOMAIN=\am-project\ -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o am-project.lo am-project.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -pthread -DGSEAL_ENABLE -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -DGSEAL_ENABLE -pthread -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libgdl-3.0 -I/usr/include/gtk-3.0 -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I../.. -I../../libanjuta -DPACKAGE_PIXMAPS_DIR=\/usr/share/pixmaps/anjuta\ -DPACKAGE_LIB_DIR=\/usr/lib/anjuta\ -DPACKAGE_DATA_DIR=\/usr/share/anjuta\ -DG_LOG_DOMAIN=\am-project\ -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c am-project.c -fPIC -DPIC -o .libs/am-project.o am-project.c: In function 'amp_project_load_root': am-project.c:1600:7: error: format not a string literal and no format arguments [-Werror=format-security] am-project.c: At top level: am-project.c:408:1: warning: 'ac_init_default_tarname' defined but not used [-Wunused-function] cc1: some warnings being treated as errors make[5]: *** [am-project.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/anjuta_2:3.0.3.0-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643352: arpalert: FTBFS: ./log.c:122:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: arpalert Version: 2.0.11-7 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: x86_64-linux-gnu-gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -DCONFIG_FILE=\/etc/arpalert/arpalert.conf\ -DPID_FILE=\/var/run/arpalert.pid\ -c -o sens_timeouts.o ./sens_timeouts.c ./loadconfig.c: In function 'convert_octal': ./loadconfig.c:608:6: warning: variable 'i' set but not used [-Wunused-but-set-variable] ./loadmodule.c: In function 'alerte_mod': ./loadmodule.c:140:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] ./log.c: In function 'logmsg': ./log.c:122:3: error: format not a string literal and no format arguments [-Werror=format-security] ./sens_timeouts.c: In function 'sens_timeout_add': ./sens_timeouts.c:131:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ./sens_timeouts.c: In function 'sens_timeout_exist': ./sens_timeouts.c:153:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ./loadconfig.c: In function 'set_option': ./loadconfig.c:813:33: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] cc1: some warnings being treated as errors make[1]: *** [log.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/arpalert_2.0.11-7_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643353: asmix: FTBFS: asmix.c:580:5: error: format not a string literal and no format arguments [-Werror=format-security]
Source: asmix Version: 1.5-4 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 -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c asmix.c asmix.c: In function 'UpdatePos': asmix.c:193:3: warning: implicit declaration of function 'aToVol' [-Wimplicit-function-declaration] asmix.c: In function 'main': asmix.c:288:7: warning: variable 'status' set but not used [-Wunused-but-set-variable] asmix.c:287:10: warning: unused variable 'pixmask' [-Wunused-variable] asmix.c: In function 'GetXPM': asmix.c:580:5: error: format not a string literal and no format arguments [-Werror=format-security] asmix.c:587:5: error: format not a string literal and no format arguments [-Werror=format-security] asmix.c:567:10: warning: unused variable 'col' [-Wunused-variable] asmix.c: In function 'main': asmix.c:515:19: warning: ignoring return value of 'system', declared with attribute warn_unused_result [-Wunused-result] cc1: some warnings being treated as errors make[1]: *** [asmix.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/asmix_1.5-4_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643354: assimp: FTBFS: WriteDumb.cpp:1153:14: error: format not a string literal and no format arguments [-Werror=format-security]
Source: assimp Version: 2.0.863+dfsg-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: make[3]: Entering directory `/build/assimp-i7t_v6/assimp-2.0.863+dfsg/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /build/assimp-i7t_v6/assimp-2.0.863+dfsg/obj-x86_64-linux-gnu/CMakeFiles 96 [ 96%] Building CXX object tools/assimp_cmd/CMakeFiles/assimp_cmd.dir/CompareDump.cpp.o cd /build/assimp-i7t_v6/assimp-2.0.863+dfsg/obj-x86_64-linux-gnu/tools/assimp_cmd /usr/bin/g++ -DASSIMP_BUILD_NO_OWN_ZLIB -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -I/build/assimp-i7t_v6/assimp-2.0.863+dfsg/include -I/build/assimp-i7t_v6/assimp-2.0.863+dfsg/code-fvisibility=hidden -o CMakeFiles/assimp_cmd.dir/CompareDump.cpp.o -c /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/CompareDump.cpp /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/CompareDump.cpp: In function 'void CompareOnTheFlyMaterialProperty(comparer_context)': /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/CompareDump.cpp:591:9: warning: enumeration value '_aiPTI_Force32Bit' not handled in switch [-Wswitch] /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/CompareDump.cpp: In function 'void CompareOnTheFlyTexture(comparer_context)': /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/CompareDump.cpp:760:17: warning: unused variable 'w' [-Wunused-variable] /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/CompareDump.cpp:761:17: warning: unused variable 'h' [-Wunused-variable] /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/CompareDump.cpp: In function 'int Assimp_CompareDump(const char* const*, unsigned int)': /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/CompareDump.cpp:845:75: warning: suggest parentheses around '' within '||' [-Wparentheses] /usr/bin/cmake -E cmake_progress_report /build/assimp-i7t_v6/assimp-2.0.863+dfsg/obj-x86_64-linux-gnu/CMakeFiles 97 [ 97%] Building CXX object tools/assimp_cmd/CMakeFiles/assimp_cmd.dir/ImageExtractor.cpp.o cd /build/assimp-i7t_v6/assimp-2.0.863+dfsg/obj-x86_64-linux-gnu/tools/assimp_cmd /usr/bin/g++ -DASSIMP_BUILD_NO_OWN_ZLIB -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -I/build/assimp-i7t_v6/assimp-2.0.863+dfsg/include -I/build/assimp-i7t_v6/assimp-2.0.863+dfsg/code-fvisibility=hidden -o CMakeFiles/assimp_cmd.dir/ImageExtractor.cpp.o -c /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/ImageExtractor.cpp /usr/bin/cmake -E cmake_progress_report /build/assimp-i7t_v6/assimp-2.0.863+dfsg/obj-x86_64-linux-gnu/CMakeFiles 98 [ 98%] Building CXX object tools/assimp_cmd/CMakeFiles/assimp_cmd.dir/Main.cpp.o cd /build/assimp-i7t_v6/assimp-2.0.863+dfsg/obj-x86_64-linux-gnu/tools/assimp_cmd /usr/bin/g++ -DASSIMP_BUILD_NO_OWN_ZLIB -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -I/build/assimp-i7t_v6/assimp-2.0.863+dfsg/include -I/build/assimp-i7t_v6/assimp-2.0.863+dfsg/code-fvisibility=hidden -o CMakeFiles/assimp_cmd.dir/Main.cpp.o -c /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/Main.cpp /usr/bin/cmake -E cmake_progress_report /build/assimp-i7t_v6/assimp-2.0.863+dfsg/obj-x86_64-linux-gnu/CMakeFiles 99 [ 99%] Building CXX object tools/assimp_cmd/CMakeFiles/assimp_cmd.dir/WriteDumb.cpp.o cd /build/assimp-i7t_v6/assimp-2.0.863+dfsg/obj-x86_64-linux-gnu/tools/assimp_cmd /usr/bin/g++ -DASSIMP_BUILD_NO_OWN_ZLIB -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -I/build/assimp-i7t_v6/assimp-2.0.863+dfsg/include -I/build/assimp-i7t_v6/assimp-2.0.863+dfsg/code-fvisibility=hidden -o CMakeFiles/assimp_cmd.dir/WriteDumb.cpp.o -c /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/WriteDumb.cpp /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/WriteDumb.cpp: In function 'uint32_t WriteBinaryMesh(const aiMesh*)': /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/WriteDumb.cpp:343:70: warning: suggest parentheses around assignment used as truth value [-Wparentheses] /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/WriteDumb.cpp: In function 'uint32_t WriteBinaryLight(const aiLight*)': /build/assimp-i7t_v6/assimp-2.0.863+dfsg/tools/assimp_cmd/WriteDumb.cpp:491:41: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
Bug#643355: at-spi: FTBFS: simple-at.c:608:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: at-spi Version: 1.30.1-3 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.. -pthread -DORBIT2=1 -I/usr/include/atk-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gail-1.0 -I/usr/include/libbonobo-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -DSPI_DEBUG-g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c simple-at.c simple-at.c: In function '_festival_write': simple-at.c:608:3: error: format not a string literal and no format arguments [-Werror=format-security] simple-at.c:613:8: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] cc1: some warnings being treated as errors make[3]: *** [simple-at.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/at-spi_1.30.1-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643356: babl: FTBFS: babl-model.c:49:7: error: format not a string literal and no format arguments [-Werror=format-security]
Source: babl Version: 0.0.22-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.. -I.. -I../babl/base -DLIBDIR=\/usr/lib\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -c babl-model.c -fPIC -DPIC -o .libs/babl-model.o babl-model.c: In function 'create_name': babl-model.c:49:7: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[4]: *** [babl-model.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/babl_0.0.22-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643357: bickley: FTBFS: kozo-db.c:79:30: error: format not a string literal and no format arguments [-Werror=format-security]
Source: bickley Version: 0.4.4-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: make[3]: Entering directory `/build/bickley-V2OHYZ/bickley-0.4.4/kozo' CCkozo-db.o kozo-db.c: In function 'handle_lookup_error': kozo-db.c:79:30: error: format not a string literal and no format arguments [-Werror=format-security] kozo-db.c:84:30: error: format not a string literal and no format arguments [-Werror=format-security] kozo-db.c: In function 'handle_put_error': kozo-db.c:95:30: error: format not a string literal and no format arguments [-Werror=format-security] kozo-db.c:99:30: error: format not a string literal and no format arguments [-Werror=format-security] kozo-db.c: In function 'check_version': kozo-db.c:173:21: warning: variable 'err' set but not used [-Wunused-but-set-variable] kozo-db.c: At top level: kozo-db.c:890:1: warning: 'dump_data' defined but not used [-Wunused-function] cc1: some warnings being treated as errors make[3]: *** [libkozo_la-kozo-db.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/bickley_0.4.4-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643358: bison: FTBFS: getargs.c:373:2: error: format not a string literal and no format arguments [-Werror=format-security]
Source: bison Version: 1:2.4.1.dfsg-3 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 -std=gnu99 -I. -I../lib -I../lib-g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c getargs.c getargs.c: In function 'skeleton_arg': getargs.c:373:2: error: format not a string literal and no format arguments [-Werror=format-security] getargs.c:375:2: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[4]: *** [getargs.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/bison_1:2.4.1.dfsg-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643359: blktool: FTBFS: util.c:31:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: blktool Version: 4-6 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/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c util.c util.c: In function 'pdie': util.c:31:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[2]: *** [util.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/blktool_4-6_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643360: cairo-dock: FTBFS: cairo-dock-log.c:78:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: cairo-dock Version: 2.3.0~3-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: [ 70%] Building C object src/gldit/CMakeFiles/gldi.dir/cairo-dock-log.c.o cd /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/obj-x86_64-linux-gnu/src/gldit /usr/bin/cc -Dgldi_EXPORTS -DGL_GLEXT_PROTOTYPES=\1\ -DCAIRO_DOCK_DEFAULT_ICON_NAME=\default-icon.svg\ -DCAIRO_DOCK_ICON=\cairo-dock.svg\ -DCAIRO_DOCK_LOGO=\cairo-dock-logo.png\ -DCAIRO_DOCK_DATA_DIR=\cairo-dock\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -fPIC -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/librsvg-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I/build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit -I/build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/icon-factory -I/build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/implementations -std=c99 -Wstrict-prototypes -Wextra -Wwrite-strings -Wuninitialized -Werror-implicit-function-declaration -o CMakeFiles/gldi.dir/cairo-dock-log.c.o -c /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c: In function '_cd_log_level_to_string': /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c:49:3: warning: enumeration value 'G_LOG_FLAG_RECURSION' not handled in switch [-Wswitch] /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c:49:3: warning: enumeration value 'G_LOG_FLAG_FATAL' not handled in switch [-Wswitch] /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c:49:3: warning: enumeration value 'G_LOG_LEVEL_MASK' not handled in switch [-Wswitch] /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c: In function 'cd_log_location': /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c:78:3: error: format not a string literal and no format arguments [-Werror=format-security] /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c: In function 'cairo_dock_log_handler': /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c:85:49: warning: unused parameter 'log_domain' [-Wunused-parameter] /build/cairo-dock-6nTsSw/cairo-dock-2.3.0~3/src/gldit/cairo-dock-log.c:88:45: warning: unused parameter 'user_data' [-Wunused-parameter] cc1: some warnings being treated as errors make[3]: *** [src/gldit/CMakeFiles/gldi.dir/cairo-dock-log.c.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/cairo-dock_2.3.0~3-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643363: clp: FTBFS: CbcOrClpParam.cpp:1078:43: error: format not a string literal and no format arguments [-Werror=format-security]
Source: clp Version: 1.12.0-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: g++ -DHAVE_CONFIG_H -I. -I`echo .` -I../inc -I`echo /src` -I`echo /inc` -I/usr/include/coin -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o CbcOrClpParam.o CbcOrClpParam.cpp CbcOrClpParam.cpp: In function 'std::string CoinReadNextField()': CbcOrClpParam.cpp:1078:43: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[3]: *** [CbcOrClpParam.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/clp_1.12.0-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643366: concalc: FTBFS: concalc.cpp:442:22: error: format not a string literal and no format arguments [-Werror=format-security]
Source: concalc Version: 0.9.2-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: g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o concalc.o concalc.cpp concalc.cpp: In function 'int main(int, char**)': concalc.cpp:442:22: error: format not a string literal and no format arguments [-Werror=format-security] concalc.cpp:506:20: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] concalc.cpp: In function 'void searchScripts(char*, Preferences*, Variable*, ThreadSync*)': concalc.cpp:609:35: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] concalc.cpp: In function 'void loadSubScripts(ThreadSync*, Preferences*, Variable*, Script*)': concalc.cpp:681:49: error: format not a string literal and no format arguments [-Werror=format-security] concalc.cpp:675:53: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] concalc.cpp: In function 'void searchScripts(char*, Preferences*, Variable*, ThreadSync*)': concalc.cpp:639:55: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] concalc.cpp: In function 'int main(int, char**)': concalc.cpp:109:53: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result] concalc.cpp:303:24: warning: ignoring return value of 'int scanf(const char*, ...)', declared with attribute warn_unused_result [-Wunused-result] concalc.cpp:529:23: warning: ignoring return value of 'int chdir(const char*)', declared with attribute warn_unused_result [-Wunused-result] cc1plus: some warnings being treated as errors make[3]: *** [concalc.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/concalc_0.9.2-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643367: contacts: FTBFS: contacts-callbacks-ui.c:224:7: error: format not a string literal and no format arguments [-Werror=format-security]
Source: contacts Version: 0.9-1.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.. -DPKGDATADIR=\/usr/share/contacts\ -DCONTACTS_LOCALE_DIR=\/usr/share/locale\ -DDATADIR=\/usr/share\ -Wall -export-dynamic -pthread -DCAMEL_HAVE_NSS -DCAMEL_HAVE_SSL -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/evolution-data-server-3.0 -I/usr/include/libxml2 -I/usr/include/gconf/2 -I/usr/include/libsoup-2.4 -I/usr/include/orbit-2.0 -pthread -DORBIT2=1 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c contacts-callbacks-ui.c contacts-callbacks-ui.c: In function 'contacts_delete_cb': contacts-callbacks-ui.c:224:7: error: format not a string literal and no format arguments [-Werror=format-security] contacts-callbacks-ui.c: In function 'contacts_export': contacts-callbacks-ui.c:403:5: warning: format '%lld' expects argument of type 'long long int', but argument 5 has type 'GnomeVFSFileSize' [-Wformat] cc1: some warnings being treated as errors make[3]: *** [contacts-callbacks-ui.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/contacts_0.9-1.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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643368: control-center: FTBFS: gnome-about-me-password.c:213:7: error: format not a string literal and no format arguments [-Werror=format-security]
Source: control-center Version: 1:2.30.1-3 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../../capplets/common -pthread -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/libxml2 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I../../ -DG_LOG_DOMAIN=\about-me-properties\ -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DCAMEL_HAVE_NSS -DCAMEL_HAVE_SSL -pthread -DORBIT2=1 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/evolution-data-server-3.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/gconf/2 -I/usr/include/libsoup-2.4 -I/usr/include/orbit-2.0 -DDATADIR=\/usr/share\ -DGNOMECC_DATA_DIR=\/usr/share/gnome-control-center\ -DGNOMECC_UI_DIR=\/usr/share/gnome-control-center/ui\ -DGNOMECC_PIXMAP_DIR=\/usr/share/gnome-control-center/pixmaps\ -DGNOMELOCALEDIR=\/usr/share/locale\-g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c gnome-about-me-password.c gnome-about-me-password.c: In function 'spawn_passwd': gnome-about-me-password.c:213:7: error: format not a string literal and no format arguments [-Werror=format-security] gnome-about-me-password.c: In function 'io_watch_stdout': gnome-about-me-password.c:430:14: warning: variable 'dialog' set but not used [-Wunused-but-set-variable] gnome-about-me-password.c: In function 'passdlg_error_dialog': gnome-about-me-password.c:720:7: error: format not a string literal and no format arguments [-Werror=format-security] gnome-about-me-password.c:726:10: error: format not a string literal and no format arguments [-Werror=format-security] gnome-about-me-password.c: In function 'passdlg_validate_passwords': gnome-about-me-password.c:870:14: warning: variable 'dialog' set but not used [-Wunused-but-set-variable] cc1: some warnings being treated as errors make[6]: *** [gnome-about-me-password.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/control-center_1:2.30.1-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643369: crack-attack: FTBFS: callbacks.cxx:116:38: error: format not a string literal and no format arguments [-Werror=format-security]
Source: crack-attack Version: 1.1.14-9 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: g++ -DHAVE_CONFIG_H -I. -I. -I../../src -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DNDEBUG -DDATA_DIRECTORY='/usr/share/games/crack-attack/' -DPACKAGE_DATA_DIR=\/usr/share/games\ -DPACKAGE_LOCALE_DIR=\/usr//locale\ -DBINARY_DIRECTORY='/usr/games' -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o callbacks.o callbacks.cxx callbacks.cxx: In function 'void ca_error_dialog(const char*)': callbacks.cxx:116:38: error: format not a string literal and no format arguments [-Werror=format-security] callbacks.cxx: In function 'gboolean networking_output(GIOChannel*, GIOCondition, gpointer)': callbacks.cxx:163:13: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[4]: *** [callbacks.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/crack-attack_1.1.14-9_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643370: d52: FTBFS: d52pass2.c:935:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: d52 Version: 3.4.1-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 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c d52pass2.c -o obj/d52pass2.o d52pass2.c: In function 'pass2': d52pass2.c:299:7: warning: suggest parentheses around operand of '!' or change '' to '' or '!' to '~' [-Wparentheses] d52pass2.c: In function 'dodir': d52pass2.c:935:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[1]: *** [obj/d52pass2.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/d52_3.4.1-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643371: dasher: FTBFS: game_mode_helper.cpp:327:15: error: format not a string literal and no format arguments [-Werror=format-security]
Source: dasher Version: 4.11-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: /bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../..-I./../DasherCore -DPROGDATA=\/usr/share/dasher\ -I../../intl -I../../intl -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -DORBIT2=1 -I/usr/include/gnome-speech-1.0 -I/usr/include/libbonobo-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/bonobo-activation-2.0 -pthread -DORBIT2=1 -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/bonobo-activation-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/at-spi-1.0 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o game_mode_helper.lo game_mode_helper.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -I./../DasherCore -DPROGDATA=\/usr/share/dasher\ -I../../intl -I../../intl -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -DORBIT2=1 -I/usr/include/gnome-speech-1.0 -I/usr/include/libbonobo-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/bonobo-activation-2.0 -pthread -DORBIT2=1 -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/bonobo-activation-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/at-spi-1.0 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c game_mode_helper.cpp -fPIC -DPIC -o .libs/game_mode_helper.o In file included from ./../DasherCore/DasherComponent.h:4:0, from ./../DasherCore/DasherModel.h:34, from ./../DasherCore/ControlManager.h:24, from GtkDasherControl.h:8, from game_mode_helper.h:4, from game_mode_helper.cpp:1: ./../DasherCore/SettingsStore.h:21:15: warning: declaration 'struct Dasher::CEventHandler' does not declare anything [enabled by default] ./../DasherCore/SettingsStore.h:22:15: warning: declaration 'struct Dasher::CParameterNotificationEvent' does not declare anything [enabled by default] game_mode_helper.cpp: In function 'void game_mode_helper_update_target_label(GameModeHelper*)': game_mode_helper.cpp:275:21: warning: variable 'co' set but not used [-Wunused-but-set-variable]
Bug#643372: dates: FTBFS: dates_gtk.c:1117:5: error: format not a string literal and no format arguments [-Werror=format-security]
Source: dates Version: 0.4.8-1.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 -std=gnu99 -DHAVE_CONFIG_H -I. -I/build/dates-L5nnhv/dates-0.4.8/./src -DPKGDATADIR=\/usr/share/dates\ -DDATES_LOCALE_DIR=\/usr/share/locale\ -DDATADIR=\/usr/share\ -std=c99 -Wall -pthread -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/evolution-data-server-3.0 -I/usr/include/ -I/usr/include/libxml2 -I/usr/include/gconf/2 -I/usr/include/libsoup-2.4 -I/usr/include/orbit-2.0-g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c: In function 'calendar_do_edit_dialog_response_cb': /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c:1117:5: error: format not a string literal and no format arguments [-Werror=format-security] /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c: In function 'create_calendars_dialog': /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c:1581:13: warning: variable 'cal_edit_button' set but not used [-Wunused-but-set-variable] /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c:1580:13: warning: variable 'cal_new_button' set but not used [-Wunused-but-set-variable] /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c: In function 'create_exceptions_dialog': /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c:1668:13: warning: variable 'repeats_close_button' set but not used [-Wunused-but-set-variable] /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c: In function 'dates_platform_import_dialog': /build/dates-L5nnhv/dates-0.4.8/./src/dates_gtk.c:2114:21: warning: variable 'default_iter' set but not used [-Wunused-but-set-variable] cc1: some warnings being treated as errors make[3]: *** [dates_gtk.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/dates_0.4.8-1.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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643373: desktop-file-utils: FTBFS: update-desktop-database.c:465:7: error: format not a string literal and no format arguments [-Werror=format-security]
Source: desktop-file-utils Version: 0.15-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/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DDATADIR=\/usr/share\ -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE-g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -c `test -f 'update-desktop-database.c' || echo './'`update-desktop-database.c update-desktop-database.c: In function 'print_desktop_dirs': update-desktop-database.c:465:7: error: format not a string literal and no format arguments [-Werror=format-security] update-desktop-database.c:467:7: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [update-desktop-database.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/desktop-file-utils_0.15-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643374: dis51: FTBFS: pass2.c:186:4: error: format not a string literal and no format arguments [-Werror=format-security]
Source: dis51 Version: 0.5-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 -c -I. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall pass2.c -o pass2.o pass2.c: In function 'dis_inst2': pass2.c:186:4: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[1]: *** [pass2.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/dis51_0.5-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643375: ebview: FTBFS: dialog.c:72:6: error: format not a string literal and no format arguments [-Werror=format-security]
Source: ebview Version: 0.3.6.2-1.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/usr/include -pthread -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c dialog.c dialog.c: In function 'idle_warning': dialog.c:72:6: error: format not a string literal and no format arguments [-Werror=format-security] dialog.c: In function 'idle_error': dialog.c:101:6: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [dialog.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/ebview_0.3.6.2-1.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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643376: epiphany-browser: FTBFS: ephy-window.c:531:7: error: format not a string literal and no format arguments [-Werror=format-security]
Source: epiphany-browser Version: 3.0.4-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: /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../lib -I../lib/egg -I../embed -I../embed -I../lib -I../lib/egg -I../lib/widgets -I../src/bookmarks -DEXTENSIONS_DIR=\/usr/lib/epiphany-browser/3.0/extensions\ -DLOADER_DIR=\/usr/lib/epiphany-browser/3.0/loaders\ -DDATADIR=\/usr/share/epiphany-browser\ -DGNOMELOCALEDIR=\/usr/share/locale\ -pthread -DGSEAL_ENABLE -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/gtk-3.0 -I/usr/include/cairo -I/usr/include/gtk-3.0/unix-print -I/usr/include/libxml2 -I/usr/include/startup-notification-1.0 -I/usr/include/webkit-3.0 -I/usr/include/libsoup-2.4 -I/usr/include/libsoup-gnome-2.4 -I/usr/include/gnome-keyring-1 -I/usr/include/gsettings-desktop-schemas -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include-Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/NetworkManager -pthread -DGSEAL_ENABLE -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/seed-gtk3 -I/usr/include/webkit-3.0 -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/libsoup-2.4 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/libxml2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o libephymain_la-ephy-window.lo `test -f 'ephy-window.c' || echo './'`ephy-window.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../lib -I../lib/egg -I../embed -I../embed -I../lib -I../lib/egg -I../lib/widgets -I../src/bookmarks -DEXTENSIONS_DIR=\/usr/lib/epiphany-browser/3.0/extensions\ -DLOADER_DIR=\/usr/lib/epiphany-browser/3.0/loaders\ -DDATADIR=\/usr/share/epiphany-browser\ -DGNOMELOCALEDIR=\/usr/share/locale\ -pthread -DGSEAL_ENABLE -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/gtk-3.0 -I/usr/include/cairo -I/usr/include/gtk-3.0/unix-print -I/usr/include/libxml2 -I/usr/include/startup-notification-1.0 -I/usr/include/webkit-3.0 -I/usr/include/libsoup-2.4 -I/usr/include/libsoup-gnome-2.4 -I/usr/include/gnome-keyring-1 -I/usr/include/gsettings-desktop-schemas -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/NetworkManager -pthread -DGSEAL_ENABLE -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/seed-gtk3 -I/usr/include/webkit-3.0 -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/libsoup-2.4 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/libxml2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c ephy-window.c -fPIC -DPIC -o .libs/libephymain_la-ephy-window.o ephy-window.c: In function 'construct_confirm_close_dialog': ephy-window.c:531:7: error: format not a string literal and no format arguments [-Werror=format-security] ephy-window.c:534:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[5]: *** [libephymain_la-ephy-window.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/epiphany-browser_3.0.4-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/msg1.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.
Bug#643377: flac: FTBFS: main.c:118:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: flac Version: 1.2.1-5 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../../.. -DFLaC__INLINE=__inline__ -DNDEBUG -I../../.. -I./include -I../../../include -O3 -funroll-loops -finline-functions -Wall -W -Winline -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -c main.c main.c: In function 'main': main.c:118:3: error: format not a string literal and no format arguments [-Werror=format-security] main.c:123:3: error: format not a string literal and no format arguments [-Werror=format-security] main.c:132:4: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[5]: *** [main.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/flac_1.2.1-5_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643378: fltk1.1: FTBFS: Fl_File_Chooser2.cxx:572:35: error: format not a string literal and no format arguments [-Werror=format-security]
Source: fltk1.1 Version: 1.1.10-7 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: g++ -I.. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Wunused -Wno-format-y2k -fPIC -fno-strict-aliasing -D_THREAD_SAFE -D_REENTRANT -I/usr/include/freetype2 -I/usr/include/freetype2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -c Fl_File_Chooser2.cxx Fl_File_Chooser2.cxx: In member function 'void Fl_File_Chooser::fileNameCB()': Fl_File_Chooser2.cxx:572:35: error: format not a string literal and no format arguments [-Werror=format-security] Fl_File_Chooser2.cxx: In member function 'void Fl_File_Chooser::newdir()': Fl_File_Chooser2.cxx:760:48: error: format not a string literal and no format arguments [-Werror=format-security] Fl_File_Chooser2.cxx: In member function 'void Fl_File_Chooser::showChoiceCB()': Fl_File_Chooser2.cxx:931:55: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[3]: *** [Fl_File_Chooser2.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/fltk1.1_1.1.10-7_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643379: fqterm: FTBFS: fqterm_mini_server.cpp:54:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: fqterm Version: 0.9.6.8-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: make[3]: Entering directory `/build/fqterm-TT4DhJ/fqterm-0.9.6.8/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /build/fqterm-TT4DhJ/fqterm-0.9.6.8/obj-x86_64-linux-gnu/CMakeFiles 92 [ 11%] Building CXX object src/unite/CMakeFiles/fqterm_unite.dir/fqterm_mini_server.o cd /build/fqterm-TT4DhJ/fqterm-0.9.6.8/obj-x86_64-linux-gnu/src/unite /usr/bin/g++ -DQT_DLL -DQT_GUI_LIB -DQT_CORE_LIB -DAUDIO_OSS -D_OS_LINUX_ -DQT_NO_DEBUG -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Os -DNDEBUG -I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/internal -I/build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/../common -I/build/fqterm-TT4DhJ/fqterm-0.9.6.8/obj-x86_64-linux-gnu/src/unite-Wall -D FQTERM_VERSION_STRING=\0.9.6\ -o CMakeFiles/fqterm_unite.dir/fqterm_mini_server.o -c /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp: In member function 'virtual void FQTerm::FQTermMiniServer::incomingConnection(int)': /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:54:3: error: format not a string literal and no format arguments [-Werror=format-security] /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp: In constructor 'FQTerm::FQTermUniteSession::FQTermUniteSession(int)': /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:65:3: error: format not a string literal and no format arguments [-Werror=format-security] /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:67:3: error: format not a string literal and no format arguments [-Werror=format-security] /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:69:3: error: format not a string literal and no format arguments [-Werror=format-security] /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:71:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[3]: *** [src/unite/CMakeFiles/fqterm_unite.dir/fqterm_mini_server.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/fqterm_0.9.6.8-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643380: gconf-cleaner: FTBFS: main.c:84:15: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gconf-cleaner Version: 0.0.3-4 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.. -DG_LOG_DOMAIN=\GConf-Cleaner\ -pthread -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c main.c main.c: In function '_gconf_cleaner_error_dialog': main.c:84:15: error: format not a string literal and no format arguments [-Werror=format-security] main.c:87:8: error: format not a string literal and no format arguments [-Werror=format-security] main.c: In function '_gconf_cleaner_question_dialog': main.c:123:15: error: format not a string literal and no format arguments [-Werror=format-security] main.c:127:8: error: format not a string literal and no format arguments [-Werror=format-security] main.c:136:11: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] cc1: some warnings being treated as errors make[3]: *** [main.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gconf-cleaner_0.0.3-4_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643381: gems: FTBFS: source/log.c:135:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gems Version: 1.1.1-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 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -DLOCALEDIR=\//usr/local/share/locale\ -I../common/ -Isource/ -c source/log.c -o bin/log.o source/log.c: In function 'g_log': source/log.c:135:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[2]: *** [bin/log.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gems_1.1.1-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643382: geomview: FTBFS: mgrib.c:163:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: geomview Version: 1.9.4-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../../../../include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c mgrib.c -fPIC -DPIC -o .libs/mgrib.o In file included from ../../../../include/point.h:28:0, from ../../../../include/mg.h:33, from mgrib.c:32: ../../../../include/hpoint3.h: In function 'HPt3TransPt3': ../../../../include/hpoint3.h:280:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] mgrib.c: In function 'mgrib_ctxcreate': mgrib.c:163:3: error: format not a string literal and no format arguments [-Werror=format-security] mgrib.c:164:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[6]: *** [mgrib.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/geomview_1.9.4-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643383: gfan: FTBFS: application.cpp:548:22: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gfan Version: 0.3dfsg-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: g++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -DGMPRATIONAL -I/usr/include/cdd -c application.cpp application.cpp: In function 'char* tail(char*)': application.cpp:32:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] application.cpp: In member function 'virtual char* DocumentationApplication::name()': application.cpp:156:12: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] application.cpp: In member function 'virtual char* InstallationApplication::name()': application.cpp:189:12: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] application.cpp: In member function 'virtual int InstallationApplication::main()': application.cpp:193:94: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] application.cpp: In constructor 'Application::Option::Option()': application.cpp:207:8: warning: unused variable 'hidden' [-Wunused-variable] application.cpp: In member function 'virtual void Application::printHelp()': application.cpp:509:16: warning: unused variable 'p' [-Wunused-variable] application.cpp: In static member function 'static void Application::makeSymbolicLinks(char*, bool, const char*)': application.cpp:548:22: error: format not a string literal and no format arguments [-Werror=format-security] application.cpp:549:15: warning: ignoring return value of 'int system(const char*)', declared with attribute warn_unused_result [-Wunused-result] cc1plus: some warnings being treated as errors make[1]: *** [application.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gfan_0.3dfsg-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643384: gfccore: FTBFS: error.cc:116:52: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gfccore Version: 2.3.1-7 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: g++ -DHAVE_CONFIG_H -I. -I. -I../.. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c error.cc -fPIC -DPIC -o .libs/error.o error.cc: In member function 'void GFC::G::Error::set(GQuark, int, const GFC::String)': error.cc:116:52: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[5]: *** [error.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gfccore_2.3.1-7_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643385: ggz-gtk-games: FTBFS: ggz_gtk.c:76:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: ggz-gtk-games Version: 0.0.14.1-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.. -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I /usr/include -I /usr/include -I /usr/include -I /usr/local/include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -fsigned-char -c ggz_gtk.c ggz_gtk.c: In function 'init_ggz_gtk': ggz_gtk.c:76:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[4]: *** [ggz_gtk.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/ggz-gtk-games_0.0.14.1-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643386: ghex: FTBFS: ui.c:920:4: error: format not a string literal and no format arguments [-Werror=format-security]
Source: ghex Version: 2.24.0-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.. -DGNOMEICONDIR=\/usr/share/pixmaps\ -DGNOMELOCALEDIR=\/usr/share/locale\ -DLOCALEDIR=\/usr/share/locale\ -DDATADIR=\/usr/share\ -DPREFIX=\/usr\ -pthread -DORBIT2=1 -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gail-1.0 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/libgnomeprintui-2.2 -I/usr/include/libgnomeprint-2.2 -pthread -I/usr/include/gail-1.0 -I/usr/include/atk-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c ui.c ui.c: In function 'about_response_cb': ui.c:239:4: warning: passing argument 1 of 'gtk_widget_destroy' from incompatible pointer type [enabled by default] /usr/include/gtk-2.0/gtk/gtkwidget.h:837:9: note: expected 'struct GtkWidget *' but argument is of type 'struct GtkDialog *' ui.c: In function 'ghex_print_run_dialog': ui.c:864:9: warning: pointer targets in passing argument 2 of 'gnome_print_dialog_new' differ in signedness [-Wpointer-sign] /usr/include/libgnomeprintui-2.2/libgnomeprintui/gnome-print-dialog.h:92:13: note: expected 'const guchar *' but argument is of type 'const char *' ui.c:875:4: warning: pointer targets in passing argument 5 of 'gnome_print_dialog_construct_range_page' differ in signedness [-Wpointer-sign] /usr/include/libgnomeprintui-2.2/libgnomeprintui/gnome-print-dialog.h:100:6: note: expected 'const guchar *' but argument is of type 'char *' ui.c:875:4: warning: pointer targets in passing argument 6 of 'gnome_print_dialog_construct_range_page' differ in signedness [-Wpointer-sign] /usr/include/libgnomeprintui-2.2/libgnomeprintui/gnome-print-dialog.h:100:6: note: expected 'const guchar *' but argument is of type 'char *' ui.c: In function 'ghex_print_preview_real': ui.c:902:2: warning: pointer targets in passing argument 2 of 'gnome_print_job_preview_new' differ in signedness [-Wpointer-sign] /usr/include/libgnomeprintui-2.2/libgnomeprintui/gnome-print-job-preview.h:48:13: note: expected 'const guchar *' but argument is of type 'gchar *' ui.c: In function 'display_error_dialog': ui.c:920:4: error: format not a string literal and no format arguments [-Werror=format-security] ui.c: In function 'display_info_dialog': ui.c:945:4: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[4]: *** [ui.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/ghex_2.24.0-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643387: gimp-gap: FTBFS: gap_arr_dialog.c:1862:10: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gimp-gap Version: 2.6.0+dfsg-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.. -I../libwavplayclient -I../libgapbase -I../libgapvidapi -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gimp-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include -DGAPLIBDIR=\/usr/lib/gimp-gap-2.6\ -DLOCALEDIR=\/usr/share/locale\ -DGIMP_DISABLE_DEPRECATED -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -fPIC -c gap_arr_dialog.c gap_arr_dialog.c: In function 'gap_arr_msg_win': gap_arr_dialog.c:1862:10: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [gap_arr_dialog.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gimp-gap_2.6.0+dfsg-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643388: gimp: FTBFS: gimpconfigwriter.c:571:22: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gimp Version: 2.6.11-3 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: /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/build/gimp-O1jlIz/gimp-2.6.11/./libgimpconfig -I.. -I/build/gimp-O1jlIz/gimp-2.6.11/. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include -DG_LOG_DOMAIN=\LibGimpConfig\ -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -c -o gimpconfigwriter.lo /build/gimp-O1jlIz/gimp-2.6.11/./libgimpconfig/gimpconfigwriter.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/build/gimp-O1jlIz/gimp-2.6.11/./libgimpconfig -I.. -I/build/gimp-O1jlIz/gimp-2.6.11/. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include -DG_LOG_DOMAIN=\LibGimpConfig\ -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -c /build/gimp-O1jlIz/gimp-2.6.11/./libgimpconfig/gimpconfigwriter.c -fPIC -DPIC -o .libs/gimpconfigwriter.o /build/gimp-O1jlIz/gimp-2.6.11/./libgimpconfig/gimpconfigwriter.c: In function 'gimp_config_writer_linefeed': /build/gimp-O1jlIz/gimp-2.6.11/./libgimpconfig/gimpconfigwriter.c:571:22: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [gimpconfigwriter.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gimp_2.6.11-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643389: gksu: FTBFS: gksu.c:151:8: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gksu Version: 2.0.2-5 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.. -DORBIT2=1 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libgksu -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/startup-notification-1.0 -I/usr/include/gnome-keyring-1 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -DLOCALEDIR=\/usr/share/locale\ -DDATA_DIR=\/usr/share\ -DPREFIX=\/usr\ -g -O2 -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c gksu.c gksu.c: In function 'gk_dialog': gksu.c:151:8: error: format not a string literal and no format arguments [-Werror=format-security] gksu.c: In function 'set_description_from_desktop': gksu.c:183:7: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [gksu.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gksu_2.0.2-5_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643391: gnome-launch-box: FTBFS: search-applications.c:34:2: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gnome-launch-box Version: 0.2-1.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.. -I.. -DMENU_I_KNOW_THIS_IS_UNSTABLE -pthread -DORBIT2=1 -D_REENTRANT -DCAMEL_HAVE_NSS -DCAMEL_HAVE_SSL -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gail-1.0 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/gnome-menus -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/evolution-data-server-3.0 -I/usr/include/libsoup-2.4 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c search-applications.c search-applications.c: In function 'applications_add_directory': search-applications.c:34:2: error: format not a string literal and no format arguments [-Werror=format-security] search-applications.c:42:3: warning: passing argument 1 of 'gmenu_tree_item_get_type' from incompatible pointer type [enabled by default] /usr/include/gnome-menus/gmenu-tree.h:107:21: note: expected 'struct GMenuTreeItem *' but argument is of type 'struct GMenuTreeDirectory *' search-applications.c:47:3: warning: passing argument 1 of 'gmenu_tree_item_get_type' from incompatible pointer type [enabled by default] /usr/include/gnome-menus/gmenu-tree.h:107:21: note: expected 'struct GMenuTreeItem *' but argument is of type 'struct GMenuTreeDirectory *' cc1: some warnings being treated as errors make[3]: *** [search-applications.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gnome-launch-box_0.2-1.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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643390: glabels: FTBFS: plessey.c:151:9: error: format not a string literal and no format arguments [-Werror=format-security]
Source: glabels Version: 2.2.8-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: /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -pthread -DORBIT2=1 -D_REENTRANT -DCAMEL_HAVE_NSS -DCAMEL_HAVE_SSL -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gail-1.0 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libxml2 -I/usr/include/libglade-2.0 -I/usr/include/evolution-data-server-3.0 -I/usr/include/libsoup-2.4 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o plessey.lo plessey.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -pthread -DORBIT2=1 -D_REENTRANT -DCAMEL_HAVE_NSS -DCAMEL_HAVE_SSL -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gail-1.0 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libxml2 -I/usr/include/libglade-2.0 -I/usr/include/evolution-data-server-3.0 -I/usr/include/libsoup-2.4 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c plessey.c -fPIC -DPIC -o .libs/plessey.o plessey.c: In function 'Barcode_pls_verify': plessey.c:48:5: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness [-Wpointer-sign] /usr/include/string.h:399:15: note: expected 'const char *' but argument is of type 'unsigned char *' plessey.c: In function 'Barcode_pls_encode': plessey.c:151:9: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [plessey.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/glabels_2.2.8-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643392: gnome-netstatus: FTBFS: netstatus-iface.c:418:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gnome-netstatus Version: 2.28.1-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../src -DPREFIX=\/usr\ -DSYSCONFDIR=\/etc\ -DDATADIR=\/usr/share\ -DLIBDIR=\/usr/lib\ -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gail-1.0 -I/usr/include/panel-2.0 -I/usr/include/gconf/2 -I/usr/include/libbonoboui-2.0 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/libxml2 -I/usr/include/libbonobo-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libgnome-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libart-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include-Wall -Wmissing-prototypes -DNETSTATUS_ICONDIR=\/usr/share/icons/gnome-netstatus\ -DNETSTATUS_BUILDERDIR=\/usr/share/gnome-netstatus\ -DGNOMELOCALEDIR=\/usr/share/locale\-g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c netstatus-iface.c netstatus-iface.c: In function 'netstatus_iface_set_polling_error': netstatus-iface.c:418:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[4]: *** [netstatus-iface.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gnome-netstatus_2.28.1-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643393: gnome-scan: FTBFS: gnome-scan-dialog.c:565:13: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gnome-scan Version: 0.6.2-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: /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\/usr/share/locale\ -DICON_DIR=\/usr/share/gnome-scan/icons\ -pthread -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/atk-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/gegl-0.0 -I/usr/include/babl-0.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -DMODULE_DIR=\/usr/lib/gnome-scan-1.0\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o libgnomescan_la-gnome-scan-dialog.lo `test -f 'gnome-scan-dialog.c' || echo './'`gnome-scan-dialog.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\/usr/share/locale\ -DICON_DIR=\/usr/share/gnome-scan/icons\ -pthread -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/atk-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/gegl-0.0 -I/usr/include/babl-0.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -DMODULE_DIR=\/usr/lib/gnome-scan-1.0\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c gnome-scan-dialog.c -fPIC -DPIC -o .libs/libgnomescan_la-gnome-scan-dialog.o gnome-scan-dialog.c: In function 'gnome_scan_dialog_dispose': gnome-scan-dialog.c:347:3: warning: suggest parentheses around assignment used as truth value [-Wparentheses] gnome-scan-dialog.c:361:3: warning: suggest parentheses around assignment used as truth value [-Wparentheses] gnome-scan-dialog.c: In function 'gsd_message_dialog': gnome-scan-dialog.c:565:13: error: format not a string literal and no format arguments [-Werror=format-security] gnome-scan-dialog.c:567:14: error: format not a string literal and no format arguments [-Werror=format-security] gnome-scan-dialog.c: In function 'gsd_build_group_box': gnome-scan-dialog.c:638:3: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c:638:3: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] gnome-scan-dialog.c:692:2: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c:692:2: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] gnome-scan-dialog.c:581:62: warning: unused variable 'eventbox' [-Wunused-variable] gnome-scan-dialog.c: In function 'gsd_show_hide_param_widget': gnome-scan-dialog.c:722:2: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c:722:2: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] gnome-scan-dialog.c:723:16: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c:735:2: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c:735:2: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] gnome-scan-dialog.c:736:10: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c: In function 'gsd_destroy_param': gnome-scan-dialog.c:767:3: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c:767:3: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] gnome-scan-dialog.c:771:16: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c:773:3: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c:773:3: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] gnome-scan-dialog.c:777:10: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c: In function 'gsd_load_backends': gnome-scan-dialog.c:799:11: warning: variable 'thread' set but not used [-Wunused-but-set-variable] gnome-scan-dialog.c: In function 'gsd_build_sink_ui': gnome-scan-dialog.c:1047:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] gnome-scan-dialog.c: In
Bug#643394: gnotime: FTBFS: dialog.c:42:12: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gnotime Version: 2.3.1~snapshot20091119-3 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/usr/include/qof -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include-I/usr/include -DGNOMELOCALEDIR=\/usr/share/locale\ -DGTTGLADEDIR=\/usr/share/gnotime\ -DPREFIX=\/usr\ -DSYSCONFDIR=\/etc/gnotime\ -DGTTDATADIR=\/usr/share/gnotime\ -DDATADIR=\/usr/share\ -DLIBDIR=\/usr/lib/gnotime\ -DWITH_DBUS=1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DORBIT2=1 -D_REENTRANT -pthread -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DORBIT2=1 -D_REENTRANT -pthread -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -DORBIT2=1 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libgtkhtml-3.14 -I/usr/include/enchant -I/usr/include/gconf/2 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1
Bug#643395: gnubik: FTBFS: src/menus.c:552:8: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gnubik Version: 2.4-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. -DLOCALEDIR=\/usr/share/locale\ -DPKGICONDIR=\/usr/share/gnubik/icons\ -DGUILEDIR=\/usr/share/gnubik\ -DSCRIPTDIR=\/usr/share/gnubik/scripts\ -Wall -Wwrite-strings -Wpointer-arith -Wno-sign-compare -Wmissing-prototypes -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -pthread -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/atk-1.0 -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include-DGDK_MULTIHEAD_SAFE=1 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o src/src_gnubik-menus.o `test -f 'src/menus.c' || echo './'`src/menus.c src/menus.c: In function 'error_dialog': src/menus.c:552:8: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [src/src_gnubik-menus.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gnubik_2.4-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643396: gnudoq: FTBFS: sudoku.C:51:13: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gnudoq Version: 0.94-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: g++ -c -m64 -pipe -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -D_REENTRANT -Wall -W -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -I. -o sudoku.o sudoku.C sudoku.C: In static member function 'static int sudoku::Sudoku::pint(const sudoku::Sudoku::attempt*, const char*)': sudoku.C:51:13: error: format not a string literal and no format arguments [-Werror=format-security] sudoku.C:52:16: error: format not a string literal and no format arguments [-Werror=format-security] sudoku.C:58:37: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[1]: *** [sudoku.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gnudoq_0.94-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643400: grace: FTBFS: utils.c:1174:9: error: format not a string literal and no format arguments [-Werror=format-security]
Source: grace Version: 1:5.1.22-11 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 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -I.. -I. -c -o utils.o utils.c utils.c: In function 'stufftext': utils.c:1174:9: error: format not a string literal and no format arguments [-Werror=format-security] utils.c:1179:2: error: format not a string literal and no format arguments [-Werror=format-security] utils.c: In function 'set_workingdir': utils.c:1225:15: warning: ignoring return value of 'getcwd', declared with attribute warn_unused_result [-Wunused-result] cc1: some warnings being treated as errors make[2]: *** [utils.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/grace_1:5.1.22-11_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643402: gtetrinet: FTBFS: tetrinet.c:235:46: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gtetrinet Version: 0.7.11-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.. -DLOCALEDIR=\/usr/share/locale\ -DPIXMAPSDIR=\/usr/share/pixmaps\ -DGTETPIXMAPSDIR=\/usr/share/pixmaps/gtetrinet\ -pthread -DORBIT2=1 -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gail-1.0 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libxml2 -DGTETRINET_DATA=\/usr/share/gtetrinet\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c tetrinet.c tetrinet.c: In function 'tetrinet_inmessage': tetrinet.c:235:46: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[4]: *** [tetrinet.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gtetrinet_0.7.11-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643403: gtodo: FTBFS: callback.c:133:4: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gtodo Version: 0.16.0~rc2-1.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 -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\gtodo\ -DVERSION=\0.16.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_TIME_H=1 -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -DGETTEXT_PACKAGE=\gtodo\ -I. -I. -pthread -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/libxml2 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -DPIXMAP_PATH=\/usr/share/pixmaps/\ -DLOCALEDIR=\/usr/share/locale/\ -DDATADIR=\/usr/share\ -Ilibgtodo/ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c `test -f 'callback.c' || echo './'`callback.c callback.c: In function 'message_box': callback.c:133:4: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[2]: *** [callback.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gtodo_0.16.0~rc2-1.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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643404: gyrus: FTBFS: gyrus-admin.c:1474:4: error: format not a string literal and no format arguments [-Werror=format-security]
Source: gyrus Version: 0.3.10-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.. -DGYRUS_DATA_DIR=\/usr/share\ -DGYRUS_UI_DIR=\/usr/share/gyrus/ui\ -DGYRUS_PIXMAPS_DIR=\/usr/share/gyrus/pixmaps\ -DGNOME_LOCALE_DIR=\/usr/share/locale\ -pthread -DORBIT2=1 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -Wall-g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c gyrus-admin.c gyrus-admin.c: In function 'gyrus_admin_listen_channel': gyrus-admin.c:734:10: warning: variable 'error' set but not used [-Wunused-but-set-variable] gyrus-admin.c: In function 'gyrus_admin_write_channel': gyrus-admin.c:786:8: warning: variable 'bytes_written' set but not used [-Wunused-but-set-variable] gyrus-admin.c: In function 'gyrus_admin_on_acl_identifier_edited': gyrus-admin.c:1474:4: error: format not a string literal and no format arguments [-Werror=format-security] gyrus-admin.c:1478:4: error: format not a string literal and no format arguments [-Werror=format-security] gyrus-admin.c:1489:4: error: format not a string literal and no format arguments [-Werror=format-security] gyrus-admin.c:1494:4: error: format not a string literal and no format arguments [-Werror=format-security] gyrus-admin.c:1498:4: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[5]: *** [gyrus-admin.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gyrus_0.3.10-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643405: hdate-applet: FTBFS: callbacks.c:360:2: error: format not a string literal and no format arguments [-Werror=format-security]
Source: hdate-applet Version: 0.15.11-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.. -DPIXMAP_DIR=\/usr/share/pixmaps/hdate-applet\ -DPACKAGE_DATA_DIR=\/usr/share\ -DPACKAGE_LOCALE_DIR=\/usr/share/locale\ -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/panel-2.0 -pthread -DORBIT2=1 -I/usr/include/evolution-data-server-3.0 -I/usr/include/ -I/usr/include/libxml2 -I/usr/include/gconf/2 -I/usr/include/libsoup-2.4 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c callbacks.c callbacks.c: In function 'copy_date_cb': callbacks.c:360:2: error: format not a string literal and no format arguments [-Werror=format-security] callbacks.c: In function 'copy_en_date_cb': callbacks.c:382:2: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [callbacks.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/hdate-applet_0.15.11-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643406: hydrogen: FTBFS: libs/hydrogen/src/object.cpp:242:30: error: format not a string literal and no format arguments [-Werror=format-security]
Source: hydrogen Version: 0.9.5-3 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: g++ -o libs/hydrogen/src/object.o -c -O3 -fomit-frame-pointer -funroll-loops -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -DOSS_SUPPORT -DALSA_SUPPORT -DJACK_SUPPORT -DLRDF_SUPPORT -DPORTAUDIO_SUPPORT -DPORTMIDI_SUPPORT -DLADSPA_SUPPORT -DLIBARCHIVE_SUPPORT -DQT_CORE_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_SHARED -I. -Igui/src -I3rdparty/install/include -Ilibs/hydrogen/include -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml libs/hydrogen/src/object.cpp libs/hydrogen/src/object.cpp: In function 'void* loggerThread_func(void*)': libs/hydrogen/src/object.cpp:242:30: error: format not a string literal and no format arguments [-Werror=format-security] libs/hydrogen/src/object.cpp:244:42: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors scons: *** [libs/hydrogen/src/object.o] Error 1 scons: building terminated because of errors. make: *** [debian/stamp-scons-build] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/hydrogen_0.9.5-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643407: infernal: FTBFS: esl_getopts.c:1273:2: error: format not a string literal and no format arguments [-Werror=format-security]
Source: infernal Version: 1.0.2-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 -std=gnu99 -I. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -msse2 -c esl_getopts.c esl_getopts.c: In function 'esl_getopts_Create': esl_getopts.c:70:7: warning: variable 'status' set but not used [-Wunused-but-set-variable] esl_getopts.c: In function 'process_stdopt': esl_getopts.c:1273:2: error: format not a string literal and no format arguments [-Werror=format-security] esl_getopts.c:1273:2: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[2]: *** [esl_getopts.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/infernal_1.0.2-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643408: iperf: FTBFS: Thread.c:384:9: error: format not a string literal and no format arguments [-Werror=format-security]
Source: iperf Version: 2.0.5-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../include -I../include -Wall -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c Thread.c Thread.c: In function 'thread_release_nonterm': Thread.c:384:9: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [Thread.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/iperf_2.0.5-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643409: ippl: FTBFS: log.c:150:5: error: format not a string literal and no format arguments [-Werror=format-security]
Source: ippl Version: 1.4.14-12 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 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Wall -DVERSION=\1.4.14\ -DDEFAULT_USER=\Debian-ippl\ -DCONFIGURATION_FILE=\/etc/ippl.conf\ -DPID_FILE=\/var/run/ippl/ippl.pid\ -c log.c log.c:35:23: warning: built-in function 'log' declared as non-function [enabled by default] log.c: In function 'log_entry': log.c:150:5: error: format not a string literal and no format arguments [-Werror=format-security] log.c:150:5: error: format not a string literal and no format arguments [-Werror=format-security] log.c:158:3: error: format not a string literal and no format arguments [-Werror=format-security] log.c:158:3: error: format not a string literal and no format arguments [-Werror=format-security] log.c:152:10: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] log.c:153:10: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] log.c:154:10: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] log.c:159:8: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] log.c:160:8: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] log.c:161:8: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] log.c:162:8: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] cc1: some warnings being treated as errors make[2]: *** [log.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/ippl_1.4.14-12_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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643410: ircd-ratbox: FTBFS: parse.c:714:2: error: format not a string literal and no format arguments [-Werror=format-security]
Source: ircd-ratbox Version: 3.0.6.dfsg-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: /bin/bash ../libtool --silent --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I../libratbox/include -Wall -Wcast-qual -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wshadow -Wwrite-strings -Wno-unused -Wunused-function -Wunused-variable -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -fstack-protector -fno-strict-aliasing -c -o parse.lo parse.c parse.c: In function 'parse': parse.c:265:6: warning: to be safe all intermediate pointers in cast from 'char **' to 'const char **' must be 'const' qualified [-Wcast-qual] parse.c: In function 'm_not_oper': parse.c:714:2: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [parse.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/ircd-ratbox_3.0.6.dfsg-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643411: italc: FTBFS: ./src/classroom_manager.cpp:437:30: error: format not a string literal and no format arguments [-Werror=format-security]
Source: italc Version: 1:1.0.13-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: g++ -DHAVE_CONFIG_H -I. -I.. -I./../lib/include -Isrc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -fPIC -I/usr/include -I/usr/include -I/usr/include/qt4 -I/usr/include/qt4/Qt -D_REENTRANT -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_XML_LIB -DQT_THREAD_SUPPORT -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -fPIC -I/usr/include -g -O2 -Wall -fPIC -c -o classroom_manager.o `test -f './src/classroom_manager.cpp' || echo './'`./src/classroom_manager.cpp ./src/classroom_manager.cpp: In member function 'void classroomManager::savePersonalConfig()': ./src/classroom_manager.cpp:437:30: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[4]: *** [classroom_manager.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/italc_1:1.0.13-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643412: jack-keyboard: FTBFS: jack-keyboard.c:261:2: error: format not a string literal and no format arguments [-Werror=format-security]
Source: jack-keyboard Version: 2.6-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: /usr/bin/cc -DHAVE_JACK=1 -DHAVE_X11=1 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -I/usr/include/gtk-2.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0-o CMakeFiles/jack-keyboard.dir/src/jack-keyboard.c.o -c /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c: In function 'warning_async': /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c:261:2: error: format not a string literal and no format arguments [-Werror=format-security] /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c: In function 'init_gtk_1': /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c:1545:3: warning: reading through null pointer (argument 3) [-Wformat] /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c: In function 'log_handler': /build/jack-keyboard-hYgQDt/jack-keyboard-2.6/src/jack-keyboard.c:1683:4: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[3]: *** [CMakeFiles/jack-keyboard.dir/src/jack-keyboard.c.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/jack-keyboard_2.6-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643413: jack-tools: FTBFS: jack.dl.c:20:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: jack-tools Version: 20101210-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 -DPACKAGE_NAME=\jack.\*\ -DPACKAGE_TARNAME=\jack--\ -DPACKAGE_VERSION=\0.5\ -DPACKAGE_STRING=\jack.\*\ 0.5\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\jack--\ -DVERSION=\0.5\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DHAVE_SYS_INOTIFY_H=1 -DHAVE_INOTIFY=1 -I. -D_POSIX_C_SOURCE=200112 -std=c99 -O3 -funroll-loops -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o jack_dl-jack.dl.o `test -f 'jack.dl.c' || echo './'`jack.dl.c jack.dl.c: In function 'fail': jack.dl.c:20:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[2]: *** [jack_dl-jack.dl.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/jack-tools_20101210-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643414: jfsutils: FTBFS: fscklog.c:255:2: error: format not a string literal and no format arguments [-Werror=format-security]
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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643415: juman: FTBFS: iotool.c:448:6: error: format not a string literal and no format arguments [-Werror=format-security]
Source: juman Version: 5.1-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.. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c iotool.c -fPIC -DPIC -o .libs/iotool.o iotool.c: In function 'getpath': iotool.c:136:6: warning: implicit declaration of function 'getcwd' [-Wimplicit-function-declaration] iotool.c:131:12: warning: unused variable 'env' [-Wunused-variable] iotool.c: In function 'my_strcpy': iotool.c:307:6: warning: pointer targets in passing argument 1 of 'strcpy' differ in signedness [-Wpointer-sign] /usr/include/x86_64-linux-gnu/bits/string3.h:103:1: note: expected 'char * __restrict__' but argument is of type 'unsigned char *' iotool.c:307:6: warning: pointer targets in passing argument 2 of 'strcpy' differ in signedness [-Wpointer-sign] /usr/include/x86_64-linux-gnu/bits/string3.h:103:1: note: expected 'const char * __restrict__' but argument is of type 'unsigned char *' iotool.c: In function 'my_strcmp': iotool.c:324:6: warning: pointer targets in passing argument 1 of '__builtin_strlen' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 1 of '__builtin_strlen' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 1 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 1 of '__builtin_strlen' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 1 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 1 of '__builtin_strlen' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 1 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 1 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:324:6: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] iotool.c:324:6: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c: In function 'compare_top_str1': iotool.c:356:6: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness [-Wpointer-sign] /usr/include/string.h:399:15: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:357:6: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness [-Wpointer-sign] /usr/include/string.h:399:15: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c: In function 'compare_top_str2': iotool.c:378:6: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness [-Wpointer-sign] /usr/include/string.h:399:15: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c:379:6: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness [-Wpointer-sign] /usr/include/string.h:399:15: note: expected 'const char *' but argument is of type 'unsigned char *' iotool.c: In function 'compare_end_str': iotool.c:400:6: warning: pointer targets in passing argument 1 of 'strlen' differ
Bug#643416: libalberta2: FTBFS: ../Common/write_mesh_gmv.c:339:3: error: format not a string literal and no format arguments [-Werror=format-security]
Source: libalberta2 Version: 2.0.1-3.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: /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DDIM_OF_WORLD=1 -DALBERTA_DEBUG=0 -I. -I../../.. -I./../0d -I./../1d -I./../2d -I./../3d -I./../Common -I../../../alberta_util/src -I../../../alberta_util/src/ -I/usr/include -Wall -O3 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c -o write_mesh_gmv.lo `test -f '../Common/write_mesh_gmv.c' || echo './'`../Common/write_mesh_gmv.c libtool: compile: gcc -DHAVE_CONFIG_H -DDIM_OF_WORLD=1 -DALBERTA_DEBUG=0 -I. -I../../.. -I./../0d -I./../1d -I./../2d -I./../3d -I./../Common -I../../../alberta_util/src -I../../../alberta_util/src/ -I/usr/include -Wall -O3 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c ../Common/write_mesh_gmv.c -fPIC -DPIC -o .libs/write_mesh_gmv.o ../Common/write_mesh_gmv.c: In function 'add_drv': ../Common/write_mesh_gmv.c:339:3: error: format not a string literal and no format arguments [-Werror=format-security] ../Common/write_mesh_gmv.c:339:3: error: format not a string literal and no format arguments [-Werror=format-security] ../Common/write_mesh_gmv.c: In function 'add_drdv': ../Common/write_mesh_gmv.c:465:5: error: format not a string literal and no format arguments [-Werror=format-security] ../Common/write_mesh_gmv.c:465:5: error: format not a string literal and no format arguments [-Werror=format-security] ../Common/write_mesh_gmv.c: In function 'add_refined_data': ../Common/write_mesh_gmv.c:945:7: error: format not a string literal and no format arguments [-Werror=format-security] ../Common/write_mesh_gmv.c:945:7: error: format not a string literal and no format arguments [-Werror=format-security] ../Common/write_mesh_gmv.c:986:7: error: format not a string literal and no format arguments [-Werror=format-security] ../Common/write_mesh_gmv.c:986:7: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[5]: *** [write_mesh_gmv.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/libalberta2_2.0.1-3.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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643417: libccscript3: FTBFS: compiler.cpp:1147:38: error: format not a string literal and no format arguments [-Werror=format-security]
Source: libccscript3 Version: 1.1.7-1.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: g++ -DHAVE_CONFIG_H -I. -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -D_GNU_SOURCE -c compiler.cpp -fPIC -DPIC -o .libs/compiler.o compiler.cpp: In member function 'char* ost::ScriptCompiler::getToken(char**)': compiler.cpp:198:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:289:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:319:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:321:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:323:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:325:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:327:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:329:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:331:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:333:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp: In member function 'int ost::ScriptCompiler::compileDefinitions(const char*)': compiler.cpp:499:62: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp: In member function 'int ost::ScriptCompiler::compile(std::istream*, char*, const char*)': compiler.cpp:819:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:934:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:935:14: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:956:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:961:14: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:962:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:968:14: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:969:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:974:14: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:975:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:980:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:985:14: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:997:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:998:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1004:14: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1006:14: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1012:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1020:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1033:13: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1094:12: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1133:11: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1147:38: error: format not a string literal and no format arguments [-Werror=format-security] compiler.cpp:1147:38: error: format not a string literal and no format arguments [-Werror=format-security] compiler.cpp:1169:15: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1206:12: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1211:12: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1216:12: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1221:12: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] compiler.cpp:1226:12: warning: deprecated conversion from
Bug#643418: libcgns: FTBFS: cgnslib.c:5341:17: error: format not a string literal and no format arguments [-Werror=format-security]
Source: libcgns Version: 2.5.5-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: cc -g -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -fPIC -I. -Iadfh -o LINUX64/cgnslib.o -c cgnslib.c cgnslib.c: In function 'cg_hole_write': cgnslib.c:5341:17: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[1]: *** [LINUX64/cgnslib.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/libcgns_2.5.5-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/msg1.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 debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
