[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Relocate issue

From: Wilson, Kalin (N-Scitor) <kalin.wilson_at_lmco.com>
Date: 2006-02-08 22:29:30 CET

Hello,

 

I ran in to a problem after relocating a working copy to a new URL and I
need to know if there are any constraints on using this command.

 

We need to move our repository to another machine - new IP, etc

Here is what I did:

1. Created a new empty repository on the new machine - svn create
d:\svnrepos
2. dumped the old repository into the new repository - svnadmin
dump y: | svnadmin load d:\svnrepos (where y: is a network mapped drive
to the other \svnrepos)
3. Told all users to update from old repository
4. shut down old repository server - svnserve - to ensure no more
changes were commited
5. did one final synch of new to old repositories to ensure both
were at same HEAD revision
6. told users to relocate working copies by executing TortoiseSVN
relocate command on root of the working copy, changing the svn:// URL to
the new URL

 

All this went fine with no errors from tortoise during the relocate.
However, I tried to commit modifications from my working copy to the new
repository and got a commit error with no explanation. I verified that
problem from another users working copy.

 

I relocated my working copy back to the old (original) repository and I
was able to commit the changes.

 

Did I do anything wrong? My guess is there is a synchronization issue
with modified files within the working copy. But it may not be practical
to require all users to commit all modifications before we have to move
the repository.

 

I'd rather avoid having to checkout new working copies from the new
repository.

 

Any advice?

 

Thanks,

 Kalin

 

Kalin Wilson

Scitor Corp.

 
Received on Wed Feb 8 22:30:50 2006

This is an archived mail posted to the Subversion Users mailing list.