title: SVN repository broken on Windows after using colon
body: <p>we are using svn in a multi OS environment. I made the mistake to commit a file containing a colon, i.e. <code>bar:foo</code> and <code>baa:foo</code>. Under linux this is ofcourse not a problem but under Windows <code>:</code> is not an allowed character for the file system. After realizing my mistake a renamed the files from linux using <code>svn mv</code>.</p>
  
  <p>The problem is that svn on Windows is stuck when ever a version containing the <code>:</code> is checked out. Consider the following procedure:</p>
  
  <ol>
  <li><p>checkout the repository on its latest state (i.e. with fixed filenames)</p></li>
  <li><p>Checkout a commit containing the filenames with colon. This leads to the following:</p></li>
  </ol>
  
  <blockquote>
    <p>Added foo</p>
    
    <p>Skipped obstructing working copy foo</p>
    
    <p>Warning! One or more files are in a conflicting state.`</p>
  </blockquote>
  
  <ol start="3">
  <li>Now trying to go back to the corrected version with <code>svn co</code> gives the error:</li>
  </ol>
  
  <blockquote>
    <p>Error 'bar:foo'  is not a valid filename in directory Folder`</p>
  </blockquote>
  
  <ol start="4">
  <li>Didn't work try again <code>svn co</code>:</li>
  </ol>
  
  <blockquote>
    <p>Error The XML response contains invalid XML</p>
    
    <p>Error Malformed XML: no element found`</p>
  </blockquote>
  
  <p>Now the repository is stuck, i.e. no more checkout is possible as you will always get the last error. Note that this creates a file <code>foo</code> which is not in the repository. I tried to remove the file and/or use <code>svn cleanup</code>. But without any success as the file is always restored before <code>svn</code> tries to perform the actuall update.</p>
  
  <p>Is there a way to fix the local svn?
  Or is the only way to make a new checkout and to avoid the affected revisions under Windows at all cost?</p>