From: <Cedric_Hombourger@mentor.com>
To: <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [PATCH 1/1] buildchroot: allow unauthenticated sources when installing dependencies
Date: Sun, 4 Feb 2018 09:40:53 +0000 [thread overview]
Message-ID: <20180204094053.86-2-Cedric_Hombourger@mentor.com> (raw)
In-Reply-To: <20180204094053.86-1-Cedric_Hombourger@mentor.com>
From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
While multistrap would accept unauthenticated sources (with a warning),
mk-build-deps (called while building custom packages) would not.
Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
---
meta/recipes-devtools/buildchroot/files/build.sh | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-devtools/buildchroot/files/build.sh b/meta/recipes-devtools/buildchroot/files/build.sh
index 760ebc8..b6075b3 100644
--- a/meta/recipes-devtools/buildchroot/files/build.sh
+++ b/meta/recipes-devtools/buildchroot/files/build.sh
@@ -9,6 +9,9 @@ cd $1
# Install command to be used by mk-build-deps
install_cmd="apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y"
+# Allow unauthenticated feeds
+install_cmd="${install_cmd} --allow-unauthenticated"
+
# Install all build deps
mk-build-deps -t "${install_cmd}" -i -r debian/control
--
2.11.0
next prev parent reply other threads:[~2018-02-04 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 9:40 [PATCH 0/1] buildchroot: allow unauthenticated sources for mk-build-deps Cedric_Hombourger
2018-02-04 9:40 ` Cedric_Hombourger [this message]
2018-02-04 12:04 ` [PATCH 1/1] buildchroot: allow unauthenticated sources when installing dependencies Jan Kiszka
2018-02-04 15:42 ` Hombourger, Cedric
2018-02-05 7:02 ` Jan Kiszka
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=20180204094053.86-2-Cedric_Hombourger@mentor.com \
--to=cedric_hombourger@mentor.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