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

Incompatible checksums on Athens v0.2.0 docker with go.sum generated by Go >= 1.11.4 #1080

Closed
machiel opened this issue Feb 21, 2019 · 4 comments

Comments

@machiel
Copy link

machiel commented Feb 21, 2019

Describe the bug
My go.sum is generated using Go 1.11.5, however the Athens v0.2.0 image I pull from docker is running on Go 1.11.2. There has been a fix in 1.11.4 affecting the way checksums are calculated for modules, so now when pulling my dependencies from Athens there's a checksum mismatch, since Athens still uses the 1.11.2 way.

More about this here: golang/go#27925

Error Message

go: verifying github.com/kylelemons/[email protected]: checksum mismatch
     downloaded: h1:SzHLOWB819X9aUXh2ct6krDIoIujoTsj5J1rDMjkRyo=
     go.sum:     h1:mkl3tvPHIuPaWsLtmHTybJeoVEW7cbePK73Ir8VtruA=

To Reproduce
Add for example kylelemons/go-gypsy to your go.mod file using go 1.11.5, then try building your application using the Athens v0.2.0 docker image running go 1.11.2.

When rebuilding the image with go 1.11.5 everything works as expected.

Expected behavior
To work with go 1.11.4 and higher generated go.sum's. A rebuild of the current docker file should be enough as it relies on 1.11, which is currently an alias for go 1.11.5

Environment (please complete the following information):

  • OS: [e.g. Linux 64bit] Linux 64bit
  • Go version : 1.11.2
  • Buffalo Version : -
  • Proxy version : v0.2.0
  • Storage (fs/mongodb/s3 etc.) : fs
@marwan-at-work
Copy link
Contributor

@machiel thanks for reporting this. The canary version of the docker image uses go1.12-rc which should be compatible with 1.11.5. Feel free to give this a try and let us know if the issue still persists. The next releas v0.3.0 will have 1.12 on by default.

Also, don't forget to delete that module from your storage backend as it was compiled with pre1.11.5 and will need to be re-compiled with the new go mod download command.

Thanks!

@machiel
Copy link
Author

machiel commented Feb 25, 2019

Perfect, thanks! I will await the 0.3.0 release, and in the mean time use the canary version.

Thanks!

@arschles
Copy link
Member

@machiel just FYI, the v0.3.1 release is out. I recommend using that instead of v0.3.0 because it has a fix for the minio storage driver in it

@machiel
Copy link
Author

machiel commented Mar 14, 2019

@arschles great! Thanks for the update! :)

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

No branches or pull requests

3 participants