Your message dated Sun, 19 Oct 2025 21:23:33 +0000
with message-id <[email protected]>
and subject line Bug#1097932: fixed in sshguard 2.5.1-1
has caused the Debian Bug report #1097932,
regarding sshguard: 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.)
--
1097932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097932
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:sshguard
Version: 2.4.3-1
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/sshguard_2.4.3-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
[...]
In file included from blocklist.c:2:
/usr/include/pthread.h:204:36: note: expected ‘void * (*)(void *)’ but argument
is of type ‘void * (*)(void)’
204 | void *(*__start_routine) (void *),
| ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~
blocklist.c:77:14: note: ‘unblock_loop’ declared here
77 | static void *unblock_loop() {
| ^~~~~~~~~~~~
make[3]: *** [Makefile:402: blocklist.o] Error 1
make[3]: *** Waiting for unfinished jobs....
blocker.c: In function ‘main’:
blocker.c:119:21: error: passing argument 2 of ‘signal’ from incompatible
pointer type [-Wincompatible-pointer-types]
119 | signal(SIGTERM, sigfin_handler);
| ^~~~~~~~~~~~~~
| |
| void (*)(void)
In file included from blocker.c:24:
/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)
| ~~~~~~~~~~~~~~~^~~~~~~~~
blocker.c:64:13: note: ‘sigfin_handler’ declared here
64 | static void sigfin_handler();
| ^~~~~~~~~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
72 | typedef void (*__sighandler_t) (int);
| ^~~~~~~~~~~~~~
blocker.c:120:20: error: passing argument 2 of ‘signal’ from incompatible
pointer type [-Wincompatible-pointer-types]
120 | signal(SIGHUP, sigfin_handler);
| ^~~~~~~~~~~~~~
| |
| 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)
| ~~~~~~~~~~~~~~~^~~~~~~~~
blocker.c:64:13: note: ‘sigfin_handler’ declared here
64 | static void sigfin_handler();
| ^~~~~~~~~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
72 | typedef void (*__sighandler_t) (int);
| ^~~~~~~~~~~~~~
blocker.c:121:20: error: passing argument 2 of ‘signal’ from incompatible
pointer type [-Wincompatible-pointer-types]
121 | signal(SIGINT, sigfin_handler);
| ^~~~~~~~~~~~~~
| |
| 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)
| ~~~~~~~~~~~~~~~^~~~~~~~~
blocker.c:64:13: note: ‘sigfin_handler’ declared here
64 | static void sigfin_handler();
| ^~~~~~~~~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
72 | typedef void (*__sighandler_t) (int);
| ^~~~~~~~~~~~~~
blocker.c: At top level:
blocker.c:299:13: error: conflicting types for ‘sigfin_handler’; have
‘void(int)’
299 | static void sigfin_handler(int sig) {
| ^~~~~~~~~~~~~~
blocker.c:64:13: note: previous declaration of ‘sigfin_handler’ with type
‘void(void)’
64 | static void sigfin_handler();
| ^~~~~~~~~~~~~~
blocker.c:64:13: warning: ‘sigfin_handler’ used but never defined
make[3]: *** [Makefile:402: blocker.o] Error 1
make[3]: Leaving directory '/build/reproducible-path/sshguard-2.4.3/src/blocker'
make[2]: *** [Makefile:433: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/sshguard-2.4.3/src'
make[1]: *** [Makefile:486: all-recursive] Error 1
make[1]: Leaving directory '/build/reproducible-path/sshguard-2.4.3'
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 ---
Source: sshguard
Source-Version: 2.5.1-1
Done: Julián Moreno Patiño <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sshguard, 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.
Julián Moreno Patiño <[email protected]> (supplier of updated sshguard 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: Sun, 19 Oct 2025 14:27:23 -0500
Source: sshguard
Architecture: source
Version: 2.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Julián Moreno Patiño <[email protected]>
Changed-By: Julián Moreno Patiño <[email protected]>
Closes: 1092728 1096204 1097932
Changes:
sshguard (2.5.1-1) unstable; urgency=medium
.
* New upstream release. (Closes: #1097932)
* debian/sshguard.service, Remove unnecessary lines. (Closes: #1092728)
* debian/control, Add recommends to firewalld. (Closes: #1096204)
+ Bump Standards-Version to 4.7.0 (no changes).
+ Remove Rules-Requires-Root field, not needed anymore.
* debian/watch, Bump version from 4 to 5.
* debian/copyright, Extend copyright holders years.
Checksums-Sha1:
50595ed06d6e8787461c596c278f4a73c8d31569 1877 sshguard_2.5.1-1.dsc
56c5a484478f0a1472faf7423c52608cc4bc39cf 759630 sshguard_2.5.1.orig.tar.gz
87de41ab80600a2016ba08b277536610175c76d4 7488 sshguard_2.5.1-1.debian.tar.xz
470aa003f963b763900974135132e6913bdfe6ad 5519 sshguard_2.5.1-1_source.buildinfo
Checksums-Sha256:
a9af4e427569a43fc12de32c36d0f98e43d626c9d05ecc070c091138b2857168 1877
sshguard_2.5.1-1.dsc
997a1e0ec2b2165b4757c42f8948162eb534183946af52efc406885d97cb89fc 759630
sshguard_2.5.1.orig.tar.gz
872a9b4ed00125b5da5206b06a396389a6ac461487f7e4736760ab7928cb8705 7488
sshguard_2.5.1-1.debian.tar.xz
0796adeb202976390082fe0b758452a3d2e98ded0664824c5dd44c6cce86a73f 5519
sshguard_2.5.1-1_source.buildinfo
Files:
296d98424af7b4177431b7c61c408dc8 1877 net optional sshguard_2.5.1-1.dsc
10a79e8b47e2331cdf20a93c25865ec7 759630 net optional sshguard_2.5.1.orig.tar.gz
a436109afa408f8d75fb6e4a864a612c 7488 net optional
sshguard_2.5.1-1.debian.tar.xz
eeb64ba08eb07f2fa50b7976897294e4 5519 net optional
sshguard_2.5.1-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEEwsiQTjFM2PoEHZsA1f38FWFov2AFAmj1U1YSHGp1bGlhbkBk
ZWJpYW4ub3JnAAoJENX9/BVhaL9gsoAQAIgWj9ou7Mscqt/su/+tH0hx6Muhiu4E
8qK27htsNCqfbTG02R5Yy7mExwMjZ64VdnRAsiyUOr7ttHlMqmyOXpdTD+YNiNeK
ZnlEL2sO5QNq8mFO+ADbYbrXaKORaKNqUzPece8EDzdCZSupwfNA7auEIDOpkNAP
OfYRykrK1OUXeAiAf8fYJYtJSEdvMyeaSqqB0QeQZ/mDBgg2u9M2BxefXGkgsVW+
Jf8jX19DGYCH7D54v5mOJU4Yb9TLKuUhQ3Va1Es98mjWEzIbAB3yRddktjkK+0+Q
5Ji67KYw0PdS7tmiHwkuzo9Kd13GF6cC+xIwLwc1wFOCjMKMWJOjC0En91lHarbK
xO28B356ZcC+aOGLdy0XuEsDAWzpaBBFqswPUAUgdFklyGfMal2Gb4qjyxxWAJ2g
V2zVA6mQjfD3JBLtImkW6BngZLstkpo9XXw0WDI6iU8FD5HFO+05PrRsdykk3C3A
Q9jL0YN87iYNLluUAuIIjjOs6ZAp/OopXT1oiJNPmFNdTVM1dteC1X+y+e6e0Lpg
jNfSA1LhOVwxSME/3uyTi0rDoesyxV2UR9jOMHFNsryR8LiVhHOUpgoeWgIt01sf
XJOcQu87i5bZT0C6ZE7hrbBreilqHNlnMQc3hapEU3b/ag2t5ZjSO3CUvzdaXqvk
4WsgzxefMFZB
=ZpMm
-----END PGP SIGNATURE-----
pgpfhVPCzmzcf.pgp
Description: PGP signature
--- End Message ---
