Debian package(s) -- preliminary
See: http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/ or fetch them directly: http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/f2py/python-f2p... http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/f2py/python-f2p... http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/f2py/python-f2p... http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/scipy-core/pyth... http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/scipy-core/pyth... http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/scipy-core/pyth... http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/scipy-main/pyth... http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/scipy-main/pyth... http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/scipy-main/pyth... Problems & ToDo: 1) altas is not necessarily needed, but if the packager used it , it should be added to "Depends"-list for python2.[1,2]-scipy. I intuitively tried "Suggests:" in the first (Source) part of debian/control -- beginner's mistake... 2) python2.[1,2]-weave (or call it -scipy-weave ?) is still missing -- and has to be added to "Depends" for python2.[1,2]-scipy. Probably, I'll do it this evening. As for scipy and scipy-core I used the (new) setup_<package>.py script for creation of the source dist, but for weave I got weave-???.tar.gz. setup_weave.py provides no version info?! 3) You'll find more ... Ralf.
I've now seen Pearu's email in scipy-dev archive about the new setup procedure -- and subscribed to the ml ;-) . I hope, that I already used setup_<package>.py correctly.
2) python2.[1,2]-weave (or call it -scipy-weave ?) is still missing -- and has to be added to "Depends" for python2.[1,2]-scipy. Probably, I'll do it this evening. As for scipy and scipy-core I used the (new) setup_<package>.py script for creation of the source dist, but for weave I got weave-???.tar.gz. setup_weave.py provides no version info?!
So, weave versioning pb is known. About the naming: Something like 'python-scipy_core' is forbidden for Debian packages (because, I believe, '_' initiate the version number). Something like '_alpha_' makes problems, too. Ralf.
On Wed, Nov 20, 2002 at 11:29:21AM +0100, RA wrote:
See: http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/
Hi Ralph, I've just downloaded the diff files and am building packages against current CVS sources of SciPy and F2PY. The immediate problem I've run into is in the build-depends line: dpkg-checkbuilddeps: Unmet build dependencies: python-dev (<< 2.2) I don't understand how you can build python2.2-* packages with this in the build-depends line. (?) There are a number of other things that don't match the Debian python policy or that lintian complains about. I've corrected all these for scipy-core, and it now builds lintian-free packages. I'm starting on F2PY now. So now what shall I do with the corrected packages? The URL above suggests that your packages are intended for woody. Is that true? My modified source packaging is targeted at Debian "unstable" (aka sid), as it must be in order to upload to Debian. Do you want the changed diff to put on the scipy.org site? Does Joe Reinhardt want to coordinate this? Shall I just upload them to Debian myself? (Personally, I'd rather not be "the" Debian maintainer for these packages, but I'm willing to help out from time to time.) -Steve
On Samstag, 23. November 2002 04:52:04, Steve M. Robbins wrote:
On Wed, Nov 20, 2002 at 11:29:21AM +0100, RA wrote:
See: http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/
Hi Ralph,
I've just downloaded the diff files and am building packages against current CVS sources of SciPy and F2PY.
The immediate problem I've run into is in the build-depends line:
dpkg-checkbuilddeps: Unmet build dependencies: python-dev (<< 2.2)
I don't understand how you can build python2.2-* packages with this in the build-depends line. (?)
I've installed both, the standard 'python' in _woody_ (2.1), and python2.2. The build dependencies are like you can find e.g. for python-numeric for _woody_.
There are a number of other things that don't match the Debian python policy or that lintian complains about. I've corrected all these for scipy-core, and it now builds lintian-free packages. I'm starting on F2PY now.
My experiences with debian packaging is limited, I just made (or updated) only a few debs for my own use. So, I'm happy about feedback.
So now what shall I do with the corrected packages? The URL above suggests that your packages are intended for woody. Is that true? My modified source packaging is targeted at Debian "unstable" (aka sid), as it must be in order to upload to Debian. Do you want the changed diff to put on the scipy.org site? Does Joe Reinhardt want to coordinate this? Shall I just upload them to Debian myself? (Personally, I'd rather not be "the" Debian maintainer for these packages, but I'm willing to help out from time to time.)
Yes, you're right, it was intended for woody. And at the moment, I'm using only the stable tree. You're right: it should be definitely included in sid. But I also believe that scipy vers. 0.2 will be released soon. So, it's worthwile to provide woody packages on scipy.org, too. Moreover, the differences between these two diff's probably only affect some python version numbers, do they? Regarding the procedure, I'm not sure. It would be fine, if you can provide me the changed diff's, so that I can use them for packages tested on woody. And you or Joe can upload the corresponding versions for sid. Ralf.
-Steve _______________________________________________ SciPy-user mailing list SciPy-user@scipy.net http://www.scipy.net/mailman/listinfo/scipy-user
On Sun, Nov 24, 2002 at 06:33:06PM +0100, RA wrote:
On Samstag, 23. November 2002 04:52:04, Steve M. Robbins wrote:
On Wed, Nov 20, 2002 at 11:29:21AM +0100, RA wrote:
See: http://www.scipy.org/Members/RalfA/packages/Debian-woody-DEB/
Hi Ralph,
I've just downloaded the diff files and am building packages against current CVS sources of SciPy and F2PY.
The immediate problem I've run into is in the build-depends line:
dpkg-checkbuilddeps: Unmet build dependencies: python-dev (<< 2.2)
I don't understand how you can build python2.2-* packages with this in the build-depends line. (?)
I've installed both, the standard 'python' in _woody_ (2.1), and python2.2.
Yeah, but if you install python-dev from python 2.2 (as I have), the build fails. There is now a python policy that suggests how python modules should be packaged. Briefly, one builds three packages: python2.1-f2py, python2.2-f2py, and python-f2py. The last is an empty package that just depends on the package for the default version of python.
Yes, you're right, it was intended for woody. And at the moment, I'm using only the stable tree. You're right: it should be definitely included in sid. But I also believe that scipy vers. 0.2 will be released soon. So, it's worthwile to provide woody packages on scipy.org, too. Moreover, the differences between these two diff's probably only affect some python version numbers, do they?
I've put revised packages up at http://people.debian.org/~smr/scipy and .../~smr/f2py. The scipy-core and f2py packages are purely python, so they are installable directly on a woody system. The main scipy packages need rebuilding on a woody system, because they depend on the newer C library package, for example. -Steve
participants (2)
-
RA -
Steve M. Robbins