Build stuck - "Could not import runpy module"

Asked by Adam Olsen on 2009-04-25

Hi, I'm trying to get an app to build in our PPA for Jaunty, but I keep getting this error:

mkdir -p /build/buildd/exaile-devel-20090425/debian/exaile-devel/usr/share/pixmaps
mkdir -p /build/buildd/exaile-devel-20090425/debian/exaile-devel/usr/share/applications
python -m compileall -q xl lib xlgui
Could not import runpy module
make[1]: *** [compile] Error 255
make[1]: Leaving directory `/build/buildd/exaile-devel-20090425'
make: *** [install] Error 2
dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave error exit status 2

Full log here:

http://launchpadlibrarian.net/25972966/buildlog_ubuntu-jaunty-i386.exaile-devel_20090425-bzr2_FAILEDTOBUILD.txt.gz

The package builds fine on my machine, I'm not sure what the problem is. runpy is a standard module, so there's no reason it shouldn't be able to import.

Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Adam Olsen
Solved:
2009-04-30
Last query:
2009-04-30
Last reply:
2009-04-26
Celso Providelo (cprov) said : #1

Hi Adam,

The source fails in the same way if you build it in a pbuilder environment [1]. You are right, runpy should be available from python2.5 (which is already a build-dep), maybe the build paths are being changed in the wrong way.

Anyway, your chances to find exactly what is missing are higher with pbuilder and maybe a quick chat with one of the MOTU guys [2]

[1] https://wiki.ubuntu.com/PbuilderHowto
[2] #ubuntu-motu on freenode.irc

Adam Olsen (arolsen) said : #2

Ok, with the help of pbuilder, I got it to build correctly by using python2.6-dev instead of python2.5-dev as one of the build depends. Still seems like something is wrong (why wouldn't it work with python2.5?), but at least it's building now.