Package: neon27 I noticed I no longer can connect to HTTP repositories using svn (while I can connect to them using telnet, browser, or svn from other computers) after upgrading. I think libneon27-gnutls is the probable cause.
$ svn co http://svn.openstreetmap.org/applications/rendering/gosmore/ svn: OPTIONS of 'http://svn.openstreetmap.org/applications/rendering/gosmore': could not connect to server (http://svn.openstreetmap.org) $ strace svn co http://svn.openstreetmap.org/applications/rendering/gosmore/ .....(probably uninteresting stuff stripped).... recvfrom(4, "\255:\201\200\0\1\0\0\0\1\0\0\3svn\ropenstreetmap\3o"..., 1880, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.1")}, [16]) = 105 close(4) = 0 socket(PF_INET, 0x80001 /* SOCK_??? */, IPPROTO_TCP) = -1 EINVAL (Invalid argument) write(2, "svn: OPTIONS of 'http://svn.open";..., 138svn: OPTIONS of 'http://svn.openstreetmap.org/applications/rendering/gosmore': could not connect to server (http://svn.openstreetmap.org) ) = 138 exit_group(1) = ? The communication on FD=4 is with bind running on localhost. Then it seems SVN start creating socket, but fail due to middle argument to socket containing something not understood by the system (1 is SOCK_STREAM, but I have not found what should 0x80000 be in any of header files). I am using 2.6.26-1-amd64 kernel (the one from "linux-image-2.6.26-1-amd64" debian package), rest of system is debian unstable (frequently updated). When I told svn to use serf instead of neon, everything started to work fine -> so the bug is probably in neon library (libneon27-gnutls, version 0.28.4-1 on my system). Also, the bug appeared with svn (and libsvn) 1.5.1, 1.6.1 and 1.5.6 (with other libraries remaining the same) In case of serf the strace is like: close(4) = 0 socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(4, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("89.16.177.88")}, 16) = -1 EINPROGRESS (Operation now in progress) e and everything works fine ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
