Your message dated Fri, 27 Mar 2026 02:33:43 +0000
with message-id <[email protected]>
and subject line Bug#1098189: fixed in yiyantang 0.7.0-11
has caused the Debian Bug report #1098189,
regarding yiyantang: 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.)


-- 
1098189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098189
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:yiyantang
Version: 0.7.0-10
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/yiyantang_0.7.0-10_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

[...]
xmalloc.c:35:7: note: ‘malloc’ is declared in header ‘<stdlib.h>’
xmalloc.c:36:7: warning: conflicting types for built-in function ‘realloc’; 
expected ‘void *(void *, long unsigned int)’ [-Wbuiltin-declaration-mismatch]
   36 | VOID *realloc ();
      |       ^~~~~~~
xmalloc.c:36:7: note: ‘realloc’ is declared in header ‘<stdlib.h>’
xmalloc.c:37:6: warning: conflicting types for built-in function ‘free’; 
expected ‘void(void *)’ [-Wbuiltin-declaration-mismatch]
   37 | void free ();
      |      ^~~~
xmalloc.c:37:6: note: ‘free’ is declared in header ‘<stdlib.h>’
xmalloc.c: In function ‘fixup_null_alloc’:
xmalloc.c:71:1: warning: old-style function definition [-Wold-style-definition]
   71 | fixup_null_alloc (n)
      | ^~~~~~~~~~~~~~~~
xmalloc.c:78:9: error: too many arguments to function ‘malloc’; expected 0, 
have 1
   78 |     p = malloc ((size_t) 1);
      |         ^~~~~~  ~~~~~~~~~~
xmalloc.c:35:7: note: declared here
   35 | VOID *malloc ();
      |       ^~~~~~
xmalloc.c: In function ‘xmalloc’:
xmalloc.c:87:1: warning: old-style function definition [-Wold-style-definition]
   87 | xmalloc (n)
      | ^~~~~~~
xmalloc.c:92:7: error: too many arguments to function ‘malloc’; expected 0, 
have 1
   92 |   p = malloc (n);
      |       ^~~~~~  ~
xmalloc.c:35:7: note: declared here
   35 | VOID *malloc ();
      |       ^~~~~~
xmalloc.c: In function ‘xcalloc’:
xmalloc.c:101:1: warning: old-style function definition [-Wold-style-definition]
  101 | xcalloc (n, s)
      | ^~~~~~~
xmalloc.c:106:7: error: too many arguments to function ‘calloc’; expected 0, 
have 2
  106 |   p = calloc (n, s);
      |       ^~~~~~  ~
xmalloc.c:34:7: note: declared here
   34 | VOID *calloc ();
      |       ^~~~~~
xmalloc.c: In function ‘xrealloc’:
xmalloc.c:117:1: warning: old-style function definition [-Wold-style-definition]
  117 | xrealloc (p, n)
      | ^~~~~~~~
xmalloc.c:123:7: error: too many arguments to function ‘realloc’; expected 0, 
have 2
  123 |   p = realloc (p, n);
      |       ^~~~~~~  ~
xmalloc.c:36:7: note: declared here
   36 | VOID *realloc ();
      |       ^~~~~~~
xmalloc.c: In function ‘xstrdup’:
xmalloc.c:132:1: warning: old-style function definition [-Wold-style-definition]
  132 | xstrdup (str)
      | ^~~~~~~
make[3]: *** [Makefile:201: xmalloc.o] Error 1
make[3]: *** Waiting for unfinished jobs....
loop.c: In function ‘loop’:
loop.c:118:33: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  118 |                                 write (ptym, ibuf, ret);
      |                                 ^~~~~~~~~~~~~~~~~~~~~~~
