STONESVN · PRACTICAL GUIDES
An SVN GUI for Linux: install StoneSVN and connect your working copy
By the StoneSVN project · Checked against StoneSVN v1.1.2 · Reviewed
StoneSVN is an MIT-licensed graphical Subversion client for Linux. It uses your installed svn command-line client to work with existing SVN repositories and working copies. The v1.1.2 release provides x86_64 AppImage, DEB and RPM packages; a Linux ARM64 installer is not part of that release.
Which Linux download should I choose?
- DEB: the package format for Debian and Ubuntu systems with a compatible desktop runtime.
- RPM: the package format for compatible RPM-based distributions.
- AppImage: an alternative package format for x86_64 Linux. It still requires the external SVN CLI and compatible system libraries; it does not make StoneSVN independent of every distribution dependency.
Download from the official v1.1.2 release. Filenames ending in amd64 and x86_64 refer to the same processor family. This is a package-selection guide, not a claim of manual installation testing on every Linux distribution.
Do I need to install Subversion separately?
Yes. On Debian or Ubuntu, install the distribution's Subversion client package and confirm that the executable is available:
sudo apt-get update
sudo apt-get install subversion
svn --version --quiet
command -v svnFor other distributions, use the appropriate package manager. Apache maintains a list of Subversion binary packages; those packages are maintained by their respective distributors. StoneSVN needs the client executable, not a new SVN server or Apache module. If the version command fails, resolve that installation problem before opening a working copy in the GUI.
How do I connect StoneSVN to an existing working copy?
- Install the compatible StoneSVN package and launch the application.
- Let StoneSVN detect SVN. If it cannot find it, use the executable path reported by
command -v svnin Settings. - Add your existing local working-copy directory to the project sidebar, or use Checkout to create a new working copy from a repository URL.
- Refresh the file list and open a changed text file to inspect the diff.
- Select the intended files or directories and review the commit message before committing.
Your repository URL, credentials, network access and permissions still apply. There is no StoneSVN-specific repository conversion.
Can I keep unfinished changes out of a commit?
Choose the files and directories included in the commit. When two tasks overlap inside a text file, save selected text hunks to a local stash and inspect the remaining diff. Local stashing is separate from SVN commits and does not share saved work with teammates.
What should I check if SVN works in a terminal but not in the app?
A desktop launcher may have a different environment from your terminal. Confirm the SVN executable path in Settings, then retry the same repository with the CLI to distinguish executable discovery from repository access. Read the actual error before changing credentials or permissions. Runtime-library failures should be investigated for the chosen package and distribution; changing SVN credentials will not fix a desktop runtime failure.
What are the current limits?
General Merge, Switch and line-by-line Blame interfaces are not available. Use the SVN CLI or another client when those workflows are required. StoneSVN is developed from OrcaSVN, using Tauri 2, Rust and Vue 3. See the user guide for the current workflow and report reproducible installation issues with your distribution, architecture, package and error message.
Download official installers · Source at v1.1.2 · Report an issue