#2131 closed defect (invalid)
Timeline view doen't working without SVN setted up
Reported by: | dimas | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | timeline | Version: | 0.9b1 |
Severity: | major | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
We setup Trac without SVN using patch found somwhere here, but Timeline doesn't working with next error message: cannot import name SubversionRepository
Stack trace
Traceback (most recent call last): File "/usr/local/src/muranosoft_dist/tools/trac/lib/python2.3/site-packages/trac/web/standalone.py", line 230, in _do_trac_req dispatch_request(path_info, req, env) File "/usr/local/src/muranosoft_dist/tools/trac/lib/python2.3/site-packages/trac/web/main.py", line 139, in dispatch_request dispatcher.dispatch(req) File "/usr/local/src/muranosoft_dist/tools/trac/lib/python2.3/site-packages/trac/web/main.py", line 107, in dispatch resp = chosen_handler.process_request(req) File "/usr/local/src/muranosoft_dist/tools/trac/lib/python2.3/site-packages/trac/Timeline.py", line 137, in process_request filters) File "/usr/local/src/muranosoft_dist/tools/trac/lib/python2.3/site-packages/trac/versioncontrol/web_ui/changeset.py", line 106, in get_timeline_events repos = self.env.get_repository() File "/usr/local/src/muranosoft_dist/tools/trac/lib/python2.3/site-packages/trac/env.py", line 143, in get_repository from trac.versioncontrol.svn_fs import SubversionRepository ImportError: cannot import name SubversionRepository
Attachments (0)
Change History (4)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
We have no way to reproduce this unless we know what patch you're referring to. Please add your comments on the place where you found the patch so that the author is aware of the issue.
comment:3 by , 19 years ago
Here this patch http://projects.edgewall.com/trac/ticket/156 It was working partially without config changing, now when config changed it works ok. But I think better to handle this error more carefuly.
comment:4 by , 19 years ago
Description: | modified (diff) |
---|
Adding [disabled_components] …
additionally to patching seems to fix issue