edA-qa wrote:
> Peter N. Lundblad wrote:
>> step cannot be performed. YOu have to update your WC and merge
>> conflicts on the client. Did someone else remove the directory you
>> were working in in a later revision?
>
> In my case I was the only person working on it (I'm the only user of
> the repository) and I only have it checked out in one directory. So
You may still need to update, which is an odd concept for sole
developers. The reason is that the previous commit bumped the revision
on some parts of your WC but not all. Try doing an update on the top
level of the WC.
> there is some kind of defect here that I triggered, and I am in the
> process of trying to reproduce it (since issuing an update after this
> situation deleted the source directory and target directory of the
> move operation, veyr scary).
Have you tried a top level update? You are aware that a rename is
implemented as a delete followed by an add (or vice versa)? You would
expect to see the directory be deleted, but you should also see a new
one (copy) appear when you update the level above.
It is possible that something was holding a file open at the time you
did your renaming commit, and that caused the delete/add in the WC to
fail at that time. Look at the repo, or check out a fresh WC to see what
is really there.
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 12 13:46:17 2005