Hi there, today I run into a FTBFS when building libraries/pytdeextensions on debian/testing (jessie). The package actually compiles, but the building process actually fails after that when invoking "dh_python".
dh_python -ppytdeextensions-trinity make: dh_python: Command not found
I tracked down the problem to be in the file "debian/python-distutils-jaunty.mk", where "dh_python2" needs to be invoked instead of "dh_python" and prepared a patch for it.
While looking at the problem I also spotted that the patch "11_fix_get_libdir_name.diff" was out-of-sync with the code by 63 lines, so I updated the patch to point to the correct line.
With both patches, the package builds correctly. I don't know if you are having the same problem I had. The nightly built package is not ready at the time of writing (it is schedule for building in a few hours), so I can't compare.
I don't know whether the patch for "dh_python" breaks the building for debian/wheezy, since last year I didn't have any problem compiling in such environment. If so, a separate entry needs to be created in the tde-packaging for
debian/jessie (instead of pointing to wheezy) and the patch added to the "libraries/pytdeextensions" files.
Cheers Michele
On Monday 02 of September 2013 13:57:46 Michele Calgaro wrote:
Hi there, today I run into a FTBFS when building libraries/pytdeextensions on debian/testing (jessie). The package actually compiles, but the building process actually fails after that when invoking "dh_python".
dh_python -ppytdeextensions-trinity make: dh_python: Command not found
I tracked down the problem to be in the file "debian/python-distutils-jaunty.mk", where "dh_python2" needs to be invoked instead of "dh_python" and prepared a patch for it.
While looking at the problem I also spotted that the patch "11_fix_get_libdir_name.diff" was out-of-sync with the code by 63 lines, so I updated the patch to point to the correct line.
With both patches, the package builds correctly. I don't know if you are having the same problem I had. The nightly built package is not ready at the time of writing (it is schedule for building in a few hours), so I can't compare.
I don't know whether the patch for "dh_python" breaks the building for debian/wheezy, since last year I didn't have any problem compiling in such environment. If so, a separate entry needs to be created in the tde-packaging for
debian/jessie (instead of pointing to wheezy) and the patch added to the "libraries/pytdeextensions" files.
Cheers Michele
Well done. I like to look at it, because just a few days ago I converted other python packages to dh_python2 and at this time I have put down pytdeextensions to later...
Slavek --
-
Michele Calgaro -
Slávek Banko