Re: cvs2svn conversion using psyco

Michael Haggerty <[email protected]>
Newsgroups gmane.comp.version-control.subversion.cvs2svn.user
Message-ID <[email protected]>
On 11/11/2010 07:04 PM, Liem Do wrote:
> Has anyone had any success with psyco and cvs2svn? The FAQ on the
> site says that psyco is known to cause the error
> “cvs2svn_lib.common.InternalError: ID changed from 2 -> 3 for Trunk,
> r2” but the link to the issue on the Psyco page shows that this issue
> is closed. I’ve also seen on other mail lists that some people have
> had success using psyco to do a conversion.

I haven't heard of any news on this front.

> I’m running cvs2svn and psyco (both checked out from trunk on
> November 1^st , 2010) on CentOS 5.2 (2Gig of RAM) with Python 2.4.3
> and SVN 1.6.13 from CollabNet but am still getting the same error in
> pass 16 (OutputPass). Running the test suite from the Psyco issue
> shows that the test passed but the error shows on an actual
> conversion. I’m also running my conversion on a cvs module which is
> about 4G in size and only on the Trunk of the repository. My final
> conversion will involve a CVS repository which is 4 times as big and
> with thousands of tags/branches. I really need to get the conversion
> time down to something manageable.

It would be great if you would reduce this to a reproducible bug report
(see the cvs2svn FAQ) then file it with the *psyco* project.

It would also be great if you would keep up posted on your experience so
that other users who want to try psyco can benefit from your work.  I'm
particularly interested whether the use of psyco speeds up cvs2svn
significantly (once it works!).  Does it seem to speed up the passes
before OutputPass?

Michael

-- 
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/

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

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.