Your message dated Tue, 1 Nov 2011 09:19:26 +0100
with message-id
<CAPdtAj10T4JF6mAQy90yD00meLHJE62B-JSdVqqKgNxzX=u...@mail.gmail.com>
and subject line Re: Bug#625423: Still able to build..
has caused the Debian Bug report #625423,
regarding sitecopy: ftbfs with gcc-4.6 -Werror
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
625423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625423
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sitecopy
Version: 1:0.16.6-3
Severity: important
Tags: wheezy sid
User: [email protected]
Usertags: ftbfs-gcc-4.6 ftbfs-werror
This package builds with -Werror, and GCC 4.6 triggers new warnings
which will make the package fail to build. Currently a Debian patch
just passes
-Wno-error=unused-but-set-variable and
-Wno-error=unused-but-set-parameter
to avoid build failures, but this patch will be reverted with the
GCC 4.6.1 release, and the severity of the report will be raised.
The full build log can be found at:
http://people.debian.org/~doko/tmp/werror/sitecopy_1:0.16.6-3_lsid64.buildlog
The last lines of the build log are at the end of this report.
--- End Message ---
--- Begin Message ---
On Tue, Nov 1, 2011 at 02:44, peter green
<[email protected]> wrote:
>>There are two -Wunused-but-set-variable warnings but the build
>>doesn't fail ...
> That is because the files in question are NOT built with -Werror. Indeed the
> only mention of -Werror in doko's build log is in the output of a configure
> check.
>
> Based on looking at a number of these bugs it would appear that doko
> searched his build logs for "-Werror" and for the warning names and
> submitted bug reports for any that hit on both searches without actually
> reading the logs to determine if the two hits were on the same gcc
> invocation.
Surprise, doko being clueless....
> If I were you I would just close this bug (indeed I was tempted to do so
> myself) but since there seems to be activity on this bug from people who
> care about the package I thought I'd leave it to them.
Thanks to all the people that worked on this bug, I indeed am able to
still build sitecopy, hence closing this report.
Cheers.
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
