[Tom Epperly] > I can't reproduce it with your site. 'svn ls > https://svn.collab.net/repos/svn' works fine several times in a row.
I talked to upstream developers about this yesterday, and one brought up the possibility that a simple 'svn ls' may succeed but more complex requests fail, because they are potentially making several connections to the server. (Yes, the svn RA (repository access) layer does often create multiple connections.) So with that in mind, could you try 'svn ls' with the URL that fails, to see if it still fails? Also, more complex things you can try against svn.collab.net: svn export https://svn.collab.net/repos/svn/branches/1.4.x upstream svn blame https://svn.collab.net/repos/svn/branches/1.4.x/STATUS The 'blame' implementation is not very efficient today, so that might make a good test. (: > ii libneon25 0.25.5.dfsg-6 An HTTP and WebDAV client library > ii libneon26 0.26.4-2 An HTTP and WebDAV client library > > I can't remove libneon25 without uninstalling things like openoffice. Don't worry, libneon25 and libneon26 don't conflict with each other. If you'd like to also test with libneon27, which we will be using soon, you can download the test packages I built last night: http://p12n.org/tmp/svn_neon27/subversion_1.4.4dfsg1-2_i386.deb http://p12n.org/tmp/svn_neon27/libsvn1_1.4.4dfsg1-2_i386.deb (Technically you only need to download libsvn1, but the Depends: relationship between the two requires that they be the same version.) Thanks, -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
