SVN copy between repositories with history

SvnVersion ControlData Migration

Svn Problem Overview


One of my teammates has asked if it is possible to export from one SVN to another, all while maintaining history.

To me, this seems like it would be a common request.

So: Is it possible to migrate between SVN repositories all while maintaining history?

It is important to note that we do not have svnadmin access on the Source, but we do have that on the Destination.

If this comes down to just checking out each revision from the source, and checking it in to the destination, we would be OK with that, as long as there was an automated process for that.

EDIT: I forgot to mention that the destination repo is on windows.

Svn Solutions


Solution 1 - Svn

[Edit: The original reply below is from pre SVN 1.7, and there this was the best way to solve the problem (although it is not the primary use case of svnsync). In SVN 1.7 client or later there is the svnrdump tool that does more directly what you are trying to achieve)]


use svnsync to synchronize the source to the destination (needs admin access to the destination repository or at least a way to add hooks, but no special access to the source repository). If the destination already has revisions, sync the source to a temporary repository, and then use svn-merge-repos.pl to merge the two local repositories.

Solution 2 - Svn

The way to typically achieve this is the svnadmin dump command. If you don't have svnadmin access then I would ask the person that does if they can supply you with a dump. This will make the process of importing much easier as well.

Are you on a shared repository currently? This might make the person that owns the repository leary of giving you a dump, since it will be a copy of the entire repository, not just your piece of it.

Solution 3 - Svn

I had a similar need (hence visited this page) and ended up writing my own program to do the work. Thought the tool may be useful to others who are still looking for a solution:

  • The tool needs no admin access to the source repository.
  • It supports add/delete/copy/move, preserves node property (e.g. svn:ignore, svn:external) and revision property (i.e., you get the correct author and date/time).
  • Can also incrementally copy new revisions.
  • Has both GUI and a command line utility.

If anybody is interested, check it out here

Solution 4 - Svn

You can use git-svn (or perhaps another SCM system) to accomplish this task.

The steps would be:

1. Get a git svn clone of each repository:
    git svn clone <SVN-REPOSITORY-FROM> source-repo
    git svn clone <SVN-REPOSITORY-TO> dest-repo

 2. Create patches to be imported:
    cd source-repo/
    export commitFrom=`git log --pretty=%H | tail -1`
    git format-patch -o /tmp/mergepatchs ${commitFrom}..HEAD .

 3. Import the patches
    cd dest-repo/
    git am /tmp/mergepatchs/*.patch

Referenced: http://blog.neutrino.es/2012/git-copy-a-file-or-directory-from-another-repository-preserving-history/

Solution 5 - Svn

If you need only a version control repo with full changeset, you can use bzr with bzr-svn plugin. When you checkout a svn repo, everything will be syncronized.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionJohn GietzenView Question on Stackoverflow
Solution 1 - SvnmihiView Answer on Stackoverflow
Solution 2 - SvnLeeView Answer on Stackoverflow
Solution 3 - SvnKenneth XuView Answer on Stackoverflow
Solution 4 - SvnscottysbView Answer on Stackoverflow
Solution 5 - SvnnaanView Answer on Stackoverflow