[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: Puig, Juan <JPuig_at_adium.com.uy>
Date: Wed, 2 Sep 2009 09:53:54 -0300

Johan, Bob, thanks for your comments, since the first time you suggested to, I deleted the working copy and made a new one so we can continue working. I was just asking as I'm a new one with TSVN maybe it was me loosing some command or something.

Thanks again for the answers,


Juan Puig
IT - Aplicaciones Corporativas
Amedrugs Corp.

-----Mensaje original-----
De: Johan Corveleyn [mailto:johan.corveleyn_at_uz.kuleuven.ac.be]
Enviado el: Martes, 01 de Septiembre de 2009 10:34
Para: Puig, Juan; Bob Archer; users_at_subversion.tigris.org
Asunto: RE: Svn Update Error REPORT <repo address>: 200 OK (<http myServer>)

> 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.


La informaci?n contenida en este mensaje de correo electr?nico y sus anexos es estrictamente confidencial, con un prop?sito espec?fico, y s?lo puede ser empleada por la persona o entidad a quien se dirige. Si usted no es el receptor autorizado, se advierte que cualquier retenci?n, difusi?n, distribuci?n, copia o uso no autorizado de este mensaje y sus anexos est? prohibida y puede ser sancionada por la ley. Si este mensaje ha sido recibido por error, se ruega reenviarlo al remitente y borrarlo de forma inmediata.

The information in this e-mail and its attachments is intended to be strictly confidential, with specific purpose, and only for use of the individual or entity to whom it is addressed. If you are not the intended and authorized recipient, please be informed that any retention, dissemination, distribution, copying or unauthorized use of this message and its attachments is strictly prohibited and may be sanctioned by law. If you receive this message in error, please forward it to the sender and delete it immediately


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-02 14:54:44 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.