By using a custom svnsync'ed FreeBSD base repository we noticed that svnup is unable to get its contents, while other tools (svn, svnlite) works without problems.

For example, if the custom repository is published under http://mysvnserver/repos/freebsd-base, here is the svnup verbose output:

# Revision: 267104
# Protocol: http
# Address: mysvnserver
# Port: 80
# Branch: repos/freebsd-base/releng/9.2
# Target: /usr/src
# Trim tree: No
# Show extra files: No
# Known files directory: /var/tmp/svnup
<< 570 bytes
REPORT /repos/!svn/me HTTP/1.1
Host: mysvnserver
User-Agent: svnup-1.05
Content-Type: text/xml
DAV: http://subversion.tigris.org/xmlns/dav/svn/depth
DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo
DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops
Transfer-Encoding: chunked

fb
<S:update-report xmlns:S="svn:">
<S:src-path>/repos/freebsd-base/releng/9.2</S:src-path>
<S:target-revision>267104</S:target-revision>
<S:depth>unknown</S:depth>
<S:entry rev="267104" depth="infinity" start-empty="true"></S:entry>
</S:update-report>


No problem when the repository is accessible under the root path (for example, http://mysvnserver/freebsd-base).

Coding is not my job, but I tried to produce a patch. Unfortunately I only managed to move the error one-step away (it breaks on the GET phase). Let me know if I can help by detailing some aspects.

Thanks.