Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

magrit 2.2.0 (new cask) #198239

Closed
wants to merge 2 commits into from
Closed

magrit 2.2.0 (new cask) #198239

wants to merge 2 commits into from

Conversation

jamu3l
Copy link

@jamu3l jamu3l commented Jan 14, 2025

After making any changes to a cask, existing or new, verify:

Additionally, if adding a new cask:

  • Named the cask according to the token reference.
  • Checked the cask was not already refused.
  • brew audit --cask --new magrit worked successfully.
  • HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
  • brew uninstall --cask magrit worked successfully.

Audit returns one error as the app is unsigned/not notarized by the developer:

audit for magrit: failed
 - Signature verification failed:
/private/tmp/cask-audit20250114-68314-iedg48/Magrit.app: code has no resources but signature indicates they must be present

macOS on ARM requires software to be signed.
Please contact the upstream developer to let them know they should sign and notarize their software.
magrit
  * line 5, col 2: Signature verification failed:
    /private/tmp/cask-audit20250114-68314-iedg48/Magrit.app: code has no resources but signature indicates they must be present

    macOS on ARM requires software to be signed.
    Please contact the upstream developer to let them know they should sign and notarize their software.
Error: 1 problem in 1 cask detected.

@jamu3l jamu3l changed the title magrit 2.2.0 magrit 2.2.0 (new cask) Jan 14, 2025
@khipp
Copy link
Member

khipp commented Jan 14, 2025

Thank you for your submission, @jamu3l. We are unable to accept it at this time because it does not pass Homebrew's signature verification check:

macOS on ARM requires applications to be signed. Please contact the upstream developer to let them know they should sign their app.

Please consider hosting this in your own Tap and if the developers sign their app in the future we would be happy to consider adding this to homebrew-cask.

@khipp khipp closed this Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants