[Deb-scipy-devel] new python-numpy package

[Ondrej Certik]

Hi,

Kumar and I have prepared a new python-numpy package. It has the DM
field set, but first it creates a new binary package and second the
changes are big, so I would like to ask you if you could review our
changes first and then possibly upload it (but this will not be that
easy, see below).

The package is lintian clean, linda says:

$ lintian /var/cache/pbuilder/result/python-numpy_1.0.4-1~oc1_i386.changes
$ linda /var/cache/pbuilder/result/python-numpy_1.0.4-1~oc1_i386.changes
E: python-f2py; No manual page for binary f2py2.4.
E: python-f2py; No manual page for binary f2py2.5.
W: python-numpy; Image file
/usr/lib/python2.4/site-packages/numpy/core/tests/testdata.fits is
installed into /usr/lib.
W: python-numpy; Image file
/usr/lib/python2.5/site-packages/numpy/core/tests/testdata.fits is
installed into /usr/lib.

But I and Kumar think linda is wrong on all of the above.

Note: the debian/rules is a mess, that should be cleaned (=converted
to pycentral, as all other python modules), but on the other hand it
works, so I am inclined to fix real problems first and then possibly
clean it.

The biggest problem is with f2py. There is a (deprecated?) package
python-f2py in Debian. Upstream now ships new f2py releases inside the
numpy tarball. I just asked them what to do about versions , because
when you run f2py from numpy it says:

Version:     2_3816
numpy Version: 1.0.3

if you look at the old python-f2py package in Debian, it has a version
"2.45.241+1926-5". So it's a mess.

Currently, the new python-numpy package has buggy conflicts and
depends, it's quite tricky to do it right, actually I don't know how
to do it right. My idea is to ask for removal of the old python-f2py
package from Debian, then upload our new python-numpy package, that
provides a new python-f2py binary. But how about versions? Currently
the new python-numpy conflicts with python-f2py <= 2.45.241+1926-5,
but this renders the new python-f2py uninstallable, because the new
python-f2py depends on the new python-numpy (it uses some stuff from
there), but the new python-numpy conflicts with it, because the new
python-f2py has the same version as numpy now has.

So what to do now?

In the meantime, I'll ask upstream to clarify the versions of f2py,
but I fear they will clarify the problem above.

Here is the new python-numpy package:

Vcs-Svn: svn://svn.debian.org/svn/python-modules/packages/numpy/trunk
Vcs-Browser: http://svn.debian.org/wsvn/python-modules/packages/numpy/trunk/

Feel free to modify it, improve it, fix it. I also put it to my repository:

http://debian.certik.cz/

but I will not guarantee it's going to work, because I use that repo
for testing the packages (installation/uninstallation, upgrade,
conflicts, etc.).

Ondrej