Edgewall Software

Opened 12 years ago

Closed 11 years ago

#8301 closed defect (duplicate)

trac-admin resync stops on copy

Reported by: yves@… Owned by: Christian Boos
Priority: normal Milestone:
Component: version control Version: 0.11.1
Severity: normal Keywords: svn scoped repository
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:


After a 'svn move' I've changed the path in my trac.ini and I did a 'trac-admin resync'. But the resync command synchronzied only 1 revision:

Resyncing repository history… 1 revisions cached. Done.

In fact I have about 500 revisions. For me it looks like the resync command stops on copy. Doing a 'svn log' on my moved project, I get all my 500 revisions.

Attachments (0)

Change History (8)

comment:1 by Christian Boos, 12 years ago

Your description is a bit terse, so please correct me if I got it wrong.

You had something like that in your trac.ini:

repository_dir = /path/to/repos/myproject

Then you did svn move myproject anothername and changed the repository_dir accordingly (/path/to/repos/anothername). At that point, the resync didn't work…

That doesn't surprise me, the "scoped repository" model doesn't really support this scenario.

comment:2 by yves@…, 12 years ago

Yes, that's exactly what I did. We have done a reorganisation of our svn structure. Is there any workaround? Ohterwise we loose our whole history which is not the case on the command line.

comment:3 by Remy Blank, 12 years ago

The only workaround I can see is not to scope the repository:

repository_dir = /path/to/repos

But that's going to change the paths to your files (within Trac), so it may introduce other issues.

comment:4 by Christian Boos, 12 years ago

Milestone: 0.11.6
Owner: set to Christian Boos

Yes, there's no easy workaround, but I have an idea how to fix this. It won't be a small change: instead of an unique scope, we would need a list of (rev,scope), rev being the revision in which the scope was introduced. We would get that list when initializing the SubversionRepository and each usage of the scope would require to call a for finding the appropriate value of the scope given the rev we're aiming at.

No promise when/if it can be done, but I'd like to give it a try.

in reply to:  4 comment:5 by Christian Boos, 12 years ago


Replying to cboos:

… instead of an unique scope, we would need a list of (rev,scope), rev being the revision in which the scope was introduced.

Note: use SubversionNode.get_copy_ancestry introduced in r8332 for that.

comment:6 by Remy Blank, 12 years ago

Should this block 0.12?

comment:7 by Christian Boos, 12 years ago

Milestone: 0.12next-minor-0.12.x

Definitely not. It would require a good deal of rewrite of the internals of svn_fs.py, but I think without any API change.

comment:8 by Christian Boos, 11 years ago

Keywords: svn scoped repository added
Milestone: next-minor-0.12.x
Resolution: duplicate
Status: newclosed

See #3470.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain Christian Boos.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Christian Boos to the specified user.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.