Modify ↓
#818 closed defect (fixed)
ImportError: no module named repository for bitten-slave
Reported by: | johnny1@… | Owned by: | osimons |
---|---|---|---|
Priority: | critical | Milestone: | 0.7 |
Component: | Build slave | Version: | dev |
Keywords: | Cc: | ||
Operating System: | Linux |
Description
I install bitten as follows:
$>python setup.py --without-master install --prefix /usr
The installation seems to be successful, but if I execute bitten-slave --help this Import Error? occurs:
Traceback (most recent call last): File "/usr/bin/bitten-slave", line 8, in <module> load_entry_point('BittenSlave==0.7dev', 'console_scripts', 'bitten-slave')() File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 277, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 2179, in load_entry_point return ep.load() File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 1912, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) File "/usr/lib/python2.6/site-packages/BittenSlave-0.7dev-py2.6.egg/bitten/slave.py", line 34, in <module> from bitten.recipe import Recipe File "/usr/lib/python2.6/site-packages/BittenSlave-0.7dev-py2.6.egg/bitten/recipe.py", line 30, in <module> from bitten.util import xmlio File "/usr/lib/python2.6/site-packages/BittenSlave-0.7dev-py2.6.egg/bitten/util/__init__.py", line 18, in <module> from bitten.util.repository import get_repos, get_chgset_resource ImportError: No module named repository
I also tried to add this module in the setup.py, but then the executable complains about trac.versioncontrol.api.
Attachments (0)
Change History (3)
comment:1 Changed 11 years ago by osimons
- Owner set to osimons
comment:2 Changed 11 years ago by osimons
- Resolution set to fixed
- Status changed from new to closed
Committed fix in [1020]. Could you please update an verify fix? Reopen ticket if this does not completely fix the issue.
comment:3 Changed 11 years ago by johnny1@…
I verified it, your change fixed it. Thanks!
Note: See
TracTickets for help on using
tickets.
I can see why:
I'll clean this and push a fix shortly.