Your message dated Mon, 19 Aug 2024 07:43:50 +0000
with message-id <e1sfx3o-000f86...@fasolo.debian.org>
and subject line Bug#1075292: fixed in mpich 4.2.0-10
has caused the Debian Bug report #1075292,
regarding mpich: ftbfs with GCC-14
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.)
--
1075292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpich
Version: 4.2.0-6
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is 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-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/mpich_4.2.0-6_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
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-14/porting_to.html
[...]
- mpix_stream_isend__@Base 4.1
+#MISSING: 4.2.0-6# mpix_stream_isend__@Base 4.1
mpix_stream_isend_c_f08ts_@Base 4.2
mpix_stream_isend_f08ts_@Base 4.1
#MISSING: 4.2# mpix_stream_isend_f08ts_large_@Base 4.1
- mpix_stream_progress@Base 4.1
+#MISSING: 4.2.0-6# mpix_stream_progress@Base 4.1
mpix_stream_progress_@Base 4.1
- mpix_stream_progress__@Base 4.1
+#MISSING: 4.2.0-6# mpix_stream_progress__@Base 4.1
mpix_stream_progress_f08_@Base 4.1
- mpix_stream_recv@Base 4.1
+#MISSING: 4.2.0-6# mpix_stream_recv@Base 4.1
mpix_stream_recv_@Base 4.1
- mpix_stream_recv__@Base 4.1
+#MISSING: 4.2.0-6# mpix_stream_recv__@Base 4.1
mpix_stream_recv_c_f08ts_@Base 4.2
mpix_stream_recv_f08ts_@Base 4.1
#MISSING: 4.2# mpix_stream_recv_f08ts_large_@Base 4.1
- mpix_stream_send@Base 4.1
+#MISSING: 4.2.0-6# mpix_stream_send@Base 4.1
mpix_stream_send_@Base 4.1
- mpix_stream_send__@Base 4.1
+#MISSING: 4.2.0-6# mpix_stream_send__@Base 4.1
mpix_stream_send_c_f08ts_@Base 4.2
mpix_stream_send_f08ts_@Base 4.1
#MISSING: 4.2# mpix_stream_send_f08ts_large_@Base 4.1
- mpix_threadcomm_finish@Base 4.2
+#MISSING: 4.2.0-6# mpix_threadcomm_finish@Base 4.2
mpix_threadcomm_finish_@Base 4.2
- mpix_threadcomm_finish__@Base 4.2
+#MISSING: 4.2.0-6# mpix_threadcomm_finish__@Base 4.2
mpix_threadcomm_finish_f08_@Base 4.2
- mpix_threadcomm_free@Base 4.2
+#MISSING: 4.2.0-6# mpix_threadcomm_free@Base 4.2
mpix_threadcomm_free_@Base 4.2
- mpix_threadcomm_free__@Base 4.2
+#MISSING: 4.2.0-6# mpix_threadcomm_free__@Base 4.2
mpix_threadcomm_free_f08_@Base 4.2
- mpix_threadcomm_init@Base 4.2
+#MISSING: 4.2.0-6# mpix_threadcomm_init@Base 4.2
mpix_threadcomm_init_@Base 4.2
- mpix_threadcomm_init__@Base 4.2
+#MISSING: 4.2.0-6# mpix_threadcomm_init__@Base 4.2
mpix_threadcomm_init_f08_@Base 4.2
- mpix_threadcomm_start@Base 4.2
+#MISSING: 4.2.0-6# mpix_threadcomm_start@Base 4.2
mpix_threadcomm_start_@Base 4.2
- mpix_threadcomm_start__@Base 4.2
+#MISSING: 4.2.0-6# mpix_threadcomm_start__@Base 4.2
mpix_threadcomm_start_f08_@Base 4.2
- mpix_wait_enqueue@Base 4.1
+#MISSING: 4.2.0-6# mpix_wait_enqueue@Base 4.1
mpix_wait_enqueue_@Base 4.1
- mpix_wait_enqueue__@Base 4.1
+#MISSING: 4.2.0-6# mpix_wait_enqueue__@Base 4.1
mpix_wait_enqueue_f08_@Base 4.1
- mpix_waitall_enqueue@Base 4.1
+#MISSING: 4.2.0-6# mpix_waitall_enqueue@Base 4.1
mpix_waitall_enqueue_@Base 4.1
- mpix_waitall_enqueue__@Base 4.1
+#MISSING: 4.2.0-6# mpix_waitall_enqueue__@Base 4.1
mpix_waitall_enqueue_f08_@Base 4.1
pmpi_abort@Base 0
pmpi_abort_@Base 0
mv debian/.debhelper/generated/libmpich12/triggers.new
debian/.debhelper/generated/libmpich12/triggers
rm -f debian/mpich/DEBIAN/shlibs
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:101: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 4.2.0-10
Done: Alastair McKinstry <mckins...@debian.org>
We believe that the bug you reported is fixed in the latest version of
mpich, 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 1075...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry <mckins...@debian.org> (supplier of updated mpich 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: SHA256
Format: 1.8
Date: Mon, 19 Aug 2024 07:50:53 +0100
Source: mpich
Architecture: source
Version: 4.2.0-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Alastair McKinstry <mckins...@debian.org>
Closes: 1075292
Changes:
mpich (4.2.0-10) unstable; urgency=medium
.
* Fix FTBFS on amd64 due to symbols. Patch thanks to Gianfranco Costamagna
Closes: #1075292
* Drop unnset Depends from d/control
* Standards-Version: 4.7.0
Checksums-Sha1:
ce69111ec0a21624a209c380c074d716985426cc 2775 mpich_4.2.0-10.dsc
2233e8e330e56ae6eb88d457d94b1d097827a64a 351920 mpich_4.2.0-10.debian.tar.xz
Checksums-Sha256:
94dfc3200e1edc00f1c431019bad3abd7fd64a71355175a53c641539b8718f36 2775
mpich_4.2.0-10.dsc
244e3ae3311a53ce68b817c92c957a19bae566f82b5ba45034831a092af09941 351920
mpich_4.2.0-10.debian.tar.xz
Files:
e89b4c813d0acab9e087d1fd5eb5bef0 2775 devel optional mpich_4.2.0-10.dsc
4acca35d440b2abdbbd6724ec58a321e 351920 devel optional
mpich_4.2.0-10.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmbC7wkACgkQy+a7Tl2a
06WofQ/9H5UhZnmQRh1KqfGiIo8Oupgcg5KpU1tdYMA1AvmUkBPfYHfg7GAqQnft
C2E5XCC0t9VmU9uqw3jaF6oy/D+uUWH2gaJ5YB7WGmpBR3FzcTNFsXmLe8oPkwot
11VyGgC4uCZeH/UTpmTDpQ2tq5cNpO9gZhXLQHSsSCsti1gV9oRpKbNhjXjvpnBq
z9sIZvy4HEaW+DphK3a9thu8QCLwGP2v7TqopreGMNkWtzie+y4NQp201UuoF1Um
5yqf5nwZJ6dRHntGe+/nXJIBi5pPw0Gtizy7AZopQnovQVAo8daaev0Xbq1Igmf3
XnjTSqrIZ9Gcyk2d234e+6TtZeo49h0sEXfS1SIg7ENBgRV6oylijeqKMmNB7YGp
f7woix/GSmwyqbgN9N/3nvagVaCeHWBfp2S5H5lJ2sNy07MdwsDQW0JxthC2MDD0
cSVw5+4SSRCyTNVAIqdmgdRy/Z4Zyk8Tb3NxsMeSRWdb2N9mwKQF9Sx9Hi0faur9
VV7oq8pmQ+uYugaujiW6DzBd8aUV0lx3GYtSTsDnE9kSrJ0YZjqDDme1qJMcOB6K
ajqw96p31A5gVX1jhp8pt2vFo15clRiWLhzA/hdRmh3yeoO4qUnGKGuuMU654Bk+
NofjMZSW1DYPVPX4gTjlW/yfEJIWND4mHyWtyeNSQ6QG8rkGMF4=
=e5GJ
-----END PGP SIGNATURE-----
pgpIxu0dI5fIm.pgp
Description: PGP signature
--- End Message ---
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
