From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: <isar-users@googlegroups.com>,
Baurzhan Ismagulov <ibr@radix50.net>, <chombourger@gmail.com>
Subject: Re: [PATCHv3 8/9] bootstrap: fix debootstrap gpg issue when base-apt is not signed
Date: Thu, 14 Nov 2019 22:45:25 +0100 [thread overview]
Message-ID: <20191114224525.697987ee@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <6825fdd8-f85f-e71c-6f63-ad3ddf1ffc8e@siemens.com>
On Thu, 14 Nov 2019 21:11:23 +0100
Jan Kiszka <jan.kiszka@siemens.com> wrote:
> On 07.11.19 19:56, Henning Schild wrote:
> > From: Henning Schild <henning.schild@siemens.com>
> >
> > DISTRO_BOOTSTRAP_KEYRING will not exist if
> > DISTRO_BOOTSTRAP_KEYFILES is empty. So the debootstrap argument
> > will not work. Simplify the logic to depend on the existance of the
> > keyring-file.
> >
> > Signed-off-by: Henning Schild <henning.schild@siemens.com>
> > ---
> > meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 10
> > +++------- 1 file changed, 3 insertions(+), 7 deletions(-)
> >
> > diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> > b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc index
> > 203a557..b506f30 100644 ---
> > a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc +++
> > b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc @@ -231,14
> > +231,10 @@ isar_bootstrap() { shift
> > done
> > debootstrap_args="--verbose --variant=minbase
> > --include=${DISTRO_BOOTSTRAP_BASE_PACKAGES}"
> > - if [ ! "x${DISTRO_BOOTSTRAP_KEYS}" = "x" ] || \
> > - [ "${ISAR_USE_CACHED_BASE_REPO}" = "1" ]; then
> > + if [ -f "${DISTRO_BOOTSTRAP_KEYRING}" ]; then
> > debootstrap_args="$debootstrap_args
> > --keyring=${DISTRO_BOOTSTRAP_KEYRING}"
> > - fi
> > - if [ "${ISAR_USE_CACHED_BASE_REPO}" = "1" ]; then
> > - if [ -z "${BASE_REPO_KEY}" ] ; then
> > - debootstrap_args="$debootstrap_args --no-check-gpg"
> > - fi
> > + else
> > + debootstrap_args="$debootstrap_args --no-check-gpg"
> > fi
> > E="${@ isar_export_proxies(d)}"
> > export IS_HOST debootstrap_args E
> >
>
> Breaks with non-empty DISTRO_BOOTSTRAP_KEYS and a non-signed base-apt.
Thanks. I will come up with a fix ASAP.
The key problem is that ci_build.sh has too many knobs and does not
test the repo build in all its beauty. In fact this fix should have
come with a test that shows the problem it fixed in the first place.
So i guess my fix will come with another change that simplifies the
build script and reduces the number of knobs. Maybe in the end just one,
fast|full. Where full would do the offline build signed, unsigned, with
other keys and without, and with+out any other variation i find on the
way.
Henning
> Jan
>
next prev parent reply other threads:[~2019-11-14 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 18:55 [PATCHv3 0/9] a few cleanups a bug and a feature Henning Schild
2019-11-07 18:55 ` [PATCHv3 1/9] rootfs: fix incorrect feature name in comment Henning Schild
2019-11-07 18:55 ` [PATCHv3 2/9] base_apt_helper: change variable names to increase readability Henning Schild
2019-11-07 18:55 ` [PATCHv3 3/9] rootfs: rename ROOTFS_INSTALL_COMMAND lock to "isar-apt-lock" Henning Schild
2019-11-07 18:55 ` [PATCHv3 4/9] dpkg-base: remove pointless ";" s at end of line Henning Schild
2019-11-07 18:55 ` [PATCHv3 5/9] dpkg-base: fix indentation from tabs to spaces Henning Schild
2019-11-07 18:56 ` [PATCHv3 6/9] base: implement BB_NO_NETWORK for apt-get Henning Schild
2019-11-07 18:56 ` [PATCHv3 7/9] meta: do not equip rootfss with resolv.conf when BB_NO_NETWORK Henning Schild
2019-11-07 18:56 ` [PATCHv3 8/9] bootstrap: fix debootstrap gpg issue when base-apt is not signed Henning Schild
2019-11-14 20:11 ` Jan Kiszka
2019-11-14 21:45 ` Henning Schild [this message]
2019-11-15 6:07 ` Baurzhan Ismagulov
2019-11-07 18:56 ` [PATCHv3 9/9] meta: dpkg-gbp: remove unneeded proxy export Henning Schild
2019-11-12 16:39 ` [PATCHv3 0/9] a few cleanups a bug and a feature Baurzhan Ismagulov
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=20191114224525.697987ee@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=chombourger@gmail.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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