Homebrew
[tcl-tk] SHA256 mismatch for itk tarball #5835
Replies: 2 comments 5 replies
-
|
No, at some point that hash was correct. Our CI would have failed the build had there been a mismatch. I don't really have any advice other than to ask upstream, or maybe @cho-m will weigh in. |
Beta Was this translation helpful? Give feedback.
-
|
Agree with above. Gentoo has archived a copy of original tarball (e.g. https://distfiles.gentoo.org/distfiles/58/itk-4-2-3.tar.gz) if anyone wants to look into diff further. |
Beta Was this translation helpful? Give feedback.
-
|
Diffing the tarballs: No changes to the contents after being unarchived though. |
Beta Was this translation helpful? Give feedback.
-
|
That should be commit tar was generated from: |
Beta Was this translation helpful? Give feedback.
-
That's the only difference when looking at both commits. I assume at some point they must have rewritten the git history to change the author e-mail address. It would be nice if someone could confirm if this is the case. |
Beta Was this translation helpful? Give feedback.
-
|
Any updates on this? Getting exact same error as @denilsonsa. |
Beta Was this translation helpful? Give feedback.
-
|
It seems nobody asked upstream what the cause was, so it'll stay that way until someone does. |
Beta Was this translation helpful? Give feedback.
-
Output of
brew configOutput of
brew doctorDescription of issue
When trying to build
tcl-tk, it fails with this message:I can see the tag itk-4-2-3 is from one year ago. I know GitHub once tried changing some setting and that caused all the hashes to change, but they seem to have reverted it. They even announced their plans on the future stability of hashes.
I can also see this SHA256 hash was introduced in the beginning of November by @cho-m.
Was the hash wrong in that commit? Or did the tarball change from GitHub?
Someone who is more familiar with tcl-tk and itk should take a look at this.
Beta Was this translation helpful? Give feedback.
All reactions