Sorry for the delay in replying - this reply got buried in my inbox a bit.
[Tom Epperly] > My previous entry about it working from the source code is > irrelevant. It wasn't the fact that I recompiled everything from > source. It was the fact that I changed networks. I was on travel, and > I was connecting to the https svn repo from my hotel and from the > conference network. The standard packaged svn works fine from my > home network too. It only doesn't work from my office network. Thanks for the additional followup. I must confess I'm puzzled. The whole thing is odd. > I am wondering if there is some kernel configuration that is > interacting badly with the work network because the other non-Debian > Linux box in my office has no trouble connecting to the svn repo. Indeed - but I can't think of any Linux kernel setting that would interfere with this. Especially if, as you say, telnet-ssl has no problem connecting to port 443. It could still be something with Debian's neon packages. You've already tested neon26 and neon27, but not neon25. (I don't know which version of neon is used in RHEL4, your known working case.) If you wish, you can test Debian's subversion 1.4.0-5 from last year, the last version to use neon25: http://snapshot.debian.net/archive/2006/10/13/debian/pool/main/s/subversion/libsvn1_1.4.0-5_i386.deb http://snapshot.debian.net/archive/2006/10/13/debian/pool/main/s/subversion/subversion_1.4.0-5_i386.deb Also, you could try copying /usr/bin/svn and /usr/lib/libsvn_*-1.so.0 from your RHEL4 box. I think the appropriate shared libraries are available on your unstable system, not that I've tried it. (As a side note, the RH library files will not overwrite the ones from libsvn1.) -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
