SVN migrating from Windows to Mac

http://my.oschina.net/grnick/blog/161424

First, Backup VISUALSVN project

1. Now use Linux as the SVN server, previously on Windows Server 2008, with VISUALSVN, as shown in.

2. Now there is a project FPP in SVN that needs to export the FPP project to a Linux environment. Run cmd, enter command svnadmin dump E:\REPOSITORIES\FPP > E:\svnbak\fpp.dump Export the project to the E:\svnbak directory. The results of the operation are as follows:

3. The visible command exports the details of each version, ensuring that the previous historical information is not lost. Now we have the backup file Fpp.dump, as follows:

4. Using batch processing to achieve the bulk export of the project, write Svnbak.bat, double-click Run, will export all items at once, the results such as:

Second, upload backup files to Linux

1. Using FTP, SSH and other tools to transfer fpp.dump files to a Linux server, where the use of direct use of openssh this software upload. , the file upload is successful and the file path is/root/fpp.dump.

Iii. installation and configuration of SVN under Linux

1. Install SVN under Linux and install it directly with the Yum command. Yum install Subversion to complete subversion installation.

2. Build the repository directory svndata.

Mkdir/svndata

Svnserve-d-r/svndata #启动svn, set the repository directory to/svndata

Killall Svnserve #关闭svn

3. Create a project library

Svnadmin CREATE/SVNDATA/FPP

4. Configure User access rights

Cd/svndata/fpp/conf

VI svnserve.conf

Release comments for the following lines

Anon-access=none

Auth-access=write

password-db=passwd

5. Increase access to the user, in the format (username = password), the equal sign with a space on either side, otherwise invalid. For example, without adding a space, it has been useless:

6. SVN's command is not introduced here, everyone to learn to use.

Iv. Importing Backup files

1. Enter the command: Svnadmin LOAD/SVNDATA/FPP </root/fpp.dump, the result of the operation is as follows:

2. In order to avoid importing items individually, a shell script was written to bulk import, traversing all *.dump files in the backup directory and producing the corresponding import commands, 15 items, which took about 10 minutes to complete the import, the script is as follows:

V. Checking out the Client for code

1.windows Terminal Mount TortoiseSVN, right-click SVN checkout

2. In the dialog box that opens, enter the address of the SVN repository to make sure you can synchronize the project. Address as follows, IP address plus project name,

3. SVN prompts for a successful checkout and can find the checked out item in the directory.

4. For the previous project, redirect to the new SVN server, right-->tortoisesvn->relocate, in the popup dialog box to fill in the new address, TortoiseSVN will be prompted to modify the success, then you can use the new SVN.

5. If you are using the Subeclipse plugin in Eclipse, first open the SVN repository view and select your project, right-click Redirect and fill in the new SVN address.

6. If you use the SVN command under Linux, the form is as follows:

SVN switch--relocate (old Repository root) (New Repository root)

SVN migrating from Windows to Mac