[Python-modules-team] Bug#521525: python-numpy: FTBFS: Fails to install f2py wrapper
Cyril Brulebois
kibi at debian.org
Fri Jul 3 09:27:22 UTC 2009
tag 521525 patch pending
thanks
Daniel Schepler <schepler at math.berkeley.edu> (27/03/2009):
> ...
> : # Adding links to manpages
> mkdir -p debian/python-numpy/usr/share/man/man1
> for v in 2.5 2.4; do \
> ln -sf f2py.1 debian/python-numpy/usr/share/man/man1/f2py$v.1; \
> ln -sf f2py.1 debian/python-numpy/usr/share/man/man1/f2py$v-dbg.1; \
> done
> : # Add unversioned numpy script
> mv /tmp/buildd/python-numpy-1.2.1/debian/tmp//usr/bin/f2py /tmp/buildd/python-
> numpy-1.2.1/debian/tmp//usr/bin/f2py2.5
> mv: cannot stat `/tmp/buildd/python-numpy-1.2.1/debian/tmp//usr/bin/f2py': No such file or directory
> make: *** [install/python-numpy] Error 1
> dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status 2
I'm not quite sure why it was previously building fine, but since I can
reproduce it on the kfreebsd-* buildds as well as on amd64 sid chroots.
So instead of using a conditional mv (based on whether the file exists
or not), I'm deleting that line entirely. If the old behaviour shows up
again, I guess it'll be time to investigate. I'd bet for some possible
python-central change or whatever, and I'm not keen on spending time on
that instead of the maintainer(s?) who didn't reply in 3 months to an RC
bug. Also, debdiffing the old binaries and the rebuilt ones show no
changes at all, so I'm quite confident I'm not obviously breaking
something here.
Uploading with the attached source debdiff. (python-numpy is also a
blocker for kfreebsd-*'s bootstrapping phase, hence my unwillingness
to wait any further.)
Mraw,
KiBi.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python-numpy+ftbfs.diff
Type: text/x-diff
Size: 947 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20090703/0ddab36c/attachment.diff>
More information about the Python-modules-team
mailing list