Re: Problems moving to dh_python2

2011-04-08 Thread Johannes Ring
JFTR, I ended up adding this in debian/rules: PY_VERSIONS = $(shell pyversions --requested debian/control) install-stamp-%: cd $(DEB_BUILDDIR) && rm CMakeCache.txt && \ cmake $(DEB_CMAKE_NORMAL_ARGS) $(DEB_CMAKE_EXTRA_FLAGS) \ -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/$*

Re: Problems moving to dh_python2

2011-04-06 Thread Johannes Ring
On Wed, Apr 6, 2011 at 3:16 PM, Piotr Ożarowski wrote: > You're not building exceptions for all supported Python versions, I made > a small mistake in last upload (/usr/bin/dh_python2:145 - remove comma > at the end of line). After next python-defaults upload you'll get this > error message: > > |

Re: Problems moving to dh_python2

2011-04-06 Thread Piotr Ożarowski
You're not building exceptions for all supported Python versions, I made a small mistake in last upload (/usr/bin/dh_python2:145 - remove comma at the end of line). After next python-defaults upload you'll get this error message: | extension for pythonX.Y is missing. Build extensions for all suppo

Problems moving to dh_python2

2011-04-06 Thread Johannes Ring
Hi, I'm in the process of moving some of my packages from python-central to dh_python2 and I have run into a problem with one of them (ufc). This package is CMake based and uses SWIG to build an extension module for Python, and I was earlier using the following to handle this in debian/rules: bin