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

go build error #68

Closed
chinaboard opened this issue Dec 5, 2018 · 13 comments · Fixed by #75
Closed

go build error #68

chinaboard opened this issue Dec 5, 2018 · 13 comments · Fixed by #75

Comments

@chinaboard
Copy link

go: verifying k8s.io/[email protected]+incompatible: checksum mismatch
downloaded: h1:tTI4hRmb1DRMl4fG6Vclfdi6nTM82oIrTT7HfitmxC4=
go.sum: h1:7Zl+OVXn0bobcsi4NEZGdoQDTE9ij1zPMfM21+yqQsM=

chinaboard added a commit to chinaboard/go-discover that referenced this issue Dec 5, 2018
@alvin-huang
Copy link
Contributor

alvin-huang commented Dec 7, 2018

@chinaboard, what go version are you using? I am unable to reproduce this on go version go1.11 darwin/amd64

This relates to golang/go#27925 and golang/go#27153 which was fixed in golang/go@1bca6ce

@chinaboard
Copy link
Author

@alvin-huang
go version go1.11.2 darwin/amd64

and you can see other pr travis build details

@pearkes
Copy link
Contributor

pearkes commented Dec 11, 2018

@u007
Copy link

u007 commented Dec 18, 2018

any workaround?
i found another issue, not sure if this is related:

go: verifying github.com/hashicorp/[email protected]: checksum mismatch
	downloaded: h1:VBj0QYQ0u2MCJzBfeYXGexnAl17GsH1yidnoxCqqD9E=
	go.sum:     h1:9HVkPxOpo+yO93Ah4yrO67d/qh0fbLLWbKqhYjyHq9A=

@szank
Copy link

szank commented Dec 18, 2018

I got exactly the same error as above. At least I am not insane.

@u007
Copy link

u007 commented Dec 18, 2018

ive the fix, if u r using docker, use golang:1.11.1

@blalor
Copy link

blalor commented Dec 19, 2018

This may be related to golang/go#29278 (comment); @u007 with golang 1.11.4, could you try deleting go.sum, running go clean -modcache, and then seeing if your problem disappears?

@u007
Copy link

u007 commented Dec 20, 2018

i tried that, didnt work.
it also happen in my ci deployment via gitlab runner i docker build when i use golang 1.11.4 or higher

@u007
Copy link

u007 commented Dec 20, 2018

just realise, i need to 1st go clean -modcache, then only delete go.sum, then go get , then it works

@u007
Copy link

u007 commented Dec 20, 2018

on my mac it works, but on docker golang:1.11, it does not even with latest go.sum updated

@blalor
Copy link

blalor commented Dec 20, 2018

In my testing I found that for affected dependencies, a go.sum generated on 1.11.3 will generate the checksum error in 1.11.4, and vice versa.

@alvin-huang alvin-huang mentioned this issue Jan 7, 2019
ostromart pushed a commit to ostromart/test-infra that referenced this issue Jan 25, 2019
Previously, we upgraded to the most recent version of kubekins, which
was built on 1/08/2019. We needed >= 1.11 because nomos-operator uses go
mod, which was included in 1.11.
However, due to an issue with go mod detailed at:
hashicorp/go-discover#68
there is a checksum mismatch during build that causes the build of the
nomos operator to fail.

Now, one possible option would be to upgrade the go version of all devs
on this repo past go1.11.4, but from what I can tell that isn't easily
available in glinux packages yet, and so feels rather frictiony and
unpleasant. So, the alternate approach is to use a different version of
kubekins that is recent enough to support go mod (>=1.11) but not so
recent as to have the change that causes the checksum mismatch
(<1.11.4). I found one such version from early december.

As 1.11.4 becomes easily available to devs, we will need to update
go.sum and the kubekins container for this job. This is a
minimum-friction holdover until then.

Change-Id: I58075d596fc2d495cad9bf5af35d0b2c3ae36240
@lidalei
Copy link

lidalei commented Jan 29, 2019

Specifying github.com/hashicorp/go-rootcerts v1.0.0 in go.mod solves my problem in MacOS.

@u007
Copy link

u007 commented Jan 30, 2019

nice, this is new :)

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

Successfully merging a pull request may close this issue.

7 participants