-
Notifications
You must be signed in to change notification settings - Fork 275
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 from source (make build) failing #246
Comments
Thanks for the report @shinenelson. To be honest, I'm not entirely sure what the issue is here. It has been building fine in CI as well as locally for me. Though blowing away
Can you try building from the PR with that change: https://github.com/terraform-providers/terraform-provider-digitalocean/pull/250 Perhaps related to: golang/go#29278 |
I can confirm that the You can merge #250. I would've approved the changes directly, but there are some other deletions that I can't vouch for, though I know it is not generated manually-by-hand. However, I also noticed a change in the checksum for https://github.com/hashicorp/go-getter, so, that's another reason why I wouldn't want to approve those changes directly. ( I wish there was a mechanism to approve specific code-snippets in a pull request and then some other reviewer(s) could take a look at the rest of the pull request ) regarding golang/go#29278, I would have to ask you with which version of |
Regenerate go.sum (Fixes: #246).
Terraform Version
Terraform v0.12.1-dev
Expected Behavior
What should have happened?
make build
should have completed without any errorsActual Behavior
What actually happened?
Steps to Reproduce
git clone
the repositorymake build
Important Factoids
I'm running
go version go1.12.5 linux/amd64
withTerraform v0.12.1-dev
(built fromhashicorp/terraform@master
). (Not that the issue is related to thego
or theterraform
binaries installed on my system, though).I suspect that the
go.sum
was missed to be updated after there was a terraform release recently (?)The text was updated successfully, but these errors were encountered: