How do I convert an existing directory to an SVN working copy (WC) without replacing local files?

Question

I have a large Subversion repository with nearly 15 GB of data spread across ~500,000 files. Now I need to check out this repository to a remote host which would take days to complete.

The host I'm checking out to already has a complete copy of the data in the repository. But seeing as the files weren't checked out directly from the repository, they do not constitute a working copy (no ".svn" folders).

I'd like to avoid copying all this data across the network, especially when it already exists on the target host. Is there a trick I can use that will turn a preexisting directory into a working copy without replacing the local files with identical copies from the repository?

Solution 1

As of SVN 1.7 (but not before) you can do this easily with:

svn co --force http://path/to/repo

This will respect the local copy as existing, and you'll see the "E" for existing before each file name in the output: E some/existing/file

If the file is different (new or modified) from the repository it will handle that gracefully too according to the book:

Prior to version 1.7, Subversion would complain by default if you try to check out a directory atop an existing directory which contains files or subdirectories that the checkout itself would have created. Subversion 1.7 handles this situation differently, allowing the checkout to proceed but marking any obstructing objects as tree conflicts. Use the --force option to override this safeguard. When you check out with the --force option, any unversioned file in the checkout target tree which ordinarily would obstruct the checkout will still become versioned, but Subversion will preserve its contents as-is. If those contents differ from the repository file at that path (which was downloaded as part of the checkout), the file will appear to have local modifications—the changes required to transform the versioned file you checked out into the unversioned file you had before checking out—when the checkout completes.

Also note that SVN 1.7 can lead to situations where this a more common problem (perhaps motivating the solution). I hit this problem when moving a sub directory to a new location on disk. In pre-1.7 that would have moved the .svn directory with it and it would have stood alone just fine. In 1.7 the directory became effectively unversioned. But svn co --force saved the day.

Solution 2

There is the relocate command: http://svnbook.red-bean.com/en/1.1/re27.html

EDIT: If the local files aren't linked to a repository then you could create a local repository, import the files into it and then use the relocate command.

Alternatively if you have physical access to both machines you can you check out the repository locally and then copy the files to the remote machine via a external HD.

Solution 3

The following command is to delete all .svn directories.

chmod -R 0755 project_dir
find /project_dir -type d -name .svn -exec rm -rf '{}' +

If you already have a checkout version, you can try to copy those .svn folders by replacing rm with cp. I didn't try though.

Solution 4

svn co --force https://PATH/TO/REPO/ .

Where the . at the end assumes you are already inside the directory which you want to turn into a working SVN copy.

For instances, if you wanted to make your public_html directory a working svn copy of a repository:

cd /home/username/public_html; svn co --force https://PATH/TO/REPO/ .

View more solutions