Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-04 Thread Gustavo Chaves
On 1 dez, 22:29, Mark Phippard wrote: > > Subversion Edge does not have the location block for SVN in the > httpd.conf file.  Have you customized the configuration files beyond > this?  There is no reason you should have to add that directive > anyway. > > Assuming you are using the default config

Issue with upgrade/server move to 1.7.1

2011-12-04 Thread Justin Finkelstein
Hi guys Today I've moved my SVN repository from 1.5.1 to 1.7.1, located on a new server. Having done this, I've upgraded the repositories served and am getting an odd error when testing. On the server, I'm running: svnserve -d -r /home/svn --foreground --listen-port 3690 When I try to chec

chakra linux binary packages

2011-12-04 Thread Drake Justice
im not sure if this is the place for this, but i was browsing the downloads/packages page @ http://subversion.apache.org/packages.html and saw chakra linux was missing. if at all possible, could someone add a section for us? a logo image: http://chakra-linux.org/wiki/images/thumb/7/7a/Chakra-gradi

Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-04 Thread Gustavo Chaves
I straced the httpd daemon to try to get any hint. The last syscalls before the error are these: 17748 read(18, "POST /admin/!svn/me HTTP/1.1\r\nUs"..., 8000) = 441 17748 stat("/l/home1/svn/admin/htdocs/admin/!svn/me", 0x7fffce99c130) = -1 ENOENT (No such file or directory) 17748 lstat("/l", {st_m

Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-04 Thread Gustavo Chaves
Just one more information. I was using the packages CollabNetSubversion-extras and CollabNetSubversion-server version 1.7.0-2. I've just upgrade them to version 1.7.1-1 but the problems remain. -- Gustavo.

SlikSVN (but also Tortoise SVN) crashes when trying to merge/reintegrate branch to Trunk

2011-12-04 Thread Thibaud Desodt
Hi, TortoiseSVN , but also the command-line SVN crash when I try to merge back a branch in the Trunk. I attach the log file as well as the Dump file. Because of my company's policy, we are still using SVN 1.6.xx . Please tell me if I can provide you with any useful information, Best regards, _

SVN 1.7.1

2011-12-04 Thread i_maliavko
Hi. I'm using it since official release. And decision to using it was my big fail. Becase: 1. commit list makes about 10 minutes time after time; 2. first update in day last over 15 minutes; I'm working on big project (over 100 000 files) and waste about an hour on waiting SVN operations. And

Re: SVN 1.7.1

2011-12-04 Thread Nico Kadel-Garcia
On Fri, Dec 2, 2011 at 2:19 AM, i_maliavko wrote: > Hi. > > I'm using it since official release. And decision to using it was my big > fail. Becase: > 1. commit list makes about 10 minutes time after time; > 2. first update in day last over 15 minutes; > > I'm working on big project (over 100 000

Re: SVN 1.7.1

2011-12-04 Thread Johan Corveleyn
On Fri, Dec 2, 2011 at 8:19 AM, i_maliavko wrote: > Hi. > > I'm using it since official release. And decision to using it was my big > fail. Becase: > 1. commit list makes about 10 minutes time after time; > 2. first update in day last over 15 minutes; Hard to say whether this is a regression, wi

Re: Issue with upgrade/server move to 1.7.1

2011-12-04 Thread Daniel Shahaf
Fixed on #svn, right? Justin Finkelstein wrote on Sun, Dec 04, 2011 at 16:24:30 +: > Hi guys > > Today I've moved my SVN repository from 1.5.1 to 1.7.1, located on a new > server. Having done this, I've upgraded the repositories served and am > getting an odd error when testing. > > On the s

Re: chakra linux binary packages

2011-12-04 Thread Daniel Shahaf
Please send a patch against the site source: http://subversion.apache.org/patches http://svn.apache.org/repos/asf/subversion/site Drake Justice wrote on Sat, Dec 03, 2011 at 14:34:10 -0500: > im not sure if this is the place for this, but i was browsing the > downloads/packages page @ http://sub

Re: Subversion 1.7.1 Migration

2011-12-04 Thread Thorsten Schöning
Guten Tag PR, am Sonntag, 4. Dezember 2011 um 00:53 schrieben Sie: > Accessing the new server from the 1.4.6 client any thing to keep > in mind or any one has faced any issues? If you access via http, SVNAdvertiseV2Protocol off may be of interest if you recognize any problems with your old