Menu
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!
990
Subversion is an open source centralized version control system. It's licensed under Apache. It's also referred to as a software version and revisioning control system.
To view or break locks, right-click in the Current Folder browser and select Source Control > Locks. If you see an SVN message reporting a working copy locked error, remove stale locks. In the Current Folder browser, right-click and select Source Control > SVN Cleanup.
svn locking information may have become corrupt and performing an svn cleanup on the local working copy may resolve this issue. Installing TortoiseSVN and restarting enables a cleanup option in the right-click menu of the local working copy (the parent folder that contains the .
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.
90
Maybe this is related to case sensitivity of Subersion since I see imageen and ImageEn in the log.This can be helpful.
40
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
