cmd/go: verifying ...: checksum mismatch #29281
Labels
Comments
|
The difference looks like it's caused by the upgrade. Go 1.11.2: Go 1.11.4: The hash in go.sum is different. The zip files differ: Looking closer at the zip files it's a bunch of odd test fixtures (symlinks) that are not included in the newer one: I guess this is probably good and intentional, but it's a surprising and annoying failure for a minor update... |
Yeah. This is #27093 and the fix was backported to 1.11.4 (#29191). The owner of the I'd close here as WAI. |
|
Right... I didn't find that issue in a search for whatever reason. |
|
Note: if you have a copy of a module with symlinks in your module cache, you likely will need to run |
dhewg
added a commit
to dhewg/packages
that referenced
this issue
Jan 3, 2019
This fixes the exact same build error reported at [0]. Upstream fixed it too, see [1], but I decided to use the minimal patch until a new version is released instead. [0] golang/go#29281 [1] prometheus/statsd_exporter#171 Signed-off-by: Andre Heider <a.heider@gmail.com>
dhewg
added a commit
to dhewg/packages
that referenced
this issue
Jan 4, 2019
This fixes the exact same build error reported at [0]. Upstream fixed it too, see [1], but I decided to use the minimal patch until a new version is released instead. [0] golang/go#29281 [1] prometheus/statsd_exporter#171 Signed-off-by: Andre Heider <a.heider@gmail.com>
|
I had similiar problem inside Dockerfile. I solved it using |
ClaymorePT
pushed a commit
to ClaymorePT/packages
that referenced
this issue
Feb 12, 2019
This fixes the exact same build error reported at [0]. Upstream fixed it too, see [1], but I decided to use the minimal patch until a new version is released instead. [0] golang/go#29281 [1] prometheus/statsd_exporter#171 Signed-off-by: Andre Heider <a.heider@gmail.com>
|
@Koshmaar Any idea what exactly is breaking here? I have run our build in |
thiagoricciardi
pushed a commit
to thiagoricciardi/packages
that referenced
this issue
Apr 3, 2019
This fixes the exact same build error reported at [0]. Upstream fixed it too, see [1], but I decided to use the minimal patch until a new version is released instead. [0] golang/go#29281 [1] prometheus/statsd_exporter#171 Signed-off-by: Andre Heider <a.heider@gmail.com>
foxcpp
added a commit
to foxcpp/go-jmap
that referenced
this issue
May 18, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
go 1.11.4, linux-amd64
Today I updated our CI builders from Go 1.11.2 to 1.11.4. These are Docker images, the upgrade involved destroying the containers and starting new ones, which wiped out the build & module caches. After the upgrade one of my projects fail with this:
Since this is a hash based pseudo version I don't think the source should have changed. I still have the old zip file etc in the build cache on my workstation.
On the build server the zip file is not retained; I guess because it fails the check? So I can't compare.
I'm not sure if this was caused by the upgrade itself, or by something external changing somehow to alter the zip hash, but I'm reporting it as it's unexpected.
The text was updated successfully, but these errors were encountered: