Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Nov 2022 09:30:56 +0800
From:      Philip Paeps <philip@freebsd.org>
To:        Jan Beich <jbeich@FreeBSD.org>
Cc:        Simon Wright <simon.wright@gmx.net>, freebsd-ports@freebsd.org
Subject:   Re: Access to FreeBSD package build server via IPv4-only network
Message-ID:  <F9AE539C-89C2-45AA-88F2-8A69D26C1E5C@freebsd.org>
In-Reply-To: <zgcz-ldmr-wny@FreeBSD.org>
References:  <3d3388c7-b9e2-2490-15ad-208a03df6627@gmx.net> <zgcz-ldmr-wny@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-11-10 10:58:04 (+0800), Jan Beich wrote:
> Simon Wright <simon.wright@gmx.net> writes:
>> My issue is that since the build servers are IPv6-only and my 
>> provider
>> in Philippines does not offer any IPv6 service at all, I need to use 
>> a
>> proxy to use curl to access this file:
>>
>> http://beefy16.nyi.freebsd.org/data/131amd64-default/.data.json
>
> https://pkg-status.freebsd.org/beefy16/data/131amd64-default/.data.json
>
> pkg-status can act as a proxy, limited to freebsd.org machines it 
> manages.

I've asked pkgmgr to change the links in the pkg-fallout reports to 
point at the pkg-status.freebsd.org proxy, rather than to the builders 
directly.  They've changed that yesterday.

Philip [hat: clusteradm]


-- 
Philip Paeps
Senior Reality Engineer
Alternative Enterprises



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F9AE539C-89C2-45AA-88F2-8A69D26C1E5C>