On Sat, 23 Jan 2010, Luca Falavigna wrote:
> First output of my elaboration can be found at [2], listing 294
> source packages. Feel free to suggest packages to be added or removed.
shogun source package from which come out binary packages
shogun-python, shogun-python-modular, and shogun-elwms wh
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.or
OoO Pendant le temps de midi du dimanche 24 janvier 2010, vers 12:58,
Steve Langasek disait :
>> > as you probably know, python2.6 has recently been added to supported
>> > Python version in unstable [1].
>> Why currently compiling a package which contains binary extensions only
>> build the
Hi Vincent,
On Sun, Jan 24, 2010 at 11:40:45AM +0100, Vincent Bernat wrote:
> OoO Pendant le journal télévisé du samedi 23 janvier 2010, vers 20:15,
> Luca Falavigna disait :
> > as you probably know, python2.6 has recently been added to supported
> > Python version in unstable [1].
> Why cur
OoO Pendant le journal télévisé du samedi 23 janvier 2010, vers 20:15,
Luca Falavigna disait :
> as you probably know, python2.6 has recently been added to supported
> Python version in unstable [1].
Why currently compiling a package which contains binary extensions only
build them for python
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
6 matches
Mail list logo