loop.c:163:41: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  163 |                                         write (STDOUT_FILENO, tbuf2, 
ret);
      |                                         
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[3]: Leaving directory '/build/reproducible-path/yiyantang-0.7.0/src'
make[2]: *** [Makefile:182: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/yiyantang-0.7.0'
make[1]: *** [Makefile:326: all-recursive-am] Error 2
make[1]: Leaving directory '/build/reproducible-path/yiyantang-0.7.0'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:13: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: yiyantang
Source-Version: 0.7.0-11
Done: xiao sheng wen <[email protected]>

We believe that the bug you reported is fixed in the latest version of
yiyantang, 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.
xiao sheng wen <[email protected]> (supplier of updated yiyantang 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, 27 Mar 2026 09:53:44 +0800
Source: yiyantang
Architecture: source
Version: 0.7.0-11
Distribution: unstable
Urgency: medium
Maintainer: xiao sheng wen <[email protected]>
Changed-By: xiao sheng wen <[email protected]>
Closes: 1098189
Changes:
 yiyantang (0.7.0-11) unstable; urgency=medium
 .
   * d/control:
       - delete Rules-Requires-Root: no
       - delete Priority: optional
   * Bump Standards-Version: 4.7.3
   * d/copyright:
       - update year info to 2026
       - fix old-fsf-address-in-copyright-file
   * d/rules: add export DEB_CFLAGS_MAINT_APPEND,
     Closes: #1098189, Thanks Adrian Bunk
Checksums-Sha1:
 ba52f04389cd9b2fb33423cbae7e93e9175e79c9 1812 yiyantang_0.7.0-11.dsc
 2901887732e3629ad8a521c1740caf2d8ccb21b4 6572 yiyantang_0.7.0-11.debian.tar.xz
 84e253accdacf4381126fff46aa473ff0a885555 6305 
yiyantang_0.7.0-11_source.buildinfo
Checksums-Sha256:
 00db33769643894c504dc2724b00e4368e109b5fba97b8979efec03d24da4db2 1812 
yiyantang_0.7.0-11.dsc
 bb4684ec2049c7fc372cf2856db220d30b24adc6eb328b1ea112aa7ba60e4adf 6572 
yiyantang_0.7.0-11.debian.tar.xz
 492cd7a2d483079e6034fc8794118513cffe4720d71885cf2f761e27dc3218f7 6305 
yiyantang_0.7.0-11_source.buildinfo
Files:
 2a83d0cc9a82494589642b8a74972058 1812 text optional yiyantang_0.7.0-11.dsc
 b0a147cca5a74574d516f0db556398fc 6572 text optional 
yiyantang_0.7.0-11.debian.tar.xz
 0b794408bf6f91d08da89fab54b01af8 6305 text optional 
yiyantang_0.7.0-11_source.buildinfo

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

iQIzBAEBCgAdFiEEvGv7H5NUQYeSuhtTJ2Egg8PSprAFAmnF5f0ACgkQJ2Egg8PS
prAzFxAAhdRTFzoXQ1VTQ0bIRRF4i0ZQbhi5WvuH89tpeSojyRdRZPbEXXTjR/8P
BoglITzPj4sPjmrt7hBvVgAy6JjNM0CaMhMZvZ8eUsdlZwI1VaJ1S3WmdOhMtpYW
G1Iyq7JHdgiW8a0o4Bt3KJPWQL4YA1l25+aNe5W2QEEI1/6TBKc156yS2yCDUMW+
fWgvRn4xhN+lYXMKmpOE6XZewtonIMmnlpazZ3chhLnrmsNUIvpEZJViv9XBSy4i
L+ms75eV7zJpnJLxRHZtzfM4/mjEN46uKLnTHR3I8BjRmebCJ1wFz7KAPmyfq3Mf
EgEJvHvGs13l5tfTkepVdV5rO2WWlf1/h948HJpa8tGC+/Ba/Z0uq3LCvrd+ZyZa
XdbsF0GpG6IJIvJaHvGrFJCwbuAJmJyheiXiES3r3BQXyC0Li3bHu6aC5eFv6JYJ
u7vsJ55EjWS4jlCjvY8y76dK1RClYQBf6H9Ny3uievgt4BxX9PqQ0uqJVAjkGW8u
VbDMFVdoo3PHhh9wS6b5sh5GpimP/nLp3bGas9aRttdye0NkMDhJ1Rbv6HgQRJqr
Q4giJuCpPYBgos1uFxPpzLuMjWWgt3gnPQljAPtCadagOcg/KnohTNT3Fx5eA1ax
JLt8dplHSufH4mpFRj4TnH/kc8MhPylXRYpYRbgp6VRKWZMzbSo=
=tjhp
-----END PGP SIGNATURE-----

Attachment: pgpxu9iRbWtn2.pgp
Description: PGP signature


--- End Message ---

Reply via email to