Re: cvs2svn --dumpfile followed by svnadmin load gives problems
Michael Haggerty <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
Skip Montanaro wrote: > I'm trying to migrate a modestly sized chunk of a CVS repo to > svn. [...] so I logged into the svn server, cd'd to the .../subversion > directory and executed: > > svnadmin load svn/repo < ~/tmp/repo.dump > > but it complained that > > file already exists: filesystem: svn/repo/db Probably your subversion repository already has contents with paths that conflict with the paths that the cvs2svn dumpfile wants to create. Normally the cvs2svn-generated dumpfile should be loaded into an empty Subversion repository. Alternatively, it is possible to load the new content into a subdirectory of the existing repository by using "svnadmin load --parent-dir foo ...". > Maybe I shouldn't be going through a dump file? I haven't been > able to find a nice end-to-end example with specific paths. All > the paths seem to be abstract. Any help appreciated... If the CVS and SVN repositories are on the same server, then there is no particular reason to use a dumpfile. But it shouldn't hurt, either (aside from the extra disk space temporarily needed). Avoiding the dumpfile will not prevent the error that you are having. Michael ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2387333 To unsubscribe from this discussion, e-mail: [[email protected]].