Page History

1. Install SubGit

...

1. tool according to the Installation guide.
   
   
2. Configure GitLab server:
   
   
   • Log in Login to GitLab web GUI and create a new project:
     Image RemovedImage Added
     

     
     

     Give a name to your project and click , do not check “Initialize repository with a README” checkbox, and click Create project button button.
     

     Image Removed

   • Login to the GitLab server (over ssh or to the local console) and install JRE:

     • for CentOS 6/7:

       $ sudo yum install java

     • for Debian and Ubuntu:

       $ sudo apt-get install default-jre

     • for OpenSUSE: $ zypper in java

     install SubGit binary:

     • On CentOS and OpenSUSE Linux download universal subgit-3.2.4.zip binary:

       https://subgit.com/download/subgit-3.2.4.zip and unzip it: $ unzip subgit-3.2.4.zip

     • on Debian and Ubuntu download Debian package:

       https://subgit.com/download/subgit3.2.4all.deb

       fetch missing dependencies and install:

       $ sudo dpkg -i subgit3.2.4all.deb $ sudo apt-get install -f

   Configure the repository:

   • 
     

     Change identity to 'git' user:

     su Image Added

      
3. Configure the repository:
   
   

   • Change identity to 'git' user:

     Code Block
     language text theme FadeToGrey title change identity to git user
     $ su git

     
     

   • Change directory to that one that contains the newly created project. GitLab usually stores its project in

     • Older versions of GitLab stored projects in

       No Format
       /var/opt/gitlab/git-data/repositories/<username>

     username here is actual GitLab user name that was

     • where <username> was the GitLab username that had been used during the project creation on step 1.

     Step into that directory:$ cd

     • Since version 10.0 GitLab uses hashed storage as follows:

       No Format
       /var/opt/gitlab/git-data/repositories

     /user

     New GitLab project we have created in step 1 is being stored here in the directory of the same name we named the project:

     $ ls -l total 0 drwxrwx---. 6 git git 131 apr 25 02:06 project.git drwxrwx---. 6 git git 131 apr 25 02:06 project.wiki.git

     Run this command to configure SubGit import:

     $ /temp/subgit-3.2.4/bin/subgit configure --layout auto --trunk trunk SVNURL GITREPO

     > To be added into pop-up cloud (when hovering on SVNURL and GITREPO): > > SVN_URL - URL to the SVN project. > > GIT_REPO - path to new Git repository where data from the SVN project will be imported to. see command example --> (to be placed in drop-down block):

     $ /tmp/subgit-3.2.4/bin/subgit configure --layout auto --trunk trunk

     • /@hashed/<hash[0..1]>/<hash[2..3]>/<hash>.git

       
       

       Note
       To find the repository path in GitLab v.10+, follow this guide.

       
       

   • Navigate to that directory:

     Code Block
     language text theme FadeToGrey title change directory
     $ cd /var/opt/gitlab/git-data/repositories/<repo_path>

     
     

   • Perform initial import configuration:

     No Format
     $ subgit configure --layout auto --trunk TRUNK SVN_URL GIT_REPO

     where

     • SVN_URL    – SVN project URL.
     • GIT_REPO  – a path to new Git repository.
     • TRUNK        –  a path, relative to SVN_URL, that leads to an SVN directory that plays a role of the main line of development.

     Expand
     title see the configuration command example.
     Code Block language text theme FadeToGrey title subgit configure example $ subgit configure --layout auto --trunk trunk http://svn.example.com/svn/repository/project ./project.git

     SubGit version

     SubGit version 3.2.4 ('Bobique') build

     #3670Configuring writable Git mirror of remote Subversion repository: Subversion repository URL :

     #3670 Configuring writable Git mirror of remote Subversion repository: Subversion repository URL : http://svn.example.com/svn/repository/project Git repository location : ./project.git

     Git repository is served by GitLab, hooks will be installed into

     Git repository is served by GitLab, hooks will be installed into 'custom_hooks' directory.

     Detecting peg

     Detecting peg location... Authentication realm:

     http

     <http://svn.example.com/:

     80

     80> Subversion Repository Username [git]: user Password for 'user': Peg location detected: r10248 project/trunk Fetching SVN history... Done. Growing trees... Done. Project origin detected: r1 project/trunk Building branches layouts... Done. Combing beards... Done. Generating SVN to Git mapping... Done.

     CONFIGURATION SUCCESSFUL

     To complete SubGit installation do the following:

     1) Adjust Subversion to Git branches mapping if necessary:

     CONFIGURATION SUCCESSFUL To complete SubGit installation do the following: 1) Adjust Subversion to Git branches mapping if necessary: /var/opt/gitlab/git-data/repositories/user/project.git/subgit/config 2) Define at least one Subversion credentials in default SubGit passwd file at: /var/opt/gitlab/git-data/repositories/user/project.git/subgit/passwd OR configure SSH or SSL credentials in the [auth] section of: /var/opt/gitlab/git-data/repositories/user/project.git/subgit/config 3) Optionally, add custom authors mapping to the authors.txt file(s) at: /var/opt/gitlab/git-data/repositories/user/project.git/subgit/authors.txt 4) Run SubGit 'install' command: subgit install ./project.git

     
     

   • Specify authors mapping.
     
     Configure authors mapping in the default authors mapping file:
     

     No Format

     Update

     GIT_REPOS/subgit/authors.txt

     file or change

     Or change core.authors option to point to  option so that it points to the global authors mapping file.
     Find more details about authors mapping in Import bookin Authors mapping article.

   
   
   
