Your message dated Tue, 03 Jun 2025 15:15:44 +0000
with message-id <e1umtme-0003kv...@fasolo.debian.org>
and subject line Bug#1096551: fixed in dtach 0.9-8
has caused the Debian Bug report #1096551,
regarding dtach: 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 ow...@bugs.debian.org
immediately.)
--
1096551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dtach
Version: 0.9-7
Severity: important
Tags: sid forky
User: debian-...@lists.debian.org
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/dtach_0.9-7_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
[...]
attach.c: In function ‘attach_main’:
attach.c:203:26: error: passing argument 2 of ‘signal’ from incompatible
pointer type [-Wincompatible-pointer-types]
203 | signal(SIGWINCH, win_change);
| ^~~~~~~~~~
| |
| void (*)(void)
/usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void
(*)(int)’} but argument is of type ‘void (*)(void)’
88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler)
| ~~~~~~~~~~~~~~~^~~~~~~~~
attach.c:100:1: note: ‘win_change’ declared here
100 | win_change()
| ^~~~~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
72 | typedef void (*__sighandler_t) (int);
| ^~~~~~~~~~~~~~
attach.c:174:41: warning: ignoring return value of ‘fchdir’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
174 | fchdir(dirfd);
| ^~~~~~~~~~~~~
attach.c:218:9: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
218 | write(1, "\33[H\33[J", 6);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
attach.c:223:9: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
223 | write(s, &pkt, sizeof(struct packet));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
attach.c:229:9: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
229 | write(s, &pkt, sizeof(struct packet));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
attach.c:263:25: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
263 | write(1, buf, len);
| ^~~~~~~~~~~~~~~~~~
attach.c:290:25: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
290 | write(s, &pkt, sizeof(pkt));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
attach.c: In function ‘process_kbd’:
attach.c:115:17: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
115 | write(s, pkt, sizeof(struct packet));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
attach.c:125:17: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
125 | write(s, pkt, sizeof(struct packet));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
attach.c:131:17: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
131 | write(s, pkt, sizeof(struct packet));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
attach.c:145:9: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
145 | write(s, pkt, sizeof(struct packet));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
attach.c: In function ‘push_main’:
attach.c:319:41: warning: ignoring return value of ‘fchdir’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
319 | fchdir(dirfd);
| ^~~~~~~~~~~~~
make[1]: *** [<builtin>: attach.o] Error 1
make[1]: *** Waiting for unfinished jobs....
master.c: In function ‘master_main’:
master.c:582:41: warning: ignoring return value of ‘fchdir’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
582 | fchdir(dirfd);
| ^~~~~~~~~~~~~
master.c:656:25: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
656 | write(2, buf, len);
| ^~~~~~~~~~~~~~~~~~
master.c: In function ‘client_activity’:
master.c:381:25: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
381 | write(the_pty.fd, pkt.u.buf, pkt.len);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
master.c:422:33: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
422 | write(the_pty.fd, &c, 1);
| ^~~~~~~~~~~~~~~~~~~~~~~~
make[1]: Leaving directory '/build/reproducible-path/dtach-0.9'
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: dtach
Source-Version: 0.9-8
Done: Stefan Völkel <b...@bc-bd.org>
We believe that the bug you reported is fixed in the latest version of
dtach, 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 1096...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefan Völkel <b...@bc-bd.org> (supplier of updated dtach 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: SHA512
Format: 1.8
Date: Mon, 02 Jun 2025 19:58:29 +0000
Source: dtach
Architecture: source
Version: 0.9-8
Distribution: unstable
Urgency: low
Maintainer: Stefan Völkel <b...@bc-bd.org>
Changed-By: Stefan Völkel <b...@bc-bd.org>
Closes: 1096551
Changes:
dtach (0.9-8) unstable; urgency=low
.
* Fix ftbfs with GCC-15 (Closes: #1096551)
* Fix lintian old-fsf-address-in-copyright-file
* Updated to Policy version 4.7.2, no changes
* Fix licenserecon warnings
Checksums-Sha1:
319776ba3c2cd4c981c5bda05419a1450c24e359 1776 dtach_0.9-8.dsc
179f7640973d9062c9710519b9486c20903a423b 4540 dtach_0.9-8.debian.tar.xz
a4c45ed845359db6414d0c9e4060a709d1ab7806 5951 dtach_0.9-8_amd64.buildinfo
Checksums-Sha256:
c1f95346cbdb319436c94e653783593996caaa227ab95af86e18675dc1e9324e 1776
dtach_0.9-8.dsc
d5f1bddd2b6128c84431a4bbbe5d3569be867f0da4d8af91dc827ba83062ed92 4540
dtach_0.9-8.debian.tar.xz
17d9aae679c5656ec3ee94c412d6d68379c2d9841b7fd0a64dd8b360cfb66e11 5951
dtach_0.9-8_amd64.buildinfo
Files:
7679bdd365ba8a55fed90d494e4164a9 1776 misc optional dtach_0.9-8.dsc
aed425a2ead2dfb64bdb0a2b9d1219f9 4540 misc optional dtach_0.9-8.debian.tar.xz
298515b33f432df49fb19188d0402631 5951 misc optional dtach_0.9-8_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfAcX+forK514ixQbptwk2dokk9EFAmg+97wACgkQptwk2dok
k9EFyw//ZNyzvC2/coYQOyBw5dn/gCmx4oVy5c1IqO7aYp8v/SCXFtEnW/zrc8yd
YS9CFWfNpzDq0BxVtM72x7ITL0hFRbXrdg/MCkOJ4KousiwqO5SUBkwc18w5WuZw
ZREdrwurV2JZQRmYFCpA6+IX6C2OsgEBmvRFvIAyTxPbHegnpdtl/pSjJx++9qzC
GSr5bHbDm+Z3CWlZrKevcLnbwFTisO9GBBRa8W+UqAWjV+g0bNolo/6ROiE2aoWm
5DjeM+XLpOHa1mgQBvpDF71iOlfS9b6ZdoUEGAEawdJbRNZAGKDAj/XAT+LrzGZz
0+fTNQ4EKu+6kkZLSfV4+dVIzNVr6P4dx1wl2fyFzAb/FDprSrz1CGy/iXB1SsR4
Xpmt7hNQ7HBmFRHu0pGbEbaQSgbcsvLOf24MbSVufUTAd1MwchNCWzuGtblg8zYd
rFAvIo6afw49Z1rtkHnr1WPPHO5vdwpLsFimFMnMylaqtLBCYJFmBbHiirNAM2Hh
BETps05pHXwBBHVgs7fWz9wiVoHq4s/Jr34zFU4zZh0mBnWhhgljv9NaXKb1evCn
0E3l6wRBU+K1+dcD+Z9DbNtYmyM7NKti5Ie79IFglBrAbYKyiVfCnhoNyZkgKnRL
wPm9o1Z9lv0Ft1cMZyiZ8hQC2OoB47Ox87V1iEgb2WQsVPgHjjs=
=qyDg
-----END PGP SIGNATURE-----
pgpiSBUZbxXmx.pgp
Description: PGP signature
--- End Message ---
