[OE-core] [PATCH 1/2] oe-init-build-env: allow GIT_SSL_CAINFO from external environment
Paul Eggleton
paul.eggleton at linux.intel.com
Tue May 24 10:23:53 UTC 2016
On Tue, 24 May 2016 08:25:58 Richard Purdie wrote:
> On Tue, 2016-05-24 at 14:40 +1200, Paul Eggleton wrote:
> > buildtools-tarball sets GIT_SSL_CAINFO so that the included
> > ca-certificates can be used by git; that can't work however unless
> > the GIT_SSL_CAINFO is still set in the environment in which git gets
> > run by the fetcher, so allow it through from the external
> > environment.
> >
> > Fixes [YOCTO #9666].
> >
> > Signed-off-by: Paul Eggleton <paul.eggleton at linux.intel.com>
> > ---
> >
> > scripts/oe-buildenv-internal | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Would it make more sense to just list this in
> lib/bb/fetch2/__init__.py:runfetchcmd() instead?
Actually it's already included in that list, but it wasn't working in the eSDK
I was testing which I hadn't noticed was built before bitbake rev
20ad1ea87712d042bd5d89ce1957793f7ff71da0 where we now also look at BB_ORIGENV,
so it appears neither of these patches are even needed. We may need to
backport that change to krogoth to fix this problem there though.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
More information about the Openembedded-core
mailing list