Hi,
I understand sparse checkouts but is there a recommended way of doing 'sparse
branches'? Often projects need to be farmed out to a release branch and then
deleted from the main trunk (to save space). It is then necessary to do the
inverse on the new branch ie delete all the projects that
On Tue, Nov 22, 2011 at 11:30 AM, James French
james.fre...@naturalmotion.com wrote:
I understand sparse checkouts but is there a recommended way of doing
‘sparse branches’? Often projects need to be farmed out to a release branch
and then deleted from the main trunk (to save space). It is
Hi everyone,
Since upgrading the svn client to 1.7.1 (following the server's upgrade to the
same version), we are getting the following error when doing a commit:
svn: E175002: Commit failed (details follow):
svn: E175002: Server sent unexpected return value (400 Bad Request) in
On 2011-11-22, at 16:09 , Aleksandr Sidorenko wrote:
Hi everyone,
Since upgrading the svn client to 1.7.1 (following the server's upgrade to
the same version), we are getting the following error when doing a commit:
svn: E175002: Commit failed (details follow):
svn: E175002:
Justin Johnson justinandto...@gmail.com writes:
during a checkout.
Could not read chunk size: connection was closed by server
In the server logs the following errors appear around the same time.
Provider encountered an error while streaming a REPORT response. [500, #0]
A failure
Justin Hibbits chmeeed...@gmail.com writes:
I tracked it down to the building of libsvn_swig_perl-1.a, and
swig_util_pl.c is compiled without -fPIC, which is required to build shared
libraries on PowerPC. Manually adding '-fPIC' to the COMPILE_SWIG_PL line
in the top-level Makefile (line
Aleksandr Sidorenko asidore...@espeo.com writes:
Since upgrading the svn client to 1.7.1 (following the server's
upgrade to the same version), we are getting the following error when
doing a commit:
svn: E175002: Commit failed (details follow):
svn: E175002: Server sent unexpected
On 2011-11-22, at 18:49, Philip Martin philip.mar...@wandisco.com wrote:
Aleksandr Sidorenko asidore...@espeo.com writes:
Since upgrading the svn client to 1.7.1 (following the server's
upgrade to the same version), we are getting the following error when
doing a commit:
svn: E175002:
Aleksandr Sidorenko asidore...@cashontime.com writes:
What is in the apache error log?
There was nothing in the error log. The access log showed the 400 response.
Perhaps you need to adjust the logging level? Subversion generates
several different HTTP_BAD_REQUEST errors and the error log
