From: Henning Schild <henning.schild@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 3/3] isar-bootstrap: Eliminate no-gpg-check option usage
Date: Tue, 27 Nov 2018 10:43:38 +0100 [thread overview]
Message-ID: <20181127104338.4d491830@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20181107160955.23426-4-mosipov@ilbers.de>
There is no problem with disabling gpg in the debootstrap case. Because
debootstrap only works against one repo and we trust this one.
Instead of the original "if [ "${ISAR_USE_CACHED_BASE_REPO}" = "1" ]"
we should depend on the trusted option, which we have available in the
python code in this file. Doing this will enable people to debootstrap
from a trusted repo, no matter if that is the cache.
Henning
Am Wed, 7 Nov 2018 17:09:55 +0100
schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
> Marking repo as trusted eliminates this option usage.
>
> Suggested-by: Henning Schild <henning.schild@siemens.com>
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
> meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc index
> cc1791c..592d042 100644 ---
> a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc +++
> b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc @@ -178,9
> +178,6 @@ isar_bootstrap() { shift
> done
> debootstrap_args="--verbose --variant=minbase --include=locales "
> - if [ "${ISAR_USE_CACHED_BASE_REPO}" = "1" ]; then
> - debootstrap_args="$debootstrap_args --no-check-gpg"
> - fi
> E="${@bb.utils.export_proxies(d)}"
> sudo -E flock "${ISAR_BOOTSTRAP_LOCK}" -c "\
> set -e
next prev parent reply other threads:[~2018-11-27 9:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 16:09 [PATCH 0/3] bitbake upstream update and eliminate " Maxim Yu. Osipov
2018-11-07 16:09 ` [PATCH 1/3] Update bitbake from the upstream Maxim Yu. Osipov
2018-11-07 17:58 ` Henning Schild
2018-11-08 9:08 ` Maxim Yu. Osipov
2018-11-07 16:09 ` [PATCH 2/3] meta: Set LAYERSERIES_* variables Maxim Yu. Osipov
2018-11-07 16:20 ` Jan Kiszka
2018-11-07 16:39 ` Maxim Yu. Osipov
2018-11-07 16:41 ` Jan Kiszka
2018-11-07 17:24 ` Maxim Yu. Osipov
2018-11-07 17:26 ` Jan Kiszka
2018-11-07 16:09 ` [PATCH 3/3] isar-bootstrap: Eliminate no-gpg-check option usage Maxim Yu. Osipov
2018-11-07 17:38 ` Henning Schild
2018-11-08 7:57 ` Maxim Yu. Osipov
2018-11-12 9:30 ` Maxim Yu. Osipov
2018-11-27 9:43 ` Henning Schild [this message]
2018-11-27 10:15 ` Maxim Yu. Osipov
2018-12-03 11:49 ` Maxim Yu. Osipov
2018-12-03 12:52 ` 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=20181127104338.4d491830@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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