On 13/09/2007, at 19:49, Constantinos Neophytou ♎ wrote:
[...] svn: Commit failed (details follow): svn: Your file or directory 'config.inc.php' is probably out-of-date 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).
(where config.inc.php is the first file that was modified in the list)
Now the problem is this: The resource is NOT out of date, and I'm the only one with access to the repository.
Does ‘svn up’ solve it?
For example if you change properties on a folder, ‘svn up’ is required.
An update command says that I have the latest revision checked out, and `svn info` verifies the fact. Subsequent check-ins come back with the same error.
What about checkins from the shell? What about ‘svn cleanup’? What does ‘svn -u st’ show?
The only way I've been able to get around this is check out a new copy of the repository, move the modified files over one by one, and check in from there. And next time I need to check in, the same thing happens. Is there an issue with the 'Find in Project' search and replace feature that I should be aware of? (I use it a lot). Also I don't have any modifications in the bundles, nor any related checked out bundles.
I assume you do not see .svn folders in your project -- the only thing TM could potentially do was mess up the svn meta data (via Find in Project), but by default, the .svn folders are excluded from projects, so shouldn’t happen.