Installing Subversion on Ubuntu 24.04

Subversion (SVN) is a centralized version control system used to track changes in files and directories. SVN remains widely used as a reliable choice for legacy systems, enterprise environments, and collaborative documentation projects. This guide walks through several paths for installation and migration.

Before You Begin

This guide assumes you’re using a fresh or updated Ubuntu 24.04 system and:

• You’ll need a user account with sudo privileges.
• Familiarity with the command line is helpful but not required.
• If you’re new to version control, see Introduction to Version Control for an overview of Git, SVN, and other tools.

System Prerequisites

• Ubuntu 24.04 LTS system (fresh or upgraded). To verify:
• Internet access to install packages using apt
• Basic system utilities (curl, wget, etc.)
• Optional: Apache (apache2) if you plan to serve SVN over HTTP/WebDAV
• Fresh systems will need to install Apache (covered in the installation steps below). Upgraded systems may already have Apache installed.

Subversion Components by Role

Contributor-Safe Notes • The client-only setup is lean and ideal for contributors who don’t need to host anything. • The server setup requires Apache modules (mod dav svn (use underscores for spaces)) and configuration for access control. • The local team setup is useful for small groups sharing a single machine or LAN-based repo.

Choose Your Path

Follow the installation path that matches your needs:

• Path A: Client-Only Setup - You need to connect to an existing remote Subversion repository. Install only the svn client.

• Path B: Fresh Server Installation - You’re setting up a new Subversion server with Apache for your team. Install Apache, Subversion, and mod dav svn (use underscores for spaces).

• Path C: Upgrade from Ubuntu 22.04 - You’re upgrading your system and need to validate or reconfigure existing SVN setup.

• Path D: Restore or Migrate Server - You’re restoring from backup or migrating to a new server. (Advanced - consider as separate guide)

Each path is self-contained. Choose one and follow it from start to finish.

Client-Only Setup (Path A)

For contributors who need to interact with an existing Subversion repository hosted elsewhere.

Install the SVN Client

    sudo apt update
    sudo apt install subversion

There is no need to install Apache or create local repositories–this setup is for accessing remote SVN servers only.

Validate Client Setup

    svn --version

