After upgrading to the new SourceForge (Allura) your SVN URLs will change. This document attempts to answer some of the more common questions about this change.
A: As the project admin, you have a choice of how you handle the change in your SVN URL.
If your repository is small, or if you have a fairly small number of developers, it’s probably easiest to have your developers delete their working copy and get a fresh checkout from the new URL. Give your developers sufficient warning of the upgrade that they can check in any outstanding changes that they have in their working copies.
However, if you have a large number of developers, or if your repository is large enough that checking it out again takes a long time, you’ll need to update the UUID on the new repository to match the old one.
To obtain the UUID that you want to change it to, in the root of your working copy (WC) type:
You’ll get various information about your working copy, one line of which will look like:
Repository UUID: 7e586231-33eb-48a5-920c-4ad53d6b1ac4
Log in to your SourceForge shell account
ssh -t USER,PROJECT@shell.sourceforge.net create
and update the UUID of your new repository from the shell:
svnadmin setuuid /home/svn/p/PROJECT/code UUID
replacing UUID with the one from your WC (the one bolded above).
Once you’ve done that, everyone with a working copy of the repository needs to update their WC to point at the new location. Run the svn relocate command in the root of your working copy:
svn relocate https://svn.code.sf.net/p/PROJECT/code/
Verify what your new svn repository URL is on your project code page. For example, if you have several repository types, they may be named svn or git, rather than code.
A: The URLs of your old repository - both the repository itself, and the ViewVC interface to that repository, will not change yet. We will keep them referencing the classic SVN repository, so you can verify that everything migrated over properly. In early 2013, we plan to redirect the ViewVC web pages over to the new code browser. We'll also be investigating how to do that for the repository itself.