> -Original Message-
> From: Evan Driscoll [mailto:drisc...@cs.wisc.edu]
> Sent: 26 January 2012 21:05
> Subject: "database disk image is malformed"
>
> [There's a lot of background information; I have some
> questions near the end.]
>
>
> When I try to commit, I see the following:
>
I did a search and looked for update_editor.c. No results found.
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about wh
On 2012-01-25 10:00, Markus Schaber wrote:
[...]
> I also searched for a list of commercial SVN supporters, but did not find
> one. Companies I found so far (together with a short, very subjective "first
> shot" characterization):
>
> - http://www.collab.net/ - Long-Time hosters of subversion de
On Jan 26, 2012, at 10:34, Mike Bailey wrote:
> Thank you! Are you saying this bug is fixed, or just it's not acceptable to
> file a bug report until you've upgraded? I am not in charge of Subversion
> upgrades so that would be the end of the road for me.
I don't use Windows and have not see
[There's a lot of background information; I have some questions near the
end.]
When I try to commit, I see the following:
Sending
...
Sending
Transmitting file data svn: Commit failed (details follow):
svn: database disk image is malformed
svn: database disk i
On Thu, Jan 26, 2012 at 3:55 AM, wrote:
> I think the reason is somewhere at the connection-specific configuration of
> apache in interaction with the behaviour of the subversion-client (which may
> has also connection-options...?).
>
> I suspect the KeepAlive-Handing... it seems that the subve
Thank you! Are you saying this bug is fixed, or just it's not acceptable to
file a bug report until you've upgraded? I am not in charge of Subversion
upgrades so that would be the end of the road for me.
Thanks,
Michael
-Original Message-
From: Ryan Schmidt [mailto:subversion-20...@r
I think the reason is somewhere at the connection-specific configuration of
apache in interaction with the behaviour of the subversion-client (which may
has also connection-options...?).
I suspect the KeepAlive-Handing... it seems that the subversion-client closes
its connection between checkin
