-
Notifications
You must be signed in to change notification settings - Fork 546
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
Build fails because of coreos/etcd checksum mismatch #1032
Comments
This was changed for some reason in b4f2c08 to an invalid value. This patch restores the previous value, which is the currently-valid value too. Fixes: operator-framework#1032 Signed-off-by: Stephen Kitt <skitt@redhat.com>
This was changed for some reason in b4f2c08 to an invalid value. This patch restores the previous value, which should never change. Closes: operator-framework#1032 Signed-off-by: Stephen Kitt <skitt@redhat.com>
I'm not sure why you're seeing a checksum mismatch, deleting go.sum and revendoring gives me the same checksum that's in master - but I suspect your environment is not using go modules, which we rely on for building. What version of |
I ran into this with 1.11, and upgraded to 1.13 to get its improved module support. #1038 fixes the Makefile, I’ll check again what happens with 1.11... It’s still weird that the checksum changed, or is that expected with the switch to modules? There are a number of other projects which still have the old checksum in their |
Bug Report
What did you do?
I cloned the OLM repository, and tried running
make
inside it.What did you expect to see?
I expected the tests to pass and the build to succeed.
What did you see instead? Under which circumstances?
Environment
d6056dd
KIND
Possible Solution
Updating the checksum in
go.mod
, but I haven’t figured out why it’s changed...Additional context
N/A.
The text was updated successfully, but these errors were encountered: