[Pkg-openmpi-maintainers] Bug#625832: python-mpi4py: importing MPI fails

Juha Jäykkä juhaj at iki.fi
Thu May 3 09:04:07 UTC 2012


> I cannot reproduce this with the version in stable, nor with the
> unstable version built on stable or in an unstable chroot.  I am
> downgrading this bug and mark it unreproducible for now.
> 
> How did you compile the above program, what architecture was this on and
> was it on an update unstable system?  Can you try again with an updated
> unstable system?

It seems to work on an up-to-date unstable now. And I am pretty sure it has 
been working for quite a long time for that matter: I do not recall the whole 
issue any longer, so it cannot have plagued me for a long time.

As it is almost a year since I reported the bug, I cannot recall the exact 
specs of the system any longer: I can guess from the bug report which computer 
it was, but not the package versions apart from those present in the report, 
which are missing some thanks to my reporting it against the wrong package 
originally.

But, as I see no changes to any of the openmpi packages since April 2011, it 
is hard to see why anything would have changed. 

From my point of view just mark this solved at the next upload.

-Juha
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-openmpi-maintainers/attachments/20120503/acf9937c/attachment-0001.pgp>


More information about the Pkg-openmpi-maintainers mailing list