[viewvc-users] Using an Existing ViewVC mySQL db during SVN conversion

"Pattalachinti, Ravi" <[email protected]>
Newsgroups gmane.comp.version-control.cvs.viewcvs.user
Message-ID <4772654C5143C84EB88BB606DD15F715B175CB@NA-MAIL-3.gs.adinternal.com>
We are getting close to migrate the cvs data to svn. 

The ViewVC conversion is adding 4 days in the downtime. Can you recommend any suggestions?

In order for ViewVC to work with new SVN repository here is what I do:
1)Python.exe svndbadmin rebuild “c:\repositories\SVN”
2)Python.exe svndbadmin update “c:\repositories\SVN”

Here are the questions:

a) We already did couple of trial conversions on our live data, and I have the ViewVC database from our last trial. Our plan is to do a full final conversion of cvs data to svn before closing the cvs repository. Can we use the existing ViewVC log database that was generated from previous trial conversion or should I redo step 1 and 2 again after final conversion?

b)If not : Can I run only step 2 above to get only the new updates since the last conversion?

c)If this is also not possible: Can the dev team start working on SVN the repository as I run the 2 steps above? 

Thanks,
Ravi

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2675460

To unsubscribe from this discussion, e-mail: [[email protected]].
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.