Skip to content

zrok: update checksum#162351

Closed
stefanb wants to merge 1 commit intoHomebrew:masterfrom
stefanb:zrok-checksum
Closed

zrok: update checksum#162351
stefanb wants to merge 1 commit intoHomebrew:masterfrom
stefanb:zrok-checksum

Conversation

@stefanb
Copy link
Copy Markdown
Member

@stefanb stefanb commented Feb 11, 2024

At

the build reported:

==> Downloading from https://codeload.github.com/openziti/zrok/tar.gz/refs/tags/v0.4.23 Downloaded to: /Users/brew/Library/Caches/Homebrew/downloads/1d5a0aa58eb7f9a54fad745f57d0f557d70cdc1004c6e6c67b0ee3e1c987cb15--zrok-0.4.23.tar.gz SHA256: 4ca9c52b8ad56498fe3cc73a65e0f6381f1d1afa2f9be2c569dc6f2e3fb810f9 Warning: Formula reports different sha256: 020a1875fa7a62bccbeff6c21fc9292a02c97283796dfe7b4820be0b6c6c7946

Upstream issue:


  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

At
* Homebrew#157782

the build reported:

   ==> Downloading from https://codeload.github.com/openziti/zrok/tar.gz/refs/tags/v0.4.23 Downloaded to: /Users/brew/Library/Caches/Homebrew/downloads/1d5a0aa58eb7f9a54fad745f57d0f557d70cdc1004c6e6c67b0ee3e1c987cb15--zrok-0.4.23.tar.gz SHA256: 4ca9c52b8ad56498fe3cc73a65e0f6381f1d1afa2f9be2c569dc6f2e3fb810f9 Warning: Formula reports different sha256: 020a1875fa7a62bccbeff6c21fc9292a02c97283796dfe7b4820be0b6c6c7946
@github-actions github-actions Bot added go Go use is a significant feature of the PR or issue nodejs Node or npm use is a significant feature of the PR or issue labels Feb 11, 2024
@stefanb stefanb mentioned this pull request Feb 11, 2024
@p-linnane
Copy link
Copy Markdown
Member

Do we have any official confirmation of re-tagging from upstream?

@p-linnane p-linnane added the checksum mismatch SHA-256 doesn't match the download label Feb 11, 2024
@chenrui333 chenrui333 added upstream issue An upstream issue report is needed CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. labels Feb 12, 2024
@chenrui333
Copy link
Copy Markdown
Member

chenrui333 commented Feb 12, 2024

@chenrui333 chenrui333 closed this Feb 12, 2024
@stefanb stefanb deleted the zrok-checksum branch February 13, 2024 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

checksum mismatch SHA-256 doesn't match the download CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. go Go use is a significant feature of the PR or issue nodejs Node or npm use is a significant feature of the PR or issue upstream issue An upstream issue report is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants