Resource out of date try updating tortoisesvn
It's also going to be much faster, especially if you have a large amount of data to move, because you won't have to transfer all that data over the network again.Are you sure you've checked out the head and not a lower revision?Now the same problem happened also to other projects, after I had to change the content of the svn:ignore property to avoid that other files are sent to the repository, and to subdirectories of the original project; so avoiding to commit the top directory is not a good solution anymore. Not those files that were part of the commit have a more recent revision, simply a higher revision number. As an commit in subversion is never an update this commit takes all directories that were not part of the commit in an "out of date" state - they are no longer present in the latest revision.I tried everything: It is not possible to send the changes of the svn:property to the repository, cleaning does help. Let me try to explain in simple words: SVN cannot merge structural changes - so if you move a file to a new localtion and somebody else does a move to a different location of the same file this will not work. Now you want to change a property in one of those directories, e.g. Try to commit: error message - which is caused by the server and not by the svn client subversive or one of its components.When I try to update that directory, I get "svn: Two top-level reports with no target" One more reason to hate SVN. Move the clean copy to the new location, and use an add and delete to do the move. svn update --force /path to filename/ If your recent file in the local directory is the same, there are no prompts.
I moved the dir to my local machine for safe-keeping, then svn deleted the stupid directory, then committed.
This includes both structural changes and property changes of the directory. One bad thing about subversive is that you cannot see whether you have a mixed revision working copy or not - the label decoration only shows the "last changed revision".
This makes sence but from time to time you need the pure revision information as provided by subversion - I allready created an issue for this but it seems not to have enough priority.
You may have had a commit that went sour between the time the new revision was added in the server and the time your client performed its post-commit admin tasks (including refreshing your local text-base copy).
This might happen for various reasons including (rarely) problems in the database back end or (more commonly) network dropouts at exactly the wrong time.
Search for resource out of date try updating tortoisesvn:
Summary: "Working copy is out of date" when trying to commit Applies to: Subversion, all versions Three kinds of situation that can cause this: 1.