Thank you. I tried and got it. ----- japanese-usage-dictionary.googlecode.com is an alias for googlecode.l.googleusercontent.com. googlecode.l.googleusercontent.com has address 173.194.72.82 googlecode.l.googleusercontent.com has IPv6 address 2404:6800:4008:c01::52 It is looked right, but the address is different from you. googlecode.l.googleusercontent.com has address 173.194.72.82
googlecode.l.googleusercontent.com has address 64.233.178.82
googlecode.l.googleusercontent.com has IPv6 address 2404:6800:4008:c01::52
googlecode.l.googleusercontent.com has IPv6 address 2607:f8b0:4003:c0a::52
----- (Test the host is available?) $ ping -c 3 173.194.72.82 PING 173.194.72.82 (173.194.72.82) 56(84) bytes of data. 64 bytes from 173.194.72.82: icmp_seq=1 ttl=42 time=49.0 ms 64 bytes from 173.194.72.82: icmp_seq=2 ttl=42 time=48.7 ms 64 bytes from 173.194.72.82: icmp_seq=3 ttl=42 time=48.8 ms --- 173.194.72.82 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 48.753/48.857/49.016/0.279 ms ----- Result of strace: $ strace -e trace=network svn checkout http://japanese-usage-dictionary.googlecode.com/svn/trunk 2>&1 | grep "^connect" connect(5, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) connect(4, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) connect(4, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("8.8.8.8")}, 16) = 0 connect(4, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6, "2404:6800:4008:c01::52", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0 connect(4, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0 connect(4, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("173.194.72.82")}, 16) = 0 connect(4, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, "2404:6800:4008:c01::52", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress) [1] 31614 exit 1 strace -e trace=network svn checkout 2>&1 | 31615 done grep --color=always "^connect" ----- Test again with IPv6: $ ping6 -c 3 2404:6800:4008:c01::52 PING 2404:6800:4008:c01::52(2404:6800:4008:c01::52) 56 data bytes --- 2404:6800:4008:c01::52 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2008ms [1] 32548 exit 1 ping6 -c 3 2404:6800:4008:c01::52 ----- Humm? IPv6 address isn't avilable... So, I added entry hosts file: 173.194.72.82 mozc.googlecode.com japanese_usage_dictionary.googlecode.com japanese-usage-dictionary.googlecode.com gyp.googlecode.com And fix PKGBUILD because mozcdic and edit are already updated and Revision 0 is not exist in Japanese Usage Dictionary's repository. AND SUCCEEDED! I attach the patch and modified PKGBUILD. Thank you very much. You wrote:
On Wed, Feb 4, 2015 at 5:25 PM, MASAKI Yuhsuke <hydrangea+ml@reasonset.net> wrote:
$ LANG=C svn checkout http://japanese-usage-dictionary.googlecode.com/svn/trunk/ svn: E000111: Unable to connect to a repository at URL 'http://japanese-usage-dictionary.googlecode.com/svn/trunk' svn: E000111: Error running context: Connection refused [1] 10182 exit 1 LANG=C svn checkout http://japanese-usage-dictionary.googlecode.com/svn/trunk
From your workstation, first show us what the IP addresses resolve to like so:
$ host japanese-usage-dictionary.googlecode.com japanese-usage-dictionary.googlecode.com is an alias for googlecode.l.googleusercontent.com. googlecode.l.googleusercontent.com has address 64.233.178.82 googlecode.l.googleusercontent.com has IPv6 address 2607:f8b0:4003:c0a::52
Next, run this command so that we can see the network connections being attempted (you may need to install 'strace' first):
$ strace -e trace=network svn checkout http://japanese-usage-dictionary.googlecode.com/svn/trunk/ 2>&1 | grep ^connect
It looks like you are having a network connection problem, so this will show everyone what IPs and connections are failing for your SVN checkout. I suspect that you have some sort of network block, or an IPv6 routing problem etc. As just an example, I do not have IPv6 capability from home (ISP does not support) so all connections fail for IPv6, but IPv4 is working find and the SVN checkout is working.
$ strace -e trace=network svn checkout http://japanese-usage-dictionary.googlecode.com/svn/trunk/ 2>&1 | grep ^connect connect(5, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) connect(4, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) connect(4, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("8.8.8.8")}, 16) = 0 connect(4, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("64.233.178.82")}, 16) = 0 connect(4, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6, "2607:f8b0:4003:c0a::52", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 ENETUNREACH (Network is unreachable) connect(4, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("64.233.178.82")}, 16) = -1 EINPROGRESS (Operation now in progress) connect(5, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("8.8.8.8")}, 16) = 0 connect(5, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6, "2607:f8b0:4003:c0a::52", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 ENETUNREACH (Network is unreachable) connect(5, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0 connect(5, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("64.233.178.82")}, 16) = 0 connect(5, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("64.233.178.82")}, 16) = -1 EINPROGRESS (Operation now in progress) connect(7, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("8.8.8.8")}, 16) = 0 connect(7, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("64.233.178.82")}, 16) = 0 connect(7, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6, "2607:f8b0:4003:c0a::52", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 ENETUNREACH (Network is unreachable)
What you're looking for is one of the IPv4 address connection lines *not* = 0 (success), but instead show it cannot connect. Then once it's identified, use a tool like curl or netcat (or even telnet) to test that IP outside of SVN to confirm.
hth, -te
****************************** * The Rider, Hacker and Musician. * +++ ENABLE YOUR HEART +++ ****************************** * MASAKI Yuhsuke. * hydrangea+ml@reasonset.net * Website: http://reasonset.net/ * GitHub : https://github.com/reasonset/ * Twitter: @reasonset ******************************