Try the following diff. It specifies the version of python when running
make, which is relevant when make decides to rerun ./configure (which it
now does on install for some reason). Since PYTHON was only specified
during the debuild configure step, it reverted to the default version
during install. Always specifying it prevents that bug.
--- debian/rules 2010-08-31 03:04:57 +0000
+++ debian/rules 2010-11-23 19:59:50 +0000
@@ -73,13 +73,13 @@
configure/python-vte:: $(addprefix configure-stamp-, $(PY_VERSIONS))
build-stamp-%:
- make -C $(buildbasedir)/$*
+ make -C $(buildbasedir)/$* PYTHON=`which $*`
touch $@
build/python-vte:: $(addprefix build-stamp-, $(PY_VERSIONS))
install-stamp-%:
- make -C $(buildbasedir)/$* install DESTDIR=$(DEB_DESTDIR)
+ make -C $(buildbasedir)/$* install DESTDIR=$(DEB_DESTDIR) PYTHON=`which
$*`
# stop shipping *.a and *.la files for the Python module;
# python-support moves them anyway (#412477)
find $(DEB_DESTDIR)/usr/lib/$* -name \*.a -exec rm -f '{}' \;
--
rebuild python-vte for python2.7
https://bugs.launchpad.net/bugs/674175
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
