Re: [PATCH v2 2/3] CI: don't care about SHA256 mismatch on upstream "perforce" package

From: Carlo Arenas <carenas@gmail.com>
Date: Apr 22, 2022, 11:15 UTC
Message-ID: <CAPUEsphEBdcxi_wbJxSQugo-bXS+eaEuhNuxciccux96M-B9cA@mail.gmail.com>
In-Reply-To: <patch-v2-2.3-2805e89623c-20220422T085958Z-avarab@gmail.com>

Show 16 quoted lines

> diff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh
> index 82fa87f97af..cab6e04a358 100755
> --- a/ci/install-dependencies.sh
> +++ b/ci/install-dependencies.sh
> @@ -37,7 +37,14 @@ macos-latest)
>         test -z "$BREW_INSTALL_PACKAGES" ||
>         brew install $BREW_INSTALL_PACKAGES
>         brew link --force gettext
> -       brew install perforce
> +       brew install perforce || {
> +               echo Installing perforce failed, assuming and working around SHA256 mismatch >&2 &&
> +
> +               path=$(brew edit --print-path perforce) &&
> +               sed 's/\(sha256.\).*/\1:no_check/' <"$path" >"$path".tmp &&
> +               mv "$path".tmp "$path" &&
> +               brew install perforce

brew install $path

seems to be a safer way to ensure that brew will use the locally modified cask

Carlo