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

Geocouch shasum changed #471

Closed
apjanke opened this issue Apr 20, 2016 · 2 comments
Closed

Geocouch shasum changed #471

apjanke opened this issue Apr 20, 2016 · 2 comments
Labels
upstream issue An upstream issue report is needed

Comments

@apjanke
Copy link
Contributor

apjanke commented Apr 20, 2016

The SHA sum for the current geocouch file (https://github.com/couchbase/geocouch/archive/couchdb1.3.x.tar.gz) has changed some time between July 2014 and now, so attempts to install from source get a SHA mismatch error.

$ brew install geocouch -s
==> Using the sandbox
==> Downloading https://github.com/couchbase/geocouch/archive/couchdb1.3.x.tar.gz
Already downloaded: /Library/Caches/Homebrew/geocouch-1.3.0.tar.gz
Error: SHA256 mismatch
Expected: 0f678b5b79f5385c5c11349b662bb897047c72e8056dfb19f0f1e484d9348953
Actual: 1bad2275756e2f03151d7b2706c089b3059736130612de279d879db91d4b21e7
Archive: /Library/Caches/Homebrew/geocouch-1.3.0.tar.gz
To retry an incomplete download, remove the file above.

I've posted this upstream at https://forums.couchbase.com/t/geocouch-couchdb1-3-x-tar-gz-checksum-changed/7889.

@apjanke apjanke added the upstream issue An upstream issue report is needed label Apr 20, 2016
@DomT4
Copy link
Member

DomT4 commented Apr 20, 2016

It changes every now and again. See #436, Homebrew/legacy-homebrew#42498, Homebrew/legacy-homebrew#49813, etc.

The problem in part is that we're not using a real tarball. It's tied to the upstream branch and every time they push a new commit to that branch or do something that tweaks the git history the checksum borks.

We could probably deal with this more obviously by using a git checkout, branch and revision, but that won't address the root problem that we're not using a "real" tag or release point.

@apjanke
Copy link
Contributor Author

apjanke commented Apr 20, 2016

I think this is also a problem with a redirect not being followed, too. I get the same SHA when I download other geocouch versions as a resource in a formula.

I'll just bump the SHA value once I get the redirect figured out; you're right about other options not addressing the problem.

@apjanke apjanke closed this as completed in 8c13fc2 Jul 2, 2016
@Homebrew Homebrew locked and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream issue An upstream issue report is needed
Projects
None yet
Development

No branches or pull requests

2 participants