SteveKing <steveking <at> gmx.ch> writes:
> Samuel Winchenbach wrote:
> > Now I delete "about.doc", and commit the changes.
> > My friend Ryan has modified his working copy of "about.doc"
>
> Sorry to say that, but this would be a good example of very bad
> communication between your team members.
Or, it could be that it's really "about.obj" that shouldn't
have been in the project to begin with; Ryan is working on
the project (and every compile modifies "about.obj")
while I'm trying to clean out such nonsense.
> > When Ryan runs "commit" he recieces a message ....
> > When Ryan runs "update" he recieves a message ....
> > [ ... If Ryan deletes the file, then commit succeeds and update leads
> > to ... ] "can't copy about.doc.svn-base to about.doc.svn-base.tmp the
> > system cannot find the file specified"
> > [ ... similar problems if you use Tortoise "delete" instead ... ]
> Again, do a "cleanup" before you proceed any further. Your working copy
> is in an "interrupted" state and must be cleaned up before any other
> commands can be used successfully.
"cleanup" doesn't help, as it turns out. The problem
persists. I've spent much of today wrestling with this
problem, and the only solution I've found is to throw out my
entire working copy and do a clean checkout of the entire project.
This isn't too bad as long as I'm on the local LAN. But I have people
accessing SVN over a slow VPN link, and can easily see a lot of expensive
developers sitting idle while they check out yet another fresh copy of
a 300MB project. That hurts.
There needs to be a better way to recover from this.
Any ideas?
Tim Kientzle
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Aug 19 20:56:01 2004