Changes between Version 3 and Version 4 of Notes/Subversion/Importing

Timestamp:

11/22/07 19:08:50 (17 years ago)

Author:

VincentMcIntyre

Comment:

--

Notes/Subversion/Importing

@@ -8 +8 @@
 Just importing the miriad tree as it stands is unsatisfactory, because we lose the revision history.
 
+'''Note:''' there is a [http://cvs2svn.tigris.org/issues/buglist.cgi?target_milestone=---&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&issue_status=CLOSED&field0-0-0=longdesc&type0-0-0=substring&value0-0-0=file%20already%20exists&field0-0-1=short_desc&type0-0-1=substring&value0-0-1=file%20already%20exists&field0-0-2=status_whiteboard&type0-0-2=substring&value0-0-2=file%20already%20exists bug] in the version of {{{cvs2svn}}} available in the Debian ''sarge'' release that causes the import to die partway through. The version available in Debian ''etch'' works correctly.
 {{{
  % mkdir miriad
  % rsync -av /nfs/atapplic/miriad/ miriad/
  % cvs2svn --dumponly --dumpfile=20071123.svndump miriad
+
  # assuming we have a repo at /srv/svn/projects/miriad
- % svn import < 20071123.svndump
-
+ % svnadmin load /srv/svn/projects/miriad < 20071123.svndump
+ % 
+ # --dumponly is useful for importing a CVS into an existing SVN
+}}}
+To do later imports
+{{{
+  % mkdir miriad2
+  % cvs2svn --dumponly --dumpfile=20071124.svndump miriad2
+  % not sure what comes next. I think
 }}}