Your message dated Tue, 28 Jul 2015 19:35:06 +0000
with message-id <e1zkaey-0007il...@franck.debian.org>
and subject line Bug#778164: fixed in vtun 3.0.3-2.1
has caused the Debian Bug report #778164,
regarding vtun: ftbfs with GCC-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.)


-- 
778164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vtun
Version: 3.0.3-2
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

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-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/vtun_3.0.3-2_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, 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-5/porting_to.html

[...]
    BF_ecb_encrypt(out_ptr, out_ptr, &key, BF_ENCRYPT);
                            ^
In file included from lfd_legacy_encrypt.c:55:0:
/usr/include/openssl/blowfish.h:115:6: note: expected 'unsigned char *' but 
argument is of type 'char *'
 void BF_ecb_encrypt(const unsigned char *in, unsigned char *out,
      ^
lfd_legacy_encrypt.c:102:22: warning: pointer targets in passing argument 1 of 
'BF_ecb_encrypt' differ in signedness [-Wpointer-sign]
       BF_ecb_encrypt(in_ptr + p,  out_ptr + p, &key, BF_ENCRYPT);
                      ^
In file included from lfd_legacy_encrypt.c:55:0:
/usr/include/openssl/blowfish.h:115:6: note: expected 'const unsigned char *' 
but argument is of type 'char *'
 void BF_ecb_encrypt(const unsigned char *in, unsigned char *out,
      ^
lfd_legacy_encrypt.c:102:35: warning: pointer targets in passing argument 2 of 
'BF_ecb_encrypt' differ in signedness [-Wpointer-sign]
       BF_ecb_encrypt(in_ptr + p,  out_ptr + p, &key, BF_ENCRYPT);
                                   ^
In file included from lfd_legacy_encrypt.c:55:0:
/usr/include/openssl/blowfish.h:115:6: note: expected 'unsigned char *' but 
argument is of type 'char *'
 void BF_ecb_encrypt(const unsigned char *in, unsigned char *out,
      ^
lfd_legacy_encrypt.c: In function 'legacy_decrypt_buf':
lfd_legacy_encrypt.c:113:22: warning: pointer targets in passing argument 1 of 
'BF_ecb_encrypt' differ in signedness [-Wpointer-sign]
       BF_ecb_encrypt(in + p, in + p, &key, BF_DECRYPT);
                      ^
In file included from lfd_legacy_encrypt.c:55:0:
/usr/include/openssl/blowfish.h:115:6: note: expected 'const unsigned char *' 
but argument is of type 'char *'
 void BF_ecb_encrypt(const unsigned char *in, unsigned char *out,
      ^
lfd_legacy_encrypt.c:113:30: warning: pointer targets in passing argument 2 of 
'BF_ecb_encrypt' differ in signedness [-Wpointer-sign]
       BF_ecb_encrypt(in + p, in + p, &key, BF_DECRYPT);
                              ^
In file included from lfd_legacy_encrypt.c:55:0:
/usr/include/openssl/blowfish.h:115:6: note: expected 'unsigned char *' but 
argument is of type 'char *'
 void BF_ecb_encrypt(const unsigned char *in, unsigned char *out,
      ^
In file included from lfd_legacy_encrypt.c:46:0:
lfd_legacy_encrypt.c: At top level:
vtun.h:240:13: warning: inline function 'clear_nat_hack_flags' declared but 
never defined
 inline void clear_nat_hack_flags(int svr);
             ^
gcc -Wall -g -O2  -I/usr/include/lzo -I/usr/include/openssl 
-I/usr/include/openssl -I/usr/include/openssl -I/usr/include/openssl -o vtund 
main.o cfg_file.tab.o cfg_file.lex.o server.o client.o lib.o llist.o auth.o 
tunnel.o lock.o netlib.o tun_dev.o tap_dev.o pty_dev.o pipe_dev.o tcp_proto.o 
udp_proto.o linkfd.o lfd_shaper.o lfd_zlib.o lfd_lzo.o lfd_encrypt.o 
lfd_legacy_encrypt.o  -Wl,-z,defs  -lz -llzo2 -lcrypto -lutil
main.o: In function `main':
/«PKGBUILDDIR»/main.c:155: undefined reference to `clear_nat_hack_flags'
collect2: error: ld returned 1 exit status
make[1]: *** [vtund] Error 1
Makefile:62: recipe for target 'vtund' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-stamp] Error 2
debian/rules:43: recipe for target 'build-stamp' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

--- End Message ---
--- Begin Message ---
Source: vtun
Source-Version: 3.0.3-2.1

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

Debian distribution maintenance software
pp.
gregor herrmann <gre...@debian.org> (supplier of updated vtun 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, 23 Jul 2015 21:10:07 +0200
Source: vtun
Binary: vtun
Architecture: source
Version: 3.0.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Roland Stigge <sti...@antcom.de>
Changed-By: gregor herrmann <gre...@debian.org>
Description:
 vtun       - virtual tunnel over TCP/IP networks
Closes: 778164
Changes:
 vtun (3.0.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "ftbfs with GCC-5": add patch from Tip Potter:
     changed inline semantics.
     (Closes: #778164)
Checksums-Sha1:
 1f4a2c47dcd8f89e9250fd8c67d5ae9ac3a6b385 1854 vtun_3.0.3-2.1.dsc
 4406ea6c130199427418443bf7398e1731bd64b1 25748 vtun_3.0.3-2.1.debian.tar.xz
Checksums-Sha256:
 cd62b6e406bc4ff2e50e0607f12c008433f5c57c9a643148e26c2143172f76b5 1854 
vtun_3.0.3-2.1.dsc
 bccc0905322307cb77784c302d0ee1cae90f61100f7988156b5b4db55fd8c2b2 25748 
vtun_3.0.3-2.1.debian.tar.xz
Files:
 f1120ba3524d93d88ef6b1c20ff51fe8 1854 net optional vtun_3.0.3-2.1.dsc
 dc2bde8227d85283cea0920d275fffef 25748 net optional 
vtun_3.0.3-2.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQJ8BAEBCgBmBQJVsTxLXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG9UEP/i0Opx7V5WAduEeJnLqdYcjA
u4tEGKC8FVe11/JER/gxphtv6pO5qv2VJBgu5j7NB65exZrgIbT02NsrKx08cwld
chYhtZfQcH7j1KJ4sKhIQ5QWPXZdRa03vdCL8U6/CC7Koy6OZlT9+OClXJkq9Jaf
zrwMtiirRll7LFSCJboiQwBfiy3fzbFotQAlSOLVx5WYuMfLhleQIlY7qK1VeNNn
+kkqsJdYUB2MUihhGScLQx887JrwviR8ut8c1R3F3+nAjw8jY44fUd7oZw+5UxVn
Wsgj06fyKWOD4bSrw/g8o7kOvjTM3b8rVkj6iBIyg+4ZfWwdp2rKxfoLjYUirp2/
W4GvUyO6qF+KfNcXJ8jlvGrcRWJLUnkuFbdf9tZmxCtDXsM8L1EJ1iU7ZVDXqMQZ
BSSAhk6G0SGrud4F3gZpSIBjnjGtN9pV2NqqKb5fMKveF9mm4kJYeu5uriesinGj
bxhssnvdkNU8+qRRFx2GFCDdpQMowUtrucVf2BKgTEe5xJtcDU3BHQZvoM4kva35
F+tXcAEYfmdmCehP2T0ER5ip4+VVlBlodm1mBwXp8B2xlIzUdMLhaugQOvzImVj3
4ItQJG+8++bTxMZ26syZRKT52EL9DODl6DHBi6SB+DUE4jnKMUZmYlDrYK1q/iIg
9nuqGXLMjozs8BNLFclX
=1nkV
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to