Re: [cvsnt] ipv6 handling in cvsnt is broken

2008-11-11 Thread Arkadiusz Miskiewicz
On Tuesday 11 of November 2008, Arthur Barrett wrote: > Arkadiusz, > > I appreciate your time and effort on this - however if you just slow down a > little and explain things a little clearer we'll be able to make much more > use of the information being supplied. Ok, I'll try to put everything in

Re: [cvsnt] ipv6 handling in cvsnt is broken

2008-11-11 Thread Arthur Barrett
Arkadiusz, I appreciate your time and effort on this - however if you just slow down a little and explain things a little clearer we'll be able to make much more use of the information being supplied. > > Again. You're trying to claim something is broken that > > I use every day. > > You don

Re: [cvsnt] ipv6 handling in cvsnt is broken

2008-11-10 Thread Arkadiusz Miskiewicz
On Monday 10 of November 2008, Tony Hoyle wrote: > Arkadiusz Miskiewicz wrote: > > A couple of points: > > This rule only applies to ::, not ::1. > > This is entirely irrelevant as there are only two possible cases. The > code is written to handle both cases transparently, and does. > > $ netstat

Re: [cvsnt] ipv6 handling in cvsnt is broken

2008-11-10 Thread Arkadiusz Miskiewicz
On Monday 10 of November 2008, Tony Hoyle wrote: > Arkadiusz Miskiewicz wrote: > > Again. You're trying to claim something is broken that I use every day. You don't use it in a way that triggers brokeness. > I even posted examples of it working correctly. You can check yourself > by connecting

Re: [cvsnt] ipv6 handling in cvsnt is broken

2008-11-09 Thread Tony Hoyle
Arkadiusz Miskiewicz wrote: A couple of points: > This rule only applies to ::, not ::1. This is entirely irrelevant as there are only two possible cases. The code is written to handle both cases transparently, and does. $ netstat -an | grep 2402 tcp0 0 127.0.0.1:2402 0

Re: [cvsnt] ipv6 handling in cvsnt is broken

2008-11-09 Thread Tony Hoyle
Arkadiusz Miskiewicz wrote: >> Again. You're trying to claim something is broken that I use every day. I even posted examples of it working correctly. You can check yourself by connecting to cvs.cvsnt.org over ipv6. Please read http://www.cvsnt.org/wiki/BugReporting and provide all the inform

Re: [cvsnt] ipv6 handling in cvsnt is broken

2008-11-09 Thread Arkadiusz Miskiewicz
On Sunday 09 of November 2008, Tony Hoyle wrote: > Arkadiusz Miskiewicz wrote: > > IPv6 support seems quite broken in cvsnt (looking at 2.5.04.3236) > > > > It doesn't support [ipv6]:port notation, binds to ::1 port while it > > should bind to ipv4 address, too (cvslockd as example. Server tries to

Re: [cvsnt] ipv6 handling in cvsnt is broken

2008-11-08 Thread Tony Hoyle
Arkadiusz Miskiewicz wrote: > IPv6 support seems quite broken in cvsnt (looking at 2.5.04.3236) > > It doesn't support [ipv6]:port notation, binds to ::1 port while it should > bind to ipv4 address, too (cvslockd as example. Server tries to > use "localhost" name which resolves only to 127.0.0.1

[cvsnt] ipv6 handling in cvsnt is broken

2008-11-08 Thread Arkadiusz Miskiewicz
IPv6 support seems quite broken in cvsnt (looking at 2.5.04.3236) It doesn't support [ipv6]:port notation, binds to ::1 port while it should bind to ipv4 address, too (cvslockd as example. Server tries to use "localhost" name which resolves only to 127.0.0.1 address, tries to connect to it but