Closed Moulick closed 1 year ago
I am curious why brew search
actually makes a call to the URL in the app stanza of transmission-nightly
?
@Homebrew/brew is brew supposed to call all URLs that have a closure attached when you run brew search
? That seems kinda weird.
even running brew info transmission-nightly
make the curl call to its release page. It looks like the structure of the transmission-nightly
cask is inconsistent with other casks
even running
brew info transmission-nightly
make the curl call to its release page. It looks like the structure of thetransmission-nightly
cask is inconsistent with other casks
So unlike most casks, that particular cask determines its download URL dynamically. And it does so by issuing a network call to another URL. Ignoring whether it should or shouldn't continue doing that, it does make some sense why brew info
would resolve that to find the full URL for display (though we could just display that it's dynamic instead). I see no reason why brew search
should resolve the URL in any case however, so maybe we can fix that.
Confirmed fix, brew search google-chrome
works fine again.
Verification
--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
Running
brew search google-chrome
throws errorIt seems that the https://build.transmissionbt.com/job/trunk-mac/lastSuccessfulBuild/artifact/release/ is now protected by Cloudflare and prevents pulling via curl.
Command that failed
brew search google-chrome
Output of command with
--verbose --debug
Output of
brew doctor --verbose
Output of
brew tap