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 > 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?

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 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 > > Mark

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 ar

Re: Commit failed Error after upgrading 1.7.7

2012-11-12 Thread Mark Phippard
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 Sent from my iPad On Nov 12, 2012, at 5:42 PM, Bob Archer wrote: >> On Mo

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 > 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

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 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): >> >> Se

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)

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): > >> Serv

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

Re: Commit failed Error after upgrading 1.7.7

2012-11-02 Thread Philip Martin
Bob Archer 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 Server Error) i