Bug#925816: marked as done (qxw: ftbfs with GCC-9)
Your message dated Sat, 28 Mar 2020 00:34:39 + with message-id <20200328003439.gk5...@tack.einval.com> and subject line Re: Bug#925816: marked as done (qxw: ftbfs with GCC-9) has caused the Debian Bug report #925816, regarding qxw: ftbfs with GCC-9 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.) -- 925816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qxw Version: 20140331-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/qxw_20140331-1_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] | ^~~~ gui.c:2072:94: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2072 | else strcpy (s," Mean length: -"); gtk_label_set_text(GTK_LABEL(st_r[1]),s); | ^~ gui.c:2074:3: warning: this 'else' clause does not guard... [-Wmisleading-indentation] 2074 | else strcpy (s," Checked light letters: -"); gtk_label_set_text(GTK_LABEL(st_r[2]),s); | ^~~~ gui.c:2074:95: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2074 | else strcpy (s," Checked light letters: -"); gtk_label_set_text(GTK_LABEL(st_r[2]),s); | ^~ gui.c:2076:3: warning: this 'else' clause does not guard... [-Wmisleading-indentation] 2076 | else strcpy (s," Checked grid cells: -"); gtk_label_set_text(GTK_LABEL(st_r[3]),s); | ^~~~ gui.c:2076:95: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2076 | else strcpy (s," Checked grid cells: -"); gtk_label_set_text(GTK_LABEL(st_r[3]),s); | ^~ gui.c: In function 'updatefeas': gui.c:2241:45: warning: '%s' directive writing up to 999 bytes into a region of size between 978 and 979 [-Wformat-overflow=] 2241 | else sprintf(p1," Feasible character%s: %s",(strlen(p0)==1)?"":"s",p0); | ^~ ~~ gui.c:2241:10: note: 'sprintf' output between 22 and 1022 bytes into a destination of size 1000 2241 | else sprintf(p1," Feasible character%s: %s",(strlen(p0)==1)?"":"s",p0); | ^ gcc -Wall -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security `pkg-config --cflags glib-2.0` `pkg-config --cflags gtk+-2.0` -I/opt/local/include -O9 -c draw.c -o draw.o draw.c: In function 'draw_finit': draw.c:460:3: warning: this 'if' clause does not g
Processed: Re: Bug#925816: marked as done (qxw: ftbfs with GCC-9)
Processing control commands:
> reopen 925816
Bug #925816 [src:qxw] qxw: ftbfs with GCC-9
Bug 925816 is not marked as done; doing nothing.
> close 925826 15+1533136590.3beb971-8
Bug #925826 {Done: Steve McIntyre } [src:shim] shim: ftbfs
with GCC-9
The source 'shim' and version '15+1533136590.3beb971-8' do not appear to match
any binary packages
Ignoring request to alter fixed versions of bug #925826 to the same values
previously set
Bug #925826 {Done: Steve McIntyre } [src:shim] shim: ftbfs
with GCC-9
Bug 925826 is already marked as done; not doing anything.
--
925816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925816
925826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#925816: marked as done (qxw: ftbfs with GCC-9)
Processing control commands:
> reopen 925816
Bug #925816 {Done: Steve McIntyre <93...@debian.org>} [src:qxw] qxw: ftbfs with
GCC-9
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions qxw/20140331-1.1 and
shim/15+1533136590.3beb971-8.
> close 925826 15+1533136590.3beb971-8
Bug #925826 [src:shim] shim: ftbfs with GCC-9
The source 'shim' and version '15+1533136590.3beb971-8' do not appear to match
any binary packages
Marked as fixed in versions shim/15+1533136590.3beb971-8.
Bug #925826 [src:shim] shim: ftbfs with GCC-9
Marked Bug as done
--
925816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925816
925826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#925816: marked as done (qxw: ftbfs with GCC-9)
Your message dated Tue, 24 Mar 2020 18:19:58 + with message-id and subject line Bug#925816: fixed in shim 15+1533136590.3beb971-8 has caused the Debian Bug report #925816, regarding qxw: ftbfs with GCC-9 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.) -- 925816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qxw Version: 20140331-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/qxw_20140331-1_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] | ^~~~ gui.c:2072:94: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2072 | else strcpy (s," Mean length: -"); gtk_label_set_text(GTK_LABEL(st_r[1]),s); | ^~ gui.c:2074:3: warning: this 'else' clause does not guard... [-Wmisleading-indentation] 2074 | else strcpy (s," Checked light letters: -"); gtk_label_set_text(GTK_LABEL(st_r[2]),s); | ^~~~ gui.c:2074:95: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2074 | else strcpy (s," Checked light letters: -"); gtk_label_set_text(GTK_LABEL(st_r[2]),s); | ^~ gui.c:2076:3: warning: this 'else' clause does not guard... [-Wmisleading-indentation] 2076 | else strcpy (s," Checked grid cells: -"); gtk_label_set_text(GTK_LABEL(st_r[3]),s); | ^~~~ gui.c:2076:95: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2076 | else strcpy (s," Checked grid cells: -"); gtk_label_set_text(GTK_LABEL(st_r[3]),s); | ^~ gui.c: In function 'updatefeas': gui.c:2241:45: warning: '%s' directive writing up to 999 bytes into a region of size between 978 and 979 [-Wformat-overflow=] 2241 | else sprintf(p1," Feasible character%s: %s",(strlen(p0)==1)?"":"s",p0); | ^~ ~~ gui.c:2241:10: note: 'sprintf' output between 22 and 1022 bytes into a destination of size 1000 2241 | else sprintf(p1," Feasible character%s: %s",(strlen(p0)==1)?"":"s",p0); | ^ gcc -Wall -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security `pkg-config --cflags glib-2.0` `pkg-config --cflags gtk+-2.0` -I/opt/local/include -O9 -c draw.c -o draw.o draw.c: In function 'draw_finit': draw.c:460:3: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 460 | if(sfb) cairo_surface_destroy(sfb); sfb=0; | ^~ draw.c:460:40: note: ...this statement, but the latter is
Bug#925816: marked as done (qxw: ftbfs with GCC-9)
Your message dated Tue, 17 Mar 2020 17:34:08 + with message-id and subject line Bug#925816: fixed in qxw 20140331-1.1 has caused the Debian Bug report #925816, regarding qxw: ftbfs with GCC-9 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.) -- 925816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qxw Version: 20140331-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/qxw_20140331-1_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] | ^~~~ gui.c:2072:94: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2072 | else strcpy (s," Mean length: -"); gtk_label_set_text(GTK_LABEL(st_r[1]),s); | ^~ gui.c:2074:3: warning: this 'else' clause does not guard... [-Wmisleading-indentation] 2074 | else strcpy (s," Checked light letters: -"); gtk_label_set_text(GTK_LABEL(st_r[2]),s); | ^~~~ gui.c:2074:95: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2074 | else strcpy (s," Checked light letters: -"); gtk_label_set_text(GTK_LABEL(st_r[2]),s); | ^~ gui.c:2076:3: warning: this 'else' clause does not guard... [-Wmisleading-indentation] 2076 | else strcpy (s," Checked grid cells: -"); gtk_label_set_text(GTK_LABEL(st_r[3]),s); | ^~~~ gui.c:2076:95: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 2076 | else strcpy (s," Checked grid cells: -"); gtk_label_set_text(GTK_LABEL(st_r[3]),s); | ^~ gui.c: In function 'updatefeas': gui.c:2241:45: warning: '%s' directive writing up to 999 bytes into a region of size between 978 and 979 [-Wformat-overflow=] 2241 | else sprintf(p1," Feasible character%s: %s",(strlen(p0)==1)?"":"s",p0); | ^~ ~~ gui.c:2241:10: note: 'sprintf' output between 22 and 1022 bytes into a destination of size 1000 2241 | else sprintf(p1," Feasible character%s: %s",(strlen(p0)==1)?"":"s",p0); | ^ gcc -Wall -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security `pkg-config --cflags glib-2.0` `pkg-config --cflags gtk+-2.0` -I/opt/local/include -O9 -c draw.c -o draw.o draw.c: In function 'draw_finit': draw.c:460:3: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 460 | if(sfb) cairo_surface_destroy(sfb); sfb=0; | ^~ draw.c:460:40: note: ...this statement, but the latter is misleadingly