You should see the installed version (1.14.3 on Ubuntu 24.04) and supported protocols including ra_svn (svn://), ra_local (file://), and ra_serf (http:// and https://).

Common Remote Access Patterns

HTTPS-based access:

    svn checkout https://your domain.com/svn/project svn update

SSH-based access:

    svn checkout svn+ssh://youruser@yourdomain.com/var/svn/project

External References

For examples of more complex usage and server configuration details:

• Subversion Quick Start
• SVN Book - Remote Access

Fresh Server Installation (Path B)

For users starting from a clean system with no prior SVN setup.

Install required packages:

    sudo apt update
    sudo add-apt-repository universe
    sudo apt install subversion apache2 libapache2-mod-svn

Pressing [ENTER] when prompted confirms that you want to add the universe repository. For further details about what is installed, see the Apache Subversion documentation.

Verify the Installation

    svn --version
    apache2 -v

Expected versions for Ubuntu 24.04: Subversion 1.14.x and Apache 2.4.x. If the versions differ verify you’re on Ubuntu 24.04 with lsb_release -a.

Enable and start Apache:

    sudo systemctl enable apache2
    sudo systemctl start apache2

Verify Apache is running

    systemctl status apache2

You should see active (running).

Create Your First Repository

The following steps create a basic Subversion repository to verify your installation and demonstrate core functionality. This example uses /var/svn/project as the repository path and configures Apache to serve it over HTTP with basic authentication.

    sudo mkdir -p /var/svn/project
    sudo svnadmin create /var/svn/project
    sudo chown -R www-data:www-data /var/svn/project

This creates a project folder, initializes it as an SVN repository by creating the internal structure (conf/, db/, hooks/, locks/ folders), and sets ownership of the repository directory and its contents which allows Apache to be able to:

• Read the repository files
• Write to the repository (when changes are committed)
• And, access the db/, locks/, and other folders.

Verify the Repository Structure and Ownership

After each command:

    ls -la /var/svn/project

You’ll see these directories: conf/, db/, hooks/, locks/ and owned by www-data:www-data.

For a minimal Apache configuration, open /etc/apache2/mods-enabled/dav_svn.conf in a text editor:

    sudo nano /etc/apache2/mods-enabled/dav_svn.conf

and add this block to the end of the file:

<Location /svn>
  DAV svn
  SVNParentPath /var/svn
  AuthType Basic
  AuthName "SVN Repository"
  AuthUserFile /etc/apache2/dav_svn.passwd
  Require valid-user
</Location>

If the file already contains a <Location> block, review it before adding this to avoid conflicts.

Then create your first SVN user for HTTP authentication (replace ‘yourusername’ with the name you want to use):

    sudo htpasswd -c /etc/apache2/dav_svn.passwd yourusername

After running the command, you are prompted to:

1. Enter a password (choose a strong password and be sure to record it for future use).
2. Re-enter the password to confirm.

This will be used to authenticate access to your SVN repository using the web browser or HTTP clients.

    sudo htpasswd -m /etc/apache2/dav_svn.passwd anotheruser

- Set a temporary password and communicate it securely to them (they cannot change it themselves via `htpasswd`).
- Ask them to provide you with their desired password to enter during creation.

Restart Apache:

    sudo systemctl restart apache2

Validate Setup

Verify that SVN and the Apache module is loaded:

Check SVN version

    svn --version

You should see the Subversion version information (e.g., version 1.14.3) along with available repository access modules.

Verify that the Apache DAV SVN module is loaded:

    apache2ctl -M | grep dav_svn

You should see dav_svn_module in the output.

Test repository access

Open your web browser and navigate to :

http://your-server-ip/svn/project

You should:

1. Be prompted for authentication (username and password you created).
2. Enter the credentials you created with ‘htpasswd’.
3. See a page displaying “project - Revision 0: /” with “Powered by Apache Subversion

The repository will show Revision 0 because it’s empty - no files have been committed yet. This is normal and confirms your setup is working correctly.

Troubleshooting

If you encounter issues:

• 404 Not Found: Verify your Apache configuration in /etc/apache2/mods-enabled/dav_svn.conf contains the <Location /svn> block and restart Apache
• 403 Forbidden: Check repository ownership with ls -la /var/svn/project - it should be owned by www-data:www-data
• Authentication fails: Verify the password file exists at /etc/apache2/dav_svn.passwd and check Apache error logs: tail -20 /var/log/apache2/error.log
• 500 Internal Server Error: Run apache2ctl configtest to check for configuration syntax errors

Upgrade from Ubuntu 22.04 (Path C)

For those who are upgrading their system and retaining or reconfiguring an existing SVN setup.

Before You Start

Document your current SVN configuration before upgrading. Run these commands and save the output:

    svn --version
    ls -la /var/svn/
    cat /etc/apache2/mods-enabled/dav_svn.conf

    sudo cp /etc/apache2/mods-enabled/dav_svn.conf/ root/dav_svn.conf.backup

Prepare the System

Ensure all packages are up to date and reboot if necessary:

    sudo apt update && sudo apt upgrade -y

If the system indicates a reboot is required (common after kernel updates), reboot your system now:

    sudo reboot

Wait for the system to restart and reconnect before proceeding.

Upgrade the OS

Ensure your system is current, then run the Ubuntu release upgrade tool:

    sudo apt update
    sudo do-release-upgrade

The upgrade process will:

• Download and install Ubuntu 24.04 packages (this may take 30-60 minutes)
• Prompt you about configuration files multiple times during the upgrade
  • For Apache files (apache2.conf, 000-default.conf, dav_svn.conf): Choose “keep your current version” or press N to preserve your SVN configuration
  • For SSH files (sshd_config): Choose “keep your current version” to maintain access
  • For other system files (like grub): The default is usually to keep your current version - press Enter to accept
  • General rule: When in doubt, keep your current version to preserve your working configuration
• Prompt you about service restarts - accept the defaults
• Require a reboot when complete

Important: When the upgrade completes, reboot your system:

    sudo reboot

Wait for the system to come back online before proceeding to the next step.

After reboot: Validate the Upgrade

Once the system restarts, log back in and verify you’re on Ubuntu 24.04:

    lsb_release -a

You should see Ubuntu 24.04.3 LTS.

Verify SVN Upgraded Successfully

Check the SVN version:

    svn --version

You should see version 1.14.3 (upgraded from 1.14.1 on Ubuntu 22.04).

Confirm Apache SVN Module

Verify the Apache SVN module is still loaded:

    apache2ctl -M | grep dav_svn

You should see dav_svn_module (shared) listed.

Validate Existing Repositories

Verify your repository integrity and permissions:

    ls -la /var/svn/testproject
    svnadmin verify /var/svn/testproject

The repository structure should be intact with www-data:www-data ownership. If permissions were changed during upgrade, restore them:

    sudo chown -R www-data:www-data /var/svn

Test Repository Access

Open your browser and navigate to:

http://your-server-ip/svn/testproject

You should be able to authenticate and see your repository, now powered by Subversion 1.14.3.

Troubleshooting Post-Upgrade Issues

If Apache fails to start after upgrade:

Check for module conflicts:

    systemctl status apache2

If you see errors about missing PHP modules (e.g., libphp8.1.so), disable the problematic module:

    sudo a2dismod php8.1
    sudo systemctl restart apache2

If SVN or Apache issues persist:

Reinstall the packages:

    sudo apt update
    sudo apt install --reinstall subversion apache2 libapache2-mod-svn
    sudo systemctl restart apache2

Verify the SVN module is loaded:

    apache2ctl -M | grep dav_svn

Restore or Migrate a Local SVN Server (Path D)

Whether you’re restoring from backup or migrating to a new server, start by preparing the destination system.

Step 1: Prepare the Target System

• Install Subversion and required system packages (see Install or Update section).

• Optional: Create a dedicated SVN admin user for ownership and SSH access.

    sudo useradd -m -s /usr/bin/bin/bash svnuser

• Create a placeholder repo directory (e.g., /srv/svn/projectname) if restoring from filesystem snapshot or hotcopy.
• Ensure correct file ownership before restoring data.

    sudo chown -R svnuser:svnuser /srv/svn

• If migrating to a new server, confirm that the hostname, IP, and firewall rules match your intended access method (e.g., HTTP or SSH).
• If restoring to a shared machine, set group ownership and permissions carefully:

    sudo chown -R svnuser:devteam /srv/svn
    sudo chmod -R g+rw /srv/svn

Consider setting umask 002 for collaborative edits.

• If using Apache, ensure mod_dav_svn is installed and enabled before restoring. You’ll re-map the repo path in Step 3 (Validate Restore and Server Setup).

Step 2: Restore from Backup

Choose the restore method that matches your backup format. All methods assume the target system is prepared (see Step 1: Prepare the Target System).

Option A: Restore from .dump File

    svnadmin create /srv/svn/projectname
    svnadmin load /srv/svn/projectname < /path/to/backup.dump

• Creates a fresh repo and loads historical data.
• Preserves commit history and UUID unless overridden.

Option B: Restore from Hotcopy

    cp -r /path/to/hotcopy /srv/svn/projectname

• This is the fastest method if source and target OS match.
• Preserves hooks, config, and UUID.

Option C: Restore from Filesystem Snapshot

• Mount or extract snapshot to /srv/svn/projectname.
• Validate file integrity and permissions post-restore.

Additional Steps:

• If restoring to a new server, confirm that the repo UUID matches expected value:

    svnlook uuid /srv/svn/projectname

• If needed, override with:

    svnadmin setuuid /srv/svn/projectname NEW-UUID

• If using Apache, ensure svn.conf or httpd.conf maps to the restored path:

    SVNPath /srv/svn/projectname

• If restoring to a shared machine, reapply group ownership:

    sudo chown -R svnuser:devteam /srv/svn/projectname
    sudo chmod -R g+rw /srv/svn/projectname

Step 3: Validate Restore and Server Setup

After restoring the repository, confirm that the server is ready to serve it—whether via local access, Apache, or SSH.

Local Validation (No Apache Required)

    svn info file:///srv/svn/projectname

• Confirms that the repo is readable and intact.
• Shows UUID, revision count, and last changed date.

Apache Validation (If HTTP Access Is Configured)

    svn info http://yourserver/svn/projectname

• Confirms that Apache is serving the repo correctly.
• Requires correct SVNPath mapping and authentication setup.

SSH Validation (If Using svn+ssh://)

    svn info svn+ssh://yourserver/srv/svn/projectname

• Confirms shell access and repo visibility via SSH.
• Requires SSH key setup and shell access to the repository path.

Troubleshooting

If svn info fails, check file permissions and ownership:

    ls -la /srv/svn/projectname

• Ensure svnuser has read/write access.

If Apache returns 403 or 404, check:

- `SVNPath` or `SVNParentPath` in `svn.conf`
- `.htpasswd` and `<Location>` block syntax
- Apache error logs: `journalctl -u apache2` or `tail -f /var/log/apache2/error.log`

If SSH fails, confirm:

- SSH public key is in `~/.ssh/authorized_keys` on the server
- Shell access is allowed for the target user
- User has filesystem permissions to access the repository path

Step 4: Reconfigure Apache or SSH Access

After restoring the repository, update your access configuration to reflect the new server paths, users, or hostname.

Option A: Configure Apache for HTTP Access

Edit your Subversion config file (e.g., /etc/apache2/sites-available/svn.conf):

<Location /svn/projectname>
    DAV svn
    SVNPath /srv/svn/projectname
    AuthType Basic
    AuthName "SVN Project"
    AuthUserFile /etc/apache2/dav_svn.passwd
    Require valid-user
</Location>

Restart Apache:

    sudo systemctl restart apache2

Validate Apache Access:

    svn info http://yourserver/svn/projectname

Option B: Configure SSH Access

For svn+ssh:// access, ensure proper permissions and validate connectivity:

1. Confirm contributors have SSH access to the server
2. Set filesystem permissions for the repository:

    sudo chown -R svnuser:devteam /srv/svn/projectname
    sudo chmod -R g+rw /srv/svn/projectname

3. Validate SSH access:

    svn info svn+ssh://yourserver/srv/svn/projectname

Step 5: Contributor Validation and Local Checkout

Once the server is restored and access is configured, contributors should validate access and update their local working copies.

Fresh Checkout

    svn checkout http://yourserver/svn/projectname

Or for SSH:

    svn checkout svn+ssh://yourserver/srv/svn/projectname

• Ensures clean sync with the restored repo.
• Validates authentication and access method.

Relocate Existing Working Copy

If the repo URL changed (e.g., new hostname or protocol), contributors can run:

    svn switch --relocate OLD_URL NEW_URL

• Avoids full re-checkout.
• Preserves local changes and history.

Additional Notes

• If contributors report UUID mismatch, they may need to re-checkout or ask the repository administrator to override the UUID using:

    svnadmin setuuid /srv/svn/projectname NEW-UUID

• If using SSH, ensure contributors have shell access and are using the correct repo path. You can validate with:

    svn info svn+ssh://yourserver/srv/svn/projectname

• If using Apache, confirm that .htpasswd is updated and that contributors are using the correct realm name.

Troubleshooting

Common Errors and Contributor-Safe Resets

References

• If contributors are unsure of whether to re-checkout or relocate, recommend:

     svn switch --relocate OLD_URL NEW_URL

This preserves local changes and avoids unnecessary resets.

• If Apache logs are unclear, use these commands for more information:

      journalctl -u apache2
      tail -f /var/log/apache2/error.log

• If SSH access is flaky, validate with:

    ssh -v username@yourserver

Additional Resources