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

Checksum mismatch on varnamelen dependency during build #1461

Closed
5 tasks
mzabaluev opened this issue Apr 29, 2022 · 4 comments
Closed
5 tasks

Checksum mismatch on varnamelen dependency during build #1461

mzabaluev opened this issue Apr 29, 2022 · 4 comments
Assignees

Comments

@mzabaluev
Copy link

Summary of Bug

Build fails due to a corrupted checksum on github.com/blizzy78/varnamelen.

Version

v7.0.1
(not fixed as of c934600)

Steps to Reproduce

Check out the repository and run make install.

I get a build error:

verifying github.com/blizzy78/varnamelen@v0.6.1/go.mod: checksum mismatch
	downloaded: h1:mGBHm+Uo4e8JnZEKHRoZgVEOQdSBdQfY/x+k4NAXBWA=
	go.sum:     h1:zy2Eic4qWqjrxa60jG34cfL0VXcSwzUrIx68eJPb4Q8=

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
  • Is a spike necessary to map out how the issue should be approached?
@okwme
Copy link
Contributor

okwme commented May 2, 2022

Hi @mzabaluev we've tried reproducing the error but don't see the hash mismatch. Can you confirm this fails for you when you use a proxy? There could be an issue with your network or the CDN in your area. At this moment we can't reproduce the error.

Also did you use go ​clean -modcache before running?

@mzabaluev
Copy link
Author

Hi @mzabaluev we've tried reproducing the error but don't see the hash mismatch. Can you confirm this fails for you when you use a proxy?

I need some education on this. Is there a proxy I can try?

There could be an issue with your network or the CDN in your area.

Maybe, but exactly the same problem was seen in open-telemetry/opentelemetry-go#2760, and the developers have fixed it by updating the dependencies.

Also did you use go ​clean -modcache before running?

I just did, it does not help.

@okwme
Copy link
Contributor

okwme commented May 5, 2022

HI @mzabaluev
I've also just tried to install after running go clean -modcache and had no problem.
i'm using go version go1.17.5 darwin/amd64
there's minimum requirement of 1.17, can you confirm your verison?

@mzabaluev
Copy link
Author

mzabaluev commented May 5, 2022

I've been using go version go1.16.15 linux/amd64.
Tried with the docker container docker.io/library/golang:1.18.1, and the problem did not appear.
Weird for it to manifest this way, but I'm ready to accept that the old go version was the cause of the problem.

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

4 participants