public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][dunfell 07/12] go: Use dl.google.com for SRC_URI
Date: Fri, 30 Apr 2021 16:58:51 +0100	[thread overview]
Message-ID: <27e726bde79ae49abcb12b0d028b8d38d2cf77a8.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAOSpxdZpcGXGP_yFzCaneJHwQ+B9_J36c_xoYEeoCKhEigk3FQ@mail.gmail.com>

On Fri, 2021-04-30 at 05:53 -1000, Steve Sakoman wrote:
> On Fri, Apr 30, 2021 at 5:44 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 
> > On Fri, 2021-04-30 at 05:33 -1000, Steve Sakoman wrote:
> > > From: Khem Raj <raj.khem@gmail.com>
> > > 
> > > golang.org/dl is resolving to this anyway
> > > 
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > (cherry picked from commit 8470e38ac1d9f9bb6d8a4ee43724af452d080057)
> > > Signed-off-by: Steve Sakoman <steve@sakoman.com>
> > > ---
> > >  meta/recipes-devtools/go/go-common.inc | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/meta/recipes-devtools/go/go-common.inc b/meta/recipes-devtools/go/go-common.inc
> > > index 39a681a712..c368b95b69 100644
> > > --- a/meta/recipes-devtools/go/go-common.inc
> > > +++ b/meta/recipes-devtools/go/go-common.inc
> > > @@ -14,7 +14,7 @@ LICENSE = "BSD-3-Clause"
> > > 
> > > 
> > > 
> > > 
> > >  inherit goarch
> > > 
> > > 
> > > 
> > > 
> > > -SRC_URI = "https://golang.org/dl/go${PV}.src.tar.gz;name=main"
> > > +SRC_URI = "https://dl.google.com/go/go${PV}.src.tar.gz;name=main"
> > >  S = "${WORKDIR}/go"
> > >  B = "${S}"
> > >  UPSTREAM_CHECK_REGEX = "(?P<pver>\d+(\.\d+)+)\.src\.tar"
> > 
> > 
> > We are seeing autobuilder issues with some go downloads which we may want to
> > resolve before merging this.
> 
> OK, haven't seen those with dunfell but will drop this patch from the
> pull request and monitor master for resolution.

It is this and the https change earlier in your series. It could just be
some corrupt files in DL_DIR but I'd be happier we get this resolved there first.

Cheers,

Richard


  reply	other threads:[~2021-04-30 15:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 15:33 [OE-core][dunfell 00/12] Patch review Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 01/12] Binutils: Fix CVE-2021-20197 Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 02/12] cve-update-db-native: skip on empty cpe23Uri Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 03/12] oeqa/selftest/bblayers: Add test case for bitbake-layers layerindex-show-depends Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 04/12] oeqa: tear down oeqa decorators if one of them raises an exception in setup Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 05/12] meta/lib/oeqa/core/tests/cases/timeout.py: add a testcase for the previous fix Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 06/12] go: update SRC_URI to use https protocol Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 07/12] go: Use dl.google.com for SRC_URI Steve Sakoman
2021-04-30 15:44   ` Richard Purdie
2021-04-30 15:53     ` Steve Sakoman
2021-04-30 15:58       ` Richard Purdie [this message]
2021-04-30 16:03         ` Khem Raj
2021-04-30 15:33 ` [OE-core][dunfell 08/12] kernel.bbclass: Configuration for environment with HOSTCXX Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 09/12] yocto-check-layer: Avoid bug when iterating and autoadding dependencies Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 10/12] linux-firmware: Package RSI 911x WiFi firmware Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 11/12] license_image.bbclass: Detect broken symlinks Steve Sakoman
2021-04-30 15:33 ` [OE-core][dunfell 12/12] license_image.bbclass: Fix symlink to generic license files Steve Sakoman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27e726bde79ae49abcb12b0d028b8d38d2cf77a8.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox