[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 4066] New - Rename to different case leads to inconsistent
From:       ktm1 () tigris ! org
Date:       2011-11-24 13:03:30
Message-ID: iz4066 () subversion ! tigris ! org
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=4066
                 Issue #|4066
                 Summary|Rename to different case leads to inconsistent state
               Component|subversion
                 Version|1.7.x
                Platform|PC
                     URL|
              OS/Version|Windows 7
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|cmdline client
             Assigned to|issues@subversion
             Reported by|ktm1






------- Additional comments from ktm1@tigris.org Thu Nov 24 05:03:30 -0800 2011 -------
Hello.

I am using svn console client which was installed as part of TortoiseSVN 
(Windows 7 64 bit) and I had the problem which I will try to explain further. I 
cannot give exact steps to reproduce it (since I don't remember them), I will 
just describe the working copy state which bothers me and will say a few words 
about how it came to this state.

1. One of our developers created a directory named 'Test' containing file 
'test.txt' and added them to repository
2. I updated my working copy, modified 'Test/test.txt' and created unversioned 
file 'Test/dummy.txt'
3. The developer renamed directory 'Test' to 'test' (changed case)
4. I performed update. During that a tree conflict appeared. I don't remember 
the exact steps I tried to resolve it, but I ended up with the following 
situation:

I execute 'svn revert -R .' on the working copy root and I get:
> Reverted 'test/test.txt'
> Reverted 'Test/test.txt'

When I execute this command again (right after the first attempt) I get the very 
same output. And so on.

Executing 'svn cleanup' does not help. Using TortoiseSVN to make revert or 
cleanup doesn't help either.

So the only solution for me now is to perform a new checkout :(  
I guess such 'unrevertable' repository state is a bug and I hope that this 
information could be somehow sufficient to locate it.

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

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]