On Fri, Jun 27, 2003 at 06:06:01PM -0400, Mark Bohlman wrote:
> Hi,
>
> I'm running Subversion 24.2 on Windows 2000 Server. Our sysadmins
> recently created a newer (and better) machine for development to use for the
> repository, and I need to migrate from the current machine (A) to the new
> machine (B). Connections are currently via svnserve as Apache is not yet
> setup (they control the ports as well, and well...)
>
> Question is how best to handle the change from the developer
> perspective. A scenario would be
> 1) Code checked out to a working directory /wd via the command "svn co
> svn://A/projects"
> 2) Developers all working in their local directories and in various states
> of completion
> 3) New machine set up and established
> 4) Was hoping that "svn switch svn://B/projects" would switch the entries in
> .svn subdirectories. This does not seem to work (consumes cycles on both A
> server through the svnserve process and on the client machine and never
> returns).
>
You should disable all access to both A and B's repositories, effect the
copy, then enable access to B (leave access to A disabled), then users
should:
svn switch --relocate svn://A/ svn://B/
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 28 00:30:22 2003