RE: Commit failed Error after upgrading 1.7.7

2012-11-13 Thread Bob Archer
If you are using LDAP and the server is on Windows there is a bug in Apache 2.2.23 that can cause an HTTP 500 on the first authenticated request for a user. See: https://issues.apache.org/bugzilla/show_bug.cgi?id=54140 Mark... that looks exactly what we are running into. Indeed we are

Re: Commit failed Error after upgrading 1.7.7

2012-11-13 Thread Mark Phippard
On Tue, Nov 13, 2012 at 10:22 AM, Bob Archer bob.arc...@amsi.com wrote: If you are using LDAP and the server is on Windows there is a bug in Apache 2.2.23 that can cause an HTTP 500 on the first authenticated request for a user. See: https://issues.apache.org/bugzilla/show_bug.cgi?id=54140

RE: Commit failed Error after upgrading 1.7.7

2012-11-13 Thread Bob Archer
On Tue, Nov 13, 2012 at 10:22 AM, Bob Archer bob.arc...@amsi.com wrote: If you are using LDAP and the server is on Windows there is a bug in Apache 2.2.23 that can cause an HTTP 500 on the first authenticated request for a user. See:

RE: Commit failed Error after upgrading 1.7.7

2012-11-12 Thread Bob Archer
I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me Subversion 1.7.7. Since then every now and then when I commit I get the following error: Commit Commit failed (details follow): Server sent unexpected return value (500 Internal Server Error) in response to POST

Re: Commit failed Error after upgrading 1.7.7

2012-11-12 Thread Johan Corveleyn
On Mon, Nov 12, 2012 at 10:12 PM, Bob Archer bob.arc...@amsi.com wrote: I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me Subversion 1.7.7. Since then every now and then when I commit I get the following error: Commit Commit failed (details follow): Server sent

RE: Commit failed Error after upgrading 1.7.7

2012-11-12 Thread Bob Archer
On Mon, Nov 12, 2012 at 10:12 PM, Bob Archer bob.arc...@amsi.com wrote: I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me Subversion 1.7.7. Since then every now and then when I commit I get the following error: Commit Commit failed (details follow):

RE: Commit failed Error after upgrading 1.7.7

2012-11-05 Thread Bob Archer
I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me Subversion 1.7.7. Since then every now and then when I commit I get the following error: Commit Commit failed (details follow): Server sent unexpected return value (500 Internal Server Error) in response to POST

Re: Commit failed Error after upgrading 1.7.7

2012-11-05 Thread Daniel Shahaf
Bob Archer wrote on Mon, Nov 05, 2012 at 11:39:30 -0500: I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me Subversion 1.7.7. Since then every now and then when I commit I get the following error: Commit Commit failed (details follow): Server sent unexpected

Re: Commit failed Error after upgrading 1.7.7

2012-11-02 Thread Philip Martin
Bob Archer bob.arc...@amsi.com writes: I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me Subversion 1.7.7. Since then every now and then when I commit I get the following error: Commit Commit failed (details follow): Server sent unexpected return value (500 Internal