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

frege-repl-1.4-SNAPSHOT.zip checksum changed #51

Closed
neutric opened this issue Apr 21, 2017 · 7 comments
Closed

frege-repl-1.4-SNAPSHOT.zip checksum changed #51

neutric opened this issue Apr 21, 2017 · 7 comments

Comments

@neutric
Copy link

neutric commented Apr 21, 2017

When frege-repl was added to Homebrew in May 2016, the sha256 for frege-repl-1.4-SNAPSHOT.zip was 2cf1c2a8f7b64c9d70b21fbfd25b2af3f5e3bebe3662f724afd435d01bddafec, but seems to be 2ca5f13bc5efaf8515381e8cdf99b4d4017264a462a30366a873cb54cc4f4640 now, which means the Homebrew installation fails with

Error: SHA256 mismatch
Expected: 2cf1c2a8f7b64c9d70b21fbfd25b2af3f5e3bebe3662f724afd435d01bddafec
Actual: 2ca5f13bc5efaf8515381e8cdf99b4d4017264a462a30366a873cb54cc4f4640

I suppose this is due to the snapshot being updated in place after the addition to Homebrew. Can you confirm this and the correctness of the checksum?

@neutric
Copy link
Author

neutric commented Apr 30, 2017

@Dierk Care to comment?

@Dierk
Copy link
Member

Dierk commented Apr 30, 2017 via email

@neutric
Copy link
Author

neutric commented Apr 30, 2017

@Dierk Sorry if I wasn't clear enough, but my question was regarding the file marked as Latest release on https://github.com/Frege/frege-repl/releases.

@mmhelloworld
Copy link
Member

Hi @neutric ,

I remember updating the snapshot. I think it is to fix this bug Frege/frege#292.

@neutric
Copy link
Author

neutric commented Apr 30, 2017

@mmhelloworld Hello! :D Thanks for your confirmation, that means we can go ahead and update the checksum.

For the future: please consider not reusing the same tag when uploading a new release so that projects like Homebrew, which rely on checksums, do not break out of the blue. Adding e.g. a date to it would suffice.

@mmhelloworld
Copy link
Member

Sorry for the confusion! If I understand this correctly, going forward we will add a date to the zip file name. Thanks for following up on this.

@neutric
Copy link
Author

neutric commented Apr 30, 2017

No worries. And that would be helpful. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants