Your message dated Fri, 07 Aug 2020 04:49:08 +0000
with message-id <e1k3ujy-0009gk...@fasolo.debian.org>
and subject line Bug#957710: fixed in proxychains 3.1-9
has caused the Debian Bug report #957710,
regarding proxychains: ftbfs with GCC-10
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.)


-- 
957710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:proxychains
Version: 3.1-8.1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. 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/gcc10-20200225/proxychains_3.1-8.1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

[...]
make[1]: Entering directory '/<<PKGBUILDDIR>>'
make  all-recursive
make[2]: Entering directory '/<<PKGBUILDDIR>>'
Making all in proxychains
make[3]: Entering directory '/<<PKGBUILDDIR>>/proxychains'
Making all in docs
make[4]: Entering directory '/<<PKGBUILDDIR>>/proxychains/docs'
Making all in en
make[5]: Entering directory '/<<PKGBUILDDIR>>/proxychains/docs/en'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/<<PKGBUILDDIR>>/proxychains/docs/en'
make[5]: Entering directory '/<<PKGBUILDDIR>>/proxychains/docs'
make[5]: Nothing to be done for 'all-am'.
make[5]: Leaving directory '/<<PKGBUILDDIR>>/proxychains/docs'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/proxychains/docs'
make[4]: Entering directory '/<<PKGBUILDDIR>>/proxychains'
/bin/bash ../libtool  --tag=CC   --mode=compile 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 
libproxychains.lo libproxychains.c
/bin/bash ../libtool  --tag=CC   --mode=compile 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 core.lo core.c
libtool: compile:  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 core.c  -fPIC -DPIC -o .libs/core.o
libtool: compile:  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 libproxychains.c  -fPIC -DPIC -o 
.libs/libproxychains.o
core.c: In function ‘proxy_gethostbyname’:
core.c:657:4: warning: ignoring return value of ‘read’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
  657 |    read(pipe_fd[0],&buff,sizeof(buff));
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/string.h:495,
                 from /usr/include/memory.h:29,
                 from core.c:24:
In function ‘strncpy’,
    inlined from ‘tunnel_to’ at core.c:314:6:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin___strncpy_chk’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
core.c: In function ‘tunnel_to’:
core.c:312:8: note: length computed here
  312 |      c=strlen(user);
      |        ^~~~~~~~~~~~
In file included from /usr/include/string.h:495,
                 from /usr/include/memory.h:29,
                 from core.c:24:
In function ‘strncpy’,
    inlined from ‘tunnel_to’ at core.c:318:6:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
core.c: In function ‘tunnel_to’:
core.c:316:8: note: length computed here
  316 |      c=strlen(pass);
      |        ^~~~~~~~~~~~
libtool: compile:  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 libproxychains.c -o libproxychains.o >/dev/null 2>&1
libtool: compile:  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 core.c -o core.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -version-info 3:0:0  -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o libproxychains.la -rpath /usr/lib/x86_64-linux-gnu 
libproxychains.lo core.lo -ldl 
libtool: link: gcc -shared  -fPIC -DPIC  .libs/libproxychains.o .libs/core.o   
-ldl  -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now 
-Wl,--as-needed   -Wl,-soname -Wl,libproxychains.so.3 -o 
.libs/libproxychains.so.3.0.0
/usr/bin/ld: .libs/core.o:./proxychains/core.h:71: multiple definition of 
`true_connect'; .libs/libproxychains.o:./proxychains/core.h:71: first defined 
here
/usr/bin/ld: .libs/core.o:./proxychains/core.h:91: multiple definition of 
`true_gethostbyaddr'; .libs/libproxychains.o:./proxychains/core.h:91: first 
defined here
/usr/bin/ld: .libs/core.o:./proxychains/core.h:88: multiple definition of 
`true_getnameinfo'; .libs/libproxychains.o:./proxychains/core.h:88: first 
defined here
/usr/bin/ld: .libs/core.o:./proxychains/core.h:82: multiple definition of 
`true_freeaddrinfo'; .libs/libproxychains.o:./proxychains/core.h:82: first 
defined here
/usr/bin/ld: .libs/core.o:./proxychains/core.h:79: multiple definition of 
`true_getaddrinfo'; .libs/libproxychains.o:./proxychains/core.h:79: first 
defined here
/usr/bin/ld: .libs/core.o:./proxychains/core.h:74: multiple definition of 
`true_gethostbyname'; .libs/libproxychains.o:./proxychains/core.h:74: first 
defined here
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:462: libproxychains.la] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/proxychains'
make[3]: *** [Makefile:534: all-recursive] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/proxychains'
make[2]: *** [Makefile:398: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:330: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j4 returned exit code 2
make: *** [debian/rules:13: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: proxychains
Source-Version: 3.1-9
Done: Daniel Echeverri <epsi...@debian.org>

We believe that the bug you reported is fixed in the latest version of
proxychains, 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 957...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Echeverri <epsi...@debian.org> (supplier of updated proxychains 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: SHA512

Format: 1.8
Date: Thu, 06 Aug 2020 22:58:59 -0500
Source: proxychains
Architecture: source
Version: 3.1-9
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverri <epsi...@debian.org>
Changed-By: Daniel Echeverri <epsi...@debian.org>
Closes: 957710
Changes:
 proxychains (3.1-9) unstable; urgency=medium
 .
   * debian/patches
     + Add gcc10.patch file to Fix FTBFS with GCC-10. (Closes: #957710)
       + Thanks to Reiner Herrmann for the patch!
   * debian/control
     + Update my contact info.
     + Bump debhelper compat to v13.
     + Bump Standards-Version to 4.5.0.
     + Mark Rules-Requires-Root: no as we don't need root for building.
   * Use debhelper-compat instead of debian/compat.
   * debian/rules
     + Drop DEB_LDFLAGS_MAINT_APPEND -Wl,--as-needed, default behavior
     in bullseye toolchain.
Checksums-Sha1:
 da0ca5953ee33b7a1e6868730cf0e8c9362f0ea0 2047 proxychains_3.1-9.dsc
 c649194f177e66c4ca8b10281ab4acdc2e62584e 327052 proxychains_3.1.orig.tar.gz
 6ef9b26f38053253404c11e14623ab792adc58ec 9736 proxychains_3.1-9.debian.tar.xz
 5e77c14c7cdc843212cd444e5fbbc55ad4ce8f78 6008 
proxychains_3.1-9_source.buildinfo
Checksums-Sha256:
 7b978a70c76a08db7a7999293770857ef1178bffea141fc5e2e31ff8ab18559b 2047 
proxychains_3.1-9.dsc
 1ad2c0ea65aa9ecba7954d93f6d6a31ba9d0f24594fa6261fa8ae207e9b2bcc5 327052 
proxychains_3.1.orig.tar.gz
 9392aa308417da4cc1fde75f2dd383e9fbe47cb23a99d3eeb45df06aa1d4fa7e 9736 
proxychains_3.1-9.debian.tar.xz
 ebab8d7663ed143efbd0a24ded652eacfa6a6e2a9344bf0d7330ba7166b9ea37 6008 
proxychains_3.1-9_source.buildinfo
Files:
 72e1851b759af93a44b5a03f6a3994bf 2047 net optional proxychains_3.1-9.dsc
 defaede2f795350e6f4f569b0f5da939 327052 net optional 
proxychains_3.1.orig.tar.gz
 b8913cb5e15cdb972020a3842bf99314 9736 net optional 
proxychains_3.1-9.debian.tar.xz
 6f4e054ffcdf92f2c7b1ecdc9d5ac465 6008 net optional 
proxychains_3.1-9_source.buildinfo

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

iQJHBAEBCgAxFiEE0NCFsWnDv9lASFj6IfwpUEtSMNsFAl8s15kTHGVwc2lsb25A
ZGViaWFuLm9yZwAKCRAh/ClQS1Iw27IZEADDjkqYfUQYFDvHJRb2Ial5Hvb7eZbG
I4TDvZM1byhLV+b3B8yF9QXr7AYxW1o7IOmhNkOutATubp59XAB4Jc22l3JHTYV8
PeXQ4V2V8bI7y1GpqlqMMraxm5K4RI32qJqdfdaL0TCW/s6L18AL3Dak5TKPzC/6
HnsrGXBZgQsbt2UEm9lejKCE37UnM9mNk5frV+kiD0iyACAlMV9xM2dqqgaemgVH
xot7xnmULJTJMiUrfHOErBWtIJkIWo89OlfyU0mQrezPZVm91udqcGlcZ4A8xy+y
hfuMjYhsi2OABzVcu+sSXy3y/zBShnvsgE2E2VK71Yl6qq4THyb+shxFtEHNXH7b
q3gK6TQLo7Ce4kss4Tt3AC/FI4F6wbGaT+0PWPcYeH1mVLdtA4XCGmBe4Ug7v6s/
N5cQarAMnRQAyakBPIuS0uyxxo7x9JKCC5qmM6xlXfCQbUcGZqxSepDSLEvyWsGL
djBinkk18SsdHHzZqH4CnllTCr7lrtdDq0sSvM8Z4ghzL78WTI29p5BFM5N0MW7p
nOwr2X2al3l4jVodCXcEfFGXVeu4CN1IXZgiF54PXotpObKdJQmGoPVKEDmIsxPm
xFszph1hQI32h2hOgW3/c5jaCTIZau/Mq78ZccifkKP+o80Xyko0rNqYtG/qcg9d
BDgcgnlpSHE51g==
=zFBF
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to