You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Puig, Juan" <JP...@adium.com.uy> on 2009/09/01 12:32:25 UTC
RE: Svn Update Error REPORT : 200 OK ()
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?
Slds.
Juan Puig
IT - Aplicaciones Corporativas
Amedrugs Corp.
-----Mensaje original-----
De: Bob Archer [mailto:Bob.Archer@amsi.com]
Enviado el: Lunes, 31 de Agosto de 2009 18:31
Para: Puig, Juan; Johan Corveleyn; users@subversion.tigris.org
Asunto: RE: Svn Update Error REPORT <repo address>: 200 OK (<http myServer>)
> > Thanks Johan for the answer, but we haven´t changed the location of
> the
> > repositories and we are not using any proxy.
> >
> > Another thing that happens is some files where deleted from the
> > repository using DEL in stead of Right Clic -> Delete, and when
> running
> > update on the working copy it restored the deleted files and then
> gave
> > the error mentioned before.
> >
> > Any other ideas?
>
> Can you just do a new clean checkout?
>
> BOb
> Hi, thanks Bob for the answer. Yes I can do a new checkout, but I have
> to copy my modified files, the modified files in subfolders, and the
> modified files in subsubfolders, seeing that in one month there been 2
> versions, I think there is a way to upgrade the working copies whitout
> having to delete them, isn't?
There should be. But, you can go crazy and figure out what the problem is. Or, just create a new working copy, copy your modified files into it and move on.
Was just trying to help.
BOb
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
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2389744
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: Svn Update Error REPORT : 200 OK ()
Posted by "Puig, Juan" <JP...@adium.com.uy>.
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,
Slds.
Juan Puig
IT - Aplicaciones Corporativas
Amedrugs Corp.
-----Mensaje original-----
De: Johan Corveleyn [mailto:johan.corveleyn@uz.kuleuven.ac.be]
Enviado el: Martes, 01 de Septiembre de 2009 10:34
Para: Puig, Juan; Bob Archer; users@subversion.tigris.org
Asunto: RE: Svn Update Error REPORT <repo address>: 200 OK (<http myServer>)
> Van: Puig, Juan [mailto:JPuig@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.
Regards,
Johan
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
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390176
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: Svn Update Error REPORT : 200 OK ()
Posted by Johan Corveleyn <jo...@uz.kuleuven.ac.be>.
> Van: Puig, Juan [mailto:JPuig@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.
Regards,
Johan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2389761
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: Svn Update Error REPORT : 200 OK ()
Posted by Bob Archer <bo...@amsi.com>.
> 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?
Well, that might be your problem right there. You really should not share a working copy. Each dev should have his own.
As I said, no this is not common. Usually you just update and the first time you touch the WC with the new version it is updated. Oh, and going from 1.6.x to 1.6.y doesn't actually change the working copy format. It is only changed from 1.x to 1.y revs.
BOb
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2389769
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].