Re: [PATCH v2 0/1] Make do_rootfs work with proxy settings

[Henning Schild <henning.schild@siemens.com>]

Am Mon, 11 Sep 2017 12:55:57 +0200
schrieb "[ext] Andreas J. Reichel" <andreas.reichel.ext@siemens.com>:

> From: Andreas Reichel <andreas.reichel.ext@siemens.com>
> 
> Regarding issue #19 on github: Consider testing with http_proxy
> 
> Diff to 1st version:
> * Remove comments before python inline code.
> * Remove -E option from sudo in dev-tools/buildchroot at configure
>   step, since a configure step should not download things

Sorry, my comment for the buildchroot was wrong. We do have an
"apt-get update" in the configure.sh for buildchroot, and for that to
work we need the proxies configured in there.
In the image the configure.sh should not get access to the internet, in
the buildchroot it is fine and currently required. So please add the -E
back in.

Henning

> If isar is built behind a proxy, multistrap fails to communicate
> with the repository.
> 
> Usually, the user's environment has *_proxy variables set to configure
> tools. However, these values are not passed correctly. With this
> patch, multistrap is able to make use of the users proxy config.
> 
> The fix is strongly oriented on how the internal fetcher deals with
> this problem.
> 
> Signed-off-by: Andreas Reichel <andreas.reichel.ext@siemens.com>
> 
> Andreas Reichel (1):
>   Add proxy support to isar-image-*.bb and buildchroot.bb
> 
>  meta-isar/recipes-core/images/isar-image-base.bb | 5 ++++-
>  meta/recipes-devtools/buildchroot/buildchroot.bb | 4 +++-
>  scripts/isar-buildenv-internal                   | 2 +-
>  3 files changed, 8 insertions(+), 3 deletions(-)
>