Re: CVS to SVN conversion

Wadhavankar, Hemant wrote:
> I tried following information given in "Repository is still too
> large" on URL http://cvs2svn.tigris.org/faq.html#testcase
> 
> The shrink_test_case.py ran apparently successfully and came out with
> one modified file only at the end. I copied this modified file back
> into original CVS repository. However I am now getting KeyError at
> new files while again running cvs2svn command. Is it possible to find
> out issues with all files in go?

I think you misunderstand the reason for running these scripts.  They
are used to find the original cause of an error, not to fix the error.
You should look at the file that it found to see if it is corrupt.
Maybe you can then fix the corruption in the original file, and/or look
for other files that are similarly corrupt.

If the file looks OK, then submit it as part of a bug report, including
all of the other information that we need.  For example, you still
haven't told us what version of cvs2svn you are using.

Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2454879

To unsubscribe from this discussion, e-mail: [[email protected]].