Your message dated Tue, 22 Aug 2017 15:05:32 +0000
with message-id <e1dkakg-000ey9...@fasolo.debian.org>
and subject line Bug#853339: fixed in bwm-ng 0.6.1-3
has caused the Debian Bug report #853339,
regarding bwm-ng: ftbfs with GCC-7
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.)


-- 
853339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bwm-ng
Version: 0.6.1-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/bwm-ng_0.6.1-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 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-7/porting_to.html

[...]
checking for getpwuid... yes
enable path to netstat as option: no
checking for egrep... (cached) /bin/grep -E
checking for netstat... no
checking whether the C compiler (gcc) accepts noreturn attribute... yes
checking for inline... inline
checking for /usr/ccs/bin/strip... no
checking for strip... strip
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
   dh_auto_build
        make -j64
make[1]: Entering directory '/<<PKGBUILDDIR>>'
make  all-recursive
make[2]: Entering directory '/<<PKGBUILDDIR>>'
Making all in src
make[3]: Entering directory '/<<PKGBUILDDIR>>/src'
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o bwm-ng.o bwm-ng.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o process.o process.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o output.o output.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o options.o options.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o help.o help.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o curses_tools.o curses_tools.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o retrieve.o `test -f 'input/retrieve.c' || echo 
'./'`input/retrieve.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o proc_net_dev.o `test -f 'input/proc_net_dev.c' || 
echo './'`input/proc_net_dev.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o proc_diskstats.o `test -f 
'input/proc_diskstats.c' || echo './'`input/proc_diskstats.c
gcc  -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wl,-z,relro -Wl,-z,now -o bwm-ng bwm-ng.o 
process.o output.o options.o help.o curses_tools.o retrieve.o proc_net_dev.o 
proc_diskstats.o -lcurses 
bwm-ng.o: In function `main':
./src/bwm-ng.c:186: undefined reference to `init'
options.o: In function `read_config':
./src/options.c:228: undefined reference to `str2out_method'
collect2: error: ld returned 1 exit status
Makefile:343: recipe for target 'bwm-ng' failed
make[3]: *** [bwm-ng] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/src'
Makefile:435: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
Makefile:333: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

--- End Message ---
--- Begin Message ---
Source: bwm-ng
Source-Version: 0.6.1-3

We believe that the bug you reported is fixed in the latest version of
bwm-ng, which is due to be installed in the Debian FTP archive.

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 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Henrique <samuel...@gmail.com> (supplier of updated bwm-ng 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...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 19 Aug 2017 11:09:54 -0300
Source: bwm-ng
Binary: bwm-ng
Architecture: source
Version: 0.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Samuel Henrique <samuel...@gmail.com>
Changed-By: Samuel Henrique <samuel...@gmail.com>
Description:
 bwm-ng     - small and simple console-based bandwidth monitor
Closes: 853339
Changes:
 bwm-ng (0.6.1-3) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.0.1.
   * d/control: Add collab-maint Vcs-* fields.
   * d/copyright: Update packaging copyright to 2017.
   * d/patches: Use-static-inline-instead-of-inline: New patch to fix ftbfs
     with gcc7, thanks to everyone who helped on the bugreport
     (closes: #853339).
Checksums-Sha1:
 19fe84edc31572925c0a5cf6d5a6734b1cebe8d7 1818 bwm-ng_0.6.1-3.dsc
 4009caa50b2214fd8aa289a5c262d6b2eb5d57bf 6388 bwm-ng_0.6.1-3.debian.tar.xz
Checksums-Sha256:
 9a25b2ef6cd9b5445fa0541a9e01ad1374b5a8073ac80b36d534667ae0165508 1818 
bwm-ng_0.6.1-3.dsc
 37385fb67a09d4614b65a7400132bab6249126fe7c5856a9e6e792e634fcf4ec 6388 
bwm-ng_0.6.1-3.debian.tar.xz
Files:
 9065237ffb19340e6c40064d32d0a56e 1818 net optional bwm-ng_0.6.1-3.dsc
 afb30a12e82201072cf85549882ab3bf 6388 net optional bwm-ng_0.6.1-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJZnD85AAoJEPNPCXROn13ZGwcQAKTSRqr8H+pIenjWkaEoiiWP
dJtfRPqt5sBP315uMa/En57kASXBd2hLOPh7P4Qo3BNNwGhX/nu9ferlzVpdzx3j
Mjdv8JBO7LfQsQjVGUf/Zt7D4MbSPA/MictS5fqrQr2icFqosNgSKY8x2SAOR8Cg
i+qu6O2axI+5d5+g24xvD4SLfhQb+r1GS8fult+lTirbwMdtOe9IplqmM5jnd+83
+yhvciTNIYh/zivSyPuN22lO4WtXuBupRfCjhO9pd70xD+Z63LgYa06K9rr/JV9r
8IOiK88sGvMD4s+UCoBXq7mlu1SarDIoNND1AGMTvsFpI29iabXjyN0Ud++XgqyP
fG3AlgYpPW1sRgcowrJDaEGFl46Mcoo3SAZSXmMxYMZEYFnGOiumTo9dVLXORd1g
huJRAn0LUmBgyrmt6QqjJY2DHcHLEVLPTCxAE3XrxDSKRL6FV9Bb3EwaD4+XU2yH
R4/UBGmaowJjErAAZnxGYHfC6ZZuff7q4xZ2RDEr50kO9Orfh99ho8MYvq8o3U7K
KnqYlAndJBoAKdIZgKM1+DoDeYQ3ti1reeWSfdzOS0LKsx8y4iGlxgs5CEpFnAb9
CNWVQCX8uyMTzxLKUyElQ3YZf0MoZPxnQzRGopwMT6JufCmPvyFLPOapNp/awn2+
tM0GXA9lHeiras62tRh0
=UuH/
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to