Your message dated Fri, 26 Sep 2025 17:49:39 +0000 with message-id <E1v2CZf-0014dU-32@fasolo.debian.org> and subject line Bug#1097417: fixed in mpack 1.6-19 has caused the Debian Bug report #1097417, regarding mpack: 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 owner@bugs.debian.org immediately.) -- 1097417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097417 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: mpack: ftbfs with GCC-15
- From: Matthias Klose <doko@debian.org>
- Date: Mon, 17 Feb 2025 17:38:22 +0000
- Message-id: <E1tk54Y-009NPO-SC@paradis.debian.org>
Package: src:mpack Version: 1.6-18 Severity: important Tags: sid forky User: debian-gcc@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/mpack_1.6-18_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 [...] md5c.c: At top level: md5c.c:277:13: error: conflicting types for ‘Encode’; have ‘void(unsigned char *, UINT4 *, unsigned int)’ {aka ‘void(unsigned char *, unsigned int *, unsigned int)’} 277 | static void Encode (unsigned char *output, UINT4 *input, unsigned int len) | ^~~~~~ md5c.c:49:13: note: previous declaration of ‘Encode’ with type ‘void(void)’ 49 | static void Encode PROTO_LIST | ^~~~~~ md5c.c:292:13: error: conflicting types for ‘Decode’; have ‘void(UINT4 *, unsigned char *, unsigned int)’ {aka ‘void(unsigned int *, unsigned char *, unsigned int)’} 292 | static void Decode (UINT4 *output, unsigned char *input, unsigned int len) | ^~~~~~ md5c.c:51:13: note: previous declaration of ‘Decode’ with type ‘void(void)’ 51 | static void Decode PROTO_LIST | ^~~~~~ md5c.c:304:13: error: conflicting types for ‘MD5_memcpy’; have ‘void(unsigned char *, unsigned char *, unsigned int)’ 304 | static void MD5_memcpy (POINTER output, POINTER input, unsigned int len) | ^~~~~~~~~~ md5c.c:53:13: note: previous declaration of ‘MD5_memcpy’ with type ‘void(void)’ 53 | static void MD5_memcpy PROTO_LIST ((POINTER, POINTER, unsigned int)); | ^~~~~~~~~~ md5c.c:314:13: error: conflicting types for ‘MD5_memset’; have ‘void(unsigned char *, int, unsigned int)’ 314 | static void MD5_memset (POINTER output, int value, unsigned int len) | ^~~~~~~~~~ md5c.c:54:13: note: previous declaration of ‘MD5_memset’ with type ‘void(void)’ 54 | static void MD5_memset PROTO_LIST ((POINTER, int, unsigned int)); | ^~~~~~~~~~ md5c.c:48:13: warning: ‘MD5Transform’ used but never defined 48 | static void MD5Transform PROTO_LIST ((UINT4 [4], unsigned char [64])); | ^~~~~~~~~~~~ md5c.c:49:13: warning: ‘Encode’ used but never defined 49 | static void Encode PROTO_LIST | ^~~~~~ md5c.c:51:13: warning: ‘Decode’ used but never defined 51 | static void Decode PROTO_LIST | ^~~~~~ md5c.c:53:13: warning: ‘MD5_memcpy’ used but never defined 53 | static void MD5_memcpy PROTO_LIST ((POINTER, POINTER, unsigned int)); | ^~~~~~~~~~ md5c.c:54:13: warning: ‘MD5_memset’ used but never defined 54 | static void MD5_memset PROTO_LIST ((POINTER, int, unsigned int)); | ^~~~~~~~~~ make[2]: *** [Makefile:457: md5c.o] Error 1 make[2]: *** Waiting for unfinished jobs.... codes.c: In function ‘md5contextTo64’: codes.c:107:5: error: too many arguments to function ‘MD5Final’; expected 0, have 2 107 | MD5Final(digest, context); | ^~~~~~~~ ~~~~~~ In file included from codes.c:42: md5.h:68:6: note: declared here 68 | void MD5Final PROTO_LIST ((unsigned char [16], MD5_CTX *)); | ^~~~~~~~ codes.c: In function ‘md5digest’: codes.c:130:5: error: too many arguments to function ‘MD5Init’; expected 0, have 1 130 | MD5Init(&context); | ^~~~~~~ ~~~~~~~~ md5.h:65:6: note: declared here 65 | void MD5Init PROTO_LIST ((MD5_CTX *)); | ^~~~~~~ codes.c:133:9: error: too many arguments to function ‘MD5Update’; expected 0, have 3 133 | MD5Update(&context, buf, nbytes); | ^~~~~~~~~ ~~~~~~~~ md5.h:66:6: note: declared here 66 | void MD5Update PROTO_LIST | ^~~~~~~~~ make[2]: *** [Makefile:457: codes.o] Error 1 make[2]: Leaving directory '/build/reproducible-path/mpack-1.6' make[1]: *** [Makefile:338: all] Error 2 make[1]: Leaving directory '/build/reproducible-path/mpack-1.6' dh_auto_build: error: make -j8 returned exit code 2 make: *** [debian/rules:6: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
- To: 1097417-close@bugs.debian.org
- Subject: Bug#1097417: fixed in mpack 1.6-19
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Fri, 26 Sep 2025 17:49:39 +0000
- Message-id: <E1v2CZf-0014dU-32@fasolo.debian.org>
- Reply-to: Andreas Beckmann <anbe@debian.org>
Source: mpack Source-Version: 1.6-19 Done: Andreas Beckmann <anbe@debian.org> We believe that the bug you reported is fixed in the latest version of mpack, 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 1097417@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann <anbe@debian.org> (supplier of updated mpack 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 ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 26 Sep 2025 19:26:51 +0200 Source: mpack Architecture: source Version: 1.6-19 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Andreas Beckmann <anbe@debian.org> Closes: 1097417 1100862 1100883 Changes: mpack (1.6-19) unstable; urgency=medium . * QA upload. * Fix building with GCC 15. (Closes: #1097417) * Editorial manpage changes, thanks to Bjarni Ingi Gislason. (Closes: #1100862, #1100883) * Drop redundant Rules-Requires-Root: no. Checksums-Sha1: 9759a4c7bafe47501b468892ffa031775f033ebc 1791 mpack_1.6-19.dsc c2492b1b54409ede306fb5deda3309231fc80a36 14524 mpack_1.6-19.debian.tar.xz e1be2f0c4266e64e9edabb57676480addd107c7d 5296 mpack_1.6-19_source.buildinfo Checksums-Sha256: 58a1b10b1e83e6a1b8ee576963dbc3f1d191bf857cd69476bd0ae606b2c587f6 1791 mpack_1.6-19.dsc bbb2f2a686609a1cd9608104cc693a8ac3c924254fd98e4702db5d2bd3fd4cd2 14524 mpack_1.6-19.debian.tar.xz ae75dd8f32ede4f8aed5b2257f50e441df59920d507d9ef1617b238f48230fd0 5296 mpack_1.6-19_source.buildinfo Files: 19db6c6684b21b388f239e249153cd56 1791 mail optional mpack_1.6-19.dsc 4f634d20cd08964360890f57f09ba5dd 14524 mail optional mpack_1.6-19.debian.tar.xz 1da8134fdc85314692bd80fc39c2e1d5 5296 mail optional mpack_1.6-19_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmjWzUsQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCHqoD/0aJ/8jGc+IQUJsREhMKZjSNa8XBd3Y9lhY yHZsel314SNQHxC6TjwYW9BVN4cxjVy0SxuzYNVLHUnPKAo6TmJDxE+/orpK2pbl 5u/7hNa82HTF/fAtfEzfQ5kC3OTSRzAa1My+TrBKgkMfNqA3zFGDC8L0qP2/woge rTvKYM+hRQfeWNrAiKYzWRaEdgulDbgrL/+yl3dphnLTM3SAb2m8YUJxLvOSL9XB m3unwrazO0UAcVhq9KMkftsalDzVYhB9Sz4qVFJEWci5+M07qoZW+mXUG7nadDvW o5WaX5gDhYyBlFfhkfAtX+FtP4GtO3TS9716OhCtcoffvg1XS0BH68PEyDY14dnb MvpsLQYdCqhkEuKonNl44HxWkpO1uKhEfUD26jek7Emh2zb4jhjcSfuk/oiiLppn 8y5/2bp4sCETCqWjaeT9uzmGJ0pfdHPwXFV1HGVvKGXiTwd0x2u5jv7F0W7LjQxh CZ6wusjFTiy49YUvNc6jYDlQDuCCVMIqh7108WxQEcPrF6ho7WqiRtrFqwHWx8+m 61Spoj4mISShluJXdjX+6+c7TRPRVJ2DeQz16WJyNIQ/M35GH1RI0fZvyZ/uB9cD SPtSoraPcs82jLDigTcovjqFSbQsQ9c6WD1dmWhBZuH1uE3yDRgh/qcsfSQ1uvpu 1lBWuGbGbQ== =UeS2 -----END PGP SIGNATURE-----Attachment: pgp5YgYZUedhw.pgp
Description: PGP signature
--- End Message ---