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

Source code build fails #583

Closed
karuppiah7890 opened this issue Nov 8, 2018 · 2 comments · Fixed by #584
Closed

Source code build fails #583

karuppiah7890 opened this issue Nov 8, 2018 · 2 comments · Fixed by #584

Comments

@karuppiah7890
Copy link
Contributor

karuppiah7890 commented Nov 8, 2018

Submission type

  • Bug report

Environment

Mac OS 10.13.6
go version go1.11.2 darwin/amd64

Stolon version

commit 979c44c1bfabea176683eeb79a42c89f13e6c890

Bug Report

I ran this to build code

./build

Expected behaviour you didn't see

Binaries in the bin directory

Unexpected behaviour you saw

Saw this error

go: verifying k8s.io/[email protected]: checksum mismatch
       downloaded: h1:wyGRYm7YXAgRnpBSiznWwhhMGOKpmp4Da6SFBYfRGsE=
	go.sum:     h1:f3mpKWzvfekpRsYqKI3PgKF1hrj05XUZR7iP6aNk35Y=

Steps to reproduce the problem

Clone the code. Git checkout to commit 979c44c1bfabea176683eeb79a42c89f13e6c890. Run ./build

@sgotti
Copy link
Member

sgotti commented Nov 8, 2018

Thanks for the report. There was a bug in go1.11 which I used to generate and publish the go.sum file and go 1.11.2 fixed it (golang/go#27153) causing this mismatch.

I created #584 to update the go.sum file using go 1.11.2.

@karuppiah7890
Copy link
Contributor Author

Yes, I checked that bug while trying to make the build work by doing different things, but couldn't make it work. So I just created the above issue. But for me the problem still exists - #585 . I think I saw a similar error before when I was trying to fix the above issue

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.

2 participants