-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
pass: update digest #181795
pass: update digest #181795
Conversation
Signed-off-by: William Woodruff <william@yossarian.net>
For posterity, here's a copy of both archives + the |
we also need to notify upstream about the issue as well |
Done -- I've sent the maintainer a DM in a shared channel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the diligence here!
🤖 An automated task has requested bottles to be published to this PR. |
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>
?This updates
pass
's digest to the latest version served by its upstream. After triage, we've concluded that this digest change was likely caused by agit archive
change. No underlying file contents were changed.@Bo98 independently confirmed that he observed the same digest from the upstream, and confirmed that only the XZ header differs. I'm also copying my
pkgdiff
results below: