Re: "400 Bad Request" on commit (mod_dav_svn)

Aleksandr Sidorenko 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 should identify it. --

Re: "400 Bad Request" on commit (mod_dav_svn)

On 2011-11-22, at 18:49, "Philip Martin" wrote: > Aleksandr Sidorenko 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):

Re: "400 Bad Request" on commit (mod_dav_svn)

Aleksandr Sidorenko 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 return value (40

Re: Problem with compiling Perl bindings (1.6.17) on PowerPC

Justin Hibbits 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 180) fixed this. Bu

Re: Could not read chunk size: connection was closed by server

Justin Johnson 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 occurred while driv

Re: "400 Bad Request" on commit (mod_dav_svn)

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:

"400 Bad Request" on commit (mod_dav_svn)

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 respons

Re: Sparse branches

On Tue, Nov 22, 2011 at 11:30 AM, James French 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 then necessary > to do the inv

Sparse branches

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 ar

[ANN] SubGit Early Access Program Build #789

Hello All, Let me introduce our new project: SubGit (http://subgit.com/). SubGit is a free tool for smooth migration from Subversion to Git. As well as from Git to Subversion. Without git-svn insanity. It works like this:  - Install SubGit into your repository on the server side - Let initial tran

Re: Could not read chunk size: connection was closed by server

On Fri, Nov 18, 2011 at 3:27 PM, Justin Johnson wrote: > Hi, > > We are running Subversion 1.6.16 and Apache 2.2.17 on Solaris 10, with > 1.6.12 clients connecting from Windows and various flavors of UNIX. > For as long as I can remember users on Windows and UNIX clients have > been getting the fo