4. Perform import and start using the new Git repository:
   
   

   • Import data to the repository by the command:

     No Format
     $

     /tmp/subgit-3.2.4/bin/subgit import

     subgit import GIT_REPO

     see command example --> (to be placed in drop-down block):

     $ /tmp/subgit-3.2.4/bin/subgit import

     
     

     Expand
     title See import example
     Code Block language text theme FadeToGrey title subgit import $ subgit import ./project.git

     SubGit version 3.2.4 ('Bobique') build #3670

     Authentication realm:

     http

     <http://svn.example.com:

     80

     80> Subversion Repository Username [git]: user Password for 'user':

     Translating Subversion revisions to Git

     Translating Subversion revisions to Git commits...

     Subversion revisions

     Subversion revisions translated: 10248. Total time: 2 hours 15 minutes 38 seconds.

     IMPORT SUCCESSFUL

     
     
     

   • When the command completes, you can clone your new Git repository and start to work with it:

     No Format
     $ git

     clone GITREPO WORKTREE

     clone GITREPO WORKTREE

     where
     WORK    WORK_TREE -  – a path to your working copy.

     GIT_REPO - GitLab project URL:

     Image Removed

     see command example --> (to be placed in drop-down block):

     $ git clone   

     Image Added

     
     

     Expand
     title See the command example
     Code Block language text theme FadeToGrey title repository cloning example $ git clone http://user@example.com/user/project.git

     ./

     /home/user/gitlab_project.git Cloning into '

     ./

     /home/user/gitlab_project.git'... Password for 'http://user@example.com': remote: Counting objects: 99, done. remote: Compressing objects: 100% (39/39), done. remote: Total 99 (delta 50), reused 99 (delta 50) Unpacking objects: 100% (99/99), done.

     
     

     Warning
     title Empty working tree case
     If Git warns you that you are cloning an empty repository and you don't see your files in the working tree, most probably automatic branches and tags mapping didn't work correctly. In this case, mapping has to be set manually, see details on mapping in Branches and tags mapping.

     
     

5. Get support:
   
   If you run into any problems, see one of the following guides for more details:
   
   
   • SubGit configuration file reference
   • Authors mapping
   • Branches and tags mapping
   • Branches and tags mapping examples

...

Should you need assistance, don't hesitate to contact us at support@subgitat support@tmatesoft.com.