Your message dated Wed, 20 Jun 2007 07:45:36 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423794: binNMUs needed for python libs ? (Was: Bug#423794:
FTBFS: Src/spmatrixmodule.c:13:37: error: Numeric/arrayobject.h: No such file
or directory)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: pysparse
Version: 1.0-1
Severity: serious
Justification: no longer builds from source
Hi!
pysparse currently fails to build from source in sid [1]:
--- 8< ---
running build_ext
building 'pysparse.spmatrix' extension
creating build/temp.linux-i686-2.5
creating build/temp.linux-i686-2.5/Src
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes
-fPIC -IInclude -I/usr/include/python2.5 -c Src/spmatrixmodule.c -o
build/temp.linux-i686-2.5/Src/spmatrixmodule.o
Src/spmatrixmodule.c:13:37: error: Numeric/arrayobject.h: No such file or
directory
In file included from Src/spmatrixmodule.c:24:
Src/ll_mat.c: In function 'LLMat_matvec_transp':
Src/ll_mat.c:763: error: 'PyArrayObject' undeclared (first use in this function)
Src/ll_mat.c:763: error: (Each undeclared identifier is reported only once
[...]
error: command 'gcc' failed with exit status 1
make: *** [stamp-build-2.5] Error 1
--- >8 ---
[1] http://people.debian.org/~lucas/logs/2007/05/13/pysparse_1.0-1_sid32.buildlog
Cheers,
--
Jérémy Bobbio .''`.
[EMAIL PROTECTED] : :Ⓐ : # apt-get install anarchism
`. `'`
`-
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
This is building 2.4 and 2.5 binaries just fine now, indeed it was never
buggy.
-Adam
On Tue, 2007-05-15 at 09:47 +0200, Lucas Nussbaum wrote:
> [ Summary:
> pysparse fails to build from source because python-numeric doesn't
> include /usr/include/python2.5/Numeric/arrayobject.h (python-numeric
> only has files for python 2.3 and 2.4, not 2.5).
> ]
>
> On 14/05/07 at 14:34 -0400, Adam C Powell IV wrote:
> > > > Have you tried rebuilding python-numeric with python 2.5, then building
> > > > pysparse? I notice that python-numeric does not appear in
> > > > http://people.debian.org/~lucas/logs/2007/05/13/ , nor in any other
> > > > subdir of http://people.debian.org/~lucas/logs/2007/ , so it seems not.
> > >
> > > if it's not here, it just means that it never failed.
> >
> > How do we know it was ever tried?
>
> if it's in main and is supposed to build on i386, it was tried. but
> anyway, I use the packages from the archive, not the ones I built, to
> build the other ones. So even if python-numeric was rebuilt, the verison
> in the archive would be used to build pysparse.
>
> > > > I see. This is a problem with the new python build system: it's hard to
> > > > tell which packages have been built with which version of python.
> > > > There's no reason for me to change my python-numeric dependency, but no
> > > > way for any build system to tell whether the same python-numeric package
> > > > has been built for the new python.
> > > >
> > > > Reclassifying this as normal. If you can show that you built its python
> > > > dependencies with 2.5, and then this failed, then I will agree that it
> > > > is a bug in pysparse.
> > >
> > > I'm not really a python expert. :-) But why did your package suddenly
> > > start to build python 2.5 files as well ?
> >
> > When you try to build a python package, it attempts to build all of the
> > current default versions. Last Fall when I first uploaded pysparse, it
> > automatically built and installed headers, .pyc files, etc. for python
> > 2.3 and 2.4.
> >
> > Now there is python 2.5, so when you try to build pysparse again, it
> > tries to build python 2.5 files.
> >
> > But python-numeric was built before python 2.5, so it only built
> > headers, pyc etc for 2.3 and 2.4 (maybe not even 2.3, I'm not sure). So
> > in order to have python-numeric headers for python 2.5, you need to
> > rebuild that package now with python 2.5.
> >
> > Otherwise, when rebuilding pysparse, it will try to build 2.5, and look
> > for python-numeric 2.5 header files, but they won't be there!
> >
> > So please try building python-numeric, install the newly-built version,
> > then try building pysparse.
> >
> > As I mentioned, this is a general problem with python upgrades using the
> > new python build system (introduced about a year ago IIRC). After a new
> > python version enters the defaults list, attempting to rebuild an
> > arbitrary python package is likely to fail, unless all of its
> > dependencies have been rebuilt and uploaded first.
> >
> > Please verify that it builds as I described above (when you rebuild and
> > install python-numeric first), then we can close this bug.
>
> After discussing that with Pierre Habouzit, it seems that binNMUs are
> needed for all python-* packages which are arch:any, support python 2.5,
> and include files in /usr/lib/python?.?. (at least python-numeric needs
> this binNMU)
>
> But I would prefer if someone more knowledgeable that me on python stuff
> could confirm :-)
--
GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6
Welcome to the best software in the world today cafe!
http://www.take6.com/albums/greatesthits.html
--- End Message ---
