Closed jsundram closed 4 years ago
what i find weird here is that 1.) its a known fact that our downloader follows redirects and 2.) i have no problems downloading processing with 'brew cask fetch'
any idea why this only affects some users?
i have no problems downloading processing with 'brew cask fetch'
Nor do I, but I use a brew
'ed curl
and I supposed this was related to https://github.com/Homebrew/homebrew-cask/issues/83481 and the system curl
.
hm, i've uninstalled the homebrew'ed curl
but still wasn't able to reproduce this
hm, i've uninstalled the homebrew'ed
curl
but still wasn't able to reproduce this
Same here ...
@jsundram can you please post the output of which -a curl
and curl -sLI https://download.processing.org/processing-3.5.4-macosx.zip | grep HTTP
, thanks.
$ which -a curl
/usr/local/anaconda3/bin/curl
/usr/bin/curl
$ curl -sLI https://download.processing.org/processing-3.5.4-macosx.zip | grep HTTP
HTTP/1.1 302 Found
HTTP/1.1 302 Found
HTTP/1.1 403 Forbidden
@miccal -- it looks like this may be a path issue with anaconda?
$ echo $PATH
/usr/local/sbin:/usr/local/anaconda3/bin:/usr/local/anaconda3/condabin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/opt/homebrew/bin
Most definitely -- the fact that /usr/local/anaconda3/bin/curl
appears before /usr/bin/curl
in the output of which -a curl
is strange.
I have no experience with anaconda
, so I am not sure what to suggest, sorry.
@miccal, thanks for your help!
I'm going to run conda remove curl
; after doing that which -a curl
no longer lists /usr/local/anaconda3/bin/curl
, so this should no longer shadow the system curl, which I think means that brew cask will no longer accidentally hit anaconda's curl in the future.
i guess 'brew cask doctor' should include the output of 'which -a curl' ?
@core-code I am fairly certain that brew
uses the system curl via /usr/bin/curl
unless HOMEBREW_FORCE_BREWED_CURL
is set; hence the output of which -a curl
would not be required.
I wanted to see @jsundram's output of which -a curl
because they were getting two different results for brew cask install processing
and curl https://download.processing.org/processing-3.5.4-macosx.zip
, which was initially confusing -- the reason, as it turns out, was that brew cask install processing
used /usr/bin/curl
while curl https://download.processing.org/processing-3.5.4-macosx.zip
used /usr/local/anaconda3/bin/curl
.
None of this explains the random SSL certificate
error, though :(
thanks for the explanation - indeed its quite weird
General troubleshooting steps
--force
.brew update-reset && brew update
and retried my command.brew doctor
, fixed as many issues as possible and retried my command.Description of issue
brew cask install Processing
yields an errorcurl: (60) SSL certificate problem: certificate has expired
(see verbose error info below)curl "https://download.processing.org/processing-3.5.4-macosx.zip"
yields a clear redirect.-L
option would allow this). I'm not sure if the best way to resolve this is just to update the formula to point tohttps://github.com/processing/processing/releases/download/processing-0270-#{version}/processing-#{version}-macosx.zip
or if this is a general problem that could/should be fixed by adding -L to the curl command to follow redirects.Command that failed
Output of command with
--force --verbose --debug
Output of
brew cask doctor
Output of
brew tap