tags:

views:

251

answers:

2

My company is performing a SVN repository migration and I would like to avoid overlapping of revision numbers between the two repositories (which are both active at the time being).

My requirement is to force the revision of the new repository to a specific revision number (say: 100.000).

By analyzing the FSFS repository I have come across the "db/current" file which sounds like the right place where to change the repository number.

Does anyone have any experience with this procedure? I would like to avoid strange things happening in the future!

PS: I understand I can create "100.000" dummy commits to the repository. Please share your experience with such procedure and possible performance issues of the repository during and after the prodecure

PS3: I understand that it might be a good idea to have everybody commit working copies before the procedure. This is not a problem for us (the new repository has very limited users right now). Still, if you have experience with this or similar requirements, please share! :)

PS3: I understand this is not a standard SVN procedure and many might object with the requirement itself. Let's just assume my requirement is sound! :)

+1  A: 

Firstly, don't bother trying to frig this. If you are to merge the 2, you can use dump/load to put the new one on top of the old and revision numbers will be handled for you. So unless you need to know what revision number a particular version is (for externals perhaps, or tags) then you needn't worry about this at all.

If you can work with the tool, its always better than finding later that svnsync or svnadmin pack, for example, won't work with your modified repository.

OK, so if you still want to do it, update the last-revision number in revprop 0 and the db/current file and you should be ok.

I don't think you'll find anyone who has direct experience with this approach though!

gbjbaanb
Thanks! I was missing the revprop 0! btw: I am not going to merge the two repositories. We are moving "project-by-project" to the new repository and we will keep the old one stale as "history" once completed all projects.Thanks again!
Pokot0
+1  A: 

http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=940194 :

Q: Is there a way to artificially increment the repository revision number in subversion?

A: The only way to do it would be to commit a number of dummy revisions.

pauldoo