Summary: | URL and JSON file used to monitor package building no longer available | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | mfv |
Component: | Package Infrastructure | Assignee: | Cluster Admin <clusteradm> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | lwhsu, philip |
Priority: | --- | ||
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any |
Description
mfv
2021-04-20 17:36:11 UTC
The builders moved to ipv6 only. I moved the package builders to an IPv6-only VLAN last week. If you have IPv6 connectivity, you can still access them directly. I still need to add a proxy for these on the legacy internet. I'll try to get around to that this week. (In reply to Philip Paeps from comment #2) Hello Philip, Thanks for your reply of last April. Since then I took your advice and set up IPv6 through tunelling. It worked and I was able to access the package build site. However, I was forced to change my ISP to Verizon/FIOS as Verizon will no longer repair their copper-based telephone system. Since my move to FIOS I have not been able to access http://beefy6.nyi.freebsd.org/data/122amd64-default/.data.json As mentioned in your last comment, has the proxy been set up as yet? With thanks, Marek This was fixed a while ago: https://pkg-status.freebsd.org/${BUILDER}/ provides a dual-stack proxy to the many package builders. The URL http://beefy6.nyi.freebsd.org/data/122amd64-default/.data.json is also available as https://pkg-status.freebsd.org/beefy6/data/122amd64-default/.data.json. I'll check if we can change the URLs in the build logs to point at the proxy rather than at the builders directly. Thanks for reporting this. |