From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] [meta] Use cached base-apt repo to debootstrap
Date: Fri, 10 Sep 2021 18:43:18 +0200 [thread overview]
Message-ID: <003b9ce4-5169-f1a6-b591-dd840274a13c@siemens.com> (raw)
In-Reply-To: <20210910153008.16499-2-ubely@ilbers.de>
On 10.09.21 17:30, Uladzimir Bely wrote:
> This patch makes local base-apt repo to be created before
> debootstrap task. So, debootstrap is then done from it.
>
> The required packages are downloaded via python-apt and
> reprepro creates debian-like repository from .deb files.
>
> For debian targets host keyring is used while ubuntu/raspbian
> targets use keys specified by DISTRO_BOOTSTRAP_KEYS variable.
>
Reasoning missing here. You have it in the cover letter, but that gets
detached once the commit is merged.
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> meta-isar/conf/distro/ubuntu-focal.conf | 4 +
> meta-isar/conf/distro/ubuntu.public.key | 53 +++++
Do we really need to store the key in-tree? Why now? So far, we fetch
them from remote (if not part of debian key ring). But that is not
needed for Ubuntu IIRC.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-09-10 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 15:30 [PATCH 0/1] Improving base-apt usage Uladzimir Bely
2021-09-10 15:30 ` [PATCH 1/1] [meta] Use cached base-apt repo to debootstrap Uladzimir Bely
2021-09-10 16:43 ` Jan Kiszka [this message]
2021-09-13 9:36 ` [PATCH 0/1] Improving base-apt usage 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=003b9ce4-5169-f1a6-b591-dd840274a13c@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@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