Closed dwijnand closed 7 years ago
In https://github.com/scala/scala-jenkins-infra/issues/198#issuecomment-259239859 we've declared the official sha256s for the 2.12.0 artefacts, for instance:
42be98ff9754518fd5c9a942c94ffba2464667a5e95ed4917e4e95565c96bdfe scala-2.12.0.tgz
Which I'm now seeing from London:
$ curl -s http://downloads.lightbend.com/scala/2.12.0/scala-2.12.0.tgz | shasum -a 256 42be98ff9754518fd5c9a942c94ffba2464667a5e95ed4917e4e95565c96bdfe -```
But I'm still seeing different ones on www.scala-lang.org:
$ curl -s https://www.scala-lang.org/files/archive/scala-2.12.0.tgz | shasum -a 256 4eb78f594421bb62e241704c20edd07ecf24954718ea0da3a107f73eb61ef7ca -
So I suspect we might need to replace the ones in EPFL?
https lightbend == http lightbend == http scala-lang
The problem is https scala-lang. Opened https://github.com/scala/scala-lang/issues/531.
In https://github.com/scala/scala-jenkins-infra/issues/198#issuecomment-259239859 we've declared the official sha256s for the 2.12.0 artefacts, for instance:
Which I'm now seeing from London:
But I'm still seeing different ones on www.scala-lang.org:
So I suspect we might need to replace the ones in EPFL?