improve handling of scoped repositories with copy history
|Reported by:||Owned by:|
|Severity:||major||Keywords:||svn scoped repository|
While testing r3015, the revisions are still not working properly. I removed trac 0.9.6, checked out and installed r3570. I ran all the required upgrade commands and resync'd, but trac still always shows one rev for the part of the svn repo moved from another part.
Here's an example… the svn repo had proj1/trunk/java/src and proj2/trunk/websrc. I renamed websrc in proj2/trunk to src. Then I created proj1/trunk/web and moved src from proj2/trunk to proj1/trunk/web. When I make a change to web/src/file1 the revision is incremented, but all files in web/src show that revision too.
If I point trac to the root of the repo and resync, things work better, but if I point to proj1, the revision for the moved code is always the latest revision for files that haven't been updated since the move.
I'm guessing this is because trac is indexing only the current point in the history since the move.
Change History (12)
comment:10 by , 9 years ago
|Summary:||r3015 didn't fix my repo move problem → improve handling of scoped repositories with copy history|