cvs2svn-1.1.0 doesn't work with dev-util/subversion-1.3.2-r1(stable version). Steps to Reproduce 1.cvs -d /tmp/testcvs init 2.cvs2svn -s /tmp/testsvn /tmp/testcvs ... ERROR: svnadmin failed with the following output while loading the dumpfile: svnadmin: Unrecognized record type in stream cvs2svn-1.3.0 works fine. please mark stable cvs2svn-1.3.0.
I agree, I had problems exporting to SVN with the old 1.1 version. Version 1.3 works better and solves a few bugs. This has been known for some time now, see e.g. this link: http://svn.haxx.se/users/archive-2005-07/0397.shtml . I am not sure but marking 1.2 stable could be sufficient, but given that 1.3 dates back to August 29, 2005, it should be stable enough.
1.3 corrupted my repository while importing into existing repository. Using subversion 1.3.2-r1.
(In reply to comment #2) > 1.3 corrupted my repository while importing into existing repository. > > Using subversion 1.3.2-r1. > The same when using 1.2.1: Command: cvs2svn -s /home/subversion/mii/ --existing-svnrepos --trunk=graphlabtrunk --branches=graphlabbranches --tags=graphlabtags /home/cvs/ Output: -- Pass 8 -- Starting Subversion Repository. Starting Subversion r1 / 617 Starting Subversion r2 / 617 Starting Subversion r3 / 617 Starting Subversion r4 / 617 Starting Subversion r5 / 617 Starting Subversion r6 / 617 Starting Subversion r7 / 617 Starting Subversion r8 / 617 ERROR: The command '['co', '-q', '-x,v', '-p1.1', '/home/cvs/root/graphtoolkit/thirdparty/junit/junit/samples/Attic/AllTests.class,v']' failed with exit status: 1 and the following output: co: /home/cvs/root/graphtoolkit/thirdparty/junit/junit/samples/Attic/AllTests.class,v:7: unknown expand mode u co aborted
I figured out the problem was related to the rcs library, which doesn't support unicode expand mode. Removed the affected files (whitch all were in attic anyway) and it worked like a charm. The corruption problem actually sorted out to be a permission problem (i ran the script as root).
Me too. I also had issues with the currently stable version of cvs2svn creating an unusable svndump for subversion 1.3.*. This article on the subversion mailing list indicates that this is a problem in this version: http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=34862 I've upgraded to cvs2svn 1.3.0 and things worked as expected on my AMD64 system. Consider this another vote for removing cvs2svn 1.0 and marking 1.3 stable.
Bumped cvs2svn to version 1.5 (removed 1.3) and it takes a month until we can stable the new version.
