Updated checksums for LBT

[ViralBShah]

No description provided.

[ViralBShah]

yikes - why is whitespace stuck?

[DilumAluthge]

We temporarily had a configuration error in Buildkite. Fixed now. I've restarted the Buildkite job.

[Sacha0]

We are seeing build failures on 1.7-RC3 for lack of this patch, e.g. locally on a fresh 1.7-RC3 checkout:

julia7 % make -f contrib/refresh_checksums.mk blastrampoline
/Library/Developer/CommandLineTools/usr/bin/make -s -C "/Users/sacha/pkg/julia7/deps" USE_BINARYBUILDER=0 FC_VERSION=7.0.0 BLASTRAMPOLINE_BB_TRIPLET= LLVM_ASSERTIONS=0 DEPS_GIT=0 checksum-blastrampoline
===============================================================================
  ERROR: sha512 checksum failure on blastrampoline-23de7a09bf354fe6f655c457bab5bf47fdd2486d.tar.gz, should be:
      7b7dbb101cf05ac833a8e5b09f1eec8eb99f0caafbe80075751a5f7e0bfe03a3
      b19d11d3507dadd13f503cfa9fc1a6cd53f3461af7d5afb39ca385a0ee26120b
  But `sha512sum /Users/sacha/pkg/julia7/deps/srccache/blastrampoline-23de7a09bf354fe6f655c457bab5bf47fdd2486d.tar.gz | awk '{ print $1; }'` results in:
      1c2558bab0aeaa76e7094d8a6a9798c95f2cf4efe2960640b70f1fd752f3dfb7
      3813d9de93b539426376571febaab22ac22c2f903ccdf3296c7b067af92fecdc
  This can happen due to bad downloads or network proxies, please check your
  network proxy/firewall settings and delete
  /Users/sacha/pkg/julia7/deps/srccache/blastrampoline-23de7a09bf354fe6f655c457bab5bf47fdd2486d.tar.gz
  to force a redownload when you are ready
===============================================================================
make[1]: *** [checksum-blastrampoline] Error 2
make: [checksum-blastrampoline-src-] Error 2 (ignored)

so I have marked it for backport to 1.7.

[nalimilan]

Any idea why these checksums changed upstream? It's not ideal to have retroactive changes like that, it means that previous releases won't build if they download blastrampoline (like in Fedora).

[ViralBShah]

I don't remember now. :-(

IIRC, we recently fixed a bug in the checksums script and the buggy version may have caused this. This is the first release with LBT though, so it shouldn't affect older releases, right?

[DilumAluthge]

We did fix some bugs in the checksums script, but as far as I can tell, none of those changes should have caused different checksum values to be computed.