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

Re: "switch --relocate" and externals

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-08-21 07:24:07 CEST

On Aug 20, 2007, at 14:05, Phil Endecott wrote:

> I have just switched a working copy from http to https access using
> "svn switch --relocate". This worked as expected. However, I have
> just remembered that there's an "svn external" in there pointing to
> another part of the same repository which needs to change too. How
> should I proceed?
> I imagine that I may need to "svn switch --relocate" from inside
> the external, and also use "svn propedit" to change the external
> definition itself. Do I need to do both? If so, in which order?
> I have uncommitted changes in the working copy, which I can no
> longer commit to the old http: URL.

You would need to "svn propedit svn:externals" and change the URL
from http to https. Then an "svn update" should fix the external
directory. I think. And then (or before the update) you can "svn
commit" the change.

The problem with this is that if you ever want to check out an
earlier version of the project, the external URL will be wrong. An
alternative is to dump the entire repository to a txt file, transform
the file to fix all the existing external URLs, and load it into a
new repository. I believe svndumptool can help you with this task:


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 21 07:22:59 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.