Re: binNMUs for python2.6
Hi Guys,
It is great to see python 2.6 finally in Debian main!!! Thanks for all
hard work.
Now though about binNMUs: we started getting emails about failed
builds, e.g.:
https://buildd.debian.org/fetch.cgi?pkg=pymvpa&arch=amd64&ver=0.4.3-2%2Bb1&stamp=1264452581&file=log
https://buildd.debian.org/fetch.cgi?pkg=pymvpa&arch=s390&ver=0.4.3-2%2Bb1&stamp=1264448371&file=log
(I guess more is to come).
where error message is
,---
| Traceback (most recent call last):
| File "setup.py", line 12, in <module>
| from numpy.distutils.core import setup, Extension
| ImportError: No module named numpy.distutils.core
| make: *** [debian/python-module-stampdir/python-mvpa-lib] Error 1
`---
And, I guess the main reason is that we build-depend on numpy and numpy
wasn't yet built for 2.6 (actually just now building for s390 for which
binary built has failed for our pymvpa)
https://buildd.debian.org/pkg.cgi?pkg=python-numpy
I understand that may be sooner or later build environment would converge to
the situation whenever all core packages (numpy/scipy/etc) are NMUed, but
wouldn't it make sense first to "manually" requests buildds for the core
packages and only then go for the iterations on the rest?
On Sat, 23 Jan 2010, Luca Falavigna wrote:
> Hello,
> as you probably know, python2.6 has recently been added to supported
> Python version in unstable [1].
> I started to work to a list of packages to be binNMUed in order to
> compile their extensions for 2.6, based on these criteria:
> 1) I looked for packages shipping .so files with site-packages or
> pyshared matches in their full path
> 2) I excluded arch:all false-positives packages
> 3) I excluded packages not depending on python-all-dev
> 4) I excluded packages with a XS-Python-Version field excluding 2.6 as a
> supported version for their extensions.
> 4) I excluded packages with a debian/pyversions excluding 2.6 as a
> supported version for their extensions.
> First output of my elaboration can be found at [2], listing 294
> source packages. Feel free to suggest packages to be added or removed.
> I also prepared a list for Release Team [3], they want to wait for
> python2.6 to migrate in testing before schedule binNMUs though, so we
> have another week to work on the list and prepare for the next steps.
> [1] http://lists.debian.org/debian-python/2010/01/msg00100.html
> [2] http://people.debian.org/~dktrkranz/python2.6/python2.6_sources
> [3] http://people.debian.org/~dktrkranz/python2.6/python2.6_binNMUs
> Regards,
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
Reply to: