The scala rules repo has a new release which uses HTTP instead, so at least
builds can pass for now with the new hash (no new tagged release). I put in
a PR to update to it https://github.com/apache/incubator-heron/pull/2937

I emailed Lightbend about their cert and hosting on GitHub, so at least
they should be aware of it once the email reaches someone who knows what to
do, so hopefully it will be sorted some time next week, but that may not be
soon enough, and hope driven development isn't great.

On 24 June 2018 at 04:30, Ning Wang <[email protected]> wrote:

> Got it. Thanks~
>
> On Sat, Jun 23, 2018 at 4:28 PM, Oliver Bristow <
> [email protected]>
> wrote:
>
> > There's an issue <https://github.com/bazelbuild/rules_scala/issues/532>
> on
> > the remote repo for it, hopefully they'll fix their cert soon - it
> expired
> > 24 hours ago. Longer term may be for them to get that archive on and from
> > GitHub
> >
> > On 24 June 2018 at 00:13, Ning Wang <[email protected]> wrote:
> >
> > > It seems bazel build is failing (
> > > https://travis-ci.org/apache/incubator-heron/builds/
> > > 395945899?utm_source=github_status&utm_medium=notification)
> > > currently because of the following error:
> > >
> > > (22:58:33) ERROR:
> > > /home/travis/.cache/bazel/_bazel_travis/be6dac4936703c7eedcb4f5cf38cdd
> > > 65/external/io_bazel_rules_scala/scala/scala.bzl:1094:3:
> > > no such package '@scala//': Error downloading
> > > [https://downloads.lightbend.com/scala/2.11.11/scala-2.11.11.tgz] to
> > > /home/travis/.cache/bazel/_bazel_travis/be6dac4936703c7eedcb4f5cf38cdd
> > > 65/external/scala/scala-2.11.11.tgz:
> > > sun.security.validator.ValidatorException: PKIX path validation
> > > failed: java.security.cert.CertPathValidatorException: validity check
> > > failed and referenced by
> > > '//external:io_bazel_rules_scala/dependency/scala/scala_library'
> > >
> > >
> > > The website hosing the library (https://downloads.lightbend.com/scala)
> > > seems to be inaccessible, maybe this is related to the error.
> > >
> > > Is there a replacement we can use?
> > >
> >
>

Reply via email to