Closed herbygillot closed 4 years ago
Hi. Thanks for the report. We've isolated the change where go.sum seems to have diverged and are reviewing the release process that caused it. In the mean time if you want to build from the tag, you should be able to delete the github.com/hashicorp/vault-plugin-*
lines from go.sum
and rebuild. This will trigger a fresh download of just those dependencies.
Thank you @kalafut. Do you think there'll be a bugfix release of 1.4.0 with a fix for go.sum
imminently, or no?
@herbygillot This turned out to be a fairly subtle error. Our repos are correct, but an error at the start of beta resulted in proxy.golang.org caching the wrong tag content. We'll bump all plugin versions, and these will be part of 1.4.1 (TBD release date, but not immediate, since our repo and the build binaries are correct).
Another interim build fix is to not use the module proxy (set GOPROXY=direct
), or don't use it for the affected dependencies (GOPRIVATE=github.com/hashicorp/vault-plugin*
). In either case, you might need to clean the module cache (go clean -modcache
) first if there are already local copies of these modules.
Thank you for the recommendations, @kalafut, build proceeds as expected.
For some more context, this is for packaging Vault for MacPorts Reference PR here: https://github.com/macports/macports-ports/pull/6818
Closing this and thanks again.
Describe the bug Cannot build Vault from source due to several invalid checksums in go.sum
make dev
fails to build and we see an error like:Seeing a different mismatch error when run each time. Got this error for the following modules:
To Reproduce Steps to reproduce the behavior:
make bootstrap
make dev
Expected behavior Expected build to proceed and complete successfully.
Environment:
vault status
): N/Avault version
): N/AAdditional context Tried building through a VPN to attempt to eliminate the possibility of a MITM; seeing the same results.