Thanks for your support.
- Initially we had repo1 and we have dumped repo1 to our local machine(
our svn is in VPS machine). Then due to some reasons our VPS server got down
for few days.
- Mean while we have loaded the dumped file in ou r local Visual SVN
server and made some commits to it.
- The revision at the time we have dumped the repo is 913
- The revision is increased to 926( in local SVN).
- Then, after VPS has been repaired and it is ready for use, we have
dumped the repo from local Visual svn server.
- Then tried to rename the present repo1 to repo1_old ( our plan is,
rename the repo1 to repo1_old and to create another repo with name repo1
then to load the dumped file to it) but it failed as svn don't have rename
- So, we have created another repository repo1_new keeping the repo1 as
it is and loaded the dumped file in it. The new repo has same revision
history and UUID
The interesting thing is, if we point our webdav location directly to the
new repo( as we did previously) then it is working. But if we modify the
webdav to point to the svn parent path, then the problem persists.
I think, the 2 step solution which you have provided should work. We will
try it once and then let you know.
I have never worked on SVN commands in such a deeper way, but with all your
help and suggestions i am able to succeed in every thing. Hope this problem
will also be solved as you have provided solution for that. Thanks for your
On Sun, Nov 29, 2009 at 5:07 AM, Ryan Schmidt <
> On Nov 28, 2009, at 07:01, Lalitha Prasad wrote:
> > Previously we have only one repository "repo1" in our svn repository
> directory and we made our WebDav to point directly to the repository itself,
> i.e. /home/repos/repo1.
> > With our new requirement, we have created 2 new repositories repo1_new
> and repo2. Now we have changed the svnpath of webdav to point to the parent
> > Up to this every thing worked fine.
> > But when we tried to switch our working copy to the new repo_new(both
> repo1 and repo_new have same code but with different versions), then we are
> getting error.
> > Our repo1_new is like a mirror to the repo1.
> How was repo1_new created from repo1? Do they have the same UUID? Do they
> have the same revision numbers?
> > Detailed information:
> > Previously, our workspace used to point to the url
> > Now we need to switch to the url http://sample.com/svn/repo1_new/trunk
> You're trying to do two things at once. You need to do them separately.
> First you need to relocate the working copy so that portion of the URL that
> points to the root of the repository is updated:
> svn switch --relocate http://sample.com/svn
> (the repository root used to be at /svn and now it is at /svn/repo1_new)
> Then you can switch the part after the repository URL, if desired. For
> example if you want to switch from branch1 to trunk, you do:
> svn switch http://sample.com/svn/repo1_new/trunk
> (the working copy has now been switched from wherever it was
> (branches/branch1) to trunk)
> > We have tried the command svn switch
> http://sample.com/svn/repo1_new/trunk from the workspace. This has thrown
> us error like this,
> > Error:
> > svn: 'http://sample.com/svn/branches/branch1'
> > is not the same repository as
> > 'http://sample.com/svn/repo1_new/trunk'
> > How can solve this one and make my workspace to switch to the new url?
> If the above doesn't help, then it sounds like they are not the same
> repository. If they aren't, then you can't switch or relocate; you must
> check out new working copies.
Thanks & Regards,
V. Lalitha Prasad,
Scube IT Solutions India Pvt. Ltd
(Cell) +91 9966282236
#4-1-319, 2nd Floor, Abids Road, Hyderabad - 01
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-11-30 08:50:02 CET