Help needed with Subversion error

I was updating a third party library and committing the new version to my SVN server. Many changes were involved (years worth). At the end of the commit, I got this message:

... lots of stuff ...
Commit succeeded, but other errors follow:
Error bumping revisions post-commit (details follow):
In directory 'D:\Documents and Settings\scottb\Desktop\imageen'
Error processing command 'committed' in 'D:\Documents and Settings\scottb\开发者_如何转开发Desktop\imageen'
Error getting 'affected time' for 'D:\Documents and Settings\scottb\Desktop\imageen\.svn\text-base\ImageEn.cnt.svn-base'
Can't stat 'D:\Documents and 
Settings\scottb\Desktop\imageen\.svn\text-base\ImageEn.cnt.svn-base': The 
system cannot find the file specified.

So from the first line it appears that the commit took place. But what do the other errors mean and do I need to do something to fix them? Is the repository damaged at this point? Will I have problems in the future committing changes?

In case it matters I'm using TortoiseSVN 1.6.7 Build 18415, Subversion 1.6.9 (client) and the server is Subversion 1.6.5. I haven't had any other issues with these tools.

It's a wonderfully detailed error message with no helpful information in it. Thanks for any insights on this!

This appears to have just been a client-side issue only and didn't affect the server. I simply deleted the directory in question and did an UPDATE command. The directory was recreated and re-downloaded and all appears to be fine now.

Maybe this is related to case sensitivity of Subersion since I see imageen and ImageEn in the log.This can be helpful.

I had the same error "Can't stat {xml file}" but I had a different cause. There was a lock by Visual Studio on my file. When I closed Visual Studio, it released the lock on the xml file and I was able to mark the parent of this folder as deleted (got the red x icon).

Before this issue, I had went to TortoiseSVN > Delete, and deleted a huge tree of folders. But the folder where that file lived didn't get the deleted status because Visual Studio was holding that lock.