Your message dated Tue, 27 Aug 2024 22:19:04 +0000 with message-id <E1sj4Wm-00EijV-I5@fasolo.debian.org> and subject line Bug#1074814: fixed in aprx 2.9.1-3 has caused the Debian Bug report #1074814, regarding aprx: 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.) -- 1074814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074814 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: aprx: ftbfs with GCC-14
- From: Matthias Klose <doko@debian.org>
- Date: Wed, 03 Jul 2024 12:22:01 +0000
- Message-id: <E1sOyzp-0040MC-V8@paradis.debian.org>
Package: src:aprx Version: 2.9.1-2 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/aprx_2.9.1-2_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 [...] beacon.c: In function ‘beacon_it’: beacon.c:940:26: warning: overflow in conversion from ‘int’ to ‘char’ changes value from ‘240’ to ‘-16’ [-Woverflow] 940 | msg[1] = 0xF0; | ^~~~ beacon.c:954:37: warning: overflow in conversion from ‘int’ to ‘char’ changes value from ‘240’ to ‘-16’ [-Woverflow] 954 | bset->exec_buf[1] = 0xF0; | ^~~~ beacon.c:1054:40: warning: format ‘%p’ expects argument of type ‘void *’, but argument 2 has type ‘const struct aprx_interface *’ [-Wformat=] 1054 | printf("Beacon: aif=%p callsign='%s' src='%s' bm->dest='%s' bm->via='%s'\n", | ~^ | | | void * 1055 | aif, callsign, src, bm->dest, bm->via); | ~~~ | | | const struct aprx_interface * ttyreader.c: In function ‘aprx_cfmakeraw’: ttyreader.c:706:1: error: type of ‘f’ defaults to ‘int’ [-Wimplicit-int] 706 | aprx_cfmakeraw(t, f) | ^~~~~~~~~~~~~~ beacon.c: In function ‘beacon_childexit’: beacon.c:1232:27: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 1232 | write(1, buf, strlen(buf)); | ^~~~~~~~~~~~~~~~~~~~~~~~~~ make[1]: *** [Makefile:142: ttyreader.o] Error 1 make[1]: *** Waiting for unfinished jobs.... netax25.c: In function ‘discard_read_fd’: netax25.c:716:15: warning: ignoring return value of ‘read’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 716 | (void)read(fd, buf, sizeof(buf)); | ^~~~~~~~~~~~~~~~~~~~~~~~~~ netax25.c: In function ‘scan_linux_devices.isra’: netax25.c:337:11: warning: ‘__builtin_strncpy’ output may be truncated copying 15 bytes from a string of length 511 [-Wstringop-truncation] 337 | strncpy(ifr.ifr_name, s, IFNAMSIZ-1); | ^ In file included from /usr/include/string.h:548, from aprx.h:82, from aprsis.c:13: In function ‘memcpy’, inlined from ‘aprsis_sockread’ at aprsis.c:459:4, inlined from ‘aprsis_postpoll_’ at aprsis.c:696:10, inlined from ‘aprsis_main’ at aprsis.c:826:3, inlined from ‘aprsis_start’ at aprsis.c:1006:3: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: warning: ‘__builtin_memcpy’ specified bound between 18446744071562067968 and 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=] 29 | return __builtin___memcpy_chk (__dest, __src, __len, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 30 | __glibc_objsize0 (__dest)); | ~~~~~~~~~~~~~~~~~~~~~~~~~~ beacon.c: In function ‘fix_beacon_time’: beacon.c:700:31: warning: ‘%02d’ directive writing between 2 and 3 bytes into a region of size between 2 and 4 [-Wformat-overflow=] 700 | sprintf(hms, "%02d%02d%02dh", hour, min, sec); | ^~~~ beacon.c:700:22: note: directive argument in the range [-59, 59] 700 | sprintf(hms, "%02d%02d%02dh", hour, min, sec); | ^~~~~~~~~~~~~~~ In file included from /usr/include/stdio.h:964, from aprx.h:13, from beacon.c:11: In function ‘sprintf’, inlined from ‘fix_beacon_time’ at beacon.c:700:2: /usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: ‘__builtin___sprintf_chk’ output between 8 and 11 bytes into a destination of size 8 30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 31 | __glibc_objsize (__s), __fmt, | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 32 | __va_arg_pack ()); | ~~~~~~~~~~~~~~~~~ make[1]: Leaving directory '/<<PKGBUILDDIR>>' dh_auto_build: error: make -j8 returned exit code 2 make: *** [debian/rules:23: build] Error 25 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
- To: 1074814-close@bugs.debian.org
- Subject: Bug#1074814: fixed in aprx 2.9.1-3
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Tue, 27 Aug 2024 22:19:04 +0000
- Message-id: <E1sj4Wm-00EijV-I5@fasolo.debian.org>
- Reply-to: Dave Hibberd <hibby@debian.org>
Source: aprx Source-Version: 2.9.1-3 Done: Dave Hibberd <hibby@debian.org> We believe that the bug you reported is fixed in the latest version of aprx, 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 1074814@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dave Hibberd <hibby@debian.org> (supplier of updated aprx 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: Tue, 27 Aug 2024 23:06:29 +0100 Source: aprx Architecture: source Version: 2.9.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org> Changed-By: Dave Hibberd <hibby@debian.org> Closes: 1074814 Changes: aprx (2.9.1-3) unstable; urgency=medium . * Added patch for GCC14 FTBFS - Closes: #1074814 * d/control - Updated my details - Bumped standards Checksums-Sha1: 47ea9d307a48ddd62ec97e9810aef0cc9f499590 1578 aprx_2.9.1-3.dsc 8f162feb7a857d30efc2398966e936d17b6385b7 9256 aprx_2.9.1-3.debian.tar.xz 1653193ff05b395af19079d5661a990aed00f012 5505 aprx_2.9.1-3_amd64.buildinfo Checksums-Sha256: 0b3a62b67a28f3a93aad053a1485abf51f7bb706728d574795697b00072237d6 1578 aprx_2.9.1-3.dsc d26d1ffc671e13dcd583944590d9002a3f8b2745e63e26ff29cea8366526c97b 9256 aprx_2.9.1-3.debian.tar.xz ff817f6360aaafc9c9f24c0f745bdf7f81cd8f8db1ac71b6d173143a6d8646b3 5505 aprx_2.9.1-3_amd64.buildinfo Files: 7958d21381d50a1a1643319f56a08f62 1578 hamradio optional aprx_2.9.1-3.dsc 160553d4f1f56454bdf60ea3d32879b6 9256 hamradio optional aprx_2.9.1-3.debian.tar.xz c138278eba87d2cc9e67e7c30b11f0c4 5505 hamradio optional aprx_2.9.1-3_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEXk9UUZPolpyKWbgKA6H7ehkEdxsFAmbOTlUACgkQA6H7ehkE dxsgdwf/eh28T+GCIu5Mq6iTNmqnjX0U50K+MY12+CjYzqex9o1XNjpIuZTM3SfG bd4bjXRhmlmVVvXUa6zqtbMP4bq/cokNJ2ipU7SqVRLi19vtlI+yRiHcrqoBM4jf KMGIqUzYow5uxXh3XnHfkOmGbC8ViXDEw9hPiRfr0KRbFAwXTxKS83srpNcagUlb +r5nF2T/jYxpTJWHXgJIHPzAfIdnou4h7gS/HGnv6Sv8JDSC9z0aGzNMuuGKJFot QidmkoJ7HFs9nmig9IM7xwWSYc+NSMzcsK1HabgiGOlSwp1tlcV2Q389n7VgCsKK wbZ+MkDN28boGZ9mZMx87qec50w2ug== =zglS -----END PGP SIGNATURE-----Attachment: pgpIJTZ6XG7U1.pgp
Description: PGP signature
--- End Message ---