Your message dated Tue, 21 Oct 2025 14:34:20 +0000 with message-id <E1vBDRM-00CBFL-0L@fasolo.debian.org> and subject line Bug#1097469: fixed in nitpic 0.1-22 has caused the Debian Bug report #1097469, regarding nitpic: 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.) -- 1097469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097469 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: nitpic: ftbfs with GCC-15
- From: Matthias Klose <doko@debian.org>
- Date: Mon, 17 Feb 2025 17:40:02 +0000
- Message-id: <E1tk56A-009No7-Nx@paradis.debian.org>
Package: src:nitpic Version: 0.1-20 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/nitpic_0.1-20_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 [...] | ^~~~~~~ instr.cc: In function ‘void instr_jump(Widget, XtPointer, XtPointer)’: instr.cc:101:26: warning: unused variable ‘w_width’ [-Wunused-variable] 101 | Dimension w_width, w_height; | ^~~~~~~ instr.cc:103:43: warning: unused variable ‘bottom’ [-Wunused-variable] 103 | int dv, top, bottom, lines, dlines; | ^~~~~~ instr.cc:103:58: warning: unused variable ‘dlines’ [-Wunused-variable] 103 | int dv, top, bottom, lines, dlines; | ^~~~~~ instr.cc:104:26: warning: unused variable ‘thumb’ [-Wunused-variable] 104 | float thumb; | ^~~~~ instr.cc: In function ‘void ipointer_refresh(Widget, XEvent*, char**, Cardinal*)’: instr.cc:167:26: warning: unused variable ‘w_height’ [-Wunused-variable] 167 | Dimension w_height, w_width; | ^~~~~~~~ instr.cc:167:36: warning: unused variable ‘w_width’ [-Wunused-variable] 167 | Dimension w_height, w_width; | ^~~~~~~ instr.cc: In function ‘void ipointer_seek(Widget, XEvent*, char**, Cardinal*)’: instr.cc:221:26: warning: unused variable ‘w_width’ [-Wunused-variable] 221 | Dimension w_width, w_height; | ^~~~~~~ instr.cc:223:43: warning: unused variable ‘bottom’ [-Wunused-variable] 223 | int dv, top, bottom, lines, dlines; | ^~~~~~ instr.cc:223:58: warning: unused variable ‘dlines’ [-Wunused-variable] 223 | int dv, top, bottom, lines, dlines; | ^~~~~~ instr.cc:224:26: warning: unused variable ‘thumb’ [-Wunused-variable] 224 | float thumb; | ^~~~~ gcc -g -O2 -Wall -I. -I./lib/Xt -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DFUNCPROTO=15 -DNARROWPROTO -c -o pu_lib.o pu_lib.c In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/stdio.h:28, from pu_lib.c:6: /usr/include/features.h:197:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 197 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ pu_lib.c:13:6: error: conflicting types for ‘PU_Clear’; have ‘void(PICDEFN *)’ {aka ‘void(struct picdefn *)’} 13 | void PU_Clear(PICDEFN *pic) | ^~~~~~~~ In file included from pu_lib.c:5: pu_defs.h:22:13: note: previous declaration of ‘PU_Clear’ with type ‘void(void)’ 22 | extern void PU_Clear(); | ^~~~~~~~ pu_lib.c:176:5: error: conflicting types for ‘PU_WriteHeader’; have ‘int(char *, PICDEFN *, char *)’ {aka ‘int(char *, struct picdefn *, char *)’} 176 | int PU_WriteHeader(char *filename, PICDEFN *pic, char *comment) | ^~~~~~~~~~~~~~ pu_defs.h:23:13: note: previous declaration of ‘PU_WriteHeader’ with type ‘int(void)’ 23 | extern int PU_WriteHeader(); | ^~~~~~~~~~~~~~ pu_lib.c:201:5: error: conflicting types for ‘PU_WriteBlock’; have ‘int(char *, PICDEFN *, int, int)’ {aka ‘int(char *, struct picdefn *, int, int)’} 201 | int PU_WriteBlock(char *filename, PICDEFN *pic, int from, int to) | ^~~~~~~~~~~~~ pu_defs.h:24:13: note: previous declaration of ‘PU_WriteBlock’ with type ‘int(void)’ 24 | extern int PU_WriteBlock(); | ^~~~~~~~~~~~~ pu_lib.c:273:5: error: conflicting types for ‘PU_WriteTrailer’; have ‘int(char *, PICDEFN *, char *)’ {aka ‘int(char *, struct picdefn *, char *)’} 273 | int PU_WriteTrailer(char *filename, PICDEFN *pic, char *comment) | ^~~~~~~~~~~~~~~ pu_defs.h:25:13: note: previous declaration of ‘PU_WriteTrailer’ with type ‘int(void)’ 25 | extern int PU_WriteTrailer(); | ^~~~~~~~~~~~~~~ make[1]: *** [<builtin>: pu_lib.o] Error 1 make[1]: Leaving directory '/build/reproducible-path/nitpic-0.1' make: *** [debian/rules:17: build-arch] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
- To: 1097469-close@bugs.debian.org
- Subject: Bug#1097469: fixed in nitpic 0.1-22
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Tue, 21 Oct 2025 14:34:20 +0000
- Message-id: <E1vBDRM-00CBFL-0L@fasolo.debian.org>
- Reply-to: Adrian Bunk <bunk@debian.org>
Source: nitpic Source-Version: 0.1-22 Done: Adrian Bunk <bunk@debian.org> We believe that the bug you reported is fixed in the latest version of nitpic, 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 1097469@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 nitpic 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: Tue, 21 Oct 2025 16:59:36 +0300 Source: nitpic Architecture: source Version: 0.1-22 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Adrian Bunk <bunk@debian.org> Closes: 1097469 Changes: nitpic (0.1-22) unstable; urgency=medium . * QA upload. * Fix FTBFS with GCC 15. (Closes: #1097469) Checksums-Sha1: 139d38edf2368241bf1ff45a41621fca0ec0e167 1731 nitpic_0.1-22.dsc af8991c927dedfc263034640ff2c693b36d535e3 11884 nitpic_0.1-22.debian.tar.xz Checksums-Sha256: cc5afb812c5433ec7abd87df06401c6857ac775c959efcd825a0292bfb8cb97c 1731 nitpic_0.1-22.dsc 491131c6feae9e3b7b113b349d2c2581021714984fb16d60e1cce97f0ee6de1a 11884 nitpic_0.1-22.debian.tar.xz Files: 892c04258f44b19b8e45ba4af9e92f7e 1731 electronics optional nitpic_0.1-22.dsc fe766f0bad6cc8634e51cda9d54389f7 11884 electronics optional nitpic_0.1-22.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmj3kkYACgkQiNJCh6LY mLHTCBAAn8nbp8ZM3AhOUJiu2eg59j6kY6pqGEho6WdPapGfgwM1E//caXaZTCSu 650JMDek2L9oZmOrBtaztg8SL4qtXcwSWJHSNXi3CrWfXzo1RaB0vmoKRAQcaLUU piO3RBn2GHLWXVK6sw/b0MYHIHb1beUQ19e9aienNYjsIJstzydWPySoBobhlhwg fewgRcFvgL1V6/LQ7EGF5yzSbkeTK0+TmZxtc8LFEj1FONdefTsesO0ekHrpS3lV dWXiNSOBdGJfodWuy5nVT9JdgwUCGsEgKsh+x0wt0GHSdNAiKDf6ElAvY+a2K108 Vx1bE/UOIQ7fHXzMF58X270VGKMThHoUItJGfNIKO08vY4SwlJ6aJjrZ6o0V1h4V oQBTGyYG21YsxAOYOZ6hKCoNHohq/RuE3slJGpZpuToftGOGEI2yVJYeDTxJojzx JmRqoXOTaajzZslk8EKFhsk4z1AGs4hCCMjcXgc1lhaXTOTCA/7JJAqi1GvzQvZ+ 9SqWxkgTLtvynmLUEymdvWEUBB/LdcyC3eH0uL2ARlt9vNzA7SofjmVgEXhXDp0I x6P0zi540EBYKpXig8fCHIPib0IynhqxANXOUhvjvU6jqm80TQLPwXXobc8dC3yN btt1blsp4JIWWnEQUDEiwWEzAv0HlOKfGfuoBblAFQDKqCGfMnE= =5x/X -----END PGP SIGNATURE-----Attachment: pgpJJyI5FHYUN.pgp
Description: PGP signature
--- End Message ---