WebDAV MERGE fails but commit succeeds?

[Mark Reibert <sv...@reibert.com>]

Hi,

I tried this on users@ but with no response ...

I am running svn_load_dirs.pl to manage a reasonably sized vendor tree
(approx. 1.5GB). The repo is accessed via https, behind a proxy SSL web
server. The "commit" phase of svn_load_dirs.pl takes some 3.5 hours for
the initial import, after which I get the message:

svn: Commit failed (details follow):
svn: MERGE request failed on '/svn/scratch/imports/drop-3/current'
svn: MERGE of '/svn/scratch/imports/drop-3/current': 502 Proxy Error

Any idea as to what might cause the 502 error? Is this a consequence of
the length of time the SSL connection is up? (The same process
connecting via http works ...)

But here is my real question. The commit - including a new revision -
appears in the repo. How does that occur if the WebDAV MERGE fails? Is
the new revision "complete" and "intact"?

SVN client is 1.3.2, server is 1.2.x.

Thanks,
Mark

-- 
----------------------
Mark S. Reibert, Ph.D.
svn@reibert.com
----------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org