Why does Brew require a newer version of curl?? #224

HariSekhon · 2020-12-04T10:18:56Z

HariSekhon
Dec 4, 2020

Some of my CI builds have started failing during the install:

curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh | bash

due to the following "error":

...
HEAD is now at cb38fe6e3 Merge pull request #9413 from Rylan12/pypi-fix
Error: Please update your system cURL.
Minimum required version: 7.41.0
Your cURL version: 7.35.0
Your cURL executable: /usr/bin/curl
Error: Curl must be installed and in your PATH!
Failed during: /home/linuxbrew/.linuxbrew/bin/brew update --force

Why is Brew not requiring a newer version of Curl and is there any workaround since I don't want to have to go and down manual curl installations on all the older CI systems...

Answered by HariSekhon

Dec 4, 2020

Ok, trawled the git log and code and found the answer here:

https://github.com/Homebrew/brew/blob/master/Library/Homebrew/brew.sh#L353

 if [[ -n "$HOMEBREW_FORCE_HOMEBREW_ON_LINUX" && -n "$HOMEBREW_ON_DEBIAN7" ]]
  then
    # Special version for our debian 7 docker container used to build patchelf and binutils
    HOMEBREW_MINIMUM_CURL_VERSION="7.25.0"
  else
    # Ensure the system Curl is a version that supports modern HTTPS certificates.
    HOMEBREW_MINIMUM_CURL_VERSION="7.41.0"
  fi
  curl_version_output="$($HOMEBREW_CURL --version 2>/dev/null)"
  curl_name_and_version="${curl_version_output%% (*}"
  if [[ $(numeric "${curl_name_and_version##* }") -lt $(numeric "$HOMEBREW_MINIMUM_CUR…

View full answer

HariSekhon · 2020-12-04T10:39:55Z

HariSekhon
Dec 4, 2020
Author

Ok, trawled the git log and code and found the answer here:

https://github.com/Homebrew/brew/blob/master/Library/Homebrew/brew.sh#L353

 if [[ -n "$HOMEBREW_FORCE_HOMEBREW_ON_LINUX" && -n "$HOMEBREW_ON_DEBIAN7" ]]
  then
    # Special version for our debian 7 docker container used to build patchelf and binutils
    HOMEBREW_MINIMUM_CURL_VERSION="7.25.0"
  else
    # Ensure the system Curl is a version that supports modern HTTPS certificates.
    HOMEBREW_MINIMUM_CURL_VERSION="7.41.0"
  fi
  curl_version_output="$($HOMEBREW_CURL --version 2>/dev/null)"
  curl_name_and_version="${curl_version_output%% (*}"
  if [[ $(numeric "${curl_name_and_version##* }") -lt $(numeric "$HOMEBREW_MINIMUM_CURL_VERSION") ]]
  then
      message="Please update your system cURL.
Minimum required version: ${HOMEBREW_MINIMUM_CURL_VERSION}
Your cURL version: ${curl_name_and_version##* }
Your cURL executable: $(type -p $HOMEBREW_CURL)"

5 replies

raakasf Aug 1, 2023

I don't understand the answer here? How do we circumvent this on older systems? It's a pain to get newer version of curl on CentOS specially in corp environment.

SMillerDev Aug 1, 2023
Collaborator

You don't, brew needs it to make secure connections. If you can't do that you can't use brew.

raakasf Aug 1, 2023

Ok, thanks, guess will have to install curl then.

osalbahr Aug 1, 2023
Sponsor

I don't understand the answer here? How do we circumvent this on older systems? It's a pain to get newer version of curl on CentOS specially in corp environment.

The way I do it in CentOS 7 is by installing curl via spack or nix (or nix-portable). After that, you can brew install curl and have Homebrew use its own curl (by setting HOMEBREW_CURL_PATH) and delete whatever you used to bootstrap it. You might need to do the same with git.

I’ve had a more reliable experience with spack and it is natively a standalone package manager so you don’t need root access, but be prepared to wait like half an hour and use half a gigabyte because it compiles the world. And you probably need your sysadmin to create a writable /home/linuxbrew to be able to reliably use Homebrew (non-default prefix is unsupported and some formulae expectedly break).

Of course, you can install curl from source manually. But that’s contingent on having the build requirements. You can install the requirements from source etc, but I found that tedious and gave up (afterall, that’s one of the reasons spack exists).

Thought experiment, as an alternative:

Install Homebrew in a different machine (or in a container)
brew install curl [git …]
[s]cp /home/linuxbrew over (or, use the same non-default prefix in the other system)

~~It should work. I said thought experiment because I haven’t tried it myself (yet?).~~

Edit: yeah, it does work (so far). I'm using Ubuntu 22.04.2 LTS (jammy) to "sideload" to CentOS Linux release 7.9.2009 (Core) (by rsync -au periodically).

osalbahr Aug 2, 2023
Sponsor

Actually, looking back at Untar anywhere (unsupported), it looks like Homebrew is already capable to "bootstrap" (i.e. install curl then git for itself). Without root, and without installing anything at a system level. Though the output might be different if you choose to install in a non-default prefix as Homebrew will need to install a lot of stuff from source which might fail depending of your dev tools.

Note: this might only work when using the default prefix. For non-default prefixes, see the workaround at the end of the previous comment.

$ docker run --rm -it centos:7
[root@f2444420d8fb /]# useradd linuxbrew
[root@f2444420d8fb /]# su linuxbrew
[linuxbrew@f2444420d8fb /]$ cd
[linuxbrew@f2444420d8fb ~]$ mkdir .linuxbrew && curl -L https://github.com/Homebrew/brew/tarball/master | tar xz --strip 1 -C .linuxbrew
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 2787k  100 2787k    0     0  2863k      0 --:--:-- --:--:-- --:--:-- 8214k
[linuxbrew@f2444420d8fb ~]$ eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
[linuxbrew@f2444420d8fb ~]$ brew update --force --quiet
Error: Please update your system curl or set HOMEBREW_CURL_PATH to a newer version.
Minimum required version: 7.41.0
Your curl version: 7.29.0
Your curl executable: 
Error: Please update your system Git or set HOMEBREW_GIT_PATH to a newer version.
Minimum required version: 2.7.0
Your Git version: ...
Your Git executable: 
==> Downloading https://ghcr.io/v2/homebrew/portable-ruby/portable-ruby/blobs/sha256:68923daf3e139482b977c3deba63a3b54ea37bb5f716482948878819ef911bad
######################################################################## 100.0%
==> Pouring portable-ruby-2.6.10_1.x86_64_linux.bottle.tar.gz
==> Downloading https://formulae.brew.sh/api/formula.jws.json
######################################################################### 100.0%
==> Fetching dependencies for curl: [email protected], glibc, gmp, isl, mpfr, libmpc, lz4, xz, zlib, zstd, binutils, gcc, brotli, libunistring, libidn2, libnghttp2, ca-certificates, openssl@3, libssh2, ncurses, readline, libxcrypt, util-linux, openldap, rtmpdump, libedit and krb5
...
==> Installing curl
==> Pouring curl--8.2.1.x86_64_linux.bottle.tar.gz
🍺  /home/linuxbrew/.linuxbrew/Cellar/curl/8.2.1: 515 files, 5MB
==> Running `brew cleanup curl`...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
[linuxbrew@f2444420d8fb ~]$ brew install -q git
Error: Please update your system curl or set HOMEBREW_CURL_PATH to a newer version.
Minimum required version: 7.41.0
Your curl version: 7.29.0
Your curl executable: 
Error: Please update your system Git or set HOMEBREW_GIT_PATH to a newer version.
Minimum required version: 2.7.0
Your Git version: ...
Your Git executable: 
==> Fetching dependencies for git: icu4c, libxml2, gettext, bzip2, pcre2 and expat
...
[linuxbrew@f2444420d8fb ~]$ export HOMEBREW_CURL_PATH=$(command -v curl) HOMEBREW_GIT_PATH=$(command -v git)
[linuxbrew@f2444420d8fb ~]$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: No developer tools installed.
Install Clang or run `brew install gcc`.
[linuxbrew@f2444420d8fb ~]$ brew config
HOMEBREW_VERSION: >=2.5.0 (shallow or no git repository)
ORIGIN: (none)
HEAD: (none)
Last commit: never
Core tap JSON: 02 Aug 01:54 UTC
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_REPOSITORY: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_CURL_PATH: /home/linuxbrew/.linuxbrew/bin/curl
HOMEBREW_GIT_PATH: /home/linuxbrew/.linuxbrew/bin/git
HOMEBREW_MAKE_JOBS: 2
Homebrew Ruby: 2.6.10 => /home/linuxbrew/.linuxbrew/Library/Homebrew/vendor/portable-ruby/2.6.10_1/bin/ruby
CPU: dual-core 64-bit skylake
Clang: N/A
Git: 2.41.0 => /home/linuxbrew/.linuxbrew/bin/git
Curl: 8.2.1 => /home/linuxbrew/.linuxbrew/bin/curl
Kernel: Linux 5.15.49-linuxkit-pr x86_64 GNU/Linux
OS: CentOS Linux release 7.9.2009 (Core)
Host glibc: 2.17
/usr/bin/gcc: N/A
/usr/bin/ruby: N/A
glibc: N/A
gcc@11: N/A
gcc: N/A
xorg: N/A
[linuxbrew@f2444420d8fb ~]$ brew update
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint: 	git config --global init.defaultBranch <name>
hint: 
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: 
hint: 	git branch -m <name>
Initialized empty Git repository in /home/linuxbrew/.linuxbrew/.git/
remote: Enumerating objects: 245344, done.
remote: Counting objects: 100% (1551/1551), done.
remote: Compressing objects: 100% (854/854), done.
remote: Total 245344 (delta 804), reused 1356 (delta 656), pack-reused 243793
Receiving objects: 100% (245344/245344), 72.02 MiB | 14.24 MiB/s, done.
Resolving deltas: 100% (179256/179256), done.
From https://github.com/Homebrew/brew
 * [new branch]          master     -> origin/master
 * [new tag]             0.1        -> 0.1
...
 * [new tag]             4.1.3      -> 4.1.3
HEAD is now at 799417343 Merge pull request #15800 from dduugg/inreplace-paths
==> Homebrew collects anonymous analytics.
Read the analytics documentation (and how to opt-out) here:
  https://docs.brew.sh/Analytics
No analytics have been recorded yet (nor will be during this `brew` run).

==> Homebrew is run entirely by unpaid volunteers. Please consider donating:
  https://github.com/Homebrew/brew#donations

Already up-to-date.
[linuxbrew@f2444420d8fb ~]$ brew config
HOMEBREW_VERSION: 4.1.3-21-g7994173
ORIGIN: https://github.com/Homebrew/brew
HEAD: 799417343a5176d710f7330d46ca0732e4b75637
Last commit: 9 hours ago
Core tap JSON: 02 Aug 02:01 UTC
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_REPOSITORY: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_CURL_PATH: /home/linuxbrew/.linuxbrew/bin/curl
HOMEBREW_GIT_PATH: /home/linuxbrew/.linuxbrew/bin/git
HOMEBREW_MAKE_JOBS: 2
Homebrew Ruby: 2.6.10 => /home/linuxbrew/.linuxbrew/Library/Homebrew/vendor/portable-ruby/2.6.10_1/bin/ruby
CPU: dual-core 64-bit skylake
Clang: N/A
Git: 2.41.0 => /home/linuxbrew/.linuxbrew/bin/git
Curl: 8.2.1 => /home/linuxbrew/.linuxbrew/bin/curl
Kernel: Linux 5.15.49-linuxkit-pr x86_64 GNU/Linux
OS: CentOS Linux release 7.9.2009 (Core)
Host glibc: 2.17
/usr/bin/gcc: N/A
/usr/bin/ruby: N/A
glibc: N/A
gcc@11: N/A
gcc: N/A
xorg: N/A

rohanssrao · 2023-08-01T20:42:21Z

rohanssrao
Aug 1, 2023

You can try using a statically compiled curl binary from https://github.com/moparisthebest/static-curl/releases/.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Homebrew

Why does Brew require a newer version of curl?? #224

{{title}}

Replies: 2 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Homebrew

Why does Brew require a newer version of curl?? #224

HariSekhon Dec 4, 2020

Replies: 2 comments · 5 replies

HariSekhon Dec 4, 2020 Author

raakasf Aug 1, 2023

SMillerDev Aug 1, 2023 Collaborator

raakasf Aug 1, 2023

osalbahr Aug 1, 2023 Sponsor

osalbahr Aug 2, 2023 Sponsor

rohanssrao Aug 1, 2023

HariSekhon
Dec 4, 2020

Replies: 2 comments 5 replies

HariSekhon
Dec 4, 2020
Author

SMillerDev Aug 1, 2023
Collaborator

osalbahr Aug 1, 2023
Sponsor

osalbahr Aug 2, 2023
Sponsor

rohanssrao
Aug 1, 2023