Your message dated Tue, 07 Oct 2025 09:49:46 +0000
with message-id <[email protected]>
and subject line Bug#1097516: fixed in opendkim 2.11.0~beta2-9.2
has caused the Debian Bug report #1097516,
regarding opendkim: 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.)
--
1097516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097516
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:opendkim
Version: 2.11.0~beta2-9.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/opendkim_2.11.0~beta2-9.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
[...]
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
69 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
70 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
rbl.c: In function 'rbl_query_check':
rbl.c:1187:30: warning: '' reply was unresolved CNAME' directive output may be
truncated writing 28 bytes into a region of size between 0 and 256
[-Wformat-truncation=]
1187 | "'%s' reply was unresolved CNAME", qname);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function 'snprintf',
inlined from 'rbl_query_check' at rbl.c:1186:3:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note:
'__builtin___snprintf_chk' output between 30 and 286 bytes into a destination
of size 257
68 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
69 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
70 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
rbl.c: In function 'rbl_query_check':
rbl.c:1084:30: warning: '' unexpected reply type/class' directive output may be
truncated writing 29 bytes into a region of size between 0 and 256
[-Wformat-truncation=]
1084 | "'%s' unexpected reply type/class", qname);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function 'snprintf',
inlined from 'rbl_query_check' at rbl.c:1083:3:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note:
'__builtin___snprintf_chk' output between 31 and 287 bytes into a destination
of size 257
68 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
69 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
70 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
rbl.c: In function 'rbl_query_check':
rbl.c:1065:38: warning: '' reply corrupt' directive output may be truncated
writing 15 bytes into a region of size between 0 and 256 [-Wformat-truncation=]
1065 | "'%s' reply corrupt", qname);
| ^~~~~~~~~~~~~~~
In function 'snprintf',
inlined from 'rbl_query_check' at rbl.c:1064:4:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note:
'__builtin___snprintf_chk' output between 17 and 273 bytes into a destination
of size 257
68 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
69 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
70 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-DCONFIG_BASE=\"/etc\" -g -O2 -Werror=implicit-function-declaration
"-ffile-prefix-map=/build/reproducible-path/opendkim-2.11.0~beta2=."
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c
rbl.c -o rbl.o >/dev/null 2>&1
/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2
-Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/opendkim-2.11.0~beta2=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2
-version-info 1:0:0 -rpath /usr/lib/x86_64-linux-gnu -Wl,-z,relro -Wl,-z,now
-Wl,-z,defs -L/usr/lib/libmilter -o librbl.la -rpath /usr/lib/x86_64-linux-gnu
rbl.lo
libtool: link: gcc -shared -fPIC -DPIC .libs/rbl.o -L/usr/lib/libmilter -g
-O2 -Werror=implicit-function-declaration
"-ffile-prefix-map=/build/reproducible-path/opendkim-2.11.0~beta2=."
-fstack-protector-strong -Werror=format-security -Wl,-z -Wl,relro -Wl,-z
-Wl,now -Wl,-z -Wl,defs -Wl,-soname -Wl,librbl.so.1 -o .libs/librbl.so.1.0.0
libtool: link: (cd ".libs" && rm -f "librbl.so.1" && ln -s "librbl.so.1.0.0"
"librbl.so.1")
libtool: link: (cd ".libs" && rm -f "librbl.so" && ln -s "librbl.so.1.0.0"
"librbl.so")
libtool: link: ar cr .libs/librbl.a rbl.o
libtool: link: ranlib .libs/librbl.a
libtool: link: ( cd ".libs" && rm -f "librbl.la" && ln -s "../librbl.la"
"librbl.la" )
make[3]: Leaving directory
'/build/reproducible-path/opendkim-2.11.0~beta2/librbl'
Making all in miltertest
make[3]: Entering directory
'/build/reproducible-path/opendkim-2.11.0~beta2/miltertest'
gcc -DHAVE_CONFIG_H -I. -I.. -I./../libopendkim -I/usr/include
-I/usr/include/lua5.3 -Wdate-time -D_FORTIFY_SOURCE=2 -DCONFIG_BASE=\"/etc\"
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/opendkim-2.11.0~beta2=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
miltertest-miltertest.o `test -f 'miltertest.c' || echo './'`miltertest.c
In file included from miltertest.c:32:
/usr/include/libmilter/mfapi.h:98:17: error: ‘bool’ cannot be defined via
‘typedef’
98 | typedef int bool;
| ^~~~
/usr/include/libmilter/mfapi.h:98:17: note: ‘bool’ is a keyword with ‘-std=c23’
onwards
make[3]: *** [Makefile:585: miltertest-miltertest.o] Error 1
make[3]: Leaving directory
'/build/reproducible-path/opendkim-2.11.0~beta2/miltertest'
make[2]: *** [Makefile:604: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/opendkim-2.11.0~beta2'
make[1]: *** [Makefile:515: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/opendkim-2.11.0~beta2'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:6: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: opendkim
Source-Version: 2.11.0~beta2-9.2
Done: Adrian Bunk <[email protected]>
We believe that the bug you reported is fixed in the latest version of
opendkim, 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.
Adrian Bunk <[email protected]> (supplier of updated opendkim 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, 05 Oct 2025 15:34:59 +0300
Source: opendkim
Architecture: source
Version: 2.11.0~beta2-9.2
Distribution: unstable
Urgency: medium
Maintainer: David Bürgin <[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 1097516
Changes:
opendkim (2.11.0~beta2-9.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Build with -std=gnu17 to workaround FTBFS with GCC 15
in Milter headers. (Closes: #1097516)
Checksums-Sha1:
a1198f05b78bd885deec7fbed88b3934286ccf84 2496 opendkim_2.11.0~beta2-9.2.dsc
d38264fa8be2150aa15cafa1574133309b6a6132 30852
opendkim_2.11.0~beta2-9.2.debian.tar.xz
Checksums-Sha256:
c592559419e7db1238fd2978c66f9149e7dff44c6a792932213db260c37da8a5 2496
opendkim_2.11.0~beta2-9.2.dsc
0514d8d7d67005824a48a65fce04bce6849f27619fdae253f16fb79a308b048e 30852
opendkim_2.11.0~beta2-9.2.debian.tar.xz
Files:
41ac99416db498f5ec8de00f2a4243f3 2496 mail optional
opendkim_2.11.0~beta2-9.2.dsc
df967ad5b186854b2d156bc09fff7bac 30852 mail optional
opendkim_2.11.0~beta2-9.2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmjiZ2oACgkQiNJCh6LY
mLEywg/+KhcG8Dgtp/yOmlPKhLvWSC01+usKgf7ObvgngQc8r/sEx+ayUPi4aAli
75opjZQwJhazs0JF5MSIcj2y6oMAXylw649UonmPSseBkIXkmBTLoYqimnk5C/6G
6WXJXYeoKkHmxgNKirrlDgfnxbStM0ZdspkhFFb/vjy9Rdm/DbFr+FWTdKPQPw1w
uLbsIFyTnjf0lDgP9hpg+aJbQVAim+2FsR7cevMPiOjjaib7GKBLw5IoLEfc9lqj
bfb6VIQc/mzpMscm2XR2iMLd+81jOhx13ZRmSMBH+srdkGXfrJX3uPb3FDk7MNPD
8Xsf2w4q22ONTTMSjY4v9U/TAr0toN1x8R19rLCjueGMLw/G/OTqobQnkj8LFMkl
Oy5O7JeJ7w8gxh0ot3ZPb4lejZwmO7+ZHxynkm2TCmjCAKShtmGIQTwvrPCWyBDy
EnUfj4IyenQTHcC80fQeoI0ax0r5n2L3cPCt2fw3muwwiypeeTlsmgfdfTtWv+mP
7f4hNGg+77iwR9eWGxOi2lPSAhnckFI8/qZ9hCVYy1ljR68uKA6P/xdv4l0xlqpj
yhiT5S0f0dVQBQQYCSWFRBcHjvB6OKK4nB1DMzcu9OCBNWUEcjptC87Ovg5J2JOD
ZqMdwHjtlRxHwdoaFtOqxK76gPD291F7bSX8hBS6UXf6ovkKNoI=
=o05x
-----END PGP SIGNATURE-----
pgplxb1PlBbUE.pgp
Description: PGP signature
--- End Message ---