title: What should I do when 'svn cleanup' fails?
body: <p>I have a lot of changes in a working folder, and something screwed up trying to do an update.</p>
  
  <p>Now when I issue an 'svn cleanup' I get:</p>
  
  <pre><code>&gt;svn cleanup .
  svn: In directory '.'
  svn: Error processing command 'modify-wcprop' in '.'
  svn: 'MemPoolTests.cpp' is not under version control
  </code></pre>
  
  <p>MemPoolTests.cpp is a new file another developer added and was brought down in the update. It did not exist in my working folder before.</p>
  
  <p>Is there anything I can do to try and move forward <strong>without</strong> having to checkout a fresh copy of the repository?</p>
  
  <p><strong>Clarification:</strong> Thanks for the suggestions about moving the directory out of the way and bringing down a new copy. I know that is an option, but it is one I'd like to avoid since there are many changes nested several directories deep (this should have been a branch...)</p>
  
  <p>I'm hoping for a more aggressive way of doing the cleanup, maybe someway of forcing the file SVN is having trouble with back into a known state (and I tried deleting the working copy of it ... that didn't help).</p>