You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2017-11-26 20:24:59 -0500 the SHA-256 was
faccec8715ed2dd2193ae4e026c1735ff354bba635b9bb60d2642e2895aa5674
Now it's changed to
bb9679045540554232eff303fc4f615d28eb4023461eae3f65f08f2427ec9ef2
Do you have any idea what happened here? To rule out malicious circumstances, we'll need to know why the file has changed before the checksum can be updated in Homebrew. Thanks!
The text was updated successfully, but these errors were encountered:
On Sun, Jan 28, 2018 at 6:34 AM, ilovezfs ***@***.***> wrote:
Homebrew users currently cannot build btfs from source due to a SHA-256
checksum mismatch for v2.18.tar.gz (https://github.com/johang/
btfs/archive/v2.18.tar.gz)
2017-11-26 20:24:59 -0500 the SHA-256 was
faccec8715ed2dd2193ae4e026c1735ff354bba635b9bb60d2642e2895aa5674
Now it's changed to
bb9679045540554232eff303fc4f615d28eb4023461eae3f65f08f2427ec9ef2
Do you have any idea what happened here? To rule out malicious
circumstances, we'll need to know why the file has changed before the
checksum can be updated in Homebrew. Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#47>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACgOHcJYjGFWpltXpSD_H_dG0UTTNiLks5tPAbegaJpZM4Rvk1U>
.
Homebrew users currently cannot build btfs from source due to a SHA-256 checksum mismatch for v2.18.tar.gz (https://github.com/johang/btfs/archive/v2.18.tar.gz)
2017-11-26 20:24:59 -0500 the SHA-256 was
faccec8715ed2dd2193ae4e026c1735ff354bba635b9bb60d2642e2895aa5674
Now it's changed to
bb9679045540554232eff303fc4f615d28eb4023461eae3f65f08f2427ec9ef2
Do you have any idea what happened here? To rule out malicious circumstances, we'll need to know why the file has changed before the checksum can be updated in Homebrew. Thanks!
The text was updated successfully, but these errors were encountered: