Your message dated Wed, 03 Dec 2025 19:20:15 +0000 with message-id <E1vQsOd-008wZg-00@fasolo.debian.org> and subject line Bug#1096475: fixed in crash 9.0.1-1 has caused the Debian Bug report #1096475, regarding crash: 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.) -- 1096475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096475 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: crash: ftbfs with GCC-15
- From: Matthias Klose <doko@debian.org>
- Date: Mon, 17 Feb 2025 17:08:25 +0000
- Message-id: <E1tk4bZ-009I4Z-I4@paradis.debian.org>
Package: src:crash Version: 8.0.6-1 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/crash_8.0.6-1_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 [...] checking whether localtime_r is compatible with its POSIX signature... no checking for lwpstatus_t.pr_reg in sys/procfs.h... yes checking for unsetenv... no checking for lwpstatus_t.pr_fpreg in sys/procfs.h... no checking for win32_pstatus_t in sys/procfs.h... yes checking for unsetenv() return type... no checking for ftello... int checking whether unsetenv obeys POSIX... yes checking for ftello64... yes checking whether iswcntrl works... yes checking for fseeko... yes checking for towlower... yes checking for fseeko64... yes checking for wctype_t... yes checking for fopen64... yes checking for wctrans_t... yes yes checking for wmemchr... checking size of off_t... yes checking for a BSD-compatible install... install --strip-program=true checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... 8 checking file_ptr type... BFD_HOST_64_BIT yes checking for stdlib.h... (cached) yes checking for style of include used by make... GNU checking whether make supports nested variables... checking for unistd.h... (cached) yes yes checking dependency style of gcc... checking for sys/param.h... gcc3 checking whether make supports nested variables... (cached) yes checking whether ln -s works... yes checking for x86_64-pc-linux-gnu-ranlib... ranlib checking for x86_64-pc-linux-gnu-ar... (cached) ar yes checking for getpagesize... (cached) yes checking for working mmap... configure: updating cache ./config.cache checking that generated files are newer than configure... yes checking for madvise... yes checking for mprotect... yes configure: updating cache ./config.cache checking that generated files are newer than configure... done configure: creating ./config.status done configure: creating ./config.status config.status: creating Makefile config.status: creating doc/Makefile config.status: creating bfd-in3.h config.status: creating po/Makefile.in config.status: creating config.h config.status: executing depfiles commands config.status: creating Makefile config.status: creating import/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing default commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing bfd_stdint.h commands config.status: executing default commands make[4]: *** [Makefile:860: all] Error 2 crash build failed make[3]: *** [Makefile:267: gdb_merge] Error 1 make[2]: *** [Makefile:258: all] Error 2 dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" returned exit code 2 make[1]: *** [debian/rules:15: override_dh_auto_build] Error 255 make[1]: Leaving directory '/build/reproducible-path/crash-8.0.6' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
- To: 1096475-close@bugs.debian.org
- Subject: Bug#1096475: fixed in crash 9.0.1-1
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Wed, 03 Dec 2025 19:20:15 +0000
- Message-id: <E1vQsOd-008wZg-00@fasolo.debian.org>
- Reply-to: Juerg Haefliger <juergh@proton.me>
Source: crash Source-Version: 9.0.1-1 Done: Juerg Haefliger <juergh@proton.me> We believe that the bug you reported is fixed in the latest version of crash, 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 1096475@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Juerg Haefliger <juergh@proton.me> (supplier of updated crash 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: Wed, 03 Dec 2025 09:08:18 +0000 Source: crash Architecture: source Version: 9.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Juerg Haefliger <juergh@proton.me> Closes: 1020461 1096475 1108875 1120855 Changes: crash (9.0.1-1) unstable; urgency=medium . * QA upload * New upstream release 9.0.1 (Closes: #1096475) * Use gdb tarball from gdb-source package (Closes: #1120855) * d/control: Add libmpfr-dev to Build-Depends * d/lintian-overrides: Update rule syntax * d/tests: Drop software-properties-common dependency (Closes: #1108875) * d/tests/live: Stop using apt-key (Closes: #1020461) * d/copyright: Convert to DEP5 format Checksums-Sha1: fd6859c10004dd39862e192f7f88c91bacf9a071 1770 crash_9.0.1-1.dsc 52b8b9ef60f93536d4b946d9d2679f747363913f 1372097 crash_9.0.1.orig.tar.gz 76dbe68d8a82c92da30058dc30ef2fbc2a57c202 173160 crash_9.0.1-1.debian.tar.xz 0557339b0dd64576f496c42a6e48988eeba493ac 5735 crash_9.0.1-1_source.buildinfo Checksums-Sha256: 3c32f6ef541585b6efebfd34b8f2a66a86742b58d033ee1a07ab6b390caae715 1770 crash_9.0.1-1.dsc 73dcdc633ec75ea2fc5329a1c3760407cceb9171428f4d0b885874f943a16797 1372097 crash_9.0.1.orig.tar.gz 459eacd05fdcc6d611b2413479c1fe7e27a30c2cb99ed2ce2fa1a73f0f0f1102 173160 crash_9.0.1-1.debian.tar.xz 2c5ea9ec7e28e59c29d70bdd4823e832f1fc1506ca4b8a10e9f4eb87603cae92 5735 crash_9.0.1-1_source.buildinfo Files: 59ae3d91b9f6011a9f340eaf16680255 1770 utils optional crash_9.0.1-1.dsc adc45740ff369692b8d884f767f2f15a 1372097 utils optional crash_9.0.1.orig.tar.gz 625856cf17263d7f1a18d659c40d4290 173160 utils optional crash_9.0.1-1.debian.tar.xz 81a0063652651caec94a0348a3a88779 5735 utils optional crash_9.0.1-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmkwiTcQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFLd3DACeJbiOGFwkLsJATVV2jRGwOVHdzqp/dUTe m4KV+CODg/of8SHpcoIrB3A7AUW7/7yV94FzGqDIDys5gKzmbJmsqKgmDvu8KKbX /yF3cPO+HbTiolODhGom8GOR+Lu733JYkSXBp97JsJLIPqzfNQrcXX8/3ogC8OKX ZFFaYBxwO3sh3a923b+qQkbbukEjcw8qZslktT0q8qsPbVOu0zgmT+IQanxByp2+ e/YCIf0JK+10nmUzlIf0jsrYJhUhboHtYOBy0HzWGFivyEhAiNaIohYtZebsKjIJ ha8Q0N7V+p7ntksSWm7VuiL4F/2kBSnxYGXLTSsdRAIgg9tD9E8UGbk9BOrt+ePM k7M419Q52x/fD66yHMGE0D19EAXSVMMagW01vFYyUtr2b4L4NPuOFqVxxgTiQVeZ 9w8tzvVbDqSvXZCSp6sdYFfjNGQ+ZpiksoHlnBrLDfjTh6Nb3Ob5vWnbqTTUv8Gs h4cQ26tilleGovr1wFbVx+8CZ4dsXtQ= =+PZh -----END PGP SIGNATURE-----Attachment: pgpVNoVsIgcks.pgp
Description: PGP signature
--- End Message ---