search

soffes / Clock.saver

Simple clock screensaver written in Swift
http://dribbble.com/shots/1460483-Clock-Screensaver
MIT License
805 stars 47 forks source link

Checksum mismatch #22

Closed neutric closed 2 years ago

neutric commented 2 years ago

A Homebrew user reported that the installation fails because of a checksum mismatch on the current version 0.7.0 of Clock.saver. I can corroborate:

==> Downloading https://github.com/soffes/Clock.saver/releases/download/v0.7.0/Clock.saver-0.7.0.zip
==> Downloading from https://objects.githubusercontent.com/github-production-release-asset-2e65be/17547174/6c9e3172-023c-4e1e-833d-998e49c0751a?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211206%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211206T101935Z&X-Amz-Expires=300&X-Amz-Signature=7ff421687218baf94dcef72dae406aee03f7e85e7ce2a9668e67637200fcf2c3&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=17547174&response-content-disposition=attachment%3B%20filename%3DClock.saver-0.7.0.zip&response-content-type=application%2Foctet-stream
Error: SHA256 mismatch
Expected: 9497e774695cadfb25fb6ad1b5689a110f806041b34d3b536b862d653de8bca4
  Actual: a5559b1bcb20ae5bc473e16e6842618aa3a51ed17e9dc583a069ed1af5931180

The latest change on the cask definition was:

df911976cc 2021-03-21 05:06:19 +0100 clocksaver: add livecheck (#101682) Markus Reiter.

Checksum was confirmed good by CI then. Did you update the file in place since then or is something else going on?

soffes commented 2 years ago

Wasn't aware it was on Homebrew. I might have updated it. I think the Developer ID cert expired awhile back. I'll try to get around to making another build soon.

neutric commented 2 years ago

Thanks for replying! I'll update the checksum in the cask definition so that installations work again. A new release is not necessary for us given that you are reasonably certain that the change isn't malicious, it would have avoided this feedback loop though.

soffes commented 2 years ago

Oh great! Thanks!

Sam

On Dec 7, 2021, at 11:41 AM, neutric @.***> wrote:

 Closed #22.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

soffes commented 2 years ago

@neutric in case it matters, I did release a new version (0.7.1) today. The previous version's Developer ID certificate was going to expire soon. I didn't update the previous release's binary. Definitely won't do that again!

neutric commented 2 years ago

Thanks Sam, I opened a PR to update the cask. Should be merged later today.