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

Interrupted update after external change may leave WC inconsistent

From: Anton V. Kravtsov <ka5_at_ukr.net>
Date: Thu, 12 Nov 2009 11:05:00 -0800 (PST)

Hi all,

I've recently encountered an issue which costed me several hours of wasted work :(

For simplicity I assume I have a directory with two externals:
ext1 https://server/proj1/trunk
ext2 https://server/proj2/trunk

Someone changes the 2nd external to point to a branch, which has a lot of updates.

After I do an update of my WC, the externals are updated and the changes are populated down the tree.
Accidentally I decide to interrupt the ongoing update (well, there are may be different reasons for that).

Next time I start the update from the root, and discover that some subdirectories become "sticky" - they still point to trunk, though I expect them to point to the "branch".

I suppose, SVN is not able to detect such inconsistencies in WC caused by interrupted "switch".
Or do I miss some option?

I think, SVN should remember somehow (in WC?) that "switch" wasn't completed, and take this information into account next time when doing update of the same tree from the top.

Version: 1.6.5 (used through TortoiseSVN and command line)

Any ideas/remarks?

thanks!

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2417182

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-12 20:06:05 CET

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.