[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: Phil Endecott <spam_from_subversion_users_at_chezphil.org>
Date: 2007-08-21 20:07:24 CEST

Ryan Schmidt wrote:
> 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.

Thanks Ryan, and also thanks also Karl for this:
> Try propediting locally after you switch, then run update? (I'm not positive
> that will work; some experimentation may be necessary.)

Based on previous experience I decided to ask the list before doing any
"experimentation", since the story about not digging if you're in a
hole seems to apply to Subversion....

Anyway, I have:

- propedit to change the URL
- switch --relocate inside the external
- commit inside the external (I had uncommited changes)
- update in the directory above, containing the external definition.
Not sure why this was needed.
- commit in this directory to save the change to the external.

This seemed to go OK. Maybe I could have done it in fewer steps.
I have other working copies, so in them I have to:

- update. This seems to automatically switch the external, and seems
safe even if there are uncommited changes (I think).

> 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.

Yes. Ugh. I think the moral is, always use https for everything from
the beginning. Do the appropriate docs suggest this? Of course, you
then run into the general SSL+virtual-hosts pain.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 21 20:05:24 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.