tags 577439 + patch
thanks

* Michael Banck <mba...@debian.org>, 2010-05-05, 19:16:
On mips python-avogadro does not ship modules for Python 2.5
(which is still the default Python version). Apparently, if
python2.6-dev happens to be installed in the chroot, only modules for
2.6 will be built. Here's an excerpt from the build log:

| Package versions: [...] libpython2.6_2.6.4-6 [...] python2.6_2.6.4-6 
python2.6-dev_2.6.4-6 python2.6-minimal_2.6.4-6 [...]
[...]
| -- [2/5] Python Libraries
| -- Found PythonLibs: /usr/lib/libpython2.6.so
| -- [3/5] Python Interpreter
| -- Found PythonInterp: /usr/bin/python2.6

What do you propose we should do?  Hardcoding to look for 2.5 first?
That would make it break the same way once the default changes and 2.5
packages happen to be installed as well.

The attached patch should do the trick. I could not test the resulting binary package, however, as it depended on python2.5-sip4 (which does not exist).

--
Jakub Wilk
--- avogadro-1.0.0/debian/rules
+++ avogadro-1.0.0/debian/rules
@@ -14,7 +14,7 @@
 DEB_SHLIBDEPS_LIBRARY_avogadro = libavogadro1
 DEB_SHLIBDEPS_INCLUDE_avogadro = debian/libavogadro1/usr/lib
 DEB_DH_INSTALL_SOURCEDIR = debian/tmp
-DEB_CMAKE_EXTRA_FLAGS = -DENABLE_GLSL=ON -DENABLE_RPATH=OFF -DENABLE_UPDATE_CHECKER=OFF
+DEB_CMAKE_EXTRA_FLAGS = -DENABLE_GLSL=ON -DENABLE_RPATH=OFF -DENABLE_UPDATE_CHECKER=OFF -DPYTHON_EXECUTABLE=/usr/bin/python -DPYTHON_LIBRARY=/usr/lib/lib$(shell pyversions -d).so -DPYTHON_INCLUDE_DIR=/usr/include/$(shell pyversions -d)/
 
 PYVER = $(shell pyversions -dv)
 DEB_DH_GENCONTROL_ARGS_python-avogadro = -- -V'pyavo:Depends=python$(PYVER)-numpy, python$(PYVER)-qt4, python$(PYVER)-sip4'

Attachment: signature.asc
Description: Digital signature

Reply via email to