Your message dated Fri, 19 Sep 2025 20:48:47 +0000 with message-id <E1uzi2B-000AX9-0J@fasolo.debian.org> and subject line Bug#1096266: fixed in 6tunnel 1:0.14-1 has caused the Debian Bug report #1096266, regarding 6tunnel: ftbfs with GCC-15 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 owner@bugs.debian.org immediately.) -- 1096266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096266 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: 6tunnel: ftbfs with GCC-15
- From: Matthias Klose <doko@debian.org>
- Date: Mon, 17 Feb 2025 17:01:51 +0000
- Message-id: <E1tk4VD-009Gyd-Jh@paradis.debian.org>
Package: src:6tunnel Version: 1:0.13-2 Severity: important Tags: sid forky User: debian-gcc@lists.debian.org Usertags: ftbfs-gcc-15 [This bug is NOT targeted to the upcoming trixie release] 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-15/g++-15, but succeeds to build with gcc-14/g++-14. The severity of this report will be raised before the forky release. The full build log can be found at: http://qa-logs.debian.net/2025/02/16/amd64exp/6tunnel_0.13-2_unstable_gccexp.log.gz The last lines of the build log are at the end of this report. To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS. Other 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-15/porting_to.html [...] /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ 6tunnel.c:560:6: note: ‘sighup’ declared here 560 | void sighup() | ^~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ 6tunnel.c:840:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 840 | signal(SIGCHLD, sigchld); | ^~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ 6tunnel.c:568:6: note: ‘sigchld’ declared here 568 | void sigchld() | ^~~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ 6tunnel.c:841:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 841 | signal(SIGTERM, sigterm); | ^~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ 6tunnel.c:578:6: note: ‘sigterm’ declared here 578 | void sigterm() | ^~~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ 6tunnel.c:842:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 842 | signal(SIGINT, sigterm); | ^~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ 6tunnel.c:578:6: note: ‘sigterm’ declared here 578 | void sigterm() | ^~~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ 6tunnel.c:843:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 843 | signal(SIGHUP, sighup); | ^~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ 6tunnel.c:560:6: note: ‘sighup’ declared here 560 | void sighup() | ^~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ make[1]: *** [Makefile:599: 6tunnel.o] Error 1 make[1]: Leaving directory '/build/reproducible-path/6tunnel-0.13' dh_auto_build: error: make -j8 returned exit code 2 make: *** [debian/rules:7: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
- To: 1096266-close@bugs.debian.org
- Subject: Bug#1096266: fixed in 6tunnel 1:0.14-1
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Fri, 19 Sep 2025 20:48:47 +0000
- Message-id: <E1uzi2B-000AX9-0J@fasolo.debian.org>
- Reply-to: Adrian Bunk <bunk@debian.org>
Source: 6tunnel Source-Version: 1:0.14-1 Done: Adrian Bunk <bunk@debian.org> We believe that the bug you reported is fixed in the latest version of 6tunnel, 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 1096266@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk <bunk@debian.org> (supplier of updated 6tunnel 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 ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 19 Sep 2025 19:30:03 +0300 Source: 6tunnel Architecture: source Version: 1:0.14-1 Distribution: unstable Urgency: low Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Adrian Bunk <bunk@debian.org> Closes: 1096266 Changes: 6tunnel (1:0.14-1) unstable; urgency=low . * QA upload. * New upstream release. - Fixes FTBFS with gcc 15. (Closes: #1096266) Checksums-Sha1: 9d4e1e261e88b9c860b1bbae0c394d028dc71454 1840 6tunnel_0.14-1.dsc c6b5f4b68f2a8c1740830b812167edf3c51c6f27 104488 6tunnel_0.14.orig.tar.gz 5ee832ba47107b4c7bc2cccd1d4de93292417521 4692 6tunnel_0.14-1.debian.tar.xz Checksums-Sha256: 8cf08de196145ae6c8cf5e7f8a8543297e21a24f1c330e26a1c06bfbfe0542ce 1840 6tunnel_0.14-1.dsc 6945312793079408f1ab40071cee68e70158a23560145f1d424a3eb16227f235 104488 6tunnel_0.14.orig.tar.gz e5c4f21202b843ad7a50791e9af3750db7c59e4764d9f3d0549af95302f41b4a 4692 6tunnel_0.14-1.debian.tar.xz Files: cb46486170d321f1c1e9aab762a472a0 1840 net optional 6tunnel_0.14-1.dsc 20a86dbd158b330817f3105818c7fca0 104488 net optional 6tunnel_0.14.orig.tar.gz 97130253fdd5ab1cd1277edcda4b3d6b 4692 net optional 6tunnel_0.14-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmjNvZAACgkQiNJCh6LY mLEoOQ//Ss4uoh0F1GhU3F5kWX0AkIAK9T20j2KAONwMLwxKPyC17Fk8/1pvCfEU C7f34GfgMQrEWVmAj1qIlHUA/9dhwO2v68p3U0Vv/ywdKPTDDGvVY0a821YpOacU 07QjvXUMa9ObKL1IgAJ2oGciXElmnVYgYciToC9isxRJxg30tHbAX0BiV6Oq7AmQ Up2D/J8Mex51zL1QE4fO2QC0mmH0WWWX2cE/b/1n+zNwhNfyzRYPc3Z6QNPIf7qI i5nMz6mtClJadLOed1v8hJ5QXcap6j3xl1lys9Ws9YmbKntJQDxhVRN54/KZc4Xy dr1UaxwUjTr9gkOUf4A2Xdg+M8hwr6L+nH8RdA5vQnh2AqDFWibCecsuy9jkA3Ky JmAyFHCBtBjlQ/KP2T/cIJzwWGgmEEkmCLqe2pnrt/blzZC5ss6uABAi+Ge6MCII Njk6hRqf61c4UDoZFeXDhC1GwUBBNGZDg0OIiP9afS3Koq3sqpj7V549PdUYM7Ny L0u+hg1b7g2987nXIr/jw82k29jT7zAxedhNpCUHxQHkEqldCpI6R+u/gB84ETc6 1+eO2IKg+2wlZd410vat7mLfNV1viY5VQ08kzA0P2kksNGtyku4WWEf+q6JHfWz0 OQeHqlYw7nsgb/j62bXoywxyy5e9nIgbPmhTYaP39CxNhlGNCEk= =TzqH -----END PGP SIGNATURE-----Attachment: pgp_vnNCsYDdO.pgp
Description: PGP signature
--- End Message ---