[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Svn Update Error REPORT <repo address>: 200 OK (<http myServer>)

From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Tue, 1 Sep 2009 15:33:43 +0200

> Van: Puig, Juan [mailto:JPuig_at_adium.com.uy]
> Yes of course, thanks bob, I prefer a funny answer than no answer.
> But, thinking that we have only one working copy (shared on a
> network drive), I think is easy for me to delete a working copy and
> making a new one, but thinking in development teams having many
> working copies, they all have to delete and re do a working copy? I
> just can't belive it! Is this normal?

No this isn't normal and isn't supposed to happen. But what Bob suggests is just the pragmatic approach right now. You could spend days/weeks (of yourself and of fellow list-users) to investigate exactly what happened, to find out what was the root cause of the corruption. This could be anything, ranging from a bug in svn or svn client software, to a dangerous file(system) manipulation made outside svn, or maybe a normal (but currently not understood) situation because something "changed" on the repository, ...

I'd agree with Bob here: unless you really want to do the forensic analysis, let's consider it a one-time glitch and repair it (nothing is really lost anyway). If it would ever happen again (or it would happen to other users on upgrading) you can still investigate.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-01 15:34:57 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.