Re: Issue 2761: merge fail with "Could not get content-type from response"

On Thu, 2007-10-18 at 03:05 -0700, Karl Fogel wrote:
> Mark Reibert <svn@reibert.com> writes:
> > I am experiencing the same problem as described in issue 2761.
> >
> > In the bug you asked for a full reproduction and output. I am observing
> > the behavior using the command:
> >
> > svn merge URL1@M URL2@N
> >
> > The merge output looks normal - just a list of modified, added, deleted,
> > conflicted, etc. files. At some point the command just stops with the
> > following solitary message:
> >
> > svn: Could not get content-type from response
> >
> > One thing that might be a factor is this merge will result in a large
> > patch set.
> >
> > Client is 1.4.5 (Win32 under Cygwin), server is 1.2.3 (Linux). Repo
> > access is ra_dav. I can get you more info if necessary.
>
> Hi, Mark. I believe this is more or less the same as a mail you
> posted on users@ (which is fine). Here's the response I posted there,
> which I think still applies:

Yes, it is. I will continue the discussion on dev@

> I unfortunately don't have time to debug this myself right now, but
> you could help us a lot with issue #2761 by putting together a true
> reproduction recipe. Just dump your repository ('svnadmin dump'), and
> zip up your working copy as it is before the merge, and attach them to
> the issue, along with a note saying what steps to take to reproduce --
> by which I mean the *exact* commands :-).

Understood and agree. The first thing I preach to my testers (and users)
is I can't fix it if I can't break it (or you can't break it for me)!

Unfortunately, I cannot give you the repo and wc. This is code for a
military radio being developed by a major U.S. defense contractor. (If I
give you this code we both end up behind bars. ;-) There is a practical
consideration as well as the repo effectively mirrors 9 large ClearCase
VOBs, making the repo many, many gigs. (A wc of the trunk is a mere
3.5G, and there are many, many branches and vendor imports.)

> I realize that all might take half an hour or so, but we're pretty
> dependent on clean reproduction recipes from users. You can greatly
> increase the chances of that issue getting fixed by taking that time.

Time is not the problem ... I am more than happy to help you help me. I
am just trying to figure out what I can tell you given that I cannot
give you the repo and all I see is a one-line error message. Is there
some kind of debugging I can do? Can I build a debug version of the
client and get you more info?

I think tomorrow I will check the Apache error log and see if anything
jumps out at me.

Thanks for your help,
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