tags:

views:

13066

answers:

9

I've been attempting move a directory structure from one location to another in Subversion and I've run up against a brick wall which is the Item '*' is out of date commit error.

I have the latest version checked out (so far as I can tell), svn st -u turns up no differences other than the mv commands, I have no idea where else to look.

Thanks in advance!

+2  A: 

Are you sure you've checked out the head and not a lower revision? Also, have you done an update to make sure you've got the latest version?

There's a discussion about this on http://svn.haxx.se/users/archive-2007-01/0170.shtml.

jgreep
+1  A: 

Perform the move directly in the repository.

Alexander
+4  A: 

I believe this problem is coming from the .svn file. It's either incorrect in the old parent, the new parent or the old one. I would try reverting back to your starting point. Use an export to get a clean copy of the folder. Move the clean copy to the new location, and use an add and delete to do the move. That's manually doing what SVN does, but it might work.

James Deville
+14  A: 

I sometimes get this with TortoiseSVN on windows. The solution for me is to svn update the directory, even though there are no revisions to download or update. It does something to the metadata, which magically fixes it.

Michael
This did the trick for me, thanks!
fandelost
I changed the svn:ignore property of a folder, and started getting the out of date error. But as you said, just updating it worked.
Sushant
When I try to update that directory, I get "svn: Two top-level reports with no target"One more reason to hate SVN. With git, I never had this type of stupid problem with basic operations like moving a directory.
dandv
+1  A: 

Like @Alexander-Klyubin suggests, do the move in the repository. 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.

svn mv https://username@server/svn/old/ https://username@server/svn/new/

should work just fine

Aeon
+1  A: 

Are you moving it using svn mv, or just mv? I think using just mv may cause this issue.

Ryan Bigg
A: 

Tried to update the local copy, and revert the item in question, and still got the 'out of date' error. This worked for some reason:

svn update --force /path/to/dir/or/file

A: 

This happened when I updated a branch of an earlier release with files from the trunk. I used Windows Explorer to copy folders from my trunk checkout folder, and pasted them into my Eclipse view of the release branch checkout folder. Now Windows Explorer was configured not to show "hidden" files starting with ".", so I was oblivious to all the incorrect .svn files being pasted into my release branch checkout folder. Doh!

My solution was to blow away the damaged Eclipse project, check it out again, and then copy the new files in more carefully. I also changed Windows to show "hidden" files.

Jim Ferrans