[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Trying to compile 1.6.15 with IPv6 enabled

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 07 Jun 2011 11:20:25 +0200

On 07.06.2011 10:30, Timothy Baldock wrote:
> Ok further problems...
>
> I have managed to build TortoiseSVN supposedly with IPv6 enabled and
> produce the msi. This installs and appears to function correctly.
> However, trying to check out a working copy of a repository using a DNS
> alias which only has AAAA records fails. Trying to use the IPv6 address

What's the error you get there?

> directly (e.g. using a URL like:
> http://[2002:526e:787b:8000:0:5efe:ffab:bacd]:82/) also fails.
> TortoiseSVN complains:
>
> Error Illegal repository URL
> 'http://%5b2002:526e:787b:8000:0:5efe:ffab:bacd%5d:82'

Are the brackets needed?
Try:
http://2002:526e:787b:8000:0:5efe:ffab:bacd:82/

> This should be working should it not? Is there something special which
> needs to be done to get Tortoise to work properly with IPv6?

I've never tested this, and even the CLI binaries for Windows are not
built with ipv6 support.

Try building TSVN from trunk with ipv6 enabled. You'll also get all the
svn CLI binaries with that build. Then try a checkout with that svn.exe.
If it also fails, you should report it on the Subversion mailing list -
now is the right time before version 1.7 is branched, otherwise such
changes might not get into 1.7...

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2759515
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-06-07 11:20:41 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.