Opened 18 years ago
Closed 18 years ago
#3367 closed defect (duplicate)
svn browser not dealing well with repo reorgs
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | version control/browser | Version: | 0.9.5 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I am trying out trac but have run into a bit of a show-stopper problem with the trac svn browser. It seems that it is not dealing well with repo reorganisations. My repo *used* to have a {trunk,branches,tags}/{foo,bar} structure, but I reorganised it sometime in the past to be of the form {foo,bar}/{trunk,branches,tags}.
Pointing trac at foo or bar now makes it deeply unhappy. It shows the top-level directory structure, and if you click on the revision history it will show that too. It won't show directory listings inside trunk or tags, however. It will show a directory listing inside branches, probably because the only branch there was created after the reorg.
The problem can be seen here, for the time being: http://ggtl.org/ggtl/browser
Attachments (0)
Change History (3)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
It's the same repo. I essentially did:
svn mv trunk/foo foo/trunk
(Although in realitity I used svk, but that shouldn't make a difference)
As I said I'm currently only evaluating trac so all this reorganisation was done long before trac was pointed at it. I did try to resync but that didn't help.
I have found out that if I point the trac browser to the top-level of the repository the browser works fine; however, now of course it shows a list of all projects available at that level, which isn't what I want.
comment:3 by , 18 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Can you elaborate about what you call a "reorganisation":
If you are talking about 1), did you resync Trac after this operation (trac-admin <project> resync) ?