On Mar 21, 2007, at 05:25, Ashutosh Mohanty wrote:
>> For historical reasons we have a single repository for many
>> products we
>> develop. These products are totally independent so it's not a big
>> deal to
>> have them in the same repository or not. However, we would like to
>> move some
>> products to their own repositories for a more logical and "clean"
>> layout.
>>
>> I know how to do this, using svnadmin dump, svndumpfilter and
>> svnadmin load,
>> keeping the revisions numbers. I have tested this procedure and it
>> works
>> fine. My problem, however, is how to minimise the impact of this
>> on the
>> developers.
>>
>> Ideally, the developers, after the migration to the new repository
>> have been
>> completed, should need only to do something like svn switch <NEW
>> URL>, but
>> it doesn't work, not even with the --relocate switch.
>>
>> The problem could be because I want to relocate a WC of http://
>> <host>/<old
>> rep>/<product> to http://<host>/<new rep>. If I try it I have the
>> error
>>
>> svn: Relocate can only change the repository part of an URL
>>
>> which, I think, means that I could only change it to something like
>> http://<host>/<new-rep>/<product>
>>
>> If I don't use the --relocate switch, then I have the error
>>
>> svn: 'http://<host>/<new rep>'
>> is not the same repository as
>> 'http://<host>/<old rep>'
>>
>> which makes sense.
[snip]
>> The only solution I could think of is for developers to delete
>> their old WCs
>> and check out new ones. But this means that if they are not
>> careful they
>> could loose their changes, that's why a solution using svn to
>> "relocate" the
>> WCs would be more desirable.
>
> You are right, you already tried all sort of things, "svn swich"
> command
> sounds okay to me," --relocate" is only for URL rewriting, anyway,
> just try
> to switch from sub-directory itself; as per your layout--
[snip]
> go to <host> /<old rep> /<product1> /<dir 1> and switch to the same
> sub-directory point in new repository, I guess it may works for you!!
Sorry, Giulio, there is no way to do what you want. "svn switch" is
for switching within a repository, for example to switch a trunk
working copy to a branch. "svn switch --relocate" is for when you
have moved a repository to a new location on the server, or to a
different hostname, or to a different repository access protocol.
Neither of these apply in your situation. In your situation, you have
actually changed the repository. You have dumped part of it and
loaded it into a new repository which has different revisions than
the original repository (revision 1 of the new repository is probably
not the same as revision 1 of the old repository, etc.), maybe has a
different layout than the old repository, has a different UUID than
the old repository, etc. You must throw away the old working copies
and check out new ones. There is no other way.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 24 04:40:56 2007