public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, Claudius Heine <ch@denx.de>,
	"Maxim Yu. Osipov" <mosipov@ilbers.de>,
	isar-users@googlegroups.com
Subject: Re: [PATCH v4 1/9] isar-bootstrap-host: disable DISTRO_APT_KEYS usage
Date: Tue, 14 May 2019 13:35:07 +0200	[thread overview]
Message-ID: <53f9a49a-2870-db37-720d-8a6f5bc2ac58@siemens.com> (raw)
In-Reply-To: <2a7d8373-b2a7-5530-98bc-c0c0e6986ed8@siemens.com>

small errata:

On 14/05/2019 13.32, Claudius Heine wrote:

>>
>> OTOH, I don't get the problem yet from just reading the commit 
>> message: Wasn't DISTRO_APT_KEYS designed to be a superset of all 
>> needed keys?
> 
> DISTRO_APT_KEYS is only used for distros that aren't Debian, because 
> debootstrap uses the keys of the host distro (Debian) per default.

DISTRO_APT_KEYS was renamed by Andreas new patchset and is now called 
DISTRO_BOOTSTRAP_KEYS.

> THIRD_PARTY_APT_KEYS is for the keys of other third party repositories 
> that are not used to bootstrap from.
> 
> We currently only support raspbian as a non-debian distribution and 
> before this patchset only 'debian-stretch' as buildchroot-host.
> After this patchset we support all Debian versions we currently support 
> for the target for the buildchroot-host as well. Since raspbian does not 
> supply packages that can be used for a buildchroot-host environment, it 
> makes sense to just use the Debian host keys for bootstrapping the 
> buildchroot-host rootfs in general.
> 
> If at one point we want to support other non-debian apt/dpkg based 
> distributions like ubuntu, that can be used for the target as well as 
> the host root file system, then it makes sense to allow specifying 
> additional keys for the buildchroot-host as well. Until that time 
> however this fix is enough to go forward.
> 
> regards,
> Claudius
> 
>> We are appending raspbian to it when using that distro. So, we are at 
>> least missing the reasoning here why that model didn't work and cannot 
>> be made working for the host/target case. And then we can refer to 
>> that when introducing split key sets.
>>
>> Thanks,
>> Jan
>>
>>
> 

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  reply	other threads:[~2019-05-14 11:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 13:44 [PATCH v4 0/9] Cleanup rootfs creation claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 1/9] isar-bootstrap-host: disable DISTRO_APT_KEYS usage claudius.heine.ext
2019-04-25 18:20   ` Maxim Yu. Osipov
2019-04-26  7:36     ` Claudius Heine
2019-04-26  8:41       ` Maxim Yu. Osipov
2019-04-26 10:39         ` Claudius Heine
2019-04-26 10:45           ` Claudius Heine
2019-04-26 11:22             ` Maxim Yu. Osipov
2019-04-26 11:47               ` Jan Kiszka
2019-04-30  9:34         ` Andreas Reichel
2019-04-30 13:30           ` Maxim Yu. Osipov
2019-04-30 15:22             ` Andreas Reichel
2019-04-30 15:30               ` Jan Kiszka
2019-04-30 15:46               ` Maxim Yu. Osipov
2019-05-02 12:14                 ` Andreas Reichel
2019-04-26 11:31       ` Jan Kiszka
2019-04-26 11:50         ` Jan Kiszka
2019-05-14  9:22           ` Fwd: " Maxim Yu. Osipov
2019-05-14 11:32           ` Claudius Heine
2019-05-14 11:35             ` Claudius Heine [this message]
2019-04-25 13:44 ` [PATCH v4 2/9] isar-bootstrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 3/9] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 4/9] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 5/9] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 6/9] bitbake.conf: remove unneeded and differently used variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 7/9] image.bbclass: make IMAGE_ROOTFS overwritable claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 8/9] bitbake.conf: set default QEMU_ARCH variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 9/9] buildchroot/configscript: make creation of builder uid/gid idempotent claudius.heine.ext

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=53f9a49a-2870-db37-720d-8a6f5bc2ac58@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=ch@denx.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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