-
-
Notifications
You must be signed in to change notification settings - Fork 12.9k
verapdf: update checksum #223427
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
verapdf: update checksum #223427
Conversation
589d5c3
to
d9d23a3
Compare
It seems that the GitHub repository for veraPDF-apps has not enabled the Issue tracker. |
d9d23a3
to
837c548
Compare
What can I do about this now? |
need to notify the upstream and find out if the checksum change was intended. |
FYI: #223427 (comment)
|
Maybe see if you get a response here? |
Alright, I’ve done that, and they’ve already confirmed it. |
🤖 An automated task has requested bottles to be published to this PR. Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch. |
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?Found from: