Thanks for the suggestion, but this does not seem to work either.
This is only a problem for WC with local modifications. So, here's
what I've done:
1) Create a patch file from the top level of the WC that contains
local modifications.
2) Checkout a new WC (with functioning svn:externals)
3) Apply the patch file to the new WC.
Fortunately we're not talking a huge number of files, but still not as
clean as I had hoped for.
Thanks,
Paul
On 3/5/07, Simon Large <simon@skirridsystems.co.uk> wrote:
>
> Issue 2209 was just a performance enhancement. Previously, if you
> changed the external to point to a different location in the same repo
> (eg a new tag) it would delete the entire WC tree for that external and
> do a fresh checkout. The new behaviour is to do the equivalent to
> 'switch' and just pull down the changes.
>
> I think what is happening is this:
>
> You update the svn:externals in the repo.
> You relocate your working copy.
> Update fails :-(
>
> Relocate does not work on externals (a known limitation of subversion).
> So until you update your working copy, it does not pull down the
> property updates from the server, and it does not know the external refs
> have changed.
>
> A workaround to try: First update-to-revision, and check the 'ignore
> externals' box. This should update the properties without trying to
> reference them. Now do a second update to update the external references
> too.
>
> Simon
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Mar 6 01:12:38 2007