I too have seen this error several times and I am convinced it happens in the
presence of an unreliable network. The network I am using is very unreliable so
this problem is seen from time to time. When it happens the checkout has to be
cleaned, then if the command is tries again it usually work
Hello everyone,
The answer is "yes". I have come across investment banks that store boost
releases in subversion. Sometimes it's a full boost release and that can be
quite large. They take a long time to checkout but at the time it seemed better
than the alternatives available at the time, e.g.
Hello everyone and thank you Detlef for reporting this situation. I want to add
that I also see this from time to time and would like to see a fix.
It is very easy for me to see network errors from subversion because I am in an
environment where the network is extremely unreliable. This fact has
Crucible.
-Original Message-
From: wuzhouhui
Sent: 11 August 2019 05:19
To: Subversion
Subject: EXTERNAL: which review tools are suitable for codes versioned by svn
Hi,
I'm searching some review tools which are suitable for codes versioned by
Subversion, any recommends?
The informati
Reply below:
-Original Message-
From: Johan Corveleyn
Sent: 24 April 2019 11:30
To: Marlow, Andrew
Cc: users@subversion.apache.org
Subject: Re: EXTERNAL: Re: svn version 1.10 lack of robustness in presence of
flaky network
> >Regarding the comment that was made, I don't k
ystem. But is it on a network share? Not sure, but I don't think so. IMO
that would be an extremely bad setup.
-Original Message-----
From: Marlow, Andrew
Sent: 24 April 2019 09:52
To: users@subversion.apache.org
Subject: RE: EXTERNAL: Re: svn version 1.10 lack of robustness in presence
Reply below:
-Original Message-
From: Stefan Sperling
Sent: 24 April 2019 07:54
To: Marlow, Andrew
Cc: Johan Corveleyn ; users@subversion.apache.org
Subject: EXTERNAL: Re: svn version 1.10 lack of robustness in presence of flaky
network
On Wed, Apr 24, 2019 at 12:55:47AM +0200, Johan
Hello everyone,
I got this error below during an svn co command. It left my workspace in a bad
state from which I had to do svn cleanup before trying again (the retry worked):
svn: E200033: Another process is blocking the working copy database, or the
underlying filesystem does not support file
