Opened 19 years ago
Closed 19 years ago
#1930 closed defect (fixed)
Revision log is broken when trying to view the root of a virtual repository
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | highest | Milestone: | 0.9 |
Component: | version control/log view | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I've set my trac.ini as follows:
repository_dir = /some/path/to/repo/project1
where /some/path/to/repo is the physical path of my repository, and project1 is a versioned directory inside the repository. Clicking "Browse Source" correctly displays project1 as the new root, but clicking "Revision Log" results in an error:
The file or directory '/' doesn't exist at revision xxx or at any previous revision.
Note: the revision log works properly for any path under root; only for root does it give the error. I tried to dig around and determine if the scope wasn't being added properly, but I didn't look very hard :)
Attachments (1)
Change History (7)
comment:1 by , 19 years ago
Milestone: | 0.9 |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
comment:2 by , 19 years ago
Milestone: | → 0.9 |
---|---|
Resolution: | duplicate |
Status: | closed → reopened |
Just noticed that I'm seeing this problem at my own site, and it's not because the selected repository subset is not self-contained.
comment:3 by , 19 years ago
#2046 is a duplicate of this one. It has the relevant traceback from the Trac log.
by , 19 years ago
Attachment: | scoped_get_path_history.patch added |
---|
get_path_history
now takes into account the repository scope
comment:4 by , 19 years ago
Owner: | changed from | to
---|---|
Priority: | normal → highest |
Status: | reopened → new |
comment:5 by , 19 years ago
cboos, that patch looks good and works for me. Nice work! Feel free to check this in.
comment:6 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thanks! Patch applied in r2311.
I think this is a duplicate of #1830. I've not yet seen any problems with subsets of a repository that are fully self-contained, but have seen exactly the problem you're reporting with those that aren't.
Maybe the root directory in this case was copied from a path outside the scope?
Anyway, can you test the patch attached to #1830 and see if that fixes the problem for you?