hmm...
further testing appears to indicate that the "svn sw --relocate" doesn't
work if the working copy is on the same system as the svnserve daemon...
however, running a separate working copy on a server different from the
svnserve, results in the 'svn sw --relocate' working as expected...
so it appears that if you create a working copy on the same server as the
one running the svnserve daemon, and if you change the svnserve url/port,
then you're going to have to recreate a new working copy.. it appears that
you can't simply do a svn sw --relocate and change the underlying working
copy url/repository root...
thoughts/comments
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2009a_at_ryandesign.com]
Sent: Sunday, April 05, 2009 12:00 AM
To: bruce
Cc: users_at_subversion.tigris.org
Subject: Re: svn relocate question...
On Apr 4, 2009, at 20:44, bruce wrote:
> I do the following.
>
> # svn sw --relocate svn://192.168.1.45/test/svn1/a
> svn://192.168.1.45:7555/test/svn1/a /s
>
> followed by:
>
> # svn info
> Path: .
> URL: svn://192.168.1.45:/test/svn1/a
> Repository Root: svn://192.168.1.45:/test/svn1/a
> Repository UUID: 2cc5218c-d834-4ee9-a3f3-14b0c62c2296
> Revision: 0
> Node Kind: directory
> Schedule: normal
> Last Changed Rev: 0
> Last Changed Date: 2009-04-03 10:23:10 -0700 (Fri, 03 Apr 2009)
>
> anyone able to tell me why the root repository/url didn't change??
>
> i'm trying to change to the new server which has the port 7555
>
> i've searched all over the 'net with no luck!
The URL and Repository Root reported by your working copy have a
curious a colon in it but no port number after that. But your switch
command does not. So to get this to work, you probably need to match
the original repository root (or substring from the start of it)
exactly:
# svn sw --relocate svn://192.168.1.45: svn://192.168.1.45:7555 /s
> i can get this to more or less work using the tortoise gui on
> windows..
In what way have you found it to differ? I haven't used TortoiseSVN
much myself, but it should be using the same Subversion libraries as
the svn command line client, so I would expect it to behave the same
way.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=15
48941
To unsubscribe from this discussion, e-mail:
[users-unsubscribe_at_subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1552450
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-05 18:05:13 CEST