Subversion: Out of date files, But not out of date?
I hope this comes useful to some people, I find sometimes when your playing about with Subversion on your Rails applications that when you commit your changes to a SVN server you get an error like
svn: The version resource does not correspond to the resource within the transaction. Either the requested version resource is out of date (needs to be updated), or the requested version resource is newer than the transaction root (restart the commit).
but the WC (working copy) file is not out of date. thus it does not allow you to commit, huge pain. after goggling i found others with the same issue and found out that deleting a simple file in each SVN directory makes it happy.
Normal Mode
find ./ -name all-wcprops -exec rm -rf {} \;
Safe Mode
find ./ -name all-wcprops -exec rm -r {} \;
Safe mode will run and ask you to confirm the delete of that file so you don’t accidentally delete valuable files
Enjoy
November 16th, 2008 at 11:09 am
Thanks for posting this - it has saved me so much hassle. Any idea why it happens?