Your message dated Thu, 11 Sep 2025 15:25:40 +0000 with message-id <E1uwjB6-00BrZb-0E@fasolo.debian.org> and subject line Bug#1097931: fixed in ssmtp 2.64-13 has caused the Debian Bug report #1097931, regarding ssmtp: 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.) -- 1097931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097931 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: ssmtp: ftbfs with GCC-15
- From: Matthias Klose <doko@debian.org>
- Date: Mon, 17 Feb 2025 17:55:04 +0000
- Message-id: <E1tk5Ki-009QVF-E1@paradis.debian.org>
Package: src:ssmtp Version: 2.64-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/ssmtp_2.64-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 [...] | ^~~~~~~~~~~~~~~~~~ | | | void (*)(void) In file included from /usr/include/x86_64-linux-gnu/sys/param.h:28, from ssmtp.c:18: /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) | ~~~~~~~~~~~~~~~^~~~~~~~~ ssmtp.c:1405:6: note: ‘handler’ declared here 1405 | void handler(void) | ^~~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ ssmtp.c:1518:30: warning: pointer targets in passing argument 1 of ‘to64frombits’ differ in signedness [-Wpointer-sign] 1518 | to64frombits(buf, auth_user, strlen(auth_user)); | ^~~ | | | char * ssmtp.h:44:19: note: expected ‘unsigned char *’ but argument is of type ‘char *’ 44 | void to64frombits(unsigned char *, const unsigned char *, int); | ^~~~~~~~~~~~~~~ ssmtp.c:1518:35: warning: pointer targets in passing argument 2 of ‘to64frombits’ differ in signedness [-Wpointer-sign] 1518 | to64frombits(buf, auth_user, strlen(auth_user)); | ^~~~~~~~~ | | | char * ssmtp.h:44:36: note: expected ‘const unsigned char *’ but argument is of type ‘char *’ 44 | void to64frombits(unsigned char *, const unsigned char *, int); | ^~~~~~~~~~~~~~~~~~~~~ ssmtp.c:1530:38: warning: pointer targets in passing argument 1 of ‘to64frombits’ differ in signedness [-Wpointer-sign] 1530 | to64frombits(buf, auth_user, strlen(auth_user)); | ^~~ | | | char * ssmtp.h:44:19: note: expected ‘unsigned char *’ but argument is of type ‘char *’ 44 | void to64frombits(unsigned char *, const unsigned char *, int); | ^~~~~~~~~~~~~~~ ssmtp.c:1530:43: warning: pointer targets in passing argument 2 of ‘to64frombits’ differ in signedness [-Wpointer-sign] 1530 | to64frombits(buf, auth_user, strlen(auth_user)); | ^~~~~~~~~ | | | char * ssmtp.h:44:36: note: expected ‘const unsigned char *’ but argument is of type ‘char *’ 44 | void to64frombits(unsigned char *, const unsigned char *, int); | ^~~~~~~~~~~~~~~~~~~~~ ssmtp.c:1540:30: warning: pointer targets in passing argument 1 of ‘to64frombits’ differ in signedness [-Wpointer-sign] 1540 | to64frombits(buf, auth_pass, strlen(auth_pass)); | ^~~ | | | char * ssmtp.h:44:19: note: expected ‘unsigned char *’ but argument is of type ‘char *’ 44 | void to64frombits(unsigned char *, const unsigned char *, int); | ^~~~~~~~~~~~~~~ ssmtp.c:1540:35: warning: pointer targets in passing argument 2 of ‘to64frombits’ differ in signedness [-Wpointer-sign] 1540 | to64frombits(buf, auth_pass, strlen(auth_pass)); | ^~~~~~~~~ | | | char * ssmtp.h:44:36: note: expected ‘const unsigned char *’ but argument is of type ‘char *’ 44 | void to64frombits(unsigned char *, const unsigned char *, int); | ^~~~~~~~~~~~~~~~~~~~~ ssmtp.c:1622:12: warning: suggest parentheses around assignment used as truth value [-Wparentheses] 1622 | if(remote_addr=getenv("REMOTE_ADDR")) { | ^~~~~~~~~~~ make[1]: *** [<builtin>: ssmtp.o] Error 1 make[1]: Leaving directory '/build/reproducible-path/ssmtp-2.64' dh_auto_build: error: make -j8 returned exit code 2 make: *** [debian/rules:18: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
- To: 1097931-close@bugs.debian.org
- Subject: Bug#1097931: fixed in ssmtp 2.64-13
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Thu, 11 Sep 2025 15:25:40 +0000
- Message-id: <E1uwjB6-00BrZb-0E@fasolo.debian.org>
- Reply-to: Bastian Germann <bage@debian.org>
Source: ssmtp Source-Version: 2.64-13 Done: Bastian Germann <bage@debian.org> We believe that the bug you reported is fixed in the latest version of ssmtp, 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 1097931@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann <bage@debian.org> (supplier of updated ssmtp 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: Thu, 11 Sep 2025 16:32:20 +0200 Source: ssmtp Architecture: source Version: 2.64-13 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Bastian Germann <bage@debian.org> Closes: 1097931 Changes: ssmtp (2.64-13) unstable; urgency=medium . * QA upload * d/copyright: Convert to machine-readable format * Revert port from openssl to gnutls * GCC 15 fix (Closes: #1097931) * Rename badly named patch * lintian: Drop non-matching override * Prevent overriding Debian CFLAGS . [ Carles Pina i Estany ] * Added po-debconf Catalan translation Checksums-Sha1: bc56dbb05d37b8cfd06f3facba791f9eace6c618 1725 ssmtp_2.64-13.dsc 723fb9fb207d9e72760a24845cab2a6d40cc7b60 40036 ssmtp_2.64-13.debian.tar.xz b6105afb8304fa19afed8202ba6eadd6f4ac9d39 6309 ssmtp_2.64-13_source.buildinfo Checksums-Sha256: 4aee31805d4b574236b84f013e31b58ed150edb8a834f97575d29c18a3ac38d4 1725 ssmtp_2.64-13.dsc ecaa0cee1aa3192099c55c46b22fa96b0456d89e7f35ec0cbe6fe64cd35920d9 40036 ssmtp_2.64-13.debian.tar.xz dda64b058b9efb6a36e97590811f851c00285a730da421359bf492ba6eedeb74 6309 ssmtp_2.64-13_source.buildinfo Files: 7baa48aa0a5dfe5a7ec2d60b42f16ec9 1725 mail optional ssmtp_2.64-13.dsc 08535f02adf8ae1583357c7f2769f20c 40036 mail optional ssmtp_2.64-13.debian.tar.xz abda9c3654d7a7f109ba2c0e3c0f2871 6309 mail optional ssmtp_2.64-13_source.buildinfo -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmjC3doQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFFGVDACnIe0oZ1golncykLkXmPvrjMyZfrGr8S5C oL03hXhwqUJCi6OajXv0W70I1RZVnGFGMb554rnvz2BbD2B3NOVsDpR8mfNUpGDD dAZvq+e7x68+S3xuOCiy9/9naRv0Pn+jrhjokvgnP3aSZ8sfc8Jy6BvwV2IT24Z3 Q2idC3C4xaJUJ7IowQElCKc1jpEWYB0P6GBtWZ7E38kSHTUSBbWN8DTJPyIM273t iWaFzmoK1Ye1Gsue6Phuti5Fhkcgbq3OOvwAIUA+tmoLvyB+I/oUxWUl6FWs2wqQ /ewMoEB9fEZs4S+wh9MRCQzzNn6SPC3RTBQ0ECMHG8UnkVqp5VSnurBg/Y1+UZZr yIYbh4tEoCCTBoMVLY5nR2/lljIzSd4vXsY6Ms/Tr9Ev64hK4KN0WEaodmJc/fX4 XJMf8la/YaUi0LBy+25nD8pBBU9w5DYF4dU3XwKHLKSOC2Fv9mhfTtAfy11Q3RjM CqxViPXQhOrcKNP+c2TM9ojeu9tfYgk= =L0Uw -----END PGP SIGNATURE-----Attachment: pgpl9FKstlP5U.pgp
Description: PGP signature
--- End Message ---