Your message dated Mon, 09 Sep 2024 23:20:08 +0000 with message-id <E1snng0-00GUFJ-Ox@fasolo.debian.org> and subject line Bug#1074965: fixed in freecdb 0.78 has caused the Debian Bug report #1074965, regarding freecdb: 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 owner@bugs.debian.org immediately.) -- 1074965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074965 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: freecdb: ftbfs with GCC-14
- From: Matthias Klose <doko@debian.org>
- Date: Wed, 03 Jul 2024 12:26:46 +0000
- Message-id: <E1sOz4Q-00416O-L3@paradis.debian.org>
Package: src:freecdb Version: 0.77 Severity: important Tags: sid trixie User: debian-gcc@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/freecdb_0.77_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 [...] 14 | if (!n) return; *--to = *--from; --n; | ^ byte_cr.c:15:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 15 | if (!n) return; *--to = *--from; --n; | ^~ byte_cr.c:15:21: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 15 | if (!n) return; *--to = *--from; --n; | ^ byte_cr.c:16:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 16 | if (!n) return; *--to = *--from; --n; | ^~ byte_diff.c: In function ‘byte_diff’: byte_diff.c:11:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 11 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_cr.c:16:21: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 16 | if (!n) return; *--to = *--from; --n; | ^ byte_diff.c:11:23: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 11 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:12:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 12 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:12:23: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 12 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:13:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 13 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:13:23: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 13 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:14:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 14 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:14:23: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 14 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o cdb.o cdb.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o cdb_hash.o cdb_hash.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o cdb_make.o cdb_make.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o error.o error.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o error_str.o error_str.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o fmt_ulong.o fmt_ulong.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o open_trunc.o open_trunc.c cdb_make.c: In function ‘cdb_make_start’: cdb_make.c:18:21: error: passing argument 2 of ‘buffer_init’ from incompatible pointer type [-Wincompatible-pointer-types] 18 | buffer_init(&c->b,write,fd,c->bspace,sizeof c->bspace); | ^~~~~ | | | ssize_t (*)(int, const void *, size_t) {aka long int (*)(int, const void *, long unsigned int)} In file included from cdb_make.h:6, from cdb_make.c:8: buffer.h:18:34: note: expected ‘int (*)()’ but argument is of type ‘ssize_t (*)(int, const void *, size_t)’ {aka ‘long int (*)(int, const void *, long unsigned int)’} 18 | extern void buffer_init(buffer *,int (*)(),int,char *,unsigned int); | ^~~~~~~~~ cdb.c: In function ‘cdb_init’: cdb.c:37:11: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘x + 1’ must not be NULL [-Waddress] 37 | if (x + 1) { | ^ gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o scan_ulong.o scan_ulong.c make[2]: *** [<builtin>: cdb_make.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory '/<<PKGBUILDDIR>>' dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" "CFLAGS=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall" returned exit code 2 make[1]: *** [debian/rules:7: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:4: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
- To: 1074965-close@bugs.debian.org
- Subject: Bug#1074965: fixed in freecdb 0.78
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Mon, 09 Sep 2024 23:20:08 +0000
- Message-id: <E1snng0-00GUFJ-Ox@fasolo.debian.org>
- Reply-to: Andreas Beckmann <anbe@debian.org>
Source: freecdb Source-Version: 0.78 Done: Andreas Beckmann <anbe@debian.org> We believe that the bug you reported is fixed in the latest version of freecdb, 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 1074965@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann <anbe@debian.org> (supplier of updated freecdb 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: SHA256 Format: 1.8 Date: Tue, 10 Sep 2024 01:00:53 +0200 Source: freecdb Architecture: source Version: 0.78 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Andreas Beckmann <anbe@debian.org> Closes: 1074965 Changes: freecdb (0.78) unstable; urgency=medium . * QA upload. * Fix FTBFS with GCC 14. (Closes: #1074965) Checksums-Sha1: 19d2475139511a846dbe1d3f2dc71a4dfed05dce 1531 freecdb_0.78.dsc 00eeb00cbd3a4c23d8dd4be8fec9fd1693d85b99 218252 freecdb_0.78.tar.xz 13b4861c5b820f94cfca968d727383e169a34e67 5335 freecdb_0.78_source.buildinfo Checksums-Sha256: 277323b8e523a4bc03928796687829eefe03c9cccfa27601a2f8e3a275620356 1531 freecdb_0.78.dsc bd5e3bf34c1391647dd32e97d67be4a4a537d0ac96728ac6e48ef33ea3373ec9 218252 freecdb_0.78.tar.xz cacee07d989944f83d9c4aa42686f382014dcbe4bc3b34e747d3aa9b827e961e 5335 freecdb_0.78_source.buildinfo Files: f1227576eca60c92f294e1d05f2fa7f7 1531 utils optional freecdb_0.78.dsc 2a678e4c9f068a87b181792f5fca3a6c 218252 utils optional freecdb_0.78.tar.xz 9b98efce9c1a21371b96aa20dfb15c8a 5335 utils optional freecdb_0.78_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmbffoQQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCPXJD/4gvB0R7gqG67P+RltIp6DI092EAFcgO7/4 8DAruEEitGF5E7iFon3aPjk2sjXxhk1e/G3WpTsz47VY1PehInc1jqJQiTyiuO0A vAVN5R5dlvW26kd4By1VywCbQAEM/1TJuQebOCuW4kd65yASacL55sP1nkLegYYv Z0nlMuvAGQxoaRk7t5MTERtxbVcIr0UHMOQqHrp4fkUBg10namQj+CAgI43hhCoe ntw6Ekdol17lLpyXwC1eDt6PDqktQ9g/czhcI9wQyyT+kUIzs0uCaS2odFwZrGvH 6jV4Orvh6NxM+w/eEQal5rx94zxpnKwDs7hjT/2wes9NCTE7+zVrXiFLFRGb97lR 5phu3qcla2O086Ke/bSDzlwFEgyAqMMHUiRwiQ1Y8YUiDsutVpwmHL32ROMcp/X7 bk6O26VTOppYjVzyaIm2iyET563Ewcfg/KmwKCCSGnb8U1AVN5HYNZ/uUgcSsPNP i2/gqMv3YnyfF661SMO2+TqsD5MIUX1rMlOX9RIVPouahGTpp2WykGa1Jsj4IvXL RTIp70ntQlgbNzWqS+ph3M4ZDX5HJGImkzzShV75IzUiFuv3wFtfiQ9wdanrBvH8 hSf29hMtZx8YiotaUM7lNE94vOC6x3tqNoENvsYmD4xAH9kAczaKpPFpqbGsa8q0 CWviHyI33g== =0Ips -----END PGP SIGNATURE-----Attachment: pgpyKlTqlc3iu.pgp
Description: PGP signature
--- End Message ---