Your message dated Thu, 20 Mar 2025 14:41:13 +0000
with message-id <[email protected]>
and subject line Bug#1097868: fixed in secure-delete 3.1-11
has caused the Debian Bug report #1097868,
regarding secure-delete: 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.)


-- 
1097868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097868
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:secure-delete
Version: 3.1-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/secure-delete_3.1-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

[...]
        ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
Just run "make" and "make install"
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/reproducible-path/secure-delete-3.1'
dh_auto_build --buildsystem=makefile
        make -j1 "INSTALL=install --strip-program=true"
make[2]: Entering directory '/build/reproducible-path/secure-delete-3.1'
gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/secure-delete-3.1=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wl,-z,relro -Wl,-z,now -c sdel-lib.c
sdel-lib.c: In function ‘__sdel_random_buf’:
sdel-lib.c:86:9: warning: ignoring return value of ‘fread’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
   86 |         fread(buf, bufsize, 1, devrandom);
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/secure-delete-3.1=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wl,-z,relro -Wl,-z,now -o srm srm.c 
sdel-lib.o -lm
srm.c: In function ‘smash_it’:
srm.c:93:13: warning: ignoring return value of ‘getcwd’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
   93 |             getcwd(current_dir, 4096);
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~
gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/secure-delete-3.1=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wl,-z,relro -Wl,-z,now -o sfill 
sfill.c sdel-lib.o -lm
gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/secure-delete-3.1=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wl,-z,relro -Wl,-z,now -o sswap 
sswap.c sdel-lib.o -lm
sswap.c: In function ‘main’:
sswap.c:118:20: error: passing argument 2 of ‘signal’ from incompatible pointer 
type [-Wincompatible-pointer-types]
  118 |     signal(SIGINT, cleanup);
      |                    ^~~~~~~
      |                    |
      |                    void (*)(void)
In file included from sswap.c:30:
/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)
      |                                          ~~~~~~~~~~~~~~~^~~~~~~~~
sswap.c:66:6: note: ‘cleanup’ declared here
   66 | void cleanup() {
      |      ^~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
   72 | typedef void (*__sighandler_t) (int);
      |                ^~~~~~~~~~~~~~
sswap.c:119:21: error: passing argument 2 of ‘signal’ from incompatible pointer 
type [-Wincompatible-pointer-types]
  119 |     signal(SIGTERM, cleanup);
      |                     ^~~~~~~
      |                     |
      |                     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)
      |                                          ~~~~~~~~~~~~~~~^~~~~~~~~
sswap.c:66:6: note: ‘cleanup’ declared here
   66 | void cleanup() {
      |      ^~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
   72 | typedef void (*__sighandler_t) (int);
      |                ^~~~~~~~~~~~~~
sswap.c:120:20: error: passing argument 2 of ‘signal’ from incompatible pointer 
type [-Wincompatible-pointer-types]
  120 |     signal(SIGHUP, cleanup);
      |                    ^~~~~~~
      |                    |
      |                    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)
      |                                          ~~~~~~~~~~~~~~~^~~~~~~~~
sswap.c:66:6: note: ‘cleanup’ declared here
   66 | void cleanup() {
      |      ^~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
   72 | typedef void (*__sighandler_t) (int);
      |                ^~~~~~~~~~~~~~
make[2]: *** [Makefile:29: sswap] Error 1
make[2]: Leaving directory '/build/reproducible-path/secure-delete-3.1'
dh_auto_build: error: make -j1 "INSTALL=install --strip-program=true" returned 
exit code 2
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 25
make[1]: Leaving directory '/build/reproducible-path/secure-delete-3.1'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: secure-delete
Source-Version: 3.1-11
Done: Georges Khaznadar <[email protected]>

We believe that the bug you reported is fixed in the latest version of
secure-delete, 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.
Georges Khaznadar <[email protected]> (supplier of updated secure-delete 
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: Thu, 20 Mar 2025 14:44:28 +0100
Source: secure-delete
Architecture: source
Version: 3.1-11
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar <[email protected]>
Changed-By: Georges Khaznadar <[email protected]>
Closes: 1097868
Changes:
 secure-delete (3.1-11) unstable; urgency=medium
 .
   * fixed two compilation issues with gcc-15
     Closes: #1097868
Checksums-Sha1:
 528199d44330a6e21a2646b2f14f00c1959e80b0 1881 secure-delete_3.1-11.dsc
 a6d219315e1e73f9c359d4477bf7c94582bbd692 17208 
secure-delete_3.1-11.debian.tar.xz
 3c2c42b17b46516b59acd6e531ee2055e290db9d 6064 
secure-delete_3.1-11_amd64.buildinfo
Checksums-Sha256:
 1164f6819254c611c29bc0b9b61d895808c2da58a24adcfd39c3168836669b88 1881 
secure-delete_3.1-11.dsc
 4a6f843122e5d5115d31a461bc5f1bb3cec3ed565bc236cc8ad3679d5c44e960 17208 
secure-delete_3.1-11.debian.tar.xz
 be06db383fb0348b95e557ac849b11013cb7926a5dafe39b562bd61782ebffda 6064 
secure-delete_3.1-11_amd64.buildinfo
Files:
 f355b397760ccdfc7bd9c03a1f2ca2ea 1881 utils optional secure-delete_3.1-11.dsc
 0f9b222aee47c8e6b720458fe8e39542 17208 utils optional 
secure-delete_3.1-11.debian.tar.xz
 097b965990015932a6e9278b1d012856 6064 utils optional 
secure-delete_3.1-11_amd64.buildinfo

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

iQIzBAEBCgAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmfcIY4ACgkQHCgWkHE2
rjlulA/9EDIOkUG612sJhgCyaUXvlvsfXIlTcB582KOF5/68Qir67TaoV7jMc/s0
gJbRk4QOk6VIipDncAjyvL5JFOBy6dRaF/mKT3JL262frZD4RKkUfM+nZYGRNYSK
Dq5EcL5CMIArsdBTD3rDTXjuP8GFCHuDAtb+jKjVPhESR1Jte3pQRv3gcDIkahn4
LZx+SgW4ciKiSq4PV2OSMruoEjZykA+/7YJy6aWph8/GBlbI0HXqh/CqnOiHQxCa
2I6xluctaoaUljWIKipJvGbgQXrym2RnqlEwWKEoTXAUMeiOy9Hus1KA8JUnC36K
qh5MekzFutcifLdnaP2YTU5HOPFZaj8youkxITVp2xQEuIj8sh+kL34eEXjkXbIJ
v6PnNk59s8FdAM64DQxXaZROJK5ERrnCTUPndA0cXL+AZJRadupj+zee01Hj9ktJ
z+Wf6Bax2JJfTwpBQZTIyozsDNarJafFYm6DmvXUeboFX5k2lpBV01LhJEUfD9T7
aSrUkpEiBHa2/44Mz5KSTg4ImxirSxla2xBvoGcLCXUB2wmsQsqXMkRmWddiNKgd
URcr+mPXwEPIOheraiVwt0azeRGeWIXcFkpda2d9zm33jg9EC+Hj+DIgD3sB4X/i
sS1l/7JX42oy5Cm3y/xZrBf9e4Ety29xCyE2Js03ZWeGbDgdX2k=
=eDJu
-----END PGP SIGNATURE-----

Attachment: pgpKd_xHDmcIp.pgp
Description: PGP signature


--- End Message ---

Reply via email to