Great! I'll do some testing today but don't expect any issues.
In fact I just recompiled (on Ubuntu 12.04) from the latest in master and
everything
came back binary equivalent (except for changelog.Debian.gz and one instance
of the build date in the docs) to the build I've been using for the past
So, per Jakub "recommendations" it seems that mpi4py builds just fine
(on sid, wheezy and ubuntu 12.04). I have pushed that tiny patch into
the repository on alioth. Would you mind giving it some testing?
if it is all good we could upload it tomorrow.
On Thu, 24 May 2012, Yaroslav Halchenko wrot
FWIW -- apparently that is a bug and Matthias promised it to be fixed in
the next upload to Debian. No ETA so far though -- if there would be no
updates today I will file an official bugreport so this doesn't go off
our radars
On Tue, 22 May 2012, Yaroslav Halchenko wrote:
> and indeed on 12.04 a
>2. It looks like -lffi is coming from the Python installation. Â Try
>running:
>$ python3.2 -c "from distutils.sysconfig import get_config_var;
>print(get_config_var('MODLIBS'))"
>-lssl -lcrypto  -lssl -lcrypto   -L/usr/lib -lz  -lexpat
>In particular, on my Ubuntu 1
1. Good catch noticing that we lost mpi.cfg:
This can be fixed by adding to python-mpi4py.install:
```
usr/lib/python2*/*-packages/*/*.cfg
```
An analogous fix is required in python3-mpi4py.install.
See
https://github.com/bfroehle/debian-mpi4py/commit/b6fae77320f2d64ba18d749251d7311d146c3c8d
2
it seems that
1. we lost mpi.cfg
neurodebian@head2:~/deb/builds/mpi4py/1.2.2-4$ dpkg -c
python-mpi4py_1.2.2-4_amd64.deb | grep mpi.cfg
neurodebian@head2:~/deb/builds/mpi4py/1.2.2-4$ cd ../1.2.2-3/
neurodebian@head2:~/deb/builds/mpi4py/1.2.2-3$ dpkg -c
python-mpi4py_1.2.2-[34]_amd64.deb | grep m
ok -- let's upload this one, see it migrate (or not) to testing and then
1.3!
thanks for all the help!
On Mon, 21 May 2012, Bradley M. Froehle wrote:
>Yes. Â Alternatively we could (and should) upgrade the package to version
>1.3.
>See [1]https://github.com/bfroehle/debian-mpi4py/com
Yes. Alternatively we could (and should) upgrade the package to version 1.3.
See https://github.com/bfroehle/debian-mpi4py/commits/, where I've squashed the
bug fixes in the previous posts.
Thanks!
On Mon, 21 May 2012, Bradley M. Froehle wrote:
> Aha, good catch. Unfortunately we cannot just add $(PY3VERS) to the list of
> versions to test, as Python 3.2 has additional failures in
> test_mem.testMemory(1|2).
> In this case the tests are incorrect, but they've already been fixed upstream.
>
Aha, good catch. Unfortunately we cannot just add $(PY3VERS) to the list of
versions to test, as Python 3.2 has additional failures in
test_mem.testMemory(1|2).
In this case the tests are incorrect, but they've already been fixed upstream.
(The tests fail when attempting to allocate a 0-byte chun
Thank you Bradley for the patches! What about excercising unittests
with python3?
> override_dh_auto_test:
> ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
> - for P in $(PYVERS); do \
> + for P in $(PY2VERS); do \
>PYTHONPATH=`/bin/ls -d $(CURDIR)/build/lib.*-$$P` \
> /
Source: mpi4py
Severity: wishlist
Tags: patch
Dear Maintainer,
Attached you'll find a short patch series, which:
* Changes the build system to dh_python2
* Adds Python 3 support
-- System Information:
Debian Release: wheezy/sid
APT prefers precise-security
APT policy: (990, 'precise-security
12 matches
Mail list logo
