Your message dated Sun, 28 Sep 2025 18:34:48 +0000 with message-id <E1v2wES-00BaOU-1p@fasolo.debian.org> and subject line Bug#1097432: fixed in nast 0.2.0-13 has caused the Debian Bug report #1097432, regarding nast: 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.) -- 1097432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097432 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: nast: ftbfs with GCC-15
- From: Matthias Klose <doko@debian.org>
- Date: Mon, 17 Feb 2025 17:38:53 +0000
- Message-id: <E1tk553-009NdQ-AA@paradis.debian.org>
Package: src:nast Version: 0.2.0-12 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/nast_0.2.0-12_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 [...] include/nast.h:60:29: note: expected ‘char *’ but argument is of type ‘u_char *’ {aka ‘unsigned char *’} 60 | void print_ascii_hex (char *data_info, u_int len, FILE *log); | ~~~~~~^~~~~~~~~ tcp.c: In function ‘handle_TCP’: tcp.c:101:13: warning: pointer targets in assignment from ‘char *’ to ‘u_char *’ {aka ‘unsigned char *’} differ in signedness [-Wpointer-sign] 101 | buf = (char *) (packet + offset + size_ip + size_tcp); | ^ tcp.c:106:27: warning: pointer targets in passing argument 1 of ‘data_sniffo’ differ in signedness [-Wpointer-sign] 106 | data_sniffo (buf, size_buf, output); | ^~~ | | | u_char * {aka unsigned char *} In file included from tcp.c:20: include/nast.h:59:25: note: expected ‘char *’ but argument is of type ‘u_char *’ {aka ‘unsigned char *’} 59 | void data_sniffo (char *data, u_int l, FILE *log); | ~~~~~~^~~~ udp.c:81:27: warning: pointer targets in passing argument 1 of ‘data_sniffo’ differ in signedness [-Wpointer-sign] 81 | data_sniffo (buf, size_buf, ldd); | ^~~ | | | u_char * {aka unsigned char *} tcp.c:112:31: warning: pointer targets in passing argument 1 of ‘print_ascii_hex’ differ in signedness [-Wpointer-sign] 112 | print_ascii_hex (buf, size_buf, output); | ^~~ | | | u_char * {aka unsigned char *} include/nast.h:60:29: note: expected ‘char *’ but argument is of type ‘u_char *’ {aka ‘unsigned char *’} 60 | void print_ascii_hex (char *data_info, u_int len, FILE *log); | ~~~~~~^~~~~~~~~ include/nast.h:59:25: note: expected ‘char *’ but argument is of type ‘u_char *’ {aka ‘unsigned char *’} 59 | void data_sniffo (char *data, u_int l, FILE *log); | ~~~~~~^~~~ tcp.c:124:27: warning: pointer targets in passing argument 1 of ‘data_sniffo’ differ in signedness [-Wpointer-sign] 124 | data_sniffo (buf, size_buf, ldd); | ^~~ | | | u_char * {aka unsigned char *} include/nast.h:59:25: note: expected ‘char *’ but argument is of type ‘u_char *’ {aka ‘unsigned char *’} 59 | void data_sniffo (char *data, u_int l, FILE *log); | ~~~~~~^~~~ make[1]: *** [Makefile:37: main.o] Error 1 make[1]: *** Waiting for unfinished jobs.... prom.c: In function ‘psearch’: prom.c:171:23: warning: pointer targets in passing argument 1 of ‘sprintf’ differ in signedness [-Wpointer-sign] 171 | sprintf (ip, "%d.%d.%d.%d", uphost[i].ip[0], uphost[i].ip[1], uphost[i].ip[2], uphost[i].ip[3]); | ^~ | | | u_char * {aka unsigned char *} In file included from /usr/include/features.h:510, from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/stdio.h:28, from /usr/include/libnet.h:53, from include/nast.h:23, from prom.c:20: /usr/include/x86_64-linux-gnu/bits/stdio2.h:28:1: note: expected ‘char *’ but argument is of type ‘u_char *’ {aka ‘unsigned char *’} 28 | __NTH (sprintf (char *__restrict __s, const char *__restrict __fmt, ...)) | ^~~~~ prom.c:172:95: warning: pointer targets in passing argument 1 of ‘inet_addr’ differ in signedness [-Wpointer-sign] 172 | n_print ("princ",ln,1,lg,"%s (%s) --------->", ip, libnet_addr2name4(inet_addr(ip), LIBNET_RESOLVE)); | ^~ | | | u_char * {aka unsigned char *} In file included from /usr/include/libnet.h:79: /usr/include/arpa/inet.h:34:41: note: expected ‘const char *’ but argument is of type ‘u_char *’ {aka ‘unsigned char *’} 34 | extern in_addr_t inet_addr (const char *__cp) __THROW; | ~~~~~~~~~~~~^~~~ make[1]: Leaving directory '/build/reproducible-path/nast-0.2.0' dh_auto_build: error: make -j8 returned exit code 2 make: *** [debian/rules:9: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
- To: 1097432-close@bugs.debian.org
- Subject: Bug#1097432: fixed in nast 0.2.0-13
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Sun, 28 Sep 2025 18:34:48 +0000
- Message-id: <E1v2wES-00BaOU-1p@fasolo.debian.org>
- Reply-to: Adrian Bunk <bunk@debian.org>
Source: nast Source-Version: 0.2.0-13 Done: Adrian Bunk <bunk@debian.org> We believe that the bug you reported is fixed in the latest version of nast, 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 1097432@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 nast 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: Sun, 28 Sep 2025 21:11:07 +0300 Source: nast Architecture: source Version: 0.2.0-13 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Adrian Bunk <bunk@debian.org> Closes: 1097432 Changes: nast (0.2.0-13) unstable; urgency=medium . * QA upload. * Fix FTBFS with GCC 15. (Closes: #1097432) Checksums-Sha1: d139c2b592c575a956819c6b0593c65062999e39 1814 nast_0.2.0-13.dsc 7e3d0615f242ad0e7573b1807d912693edace8ff 23060 nast_0.2.0-13.debian.tar.xz Checksums-Sha256: 3a8a97f6506df2b70591ad0911a315d7f10fcb12780764a9a93044e3689909e9 1814 nast_0.2.0-13.dsc 8f2aded04ad18128314610e016b78fa23e17c38a3377d1d17b69e83bd35ee0bb 23060 nast_0.2.0-13.debian.tar.xz Files: 590edd78b2dc2cb2b458a05f63e65d50 1814 net optional nast_0.2.0-13.dsc 3fca4ade2daf07cb3f4defe74730ed58 23060 net optional nast_0.2.0-13.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmjZerIACgkQiNJCh6LY mLHQ0Q/+KfnpzTKuavt+5uUFB0m0v+QYgbKLQQbnJ56qN3DF6jJ8lKq5aZmBHz8O v+0EX8cT0jNWIlbNmJ/H/A6gr8ggA4znTXvYSl3+TPAlY8SQLxIiaenXhXv0p3DH 8SJ5sE5QZhZJaopxLr8xe9o43k4i5aGS6y3MUTJ7Qfes265UOfpGNbf5zCxGC3EO D3LLwQv1bIu1DuFmrzloolF1M3HP2S8z/ICVRzj/Ls5S/AWM0DqZJ4jXPvZ3ABCa 5IBltmcki2zsgA+nuizBbPBXgyzvS4+gPV8SKzN7lYdeh+0nE1uqtTlFJLZNoytZ UIJdIdcJ4ooDY7E1QTBaU6yWw3M0OBcfnEC8liLbo+Ut+K2YH0iPVa+4F+VsCWHN Z3g0LcgkC0v4y5g9fybz0tJz/MCzL/Jw00wCDNMT46Lz3BaUDMr8H8VM0lie/E3i 084sv3ycay2fQgggcwm6IvnUyGDfFQzT0nefwbhhnBHvyLTTDb3mYGb/p7M0MYOx TEbVsm4MwI9pnP3Wggelas2JSNBEUw0qRnIJjiVXgYtzk1sMJO7AbH28trzHVkPp W19lfnmkbREcG8M3SRd0WVGU2d4CpyiGLuesqaJf3PiiXl8GLvPaIl3nuHMkqDVk pf71LsVubQV2m5bN39NGQ0aJ3+qW3ZDr4WukHv+bLhDjCGlLWAk= =1VPr -----END PGP SIGNATURE-----Attachment: pgpDqbkbtnz3o.pgp
Description: PGP signature
--- End Message ---