Frank Capodieci <frank.capodieci_at_musicmastermind.com> writes:
>> What is the nature of the changes that update was trying to pull? (You
>> can determine that with 'svn log -q -v -r BASE:HEAD', or with the
>> equivalent Tortoise screen.) Specifically, do they include any tree
>> changes, or symlink changes?
>
> There were a couple of files Moved, in a check in made on Ubuntu 10.10. I
> did have some local modifications, but the problem persisted after I copied
> the changes out and reverted.
>
> I tried deleting the folders with the tree changes, but the exception still
> happens when I update.
>
> Another programmer is getting the same problem, also on Windows.
We still don't have enough information to understand the problem. Does
the problem occur if update individual subdirectories of files? What is
the smallest part of the working copy that causes the problem? Please
the dsecribe the changes that the update is making more fully. Are
there text changes, property changes, svn:special changes, adds,
deletes, copies?
Is the problem reproducible in a new working copy? If you checkout a
new working copy at the old revision and update does the problem occur
in the new working copy?
--
Philip
Received on 2012-01-19 10:29:32 CET