Your message dated Wed, 22 Oct 2025 11:35:13 +0000
with message-id <[email protected]>
and subject line Bug#1098165: fixed in xsane 0.999-13
has caused the Debian Bug report #1098165,
regarding xsane: 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.)


-- 
1098165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098165
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:xsane
Version: 0.999-12.2
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/xsane_0.999-12.2_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 ());
      |                                    ~~~~~~~~~~~~~~~~~
xsane-fax-project.c: In function ‘xsane_fax_project_save’:
xsane-fax-project.c:501:58: warning: ‘__builtin___snprintf_chk’ output 
truncated before the last format character [-Wformat-truncation=]
  501 |     snprintf(buf, 32, "%s@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@", 
xsane.fax_status); /* fill 32 characters status line */
      |                                                          ^
In function ‘snprintf’,
    inlined from ‘xsane_fax_project_save’ at xsane-fax-project.c:501:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note: 
‘__builtin___snprintf_chk’ output 33 or more bytes into a destination of size 32
   68 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   69 |                                    __glibc_objsize (__s), __fmt,
      |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   70 |                                    __va_arg_pack ());
      |                                    ~~~~~~~~~~~~~~~~~
xsane-fax-project.c: In function ‘xsane_fax_project_save’:
xsane-fax-project.c:484:39: warning: ‘%s’ directive output may be truncated 
writing up to 4095 bytes into a region of size 253 [-Wformat-truncation=]
  484 |     snprintf(buf, sizeof(buf), "%s %s %s\n", ERR_DURING_SAVE, 
ERR_CREATE_SECURE_FILE, filename);
      |                                       ^~                                
              ~~~~~~~~
In function ‘snprintf’,
    inlined from ‘xsane_fax_project_save’ at xsane-fax-project.c:484:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note: 
‘__builtin___snprintf_chk’ output 4 or more bytes (assuming 4099) into a 
destination of size 255
   68 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   69 |                                    __glibc_objsize (__s), __fmt,
      |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   70 |                                    __va_arg_pack ());
      |                                    ~~~~~~~~~~~~~~~~~
xsane-viewer.c:281:5: warning: ‘__builtin_strncpy’ specified bound 1024 equals 
destination size [-Wstringop-truncation]
  281 |     strncpy(outputfilename, preferences.filename, 
sizeof(outputfilename));
      |     ^
xsane-viewer.c:277:5: warning: ‘__builtin_strncpy’ specified bound 1024 equals 
destination size [-Wstringop-truncation]
  277 |     strncpy(outputfilename, v->output_filename, sizeof(outputfilename));
      |     ^
xsane-fax-project.c: In function ‘xsane_fax_entry_insert_callback’:
xsane-fax-project.c:931:45: warning: ‘%s’ directive output may be truncated 
writing up to 4095 bytes into a region of size 1022 [-Wformat-truncation=]
  931 |           snprintf(buf, sizeof(buf), "%s %s %s\n", ERR_DURING_SAVE, 
ERR_CREATE_SECURE_FILE, destpath);
      |                                             ^~                          
                    ~~~~~~~~
In function ‘snprintf’,
    inlined from ‘xsane_fax_entry_insert_callback’ at 
xsane-fax-project.c:931:11:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note: 
‘__builtin___snprintf_chk’ output 4 or more bytes (assuming 4099) into a 
destination of size 1024
   68 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   69 |                                    __glibc_objsize (__s), __fmt,
      |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   70 |                                    __va_arg_pack ());
      |                                    ~~~~~~~~~~~~~~~~~
xsane-viewer.c: In function ‘xsane_viewer_read_image.isra’:
xsane-viewer.c:2312:46: warning: ‘%s’ directive output may be truncated writing 
up to 4095 bytes into a region of size 251 [-Wformat-truncation=]
 2312 |       snprintf(buf, sizeof(buf), "%s\n%s %s: %s\n", ERR_CMS_CONVERSION, 
ERR_CMS_OPEN_ICM_FILE, CMS_SCANNER_ICM, image_info.icm_profile);
      |                                              ^~                         
                                        ~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/stdio.h:970,
                 from xsane.h:47:
In function ‘snprintf’,
    inlined from ‘xsane_viewer_read_image.isra’ at xsane-viewer.c:2312:7:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note: 
