Re: 1.3.0 RC1 ready to be rolled

kfogel@collab.net writes:

> John Peacock <jpeacock@rowman.com> writes:
>> After testing, it seems it _was_ Neon 0.25.0 that broke things. I
>> don't have time to get an ethereal trace right now, but I'll try to
>> rebuild and get a trace tonight or tomorrow.
>
> Oooooh. Okay, thanks for narrowing it down. That's a 1.3.0
> showstopper IMHO, at least until we know more. I.e., if it turns out
> to be a bug in Neon 0.25.x, then we might as well ship, because no
> better Neon is available. Users can just choose 0.24 or 0.25.
>
> However, my instinct is it's a bug in SVN, since it shows itself when
> client and server have relative version skew.

I have a 1.3.x@HEAD build that uses neon 0.25.0 and it seems to work

$ /usr/local/subversion2/bin/svn --version -q
1.3.0-dev
$ ldd /usr/local/subversion2/bin/svn | grep neon
        libneon.so.25 => /usr/lib/libneon.so.25 (0x402c8000)
$ /usr/local/subversion2/bin/svn ls http://svn.collab.net/repos/svn/
README
branches/
tags/
trunk/

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