From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "[ext] Andreas J. Reichel" <andreas.reichel.ext@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v5 0/5] Fix usage of additional apt keys and repos
Date: Mon, 18 Mar 2019 14:47:17 +0100 [thread overview]
Message-ID: <7b35069cd28fc37bfc47257a2d236d916c70b7df.camel@siemens.com> (raw)
In-Reply-To: <20190318133205.29705-1-andreas.reichel.ext@siemens.com>
Hi Andi,
On Mon, 2019-03-18 at 14:31 +0100, [ext] Andreas J. Reichel wrote:
> From: Andreas Reichel <andreas.reichel.ext@siemens.com>
>
> Diff to v4:
> * don't remove keyring deployed to target rootfs
> so that one can do updates later
> * keys are temporarily held in WORKDIR/aptkeys, not
> TMPDIR/aptkeys
> * variable renamed from APTKEYTMPDIR to APT_KEYS_DIR
>
> Unchanged with reason:
> * function for retreiving override for https is unchanged,
> since renaming this to one global function
> "get_distro_overrides" is better done in a separate patch.
> This patch should concentrate on getting things finally
> working, before changing too much code that is more or less
> a beautification.
> * (Other comments on mailing list)
> * HAVE_CUSTOM_APT_KEYS is used in patch 4, but introduced in
> patch 5, which is okay here, because we check if it exists...
>
> What this series does:
> * Enable/fix possibility of additional apt repos
> * Enable/fix handling of additional apt keys
> * Deduplicate some code
LGTM
>
> Signed-off-by: Andreas Reichel <andreas.reichel.ext@siemens.com>
Acked-by: Claudius Heine <ch@denx.de>
>
> Andreas Reichel (5):
> Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS"
> Remove duplicate code from apt-keyring generation
> Fix fetched key location in apt-keyring generator
> Use apt-key to generate apt-keyring
> If we use a custom keyring debootstrap may fall to https
>
> .../conf/multiconfig/qemuamd64-buster.conf | 1 -
> .../conf/multiconfig/qemuamd64-jessie.conf | 1 -
> meta/classes/isar-bootstrap-helper.bbclass | 2 +
> meta/conf/bitbake.conf | 1 +
> .../isar-bootstrap/isar-bootstrap.inc | 62 +++++++++++++--
> ----
> 5 files changed, 47 insertions(+), 20 deletions(-)
>
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-03-18 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 13:31 Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 1/5] Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS" Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 2/5] Remove duplicate code from apt-keyring generation Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 3/5] Fix fetched key location in apt-keyring generator Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 4/5] Use apt-key to generate apt-keyring Andreas J. Reichel
2019-03-18 13:32 ` [PATCH v5 5/5] If we use a custom keyring debootstrap may fall to https Andreas J. Reichel
2019-03-18 13:47 ` Claudius Heine [this message]
2019-03-18 15:13 ` [PATCH v5 0/5] Fix usage of additional apt keys and repos Maxim Yu. Osipov
2019-03-19 9:47 ` Andreas Reichel
2019-03-19 10:16 ` Andreas Reichel
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=7b35069cd28fc37bfc47257a2d236d916c70b7df.camel@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=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