‘__builtin___snprintf_chk’ output 6 or more bytes (assuming 4101) into a 
destination of size 255
   68 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   69 |                                    __glibc_objsize (__s), __fmt,
      |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   70 |                                    __va_arg_pack ());
      |                                    ~~~~~~~~~~~~~~~~~
make[2]: Leaving directory '/build/reproducible-path/xsane-0.999/src'
make[1]: *** [Makefile:63: all-recursive] Error 1
make[1]: Leaving directory '/build/reproducible-path/xsane-0.999'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: xsane
Source-Version: 0.999-13
Done: Jörg Frings-Fürst <[email protected]>

We believe that the bug you reported is fixed in the latest version of
xsane, 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.
Jörg Frings-Fürst <[email protected]> (supplier of updated xsane 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: Fri, 17 Oct 2025 13:16:30 +0200
Source: xsane
Architecture: source
Version: 0.999-13
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst <[email protected]>
Changed-By: Jörg Frings-Fürst <[email protected]>
Closes: 1098165
Changes:
 xsane (0.999-13) unstable; urgency=medium
 .
   * debian/rules:
     - Fix/Add -std=gnu17 to CFLAGS to fix FTBFS with GCC-15 (Closes: #1098165).
   * debian/control:
     - Declare compliance with Debian Policy 4.7.2.0 (No changes needed).
     - Change VCS-* to the new URL.
   * debian/copyright:
     - Add year 2025 to myself.
     - Add Mattia Rizzolo and Boyuan Yang to debian/*.
Checksums-Sha1:
 1df9cb90185d46cc7e50c336db94fe6542bfaa67 1801 xsane_0.999-13.dsc
 deac67e5aaa63331108e934bc532ab865c7f72df 131512 xsane_0.999-13.debian.tar.xz
 48fd0bba72e446105d7d0fb9fb0a9a69c7dcf791 5522 xsane_0.999-13_source.buildinfo
Checksums-Sha256:
 71e3697a3151f873f55466ff240729781d02b8f0575fa8fc46310e21f43f2242 1801 
xsane_0.999-13.dsc
 d8392dddd5842434f25965e2e4bea99011bf0c15e63c4c923e1be038044404b1 131512 
xsane_0.999-13.debian.tar.xz
 e28598e52d28323d009ffa7e64d3981a59c5e0b040485c1436d1c70642e1e006 5522 
xsane_0.999-13_source.buildinfo
Files:
 8129d16dff6067742152f8ce2eeceaaf 1801 graphics optional xsane_0.999-13.dsc
 6e052e68f710bd7fa54eadea4c78c584 131512 graphics optional 
xsane_0.999-13.debian.tar.xz
 7a1805e7f0323aab69412a9902586ff9 5522 graphics optional 
xsane_0.999-13_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmj4vPgQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFFlpDAC+h7+xDKGVoFk5IdvJvgkqpU+c65MQ6ZKi
QQIDRuWFwVGji7tXRQKAzlxx7ZIdOkW3mXyiuOb6gqgUlOGQl2uTxjFsLsW/7e9H
GEz02MrpIfG35MYDKAd1xUkJJ6dfYg5NEyu/6/8hNNSoAhoXIZ5PxKMhMLcgOzw0
ODMCkNjvxPmiHPuTfxXmU2K/Wy0gPfmJHZA6a95KRLC6bBsvKql/ZVaoC7402/eQ
IU3u/WTkAK4xgpNuxlpCo3jBOmqs8exFvUcOsK9LFaI7zQBCfhtVbKaF4uxENckQ
u+CtaJvcMO73uPDOvDLiRwyfmY1TYNqgcOUv0+Ec1+7Ofq7vuu7V9Saon6Pu1/Am
/zFN+iTFJjczb/+sg2z/eRnUaWsY3iQZdmgtZYzthUJjPVc8cWlu8Lxriad868cd
j8iPR82C6/0Aqeu+mEG5Cuhb6RNtG9wUp6z7Vs0etTOudhzNQlNGdqQcrn3Ye1SE
GZQi/yQg6j0EtOU25SdXJIn/8DNTyxI=
=bWvn
-----END PGP SIGNATURE-----

Attachment: pgp3i6pAvF5mq.pgp
Description: PGP signature


--- End Message ---

Reply via email to