Buildjail fails on Lucid jail build due to missing python2.5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
IVLE |
Fix Released
|
Critical
|
William Grant |
Bug Description
On Lucid, by default (at least, using bin/ivle-
Package python2.5 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package python2.5 has no installation candidate
Traceback (most recent call last):
File "/usr/local/
['python2.5', 'python-cjson', 'python-svn', 'python-
File "/usr/local/
_execute_
File "/usr/local/
raise JailBuildError(
ivle.jailbuilde
This is because buildjail specifically depends on python2.5, but that package has been removed in Lucid in favour of python2.6.
Not sure how to fix this and remain backwards-
Workarounds:
- Change /etc/ivle.conf - jail/suite to karmic manually before running ivle-buildjail -r.
- In ivle-buildjail, manually s/python2.
Related branches
tags: | added: scripts |
Changed in ivle: | |
milestone: | none → 1.0.2 |
Changed in ivle: | |
importance: | Medium → Critical |
Changed in ivle: | |
status: | Triaged → In Progress |
assignee: | nobody → William Grant (wgrant) |
Changed in ivle: | |
status: | Fix Committed → Fix Released |
I managed to get a fresh build of IVLE running in Lucid (with a Lucid jail) just by modifying ivle-buildjail to use python2.6 instead of python2.5. So the fix for this should be to make ivle-buildjail somehow smart enough to figure out which version of Python to install.
But I don't think using sys.version is correct -- that will set the jail version to whichever version is running outside the jail, which isn't necessarily correct.