How to depend on Bazel release (not on the tarball from Github of 0.5.4 tag -> checksum changed) #3722
Description
Sometime today it appears that Bazel archives changed their checkums.
bazel_buildifier have had this http_archive for a while:
http_archive(
name = "io_bazel",
sha256 = "71e8b433b5d210867322336a2afcc8d11e832cb5db9e04100e3ac8bba2c9af96",
strip_prefix = "bazel-0.5.4",
urls = [
"http://mirror.bazel.build/github.com/bazelbuild/bazel/archive/0.5.4.tar.gz",
"https://github.com/bazelbuild/bazel/archive/0.5.4.tar.gz",
],
)
See https://github.com/bazelbuild/buildtools/blob/master/WORKSPACE#L30
But now the checksum has changed to "8c33ee6b198359265186f95fbd6aa7ad4e84c3a1fd9b14d22efc3ffb22699f63":
$ wget https://github.com/bazelbuild/bazel/archive/0.5.4.tar.gz && sha256sum 0.5.4.tar.gz
--2017-09-11 15:53:37-- https://github.com/bazelbuild/bazel/archive/0.5.4.tar.gz
Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
Connecting to github.com (github.com)|192.30.253.113|:443...
connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/bazelbuild/bazel/tar.gz/0.5.4 [following]
--2017-09-11 15:53:37-- https://codeload.github.com/bazelbuild/bazel/tar.gz/0.5.4
Resolving codeload.github.com (codeload.github.com)... 192.30.253.120, 192.30.253.121
Connecting to codeload.github.com (codeload.github.com)|192.30.253.120|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 92946464 (89M) [application/x-gzip]
Saving to: ‘0.5.4.tar.gz.1’
100%[==========================================================================================================>] 92,946,464 27.4MB/s in 3.4s
2017-09-11 15:53:40 (26.1 MB/s) - ‘0.5.4.tar.gz.1’ saved [92946464/92946464]
8c33ee6b198359265186f95fbd6aa7ad4e84c3a1fd9b14d22efc3ffb22699f63 0.5.4.tar.gz
This is causing the following failure on bazel build:
Error downloading [http://mirror.bazel.build/github.com/bazelbuild/bazel/archive/0.5.4.tar.gz, https://github.com/bazelbuild/bazel/archive/0.5.4.tar.gz] to <REDACTED>: Checksum was 8c33ee6b198359265186f95fbd6aa7ad4e84c3a1fd9b14d22efc3ffb22699f63 but wanted 71e8b433b5d210867322336a2afcc8d11e832cb5db9e04100e3ac8bba2c9af96
What's going on? Is this expected?