[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: more problems when using serf

From: Mark Phippard <markphip_at_gmail.com>
Date: Sat, 22 May 2010 09:42:51 -0400

On Sat, May 22, 2010 at 3:18 AM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:

> On the TSVN mailing list, a user reported problems when accessing the
> codeplex repositories with TSVN linked against the svn trunk.
> Further testing on my side revealed that this problem is due to the fact
> that serf is now the default DAV lib.
> When using neon, everything works as expected.
> For example:
> svn ls https://mvvmfoundation.svn.codeplex.com/svn
> with serf leads to:
> subversion\subversion\svn\list-cmd.c:289: (apr_err=175003)
> subversion\subversion\libsvn_client\list.c:272: (apr_err=175003)
> subversion\subversion\libsvn_client\list.c:73: (apr_err=175003)
> subversion\subversion\libsvn_ra_serf\serf.c:895: (apr_err=175003)
> subversion\subversion\libsvn_ra_serf\serf.c:833: (apr_err=175003)
> svn: The PROPFIND response did not include the requested resourcetype value
> Most other commands don't work either when using serf:
> svn checkout
> svn log
> svn diff
> ...
> Using neon works ok.

Aren't they just emulating a Subversion server and the Subversion
protocol? They have probably just not implemented it correctly.

Github has started doing the same thing, it would be interesting to
see if they have the same problems.

Mark Phippard
Received on 2010-05-24 12:10:04 CEST

This is an archived mail posted to the Subversion Dev mailing list.