Your message dated Wed, 11 Sep 2024 13:24:10 +0000
with message-id <e1sonkm-0072t5...@fasolo.debian.org>
and subject line Bug#1075339: fixed in opendkim 2.11.0~beta2-9.1
has caused the Debian Bug report #1075339,
regarding opendkim: ftbfs with GCC-14
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 ow...@bugs.debian.org
immediately.)
--
1075339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opendkim
Version: 2.11.0~beta2-9
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is 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-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/opendkim_2.11.0~beta2-9_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
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-14/porting_to.html
[...]
make[3]: Leaving directory '/<<PKGBUILDDIR>>/contrib'
Making all in docs
make[3]: Entering directory '/<<PKGBUILDDIR>>/docs'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/docs'
Making all in libvbr
make[3]: Entering directory '/<<PKGBUILDDIR>>/libvbr'
/bin/sh ../libtool --tag=CC --mode=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=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
vbr.lo vbr.c
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=/<<PKGBUILDDIR>>=." -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2 -c vbr.c -fPIC -DPIC -o .libs/vbr.o
vbr.c: In function ‘vbr_query’:
vbr.c:1069:43: warning: ‘unable to start resolver for..’ directive output
truncated writing 30 bytes into a region of size 8 [-Wformat-truncation=]
1069 | "unable to start resolver for '%s'",
| ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/stdio.h:964,
from /usr/include/resolv.h:58,
from vbr.c:25:
In function ‘snprintf’,
inlined from ‘vbr_query’ at vbr.c:1068:4:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note:
‘__builtin___snprintf_chk’ output between 32 and 288 bytes into a destination
of size 8
54 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
vbr.c: In function ‘vbr_query’:
vbr.c:1081:43: warning: ‘unable to start query for '’ directive output
truncated writing 27 bytes into a region of size 8 [-Wformat-truncation=]
1081 | "unable to start query for '%s'",
| ~~~~~~~~^~~~~~~~~~~~~~~~~~~
In function ‘snprintf’,
inlined from ‘vbr_query’ at vbr.c:1080:4:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note:
‘__builtin___snprintf_chk’ output between 29 and 285 bytes into a destination
of size 8
54 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 | __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=/<<PKGBUILDDIR>>=." -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2 -c vbr.c -o vbr.o >/dev/null 2>&1
/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2
-version-info 2:0:0 -rpath /usr/lib/x86_64-linux-gnu -Wl,-z,relro -Wl,-z,now
-Wl,-z,defs -L/usr/lib/libmilter -o libvbr.la -rpath /usr/lib/x86_64-linux-gnu
vbr.lo
libtool: link: gcc -shared -fPIC -DPIC .libs/vbr.o -L/usr/lib/libmilter -g
-O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,defs
-Wl,-soname -Wl,libvbr.so.2 -o .libs/libvbr.so.2.0.0
libtool: link: (cd ".libs" && rm -f "libvbr.so.2" && ln -s "libvbr.so.2.0.0"
"libvbr.so.2")
libtool: link: (cd ".libs" && rm -f "libvbr.so" && ln -s "libvbr.so.2.0.0"
"libvbr.so")
libtool: link: ar cr .libs/libvbr.a vbr.o
libtool: link: ranlib .libs/libvbr.a
libtool: link: ( cd ".libs" && rm -f "libvbr.la" && ln -s "../libvbr.la"
"libvbr.la" )
make[3]: Leaving directory '/<<PKGBUILDDIR>>/libvbr'
Making all in librbl
make[3]: Entering directory '/<<PKGBUILDDIR>>/librbl'
/bin/sh ../libtool --tag=CC --mode=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=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
rbl.lo rbl.c
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=/<<PKGBUILDDIR>>=." -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2 -c rbl.c -fPIC -DPIC -o .libs/rbl.o
rbl.c: In function ‘rbl_res_close’:
rbl.c:336:20: error: passing argument 1 of ‘__res_nclose’ from incompatible
pointer type [-Wincompatible-pointer-types]
336 | res_nclose(res);
| ^~~
| |
| struct state *
In file included from rbl.c:14:
/usr/include/resolv.h:305:29: note: expected ‘res_state’ {aka ‘struct
__res_state *’} but argument is of type ‘struct state *’
305 | void res_nclose (res_state) __THROW;
| ^~~~~~~~~
make[3]: *** [Makefile:569: rbl.lo] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/librbl'
make[2]: *** [Makefile:599: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:510: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
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.1
Done: Helmut Grohne <hel...@subdivi.de>
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 1075...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Helmut Grohne <hel...@subdivi.de> (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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 11 Sep 2024 14:59:31 +0200
Source: opendkim
Architecture: source
Version: 2.11.0~beta2-9.1
Distribution: unstable
Urgency: medium
Maintainer: David Bürgin <dbuer...@gluet.ch>
Changed-By: Helmut Grohne <hel...@subdivi.de>
Closes: 1073606 1075339
Changes:
opendkim (2.11.0~beta2-9.1) unstable; urgency=medium
.
[ Helmut Grohne]
* Non-maintainer upload.
.
[ Tim Woodall ]
* debian/patches/ftbfs-gcc-14-1075339.patch: Fix FTBFS with gcc-14. (Closes:
#1075339)
* Move /lib/opendkim/opendkim.service.generate to /usr (DEP17). (Closes:
#1073606)
Checksums-Sha1:
ac1c588b4b2c039254f9f45dc1a65459d63b30d0 2619 opendkim_2.11.0~beta2-9.1.dsc
d2f77ddf1a071971fe0f6238e5225aaa366a1657 30752
opendkim_2.11.0~beta2-9.1.debian.tar.xz
Checksums-Sha256:
c67f213498cce7660a93bdb1882a85431dccd9c38ae5cdb3bcd9a5629ed54f46 2619
opendkim_2.11.0~beta2-9.1.dsc
5ca4eaf0e8386cc0c11aa7064787b7031d9a405e5ffb4f3090b13489cb7de46e 30752
opendkim_2.11.0~beta2-9.1.debian.tar.xz
Files:
29ea90a550b633cd674d82d79fc5c9d5 2619 mail optional
opendkim_2.11.0~beta2-9.1.dsc
635a2183de6176e5e95289d7d1c0d80c 30752 mail optional
opendkim_2.11.0~beta2-9.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEETMLS2QqNFlTb+HOqLRqqzyREREIFAmbhlG0ACgkQLRqqzyRE
REItYxAAimpE3mVdOy82jc9PHDnR9SfON8jOJI8jkTvrnbXvw0+oh5S2r879QH3V
1ikowmTEzulFLGwpQghTqwycMM1WcKpcoaw7dqaTIg657Yrw/TGvWgl9LPLCVD3p
9mq7cHrMMRLM5CllM3dtTtgMPg5IprxXN4yu5xdJBaIqt+kmbtUEERPXES92sTcz
aVWhAMklHLUXrqoTX/nuxc4thpXgpUSVbRfrXRpeyjT6N+yNXz9AExCCUNtu+S1U
TAoay0QxO5eY1gExHmeiQYy9OLuXBzmexhS3fyXwLJicSuDrCtf6dwdQaHrRh0v/
MQ9esAjfYdTUs4xP415nGo3lgoFf0GucwDZWhpuT9iDGm+UPpK0KghUstm0zJMTO
Xc22RZFqRrWYRwOAAnzBsjPASYdy39j8vGW70RM6Y4uTlED2nNghyEuj52w1CUm/
0MGTTY2/H/U+xv6zPH8hYEm6lTrMsYPb0od4mjQyjbxjOfGhhVgzQPCddLR18Or7
T6CrCregPWuUJ9n9IYDsUsxvjGddhz/X5O0AqTu5VqKMV2bDXd5B85Vlx1FGxJQe
SSPzWIreOBfomvjUCi/CLDLT8+75XRWWCHC4syYykxBwyOVVu1y+6yqNtuSgtiiq
Tv+e+rZI8BW7bMGx/lm3kApopiIXeZpbZDFqFU0Vjo8YhoFkCsg=
=YQCy
-----END PGP SIGNATURE-----
pgpirbdge0kms.pgp
Description: PGP signature
--- End Message ---
