svn - file in working copy seems "lost"

svn tortoisesvn visualsvn
jeroenh picture jeroenh · Nov 11, 2009 · Viewed 7.2k times · Source

I just managed to get into a weird situation with svn. One of my files seems 'lost' as far as the working copy is concerned. When I look on the server or do a fresh checkout of the containing folder in another location, the file is there, but in this one specific working copy it seems 'lost in space'.

svn status reports no changes (so not even a missing file)

svn update does nothing

I even tried re-exporting the file to my working copy, to no effect.

  • What is going on here?
  • How can I fix the working copy?

I would like to avoid having to resort to a fresh checkout of the whole working copy, if possible.

Answer

Wim Coenen picture Wim Coenen · Nov 11, 2009

SVN 1.6.1 clients (including TortoiseSVN) had a bug where folders would sometimes erroneously be set to depth "empty". This causes the symptoms you describe. (Note that it's possible that the folder was made "empty" by svn 1.6.1 and has remained that way even though you've already upgraded to a newer svn client in the mean time.)

To fix it, use the "update to revision" menu item in TortoiseSVN and select the depth "fully recursive".

Related questions

Working Copy Locked

I'm developing a web using subversion as version control, but got "working directory locked" error message Here's the story: I have PC-A: Windows XP Pro VisualSVN 2.5.2 Tortoise SVN 1.7.3 PC-B: Windows XP Home Tortoise SVN 1.7.3 I have create repository on PC-A …

Read More
SVN Commit failed, access forbidden

Recently I am facing problem of commit to SVN. The SVN server I am using is VisualSVN Server 2.5.9 and the client is TortoiseSVN 1.7.12. At first, one user is having problem to commit files to SVN. But that user still can …

Read More
Access to '/SVN/[repo name]/!svn/me' forbidden

I am having some issue with some SVN users where they get the following message Access to '/SVN/[repo name]/!svn/me' forbidden I am having some issues figuring out the root cause of it. The current setup is …

Read More