[Savannah-cvs] [86] tweak svn import recipe, etc.

[karl]

Revision: 86
          http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=86
Author:   karl
Date:     2014-05-20 23:07:03 +0000 (Tue, 20 May 2014)
Log Message:
-----------
tweak svn import recipe, etc.

Modified Paths:
--------------
    trunk/sviki/AdminSvnImport.mdwn

Modified: trunk/sviki/AdminSvnImport.mdwn
===================================================================
--- trunk/sviki/AdminSvnImport.mdwn     2014-05-14 22:32:52 UTC (rev 85)
+++ trunk/sviki/AdminSvnImport.mdwn     2014-05-20 23:07:03 UTC (rev 86)
@@ -1,8 +1,8 @@
-Importing History Into Subversion
+Importing history into Subversion
 =================================
 
-With Supplied History
----------------------
+With existing SVN history
+-------------------------
 
 For Savannah administrators: here's how to import an SVN repository.
 
@@ -10,47 +10,45 @@
 This will create the svn repository with the correct ownership and
 permissions.
 
-You need to ask the project developers to create an SVN dump as
-explained at [[SvnImportExistingRepo]].
+The project developers need to create an SVN dump as explained at
+[[SvnImportExistingRepo]].
 
 Once the user has provided it, login at Savannah, then use this recipe
 as a guideline to import the project.
 
     ssh vcs
-    screen
+    screen # or whatever, see below
     cd /root/vcs-imports
-    wget http://url/to/theirproject.dump.bz2
     proj=THEIRPROJECT
-    bzcat theirproj.dump.bz2 | svnadmin load /srv/svn/$proj/ 
>/tmp/$proj.svimport.out 2>/tmp/$proj.svimport.err
+    wget http://url/to/$proj-dump.bz2
+    # or whatever, e.g.,
+    # scp dl.sv.gnu.org:/srv/download/$proj/$proj-dump.bz2 .
+    bzcat $proj-dump.bz2 | nice svnadmin load /srv/svn/$proj/ 
>/tmp/$proj.svimport.out 2>/tmp/$proj.svimport.err
     tail /tmp/$proj.svimport.err
     tail /tmp/$proj.svimport.out
-    rm theirproj.dump.bz2
+    rm $proj-dump.bz2
 
 Sometimes we may be given a tar of their svn repository.  In this case,
-please ask for a proper svn dump (produced by `svnadmin dump`).  Using a
-direct tar is not recommended because we may not be using the same
-versions of SVN, and sometimes the format changes with the new versions
-of SVN.
+we must ask for a proper svn dump (produced by `svnadmin dump`).  Using
+a direct tar is not safe because we may not be using the same versions
+of SVN, and sometimes the format changes with the new versions of SVN.
 
-The subversion svnadmin load of a thousand version is machine
-intensive and time consuming.  A typical project might load at the
-rate of one version per six seconds.  Meaning that this import might
+The svnadmin load is machine intensive and time consuming; it can easily
+take several seconds per revision.  Meaning that this import might
 easily take several hours to load on a project with any significant
 history.  Planning accordingly by running the task under a screen
-session so that it can complete even if your connection to it is
-dropped is a good idea.
+session, or using nohup, or some such, so that it can complete even if
+your connection to it is dropped is a good idea.
 
-**Note:** If converting from another version control system on
-Savannah then as a final step the prior system should be disabled to
-prevent further commit access there.
+If converting from another version control system on Savannah then as a
+final step the prior system should be disabled to prevent further commit
+access there, see for example [[CvsDisabling]].
 
-* [[CvsDisabling]]
-
-Manually Creating A Subversion Repository
+Manually creating a Subversion repository
 -----------------------------------------
 
-If as a root admin you manually create a subversion repository then
-the files will be set too user:group root:root and the permissions
+If as a root admin you manually create a Subversion repository then
+the files will be set to user:group root:root and the permissions
 will be restricted by the root umask 022.  These will need to be
 converted to the project group and permissions.