On Mon, Aug 20, 2012 at 12:43 PM, Lieven Govaerts <svnlgo_at_mobsol.be> wrote:
> On Mon, Aug 20, 2012 at 10:18 AM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>> On Sun, Aug 19, 2012 at 1:53 PM, Lieven Govaerts <svnlgo_at_mobsol.be> wrote:
>>> Hi Johan,
>>>
>>>
>>> as you seem to be the only one encountering issue 4174, would you mind
>>> testing attached serf patch?
>>> You'll have to update serf trunk to r1627 to apply it cleanly.
>>>
>>> It fixes the issue for me on Windows 7 with svn trunk and serf trunk.
>>> While I have tested the patches on Mac OS X too, I couldn't reproduce
>>> the original problem.
>>
>> Great, it works!
>>
>> - svn trunk_at_1374802 with serf trunk_at_1627 without patch: verified that
>> I could still reproduce the original issue.
>>
>> - svn trunk_at_1374802 with serf trunk_at_1627 with your patch: the issue
>> did not occur anymore. I could successfully export the dreaded large
>> working copy from our repository over https. I tried a couple of times
>> to be sure, and there was no problem anymore.
>>
>
> Okay, thanks for testing! I've committed the fix in serf r1628.
If this would be backported to serf-1.1.x, and a new release of serf
is cut with the fix, could this be taken along for the next 1.7
release of svn? Is this simply up to the packagers (managing their
dependencies etc.), or can we bump the recommended / required serf
versions in our buildscripts / dependencies for 1.7.x ?
It's not really a deal-breaker, because 1.7 has neon, but still ...
this bug makes 1.7 w/serf unusable in some https environments. It
might be nice to fix that, also for 1.7 (and give (ra_)serf a little
bit more possible coverage that way).
--
Johan
Received on 2012-08-23 11:08:37 CEST