Launchpad itself

PyPi cannot be accessed from builder

Asked by Kenneth Loafman

The repo version of lockfile is ancient and I need the latest from PyPi to run the tests. It's trying, but cannot access PyPi. Help, please!

./setup.py test
running test
Searching for lockfile>=0.11.0
Reading https://pypi.python.org/simple/lockfile/
Download error on https://pypi.python.org/simple/lockfile/: [Errno -2] Name or service not known -- Some packages may not be found!
Couldn't find index page for 'lockfile' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [Errno -2] Name or service not known -- Some packages may not be found!
No local packages or download links found for lockfile>=0.11.0
error: Could not find suitable distribution for Requirement.parse('lockfile>=0.11.0')
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory `/«BUILDDIR»/duplicity-0.7.05+bzr1143'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
Last query:
Last reply:
Revision history for this message
Best Colin Watson (cjwatson) said : 		#1

That's right, builders intentionally aren't allowed access to external network resources. I recommend that you package an upgraded version of lockfile (which shouldn't be too hard based on the existing packaging) and upload that to your PPA; you can then build-depend on that.

Revision history for this message
Kenneth Loafman (kenneth-loafman) said : 		#2

Thanks Colin Watson, that solved my question.