RE: Commit problem

Hi Russell,
 
Thanks for your help. The downgrade to 1.2.3 worked.
 
I also tried upgrading to 1.3.1. One repository started accepting commits
but another one was still broken. I even tried using the new logging
feature available in 1.3.1 with the example line from the release notes but
all it did was create the log file--it never actually logged anything.
 
There has to be a bug with 1.3.x. I'd submit a report about it but I have
no idea how the problem started let alone how to reproduce it.
 
 
Regards,
Philip

  _____

From: RUSSELL.D.JOHNSON@saic.com [mailto:RUSSELL.D.JOHNSON@saic.com]
Sent: April 20, 2006 4:22 PM
To: Philip de Vries; users@subversion.tigris.org
Subject: RE: Commit problem

Unfortunately, I was unable to determine the cause.
I was able to rule out TortoiseSVN as well as Apache 2.0.55 (I downgraded to
Apache 2.0.54 before downgrading Subversion and have since reupgraded Apache
to 2.0.55.)

  _____

From: Philip de Vries [mailto:philipd@novacatv.com]
Sent: Thursday, April 20, 2006 11:34 AM
To: Johnson, Russell D.; users@subversion.tigris.org
Subject: RE: Commit problem

Hi Russell,
 
I've seen that solution too but my understanding was that it was a problem
associated with BDB.
 
What was the cause of the problem you encountered?
 
 
Thanks,
Philip

 
Received on Fri Apr 21 18:13:07 2006