tags:

views:

141

answers:

2

Here is our scenario:

Developer A checks in changes which include new files files. Developer B does an update and all of a sudden, stuff breaks because files are missing. Developer B tries another update, nothing is pulled in, so he calls Developer A. Developer A says: "Hey, I checked them in, are you blind?" Only when Developer B uses the TortiseSVN Repo Browser does he see that, indeed new files are available. The fix is to 'update item to revision in TortiseSVN Repo Browser. Even if Developer B updates through TortoiseSVN in explorer or the Subversive client in Eclipse, he can't see the new files. We also can't see the file via the SVN command line client in Cygwin.

It doesn't happen all the time, and we can't seem to reproduce it at will. But when it does, it's highly annoying.

+1  A: 

This would happen if the working copy is sparse (a.k.a. shallow, non-recursive). Perhaps that is the problem.

You can tell if a working copy is non-recursive by running svn info on it and looking for a line like Depth: immediates. Normal working copies will not have this line.

Michael Hackner
Worth looking at how a client is configured -- we purposely didn't check things out with sparse. Will keep looking.
MikeHoss
+1  A: 

Have a look at this FAQ entry.

Stefan
We're using "TortoiseSVN 1.6.5, Build 16974 - 32 Bit , 2009/08/20 08:13:46" but the Update to Revision is what always works.Again, this happens intermittently but enough where it has become an issue. When it crops up again, we will look closer at it.
MikeHoss
This happened in our environment. We had different versions of clients and different kinds of clients (TortoiseSVN, Ankh). It realy looked like in the end we had lokal working copies set to shallow checkouts. We now only work with TortoiseSVN and all is fine.
Malcolm Frexner