From: "Andreas J. Reichel" <andreas.reichel.ext@siemens.com>
To: isar-users@googlegroups.com
Cc: Andreas Reichel <andreas.reichel.ext@siemens.com>
Subject: [PATCH v2 0/1] Make do_rootfs work with proxy settings
Date: Mon, 11 Sep 2017 12:55:57 +0200 [thread overview]
Message-ID: <20170911105558.7308-1-andreas.reichel.ext@siemens.com> (raw)
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
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(-)
--
2.14.1
next reply other threads:[~2017-09-11 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 10:55 Andreas J. Reichel [this message]
2017-09-11 10:55 ` [PATCH v2 1/1] Add proxy support to isar-image-*.bb and buildchroot.bb Andreas J. Reichel
2017-09-15 8:11 ` [PATCH v2 0/1] Make do_rootfs work with proxy settings Henning Schild
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=20170911105558.7308-1-andreas.reichel.ext@siemens.com \
--to=andreas.reichel.ext@siemens.com \
--cc=isar-users@googlegroups.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