Bug 245055

Summary: Mk/bsd.sites.mk: cloud.github.com down (deprecated?)
Product: Ports & Packages Reporter: John Hein <jcfyecrayz>
Component: Individual Port(s)Assignee: Port Management Team <portmgr>
Status: Closed DUPLICATE    
Severity: Affects Some People CC: ak, portmgr
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
[patch] update SITE_GITHUB_CLOUD (cloud.github.com down) jcfyecrayz: maintainer-approval? (portmgr)

Description John Hein 2020-03-25 16:21:07 UTC 
Created attachment 212702 [details]
[patch] update SITE_GITHUB_CLOUD (cloud.github.com down)

Today it seems cloud.github.com is not available:

% host -t any cloud.github.com
cloud.github.com is an alias for d24z2fz21y4fag.cloudfront.net.
% host -t any d24z2fz21y4fag.cloudfront.net.
d24z2fz21y4fag.cloudfront.net has no ANY record

Any port that has GHC for the master site is failing to fetch.

There is some anecdotal evidence that it is deprecated:

https://github.com/square/PonyDebugger/issues/205

However, I did not find an authoritative statement of that.

Nonetheless, github.com seems to work instead:
Comment 1 John Hein 2020-03-25 18:13:53 UTC 
Maybe MASTER_SITE_GITHUB_CLOUD should be renamed to MASTER_SITE_GITHUB_DOWNLOADS.

"downloads" is an official name of a class of files described by the github REST API, so that name seems more fitting.

Example:

% curl 'https://api.github.com/repos/sodabrew/libsieve/downloads' | g _url
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1237  100  1237    0     0   2593      0 --:--:-- --:--:-- --:--:--  2593
    "html_url": "https://github.com/downloads/sodabrew/libsieve/libsieve-2.3.1.tar.gz",
    "html_url": "https://github.com/downloads/sodabrew/libsieve/libsieve-2.3.0.tar.gz",
    "html_url": "https://github.com/downloads/sodabrew/libsieve/libsieve-2.2.9.tar.gz",
Comment 2 Charlie Li freebsd_committer freebsd_triage 2021-06-11 13:42:24 UTC 

*** This bug has been marked as a duplicate of bug 242268 ***