Your message dated Wed, 23 Jul 2025 10:49:02 +0000
with message-id <[email protected]>
and subject line Bug#694307: fixed in mpi4py 4.1.0-1
has caused the Debian Bug report #694307,
regarding Please allow using mpi4py with MPICH2
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.)


-- 
694307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694307
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mpi4py
Version: 1.3+hg20120611-1

Presently mpi4py assumes Open MPI as MPI implentation.

Please allow using MPICH2 as well, as most packaged software in Debian does.

--- End Message ---
--- Begin Message ---
Source: mpi4py
Source-Version: 4.1.0-1
Done: Drew Parsons <[email protected]>

We believe that the bug you reported is fixed in the latest version of
mpi4py, 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.
Drew Parsons <[email protected]> (supplier of updated mpi4py 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: Wed, 23 Jul 2025 11:22:51 +0200
Source: mpi4py
Architecture: source
Version: 4.1.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: Drew Parsons <[email protected]>
Closes: 694307
Changes:
 mpi4py (4.1.0-1) experimental; urgency=medium
 .
   * New upstream release
   * build with MPI4PY_BUILD_MPIABI=1 to enable enhanced support for
     the MPI 5.0 standard ABI and the MPICH or Open MPI legacy ABIs
     Common ABI enables cross-support between OpenMPI and mpich,
     so Closes: #694307.
   * Build-Depends: pybuild-plugin-pyproject
     to build via pyproject.toml
   * update debian/rules
     - drop dh_auto_build override, use default mpicc wrapper
     - build docs before dh_auto_install, to ensure dh_auto_build has
       already been run
     - replace redundant overrides with execute_after_
     - remove redundant get-orig-dev-source
       (upstream now uses github not mercury hg for source repo)
   * debian patch doc_sphinx8.1_revert_PR629.patch reverts upstream
     PR#629 to enable doc build with sphinx 8.1.3.
     See upstream Issue#668.
Checksums-Sha1:
 a3e7a69b29a350c7d558f94ff73291a3e46e99e7 2553 mpi4py_4.1.0-1.dsc
 550f42c717c0a4bf9483f52d54f092cbb8238b32 498940 mpi4py_4.1.0.orig.tar.gz
 b9a621880ba13f24bc8d452c54168dc82d30085f 15784 mpi4py_4.1.0-1.debian.tar.xz
Checksums-Sha256:
 dd3a319de8fed75391b19cfc1c7a4ec27ac0b90cdae50b86fa375c17136cb119 2553 
mpi4py_4.1.0-1.dsc
 c46d32e7e29e03313ac62b34ce7442953589dce91fef2e518629247d53b6d9ea 498940 
mpi4py_4.1.0.orig.tar.gz
 2b804db89b12b9967ef04b336c61b09fe294912326168b84dd73565f0de6546b 15784 
mpi4py_4.1.0-1.debian.tar.xz
Files:
 94864ce2b81b07847f63256f2d427753 2553 python optional mpi4py_4.1.0-1.dsc
 566a292103b096c4b1fbd05c12b17f53 498940 python optional 
mpi4py_4.1.0.orig.tar.gz
 f4999f1af4f70f5e2002973cc4304299 15784 python optional 
mpi4py_4.1.0-1.debian.tar.xz

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

iQIzBAEBCgAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmiAt8kACgkQVz7x5L1a
AfrKyQ//dFtJih+UbAvjL8kLSR9ecI7/twIdDsf/ICWYcvixN9BjAyNWU0Oap1Rw
iOFnpJkMASuqQBGnc+MzuhUwLg03MCMf+sSOGs44AoMXRGKgqZe+emyHV8AmZBmU
b3KKSx63j/rCJZHeOlgXapM8fhA2BS88dIDryOoicTxeK+08nN+ms3Bq2TBYrR/Z
xg9T2RHKYeVe0MIGO9v/l0o5VyeUFZKNaOufgdWr6ijad1l3NbXq5th53Z19eiCB
zF1kmP28cT8cSURpzbfSJDYH/kqUIZoUdOruUegpeHTAW614d0Q9nUDJfLB9cwn2
b3N5rPiGHWTQxcaMJbbXn161s+noLL4rwOt/KU8VPAAdoB0yWO1S5Gob4wER6K34
N9j+xH2KpB1K65XHL5GhlZCMvSeIYMGARyWDcvD3i8Vel0n+1stXMDz0Oj362I/U
NpP9l3Az3DbiFUyihrly/u+52XV855H3lNX64daVbL9m56TqB0p2+HMfgU1I+Maw
zSHnqtvDqygrhooXD6UKlLH7KTAZwW99ouNsTsKrUgD1Wc/CBNp1JD3pJsn1PKxE
9hDtxKt8+ldwztYETl53dk9yW+JnjNM74l3blSHdlaq0+QypP6Zxjr2rL72H2PSr
fwsZhxy4ig4hyiFsdAQIk8KI8psLQNDGmbsBkvHEAs5QjPGPr0U=
=wH3L
-----END PGP SIGNATURE-----

Attachment: pgpO52XcdZmW6.pgp
Description: PGP signature


--- End Message ---

Reply via email to