![\"install-collabnet-svn-command-line-client-in-windows\"](\"https:\/\/www.scmgalaxy.com\/tutorials\/wp-content\/uploads\/2008\/12\/install-collabnet-svn-comma.png\")
<\/p>\n<\/p>\n
<\/p>\n
Link: http:\/\/www.collab.net\/downloads\/subversion\/<\/a><\/strong><\/p>\n 1. Platform and configuration<\/strong><\/p>\n \n \u00a0\u00a0 Product: CollabNet Subversion server<\/p>\n \u00a0\u00a0 Certified platforms: Windows XP SP2, Win 2003(Standard Edition) R2<\/p>\n \u00a0\u00a0 Apache version: 2.2.8<\/p>\n \u00a0\u00a0 ViewVC: 1.0.5 (requires ActiveState Python 2.5)<\/p>\n \u00a0\u00a0 Repository format: fsfs (bdb support not included)<\/p>\n \n \u00a0 \u00a0Prerequisite: The user needs administrative privileges to install<\/p>\n \u00a0\u00a0 and uninstall CollabNet Subversion.<\/p>\n \n 2. IMPORTANT: Apache version upgraded from 2.0 to 2.2<\/strong><\/p>\n \n \u00a0\u00a0 With the CollabNet Subversion 1.5.0 release, we have upgraded the included<\/p>\n \u00a0\u00a0 Apache server version from 2.0 to 2.2. This is consistent with the<\/p>\n \u00a0\u00a0 packages we provide for other operating systems, and also upgrades our<\/p>\n \u00a0\u00a0 package to the best available version of Apache.<\/p>\n \n \u00a0\u00a0 This is important to existing users because your current Apache 2.0 server<\/p>\n \u00a0\u00a0 configuration cannot be automatically updated to the format of the Apache<\/p>\n \u00a0\u00a0 2.2 configuration file. If you allow the installer to upgrade your existing<\/p>\n \u00a0\u00a0 installation, it backs up your Apache conf, logs, and htdocs folders so<\/p>\n \u00a0\u00a0 that you can refer to your previous configuration when configuring your new<\/p>\n \u00a0\u00a0 server.<\/p>\n \n 3. Installation tips<\/strong><\/p>\n \n \u00a0\u00a0\u00a0\u00a0 If you install an Apache server, the installer asks you for a<\/p>\n \u00a0\u00a0\u00a0\u00a0 \u201cRepository URL.\u201d This represents the prefix of the URL which users can<\/p>\n \u00a0\u00a0\u00a0\u00a0 use to connect to Subversion. If you set this URL to \u2018\/svn\u2019, then users<\/p>\n \u00a0\u00a0\u00a0\u00a0 can checkout their repository from:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 http:\/\/hostname\/svn\/repos-name<\/a><\/p>\n \n \u00a0\u00a0\u00a0\u00a0 We recommend that you use \u2018\/svn\u2019 as your URL prefix, as this is common<\/p>\n \u00a0\u00a0\u00a0\u00a0 practice.<\/p>\n \n 4. ViewVC installation<\/strong><\/p>\n \n \u00a0\u00a0 Users of the Apache web server option can now also have ViewVC automatically<\/p>\n \u00a0\u00a0 installed and configured as part of the installation. You must have<\/p>\n \u00a0\u00a0 ActiveState\u2019s ActivePython 2.5 installed before installing CollabNet Subversion.<\/p>\n \u00a0\u00a0 Download a free version of ActivePython from:<\/p>\n \n \u00a0\u00a0 http:\/\/www.activestate.com\/Products\/activepython\/index.mhtml<\/a><\/p>\n \n \u00a0\u00a0 You must install version 2.5.x.<\/p>\n \n 5. Upgrade procedure<\/strong><\/p>\n \n \u00a0\u00a0 When the installer detects a previous version, it offers to upgrade your existing<\/p>\n \u00a0\u00a0 installation. However, if you want to add ViewVC to your installation, we<\/p>\n \u00a0\u00a0 recommend you use the following process for an upgrade. In general, this is<\/p>\n \u00a0\u00a0 the best process for any upgrade scenario:<\/p>\n \n \u00a0\u00a0 1. Stop Apache or Subversion Server services, if running.<\/p>\n \u00a0\u00a0 2. Copy\/back up any customizations that were done to your Apache installation.<\/p>\n \u00a0\u00a0\u00a0\u00a0 (For example, your httpd.conf file, a password database, any content you<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0 added to the htdocs folder, and so on.)<\/p>\n \u00a0\u00a0 3. Uninstall the currently installed version.<\/p>\n \u00a0\u00a0 4. Manually delete the existing folder if the installer did not remove it. The<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0 uninstall process does not remove files that were added or modified after<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0 installation.<\/p>\n \u00a0\u00a0 5. Follow the normal install instructions for 1.5.<\/p>\n \u00a0\u00a0 6. Manually put back your Apache customizations. NOTE:\u00a0 You cannot simply copy<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0 back the previous configuration file. You must make the appropriate edits<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0 to your new Apache 2.2 version of the configuration file.<\/p>\n \n 6. Post-installation instructions<\/strong><\/p>\n \n \u00a0\u00a0 The installer created a folder to store your repositories. You are not required<\/p>\n \u00a0\u00a0 to use this folder, but if you let the installer install the server to run as a<\/p>\n \u00a0\u00a0 service, then the server has also been configured to serve repositories from this<\/p>\n \u00a0\u00a0 location. It is a good idea to use the location you specified in the installer.<\/p>\n \n \u00a0\u00a0 A. Using svnserve<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0 ==============<\/p>\n \n \u00a0\u00a0 To use svnserve as your server, follow these steps:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 1. Open a new terminal (command prompt).<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NOTE: If you have an old command prompt open (prior to the Subversion<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 installation), remember to open a brand new command prompt.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 2. Create a subversion repository.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 cd <Repository_Path><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 svnadmin create <Repository_Name><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 For example:<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 cd \\repositories<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 svnadmin create my-first-repos<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 3. Setup a password database.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Using notepad, edit the svnserve.conf file inside the conf directory of your<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 repository.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 For example:<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 If your repository is C:\\repositories\\my-first-repos<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 svnserve.conf is:<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C:\\repositories\\my-first-repos\\conf\\svnserve.conf<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Inside svnserve.conf, you see the following information:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ### The password-db option controls the location of the password<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ### database file.\u00a0 Unless you specify a path starting with a \/,<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ### the file\u2019s location is relative to the conf directory.<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ### Uncomment the line below to use the default password file.<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #password-db = passwd<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Follow the above instructions, and uncomment the \u201cpassword-db=passwd\u201d<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 line, so that it simply says:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 password-db = passwd<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 4. Setup usernames and passwords.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Next, edit the passwd file. This passwd file is located in the<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 same directory as svnserve.conf.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Inside the passwd file, you see the following information:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ### This file is an example password file for svnserve.<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ### Its format is similar to that of svnserve.conf. As shown in the<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ### example below it contains one section labelled [users].<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ### The name and password for each user follow, one account per line.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [users]<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #harry = harryssecret<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #sally = sallyssecret<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 To add a new user account, add your own username and password<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 inside the [users] section. For example, if your name is \u201cjoe\u201d,<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 and you want to set your password to \u201csuper-secret\u201d, add a<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 new line like this:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 joe = super-secret<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Add as many users as you like.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 5. Open Port on Windows firewall.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Before starting the server, the firewall must be notified that<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this particular port is going to be used. To enable this port in the<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Windows firewall, follow the instructions found here:<\/p>\n \n \u00a0\u00a0\u00a0 http:\/\/www.microsoft.com\/windowsxp\/using\/security\/internet\/sp2_wfexceptions.mspx<\/a><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Note: svnserve.exe is the program name which needs to be added to the<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 exceptions list. Alternatively, you can also use the port where<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 you decide to run the server. By default, svnserve runs on 3690.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 6. Start svnserve.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 If you elected to have the installer setup svnserve as a service, then open<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 the Services application, find the entry for the Subversion server, and take<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 the Start option. The service has been configured to start automatically<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 on reboot. You can also run this command from the command line:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 net start svnserve<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 If you did not install svnserve as a service and want to start the server<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 manually, run this command:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 svnserve -d -r <Repository_Path><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 For example: svnserve -d -r C:\\repositories<\/p>\n \n \u00a0\u00a0 \u00a0\u00a07. To provide read and write access to anonymous users, modify the <\/strong><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0conf\/svnserve.conf file inside the repository.<\/strong><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 anon-access = write<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 To restrict an anonymous user from the repository:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 anon-access = none<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 8. Check out the repository.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 svn co svn:\/\/localhost\/<Repository_Name><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 For example: svn co svn:\/\/localhost\/my-first-repos<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 Tip: If you check out your Subversion repository from a different computer,<\/p>\n \u00a0\u00a0\u00a0\u00a0 replace \u2018localhost\u2019 with the IP address or hostname of the machine which<\/p>\n \u00a0\u00a0\u00a0\u00a0 hosts the Subversion repository.<\/p>\n \n \u00a0\u00a0 B. Using Apache<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0 ============<\/p>\n \n \u00a0\u00a0 To use Apache as your server, follow these steps:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 1. Configure Apache.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 The installer did these steps automatically based on the repository location<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 entered in the installer. This information is only presented if you want to<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 manually modify the configuration.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Use notepad to edit the httpd.conf file inside the httpd\\conf directory of your<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 CollabNet Subversion Server installation.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Tip: By default, httpd.conf is in the following directory:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C:\\Program Files\\CollabNet Subversion Server\\httpd\\conf\\httpd.conf<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 At the bottom of the httpd.conf file, you see a location directive that looks<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 something like this:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <Location \/svn><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DAV svn<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SVNParentPath C:\\repositories<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/Location><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Change the above section to look like the following:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <Location \/svn><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 DAV svn<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SVNParentPath C:\\repositories<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SVNListParentPath On<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Require valid-user<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 AuthType Basic<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 AuthName \u201cSubversion repository\u201d<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 AuthUserFile C:\\repositories\\password-file<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/Location><\/p>\n \n \u00a0\u00a0\u00a0\u00a0 2. Open a new terminal (command prompt).<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NOTE: If you have an old command prompt open (prior to the Subversion<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 installation), remember to open a new command prompt.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 3. Create Subversion users.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Now create usernames with passwords that can be used to authenticate with<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Apache. Use the htpasswd command to create usernames and passwords for the<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Apache server.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Type the following at the command prompt:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 htpasswd -cm <password-file> <username><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 This command prompts you for a password for the user. Enter the<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 password and retype the password when prompted.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 For example: If you want to create a user \u2018joe\u2019, and the file at<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u201cC:\\repositories\\password-file\u201d, type the following at the<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0command prompt:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 htpasswd -cm C:\\repositories\\password-file joe<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Enter the desired password for the user and retype the password<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 when prompted.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 For additional users, use the following command at the command prompt:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 htpasswd -m C:\\repositories\\password-file joe<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 4. Create a Subversion repository.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 svnadmin create <Repository_Path>\\<Repository_Name><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 For example: svnadmin create C:\\repositories\\my-first-repos<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 5. Open Port on Windows firewall.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Before starting the server, the firewall must be notified that<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this particular port is going to be used. To enable this port in the<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Windows firewall, follow the instructions found here:<\/p>\n \n \u00a0\u00a0\u00a0 http:\/\/www.microsoft.com\/windowsxp\/using\/security\/internet\/sp2_wfexceptions.mspx<\/a><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Note: apache.exe is the program name which you need add to the<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 exceptions list. Alternatively, you can also use the port where<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 you decide to run the server. By default, apache is run on 80.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 6. Start Apache.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 If you elected to have the installer set up Apache as a service, then open<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 the Services application, find the entry for Apache\/2, and take<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 the Start option. The service was configured to start automatically<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 on reboot. You can also run this command from the command line:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 net start apache2<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 To start the server manually, run the following at the command prompt:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 apache<\/p>\n \n \u00a0\u00a0\u00a0\u00a0 7. Checkout the repository.<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 svn co http:\/\/localhost\/svn\/<Repository_Name><\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 For example: svn co http:\/\/localhost\/svn\/my-first-repos<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Tip: If you check out your Subversion repository from a different<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 computer, replace \u2018localhost\u2019 with the IP address or hostname<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 of the machine which hosts the Subversion repository.<\/p>\n \n 7. Known issues<\/strong><\/p>\n \n \u00a0\u00a0 When trying to access a repository via ViewVC, you might see an error<\/p>\n \u00a0\u00a0 trace that ends with this message:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0 ImportError: DLL load failed with error code 182<\/p>\n \n \u00a0\u00a0 This error occurs when you have an older version of the OpenSSL DLLs in your<\/p>\n \u00a0\u00a0 PATH ahead of the CollabNet Subversion bin folder. Many Windows applications<\/p>\n \u00a0\u00a0 ship the OpenSSL DLLs and many of them also use older versions. To fix this<\/p>\n \u00a0\u00a0 problem:<\/p>\n \n \u00a0\u00a0\u00a0\u00a0\u00a0 1. Edit your PATH so that the CollabNet Subversion bin folder is at or<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 near the beginning of your PATH.<\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0 2. Reboot so that your Apache service can pick up the change.<\/p>\n \n 8. Back-end support<\/strong><\/p>\n \n \u00a0 If you try to access an existing BDB (Berkeley DB) based repository through<\/p>\n \u00a0 CollabNet Subversion, then you might receive an alert \u201cFailed to load module<\/p>\n \u00a0 for FS type \u2018bdb\u2019.\u201d This is because CollabNet Subversion does not support BDB.<\/p>\n \u00a0 CollabNet recommends FSFS over BDB for ease of maintenance and supportability.<\/p>\n \n 9. Support for CollabNet Subversion<\/strong><\/p>\n \n \u00a0\u00a0 Find out about CollabNet Technical Support at<\/p>\n \u00a0\u00a0 http:\/\/www.collab.net\/services\/subversion\/<\/a><\/p>\n \n \u00a0\u00a0 Information about CollabNet Training, Consulting, and Migration<\/p>\n \u00a0\u00a0 services is at http:\/\/www.collab.net\/services\/subversion\/training.html<\/a><\/p>\n \n \u00a0\u00a0 Join openCollabNet for community support: http:\/\/open.collab.net<\/a><\/p>\n \n