# Install git-svn with Homebrew, apk, apt, dnf, zypper Bidirectional operation between a Subversion repository and Git. Version 2.55.0 via Homebrew; verified 2026-06-29. Also installable with debian: sudo apt install git-svn. ## Install ```sh sudo av install brew:git-svn ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install git-svn ``` Evidence: local Homebrew formula metadata ### Linux - apk (92%): ```sh sudo apk add git-svn ``` Evidence: Alpine Linux edge package indexes: git-svn from https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz - Debian apt (92%): ```sh sudo apt install git-svn ``` Evidence: Debian stable package indexes: git-svn from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - dnf (92%): ```sh sudo dnf install git-svn ``` Evidence: Fedora Rawhide package metadata: git-svn from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst - zypper (92%): ```sh sudo zypper install git-svn ``` Evidence: openSUSE Tumbleweed package metadata: git-svn from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst ## Package facts - **Package key:** brew:git-svn - **Package manager:** Homebrew - **Version:** 2.55.0 - **Source summary:** Bidirectional operation between a Subversion repository and Git - **Homepage:** - **Repository:** - **Last updated:** 2026-06-29T20:54:54Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - git-svn (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 2.55.0 ## Project history and usage git-svn is Git's built-in bridge for teams that need bidirectional operation between a Subversion repository and a Git repository. It lets a Git checkout track SVN trunk, branches, and tags while still sending commits back with dcommit. ### Project history The git-svn manual describes the command as a conduit between Subversion changesets and Git commits. Its design grew around SVN layouts rather than Git remotes alone: users can initialize tracking for standard trunk/branches/tags repositories, customize trunk, tag, and branch paths, and store SVN remote metadata in Git configuration. ### Adoption history git-svn became important during the long migration from centralized Subversion repositories to distributed Git workflows. Package managers often ship it as a separate package from core Git because SVN interoperability brings extra runtime dependencies, making it visible as its own installable tool even though it belongs to the Git source tree. ### How it is used Practitioners use git svn clone or init plus fetch to import SVN history, rebase local Git work onto new SVN revisions, and dcommit Git commits back to the SVN server. It is also used as a migration tool: teams import a legacy SVN repository into Git, inspect or repair branch/tag mapping, and later stop using SVN once the Git repository becomes authoritative. ### Why package nerds care The package matters because it captures an interoperability boundary in packaging form. Installing git alone is not always enough for old enterprise repositories; installing git-svn adds the SVN bridge, Perl plumbing, and documentation needed to keep legacy repositories moving while the rest of a toolchain speaks Git. ### Timeline - Before Git 2.0: SVN-tracking refs used no default prefix, placing them directly under refs/remotes. - Git 2.0: git-svn documentation records origin/ as the default prefix for SVN-tracking refs. - Git 2.55.0: Homebrew packages git-svn from the Git release tarball as a separate formula. ### Related projects - git-svn is related to Subversion itself, one-way conversion helpers such as git-svn-abandon, and third-party svn2git tools that focus on final migration rather than ongoing bidirectional operation. ### Sources - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: .git/config, ~/.gitconfig, ~/.config/git/config, /etc/gitconfig ## Other Package-Manager Records - Debian apt - git-svn - 1:2.47.3-0+deb13u1: normalized package name match | Debian stable package indexes: git-svn from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | fast, scalable, distributed revision control system (svn interoperability) | https://git-scm.com/ - Ubuntu apt - git-svn - 1:2.43.0-1ubuntu7: normalized package name match | Ubuntu 24.04 LTS package indexes: git-svn from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | fast, scalable, distributed revision control system (svn interoperability) | https://git-scm.com/ - apk - git-svn - 2.55.0-r0: normalized package name match | Alpine Linux edge package indexes: git-svn from https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz | Subversion support for git | https://www.git-scm.com/ - dnf - git-svn - 2.55.0-2.fc45: normalized package name match | Fedora Rawhide package metadata: git-svn from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | Git tools for interacting with Subversion repositories | https://git-scm.com/ - zypper - git-svn - 2.55.0-2.3: normalized package name match | openSUSE Tumbleweed package metadata: git-svn from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Git tools for importing Subversion repositories | https://git-scm.com/ ## Combined YAML source View the package source record on GitHub. [combined/git-svn.yml](https://github.com/mxcl/pkgdb/blob/main/combined/git-svn.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph