On Jul 15, 2011, at 3:16 PM, Greg Stein wrote:
> On Fri, Jul 15, 2011 at 18:06, Blair Zajac <blair_at_orcaware.com> wrote:
>>
>> On Jul 15, 2011, at 3:03 PM, Greg Stein wrote:
>>
>>> Hi all,
>>>
>>> I'm pleased to finally announce the 1.0.0 release of serf!
>>>
>>> The serf 1.0.x series is intended to support Apache Subversion 1.6.x
>>> and the upcoming 1.7.x for their supported lifetimes.
>>
>> Nice!
>>
>> So any version of Subversion 1.6.x, assuming it is recompiled, will
>> work with serf 1.0.x? Or do we need to wait for 1.6.18?
>
> I honestly don't know. I haven't investigated that, although I believe
> others have.
Just tried, svn 1.6.x doesn't compile against serf 1.0.0 due to
configure looking for serf-0 instead of serf-1. If I s/serf-0/serf-1/
g in configure, than it doesn't compile due to the removal of
serf_bucket_snapshot().
Given that serf-0 and serf-1 can be simultaneously installed, it
doesn't appear necessary for us to make 1.6.x work with serf 1.0.x,
but it may be nice for some distributions. For MacPorts, it looks
like we'll just provide svn 1.7.x and let Mac OS X provide 1.6.x
One other thing. With 0.7.2, make check passed all tests, but 1.0.0
fails 7 tests on Mac OS X 10.6 against MacPorts' provided apr:
== Running test_all ==
FFFFFFF..........
There were 7 failures:
1) test_serf_connection_request_create: test/test_context.c:166:
expected <0> but was <47>
2) test_serf_connection_priority_request_create: test/test_context.c:
265: expected <0> but was <47>
3) test_serf_closed_connection: test/test_context.c:404: expected <0>
but was <47>
4) test_serf_setup_proxy: test/test_context.c:505: expected <0> but
was <47>
5) test_keepalive_limit_one_by_one: test/test_context.c:656: expected
<0> but was <47>
6) test_keepalive_limit_one_by_one_and_burst: test/test_context.c:810:
expected <0> but was <47>
7) test_serf_progress_callback: test/test_context.c:932: expected <0>
but was <47>
Is there anything different I should do, or should the unit test just
work?
Blair
Received on 2011-07-17 00:14:54 CEST