On Sat, Jan 24, 2015 at 4:55 PM, Joerg Sonnenberger wrote:
> On Sat, Jan 24, 2015 at 04:27:55PM -0500, Richard Hipp wrote:
> > I would hope that the local machine knows that it cannot provide IPv6
> > service and that getaddrinfo() should therefore always return an IPv4
> > address. But apparent
On 25 January 2015 at 13:54, Joerg Sonnenberger wrote:
>
> Ah, do you have security/mozilla-rootcerts installed? NetBSD doesn't
> provide a default set of CAs out of the box.
that did it, thx.
Michai
___
fossil-users mailing list
fossil-users@lists.fos
On Sun, Jan 25, 2015 at 12:11:53PM +0100, Michai Ramakers wrote:
> On 25 January 2015 at 00:09, Joerg Sonnenberger
> wrote:
> > On Sat, Jan 24, 2015 at 04:57:17PM -0500, Richard Hipp wrote:
> >> But another problem emerged during testing. It seems that Michai's
> >> machine is not accepting the
On 25 January 2015 at 00:09, Joerg Sonnenberger wrote:
> On Sat, Jan 24, 2015 at 04:57:17PM -0500, Richard Hipp wrote:
>> But another problem emerged during testing. It seems that Michai's
>> machine is not accepting the certificate on
>> https://www.fossil-scm.org/. It is giving me an error:
>
On 25 January 2015 at 00:10, Andy Bradford wrote:
> Thus said Richard Hipp on Sat, 24 Jan 2015 16:27:55 -0500:
>
>> I would hope that the local machine knows that it cannot provide IPv6
>> service and that getaddrinfo() should therefore always return an IPv4
>> address. But apparently that is no
Thus said Richard Hipp on Sat, 24 Jan 2015 17:18:18 -0500:
> OK. Enhanced to do as Joerg describes. Seem to work fine on Michai's
> machine now without needing to --ipv4 manually.
Excellent change! After my last email, I started to look at the changes
required and you beat me to it. :-)
Thank
Thus said Joerg Sonnenberger on Sat, 24 Jan 2015 22:55:31 +0100:
> That's not how it is supposed to work. You are supposed to try the
> entries returned by gai as long as you get unreachable errors. That
> can happen for IPv4 too.
Yes, that is how it *should* work... As far as I know, Fo
Thus said Richard Hipp on Sat, 24 Jan 2015 16:27:55 -0500:
> I would hope that the local machine knows that it cannot provide IPv6
> service and that getaddrinfo() should therefore always return an IPv4
> address. But apparently that is not happening on Michai's machine.
That's a fair point. I
On Sat, Jan 24, 2015 at 04:57:17PM -0500, Richard Hipp wrote:
> But another problem emerged during testing. It seems that Michai's
> machine is not accepting the certificate on
> https://www.fossil-scm.org/. It is giving me an error:
Does it work with sqlite.org? If yes, the problem is likely a
On 1/24/15, Joerg Sonnenberger wrote:
> On Sat, Jan 24, 2015 at 04:27:55PM -0500, Richard Hipp wrote:
>> I would hope that the local machine knows that it cannot provide IPv6
>> service and that getaddrinfo() should therefore always return an IPv4
>> address. But apparently that is not happening
The new --ipv4 option seems to have cleared the problem for Michai.
It is still a question as to whether or not this issue will come up
with others.
But another problem emerged during testing. It seems that Michai's
machine is not accepting the certificate on
https://www.fossil-scm.org/. It is g
On Sat, Jan 24, 2015 at 04:27:55PM -0500, Richard Hipp wrote:
> On 1/24/15, Andy Bradford wrote:
> > Should Fossil have such a
> > selection mechanism in an option that indicates whether IPv6 should be
> > preferred, with the default falling to IPv4?
> >
>
> I would hope that the local machi
On 1/24/15, Andy Bradford wrote:
> Should Fossil have such a
> selection mechanism in an option that indicates whether IPv6 should be
> preferred, with the default falling to IPv4?
>
I would hope that the local machine knows that it cannot provide IPv6
service and that getaddrinfo() should t
On 24 January 2015 at 22:00, Andy Bradford wrote:
>
>> > Does your network have IPv6 support?
>>
>> none whatsoever.
>
> Ok, so apparently Fossil has recently had IPv6 support enabled in the
> client and it does seem that it is choosing to use IPv6 in favor of
> IPv4, even though you don't
On 1/24/15, Michai Ramakers wrote:
> On 24 January 2015 at 22:00, Andy Bradford
> wrote:
>>
>>> > Does your network have IPv6 support?
>>>
>>> none whatsoever.
>>
>> Ok, so apparently Fossil has recently had IPv6 support enabled in the
>> client and it does seem that it is choosing to use
On 1/24/15, Richard Hipp wrote:
> On 1/24/15, Michai Ramakers wrote:
>
>> michai@delle:/tmp/f/f/f2$ mkdir f3
>> michai@delle:/tmp/f/f/f2$ cd f3
>> michai@delle:/tmp/f/f/f2/f3$ f ver
>> This is fossil version 1.30 [331204dc93] 2014-11-14 19:30:13 UTC
>> michai@delle:/tmp/f/f/f2/f3$ f clo
Thus said "Andy Bradford" on 24 Jan 2015 14:00:22 -0700:
> Should Fossil have such a selection mechanism in an option that
> indicates whether IPv6 should be preferred, with the default falling
> to IPv4?
s/in/or/
Should Fossil have such a selection mechanism or an option that
Thus said Michai Ramakers on Sat, 24 Jan 2015 21:09:05 +0100:
> > Does your network have IPv6 support?
>
> none whatsoever.
Ok, so apparently Fossil has recently had IPv6 support enabled in the
client and it does seem that it is choosing to use IPv6 in favor of
IPv4, even though you don'
On 1/24/15, Michai Ramakers wrote:
> michai@delle:/tmp/f/f/f2$ mkdir f3
> michai@delle:/tmp/f/f/f2$ cd f3
> michai@delle:/tmp/f/f/f2/f3$ f ver
> This is fossil version 1.30 [331204dc93] 2014-11-14 19:30:13 UTC
> michai@delle:/tmp/f/f/f2/f3$ f clone http://fossil-scm.org f.f
> Round-tr
On 1/24/15, Andy Bradford wrote:
> Thus said Michai Ramakers on Sat, 24 Jan 2015 20:19:20 +0100:
>
>> michai@delle:/tmp/f/f/f2$ ../fossil clone http://fossil-scm.org f.f
>> cannot connect to host fossil-scm.org:80
>> Clone done, sent: 0 received: 0 ip: 2600:3c00::f03c:91ff:fe96:b959
>> s
On 24 January 2015 at 20:43, Andy Bradford wrote:
>
>> michai@delle:/tmp/f/f/f2$ ../fossil clone http://fossil-scm.org f.f
>> cannot connect to host fossil-scm.org:80
>> Clone done, sent: 0 received: 0 ip: 2600:3c00::f03c:91ff:fe96:b959
>> server returned an error - clone aborted
>
> It
Thus said Michai Ramakers on Sat, 24 Jan 2015 20:19:20 +0100:
> michai@delle:/tmp/f/f/f2$ ../fossil clone http://fossil-scm.org f.f
> cannot connect to host fossil-scm.org:80
> Clone done, sent: 0 received: 0 ip: 2600:3c00::f03c:91ff:fe96:b959
> server returned an error - clone aborted
Hello,
for some reason I can't seem to clone fossil's own repo from at least
2 machines behind the same NAT-router:
With fossil built from recent trunk:
michai@delle:/tmp/f/f$ mkdir f2
michai@delle:/tmp/f/f$ cd f2
michai@delle:/tmp/f/f/f2$ ../fossil ver
This is fossil version 1.30 [f55b5
23 matches
Mail list logo