Your message dated Mon, 11 Aug 2025 13:01:37 +0000
with message-id <[email protected]>
and subject line Bug#1096472: fixed in cputool 1.1.0-1
has caused the Debian Bug report #1096472,
regarding cputool: 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 [email protected]
immediately.)
--
1096472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096472
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:cputool
Version: 0.0.8-2
Severity: important
Tags: sid forky
User: [email protected]
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/cputool_0.0.8-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
[...]
479 | static void sigusr1() {
| ^~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
72 | typedef void (*__sighandler_t) (int);
| ^~~~~~~~~~~~~~
cputool.c: In function ‘sigusr2’:
cputool.c:492:25: error: passing argument 2 of ‘signal’ from incompatible
pointer type [-Wincompatible-pointer-types]
492 | signal(SIGUSR2, sigusr2);
| ^~~~~~~
| |
| 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)
| ~~~~~~~~~~~~~~~^~~~~~~~~
cputool.c:488:13: note: ‘sigusr2’ declared here
488 | static void sigusr2() {
| ^~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
72 | typedef void (*__sighandler_t) (int);
| ^~~~~~~~~~~~~~
cputool.c: In function ‘main’:
cputool.c:596:25: error: passing argument 2 of ‘signal’ from incompatible
pointer type [-Wincompatible-pointer-types]
596 | signal(SIGUSR1, sigusr1);
| ^~~~~~~
| |
| 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)
| ~~~~~~~~~~~~~~~^~~~~~~~~
cputool.c:479:13: note: ‘sigusr1’ declared here
479 | static void sigusr1() {
| ^~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
72 | typedef void (*__sighandler_t) (int);
| ^~~~~~~~~~~~~~
cputool.c:597:25: error: passing argument 2 of ‘signal’ from incompatible
pointer type [-Wincompatible-pointer-types]
597 | signal(SIGUSR2, sigusr2);
| ^~~~~~~
| |
| 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)
| ~~~~~~~~~~~~~~~^~~~~~~~~
cputool.c:488:13: note: ‘sigusr2’ declared here
488 | static void sigusr2() {
| ^~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
72 | typedef void (*__sighandler_t) (int);
| ^~~~~~~~~~~~~~
cputool.c:600:24: error: passing argument 2 of ‘signal’ from incompatible
pointer type [-Wincompatible-pointer-types]
600 | 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)
| ~~~~~~~~~~~~~~~^~~~~~~~~
cputool.c:495:13: note: ‘sighup’ declared here
495 | static void sighup() {
| ^~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
72 | typedef void (*__sighandler_t) (int);
| ^~~~~~~~~~~~~~
make[2]: *** [Makefile:443: cputool.o] Error 1
make[2]: Leaving directory '/build/reproducible-path/cputool-0.0.8'
make[1]: *** [Makefile:325: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/cputool-0.0.8'
dh_auto_build: error: make -j1 returned exit code 2
make: *** [debian/rules:4: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: cputool
Source-Version: 1.1.0-1
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
cputool, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <[email protected]> (supplier of updated cputool 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 24 Jul 2025 07:28:19 +0200
Source: cputool
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Package Salvaging Team <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1081634 1096472 1109810
Changes:
cputool (1.1.0-1) unstable; urgency=medium
.
* New upstream version
Closes: #1081634, #1096472
* Maintain package in Salvage team
Closes: #1109810
* Fix Homepage
* Point watch file to Git repository and use git mode (no signature)
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Secure URI in copyright format (routine-update)
* Trim trailing whitespace.
* Re-export upstream signing key without extra signatures.
* Set field Upstream-Name in debian/copyright.
* Add debian/upstream/metadata
* d/control: Build-Depends
- Add meson
- s/docbook-to-man/python3-docutils/
* Propagate hardening options
Checksums-Sha1:
cbb1a03437e677762aac632644d780652745ee73 1995 cputool_1.1.0-1.dsc
63de4db9bb956ee85a33b24214b83e272fd31402 22792 cputool_1.1.0.orig.tar.xz
eb869c52fb6e21c8fc2bfb73cedc38f9e06bf575 2604 cputool_1.1.0-1.debian.tar.xz
22a4deb3178aadcb386c063c4f7dba91800434df 7107 cputool_1.1.0-1_amd64.buildinfo
Checksums-Sha256:
88f2eb8159318b8dd5d3fe75c2aa292a186afc66432f00a097f2ac9b15acf10a 1995
cputool_1.1.0-1.dsc
d92972c346c0cd249de3b4a064d2e4384ffbd5f188176b9f35b2f87282bb04f8 22792
cputool_1.1.0.orig.tar.xz
0c09521a2f87394cf27897f391d590b275d7aa8f5257dc62a1ba3edf3aad99f6 2604
cputool_1.1.0-1.debian.tar.xz
b1cb4a28afea184aba823205daa95b433e390ab484af64dcf10f5cf76fa052c2 7107
cputool_1.1.0-1_amd64.buildinfo
Files:
b06875e8ae73478e022fcd958be56e84 1995 utils optional cputool_1.1.0-1.dsc
4c1a475d1ea5c7b7277c75676fcd7dba 22792 utils optional cputool_1.1.0.orig.tar.xz
6e7b1f130b9c359241c5e0b0f9a0bebf 2604 utils optional
cputool_1.1.0-1.debian.tar.xz
3f0f5824cc99ba8d550e0ae2165df1f6 7107 utils optional
cputool_1.1.0-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmiHZscRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHMnRAAgwtzcwkQVyu2hH1wyYlu7z3CEOFeSMJX
sTMTj0TVgftlZ3midNMaCuX6Q+WrSRBRXMDg644sirSc0rX1+jlLXDJJul44d/vy
JVE3rLG17w3fncN7Yk6MpdzvhASWQ7ctVtAXtjV15ubjxogjd/7uwrgV+QDNugnj
poe84AXj+lFM5EPx1GbsJRfrkXO7fg5wdj3AWwTizAoPrMCh9ikZP15hjw+JZz3N
3SJCYEWDrSsisRnLs61yIdHRPHFXdEVakOikmSBM89l9V5kBwhAsQG/HpNzwnb3z
f5dvFsXnfSRntFNNcvofr92SBxK53+ttvxEAi3t6HbZ3PWrDghO6Wvqt/+4AQX2f
tEKETIQch2dRfW+fXy0oq/ONENpGIGdEV7z9XALwPEN20Olz7EMi5MeEVLraCEWz
/9cBfhGWROttaE6OqA900zT+JeVLeNasFZ2bfQyM8MmiM2+9IrJ/8M25+/RY9vV7
vx3X2zYsfXBuywGrJL0Cdeo/0yD9FMz0c4ejABEirXCfuvP3tXcPoJvX4ShxNrQV
ISyVRprxl74fY2MiXJn7WfemP/XhYBPwySm7GS0VEIBtfo/GO0ca79h+n2BGaxlA
rr0ATNxk4UZzQ3n2DRaipqEl71dzkM1gi1G8ow4LlUK6nFCfV5MolfLrLMgRLQbN
GlykW4tvkwg=
=Kpxq
-----END PGP SIGNATURE-----
pgpH3_UTr0lZE.pgp
Description: PGP signature
--- End Message ---
