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


Ignore:
Timestamp:
11/22/07 19:56:02 (17 years ago)
Author:
VincentMcIntyre
Comment:

try to document the import process

Legend:

Unmodified
Added
Removed
Modified
  • Notes/Subversion/Importing

    v4 v5  
    66
    77=== Initial Import ===
    8 Just importing the miriad tree as it stands is unsatisfactory, because we lose the revision history.
     8Just importing the miriad tree as it stands is unsatisfactory, because we lose the revision history. So we use {{{cvs2svn}}}.
    99
    1010'''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.
     11
    1112{{{
    1213 % mkdir miriad
    1314 % rsync -av /nfs/atapplic/miriad/ miriad/
    14  % cvs2svn --dumponly --dumpfile=20071123.svndump miriad
    1515
    16  # assuming we have a repo at /srv/svn/projects/miriad
    17  % svnadmin load /srv/svn/projects/miriad < 20071123.svndump
    18  %
    19  # --dumponly is useful for importing a CVS into an existing SVN
     16 # method 1
     17 # we'll create a new repository in a directory named 'svnmiriad'
     18 % cvs2svn -s svnmiriad  miriad
     19
     20 # method 2
     21 # we can create an empty repository named 'svnmiriad' and load via a dumpfile
     22 % cvs2svn --dumpfile=20071123.svndump miriad
     23 % svnadmin load svnmiriad < 20071123.svndump
     24
     25 # method 3
     26 # add to an existing repository
     27 % svnadmin create svnmiriad
     28 % cvs2svn --existing-repos -s svnmiriad miriad
     29
    2030}}}
    21 To do later imports
     31
     32To do later imports, we would have to do something like this:
    2233{{{
    2334  % mkdir miriad2
    24   % cvs2svn --dumponly --dumpfile=20071124.svndump miriad2
    25   % not sure what comes next. I think
     35  % rsync -a /nfs/atapplic/miriad/ miriad2/
     36  # create a new repos
     37  % cvs2svn -s svnmiriad2 miriad2
     38  # assuming a repository named 'svnmiriad'
     39  % svn merge -rN:M svnmiriad2 svnmiriad  ???
    2640}}}
    2741