Your message dated Sat, 02 Nov 2024 05:22:47 +0000
with message-id <e1t76b1-007mvk...@fasolo.debian.org>
and subject line Bug#1075531: fixed in spectools 201601r1-6
has caused the Debian Bug report #1075531,
regarding spectools: 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.)
--
1075531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:spectools
Version: 201601r1-5
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/spectools_201601r1-5_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
[...]
| ^~
In function ‘snprintf’,
inlined from ‘ubertooth_u1_device_scan’ at ubertooth_hw_u1.c:261:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note: ‘__builtin_snprintf’
output between 1 and 4097 bytes into a destination of size 64
54 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
wispy_hw_gen1.c: In function ‘wispy1_usb_device_scan’:
wispy_hw_gen1.c:227:61: warning: ‘%s’ directive output may be truncated writing
up to 4096 bytes into a region of size 64 [-Wformat-truncation=]
227 | snprintf(auxpair->bus, 64, "%s",
bus->dirname);
| ^~
In file included from /usr/include/stdio.h:964,
from wispy_hw_gen1.c:28:
In function ‘snprintf’,
inlined from ‘wispy1_usb_device_scan’ at wispy_hw_gen1.c:227:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note: ‘__builtin_snprintf’
output between 1 and 4097 bytes into a destination of size 64
54 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
wispy_hw_gen1.c: In function ‘wispy1_usb_device_scan’:
wispy_hw_gen1.c:228:61: warning: ‘%s’ directive output may be truncated writing
up to 4096 bytes into a region of size 64 [-Wformat-truncation=]
228 | snprintf(auxpair->dev, 64, "%s",
dev->filename);
| ^~
In function ‘snprintf’,
inlined from ‘wispy1_usb_device_scan’ at wispy_hw_gen1.c:228:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note: ‘__builtin_snprintf’
output between 1 and 4097 bytes into a destination of size 64
54 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
wispy_hw_24x.c: In function ‘wispy24x_usb_device_scan’:
wispy_hw_24x.c:274:61: warning: ‘%s’ directive output may be truncated writing
up to 4096 bytes into a region of size 64 [-Wformat-truncation=]
274 | snprintf(auxpair->bus, 64, "%s",
bus->dirname);
| ^~
In file included from /usr/include/stdio.h:964,
from wispy_hw_24x.c:17:
In function ‘snprintf’,
inlined from ‘wispy24x_usb_device_scan’ at wispy_hw_24x.c:274:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note: ‘__builtin_snprintf’
output between 1 and 4097 bytes into a destination of size 64
54 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
wispy_hw_24x.c: In function ‘wispy24x_usb_device_scan’:
wispy_hw_24x.c:275:61: warning: ‘%s’ directive output may be truncated writing
up to 4096 bytes into a region of size 64 [-Wformat-truncation=]
275 | snprintf(auxpair->dev, 64, "%s",
dev->filename);
| ^~
In function ‘snprintf’,
inlined from ‘wispy24x_usb_device_scan’ at wispy_hw_24x.c:275:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:54:10: note: ‘__builtin_snprintf’
output between 1 and 4097 bytes into a destination of size 64
54 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: spectools
Source-Version: 201601r1-6
Done: Petter Reinholdtsen <p...@debian.org>
We believe that the bug you reported is fixed in the latest version of
spectools, 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.
Petter Reinholdtsen <p...@debian.org> (supplier of updated spectools 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: SHA256
Format: 1.8
Date: Sat, 02 Nov 2024 05:58:38 +0100
Source: spectools
Architecture: source
Version: 201601r1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Petter Reinholdtsen <p...@debian.org>
Closes: 1075531
Changes:
spectools (201601r1-6) unstable; urgency=medium
.
* QA upload.
.
* Fixed build problems with GCC 14 (Closes: #1075531).
* Renamed Appstream metainfo XML to file name based on ID.
* Tracked down and added upstream homepage and contact.
Checksums-Sha1:
ae819347edf485b08e94b2d0b71a416048385f73 1912 spectools_201601r1-6.dsc
4f14e23f3207a36663426d4bd00cd5846d3c2ad3 12184
spectools_201601r1-6.debian.tar.xz
4660eb66e5964c11627626677e3fdb3933da7d51 6527
spectools_201601r1-6_source.buildinfo
Checksums-Sha256:
38f94d718f4d8c18f6fc939eeab7612d0165fc0c4c06fb8b0b60be50944235d4 1912
spectools_201601r1-6.dsc
6e7b2a0b0c80937adec1bc665814fe8bf49701e90583db88f5a47d33c81df688 12184
spectools_201601r1-6.debian.tar.xz
444f7cc97e0df7c4c480886cfb4afdccb4d4bdd282576b79f6e14354147ee23d 6527
spectools_201601r1-6_source.buildinfo
Files:
2701618d78f9de1dd0acf04ed315a340 1912 electronics optional
spectools_201601r1-6.dsc
15664cd97f5369d020d4e39fc1067c23 12184 electronics optional
spectools_201601r1-6.debian.tar.xz
3d508e2412b73309886bdb7591ee1d59 6527 electronics optional
spectools_201601r1-6_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmclsf0ACgkQgSgKoIe6
+w604hAAl7CrcX0GVvClTyo4HVJvZuf/IgSTO9e2ubleS0XKSyxdB4cG2qQU42f8
B+6Ypuwt8VVFCEoEc2TnRZvYou7QU9zlObnXll+3aPCBg3KFU22Q/naQ/gTK5SZk
wvBniG+tM6eh8QJ2LVa6d5Pig7ohkzhzMdCjTV7UKIGHBz0VH9vxjWHv3VxtaVgz
jnFvkDVm49aABU689cFYBSsiu+i6n+giHaZuoboQUrNW/gaPVWWirxMLqwMGd0b8
U/jEsLintuIyICZg1jGGGKImPmxkPm22KaPUbK+piiA/CeKZJP6u0y5SFMqS6gFq
sckY+LLa2ZighS0J75tP3w8fgMKJbG1K2xmfR5w293onmHQOa2kkPvoYIZ6VnNtE
F1K6ySzFQlRc76qiLCpmtnuZ7igT8shVuGclXBDeZpUzJFO0Wd95tg9//FXH2ckX
b3zbyjIJllRlTfRl/xcpUMj5lSCt5GTW8iQekk46sf/D0TQOngP8JH9haSpJo09D
hri9UeMRBNRgMe5Q4QAhHLthiFyN1G/uJqQ+Fuqpkr+IaMfo1MWDVuj7sTun3+b1
nyqdqcMhUGgvCFN0pE0Es23XQGeyvtfzumQSbUVVlUIiHFLBgRIUjRonh/NnAQ/1
xQ+F/KRysYfXaEWbNuY01rjaCQqsP4my7gog2XLPt2qRARc4qLw=
=+PUa
-----END PGP SIGNATURE-----
pgpsA1ZJUfbS9.pgp
Description: PGP signature
--- End Message ---
