Quoting Maxim Yu. Osipov (2019-04-26 10:41:16)
> Hi Claudius, Andreas,
> 
> @Andreas
> Your input is very welcome at this topic as you were busy with all this 
> APT keys stuff.
> 
> On 4/26/19 9:36 AM, Claudius Heine wrote:
> > Hi Maxim,
> > 
> > Quoting Maxim Yu. Osipov (2019-04-25 20:20:59)
> >> On 4/25/19 3:44 PM, claudius.heine.ext@siemens.com wrote:
> >>> From: Claudius Heine <ch@denx.de>
> >>>
> >>> isar-bootstrap-host only supports bootstrapping Debian root file
> >>> systems. Therefore deactivate any DISTRO_APT_KEYS from other
> >>> distributions.
> >>>
> >>> Signed-off-by: Claudius Heine <ch@denx.de>
> >>> ---
> >>>    meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb | 2 ++
> >>>    1 file changed, 2 insertions(+)
> >>>
> >>> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb b/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb
> >>> index 08b068f..3e96281 100644
> >>> --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb
> >>> +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb
> >>> @@ -12,6 +12,8 @@ DEPLOY_ISAR_BOOTSTRAP = "${DEPLOY_DIR_BOOTSTRAP}/${HOST_DISTRO}-${HOST_ARCH}"
> >>>    ISAR_BOOTSTRAP_LOCK = "${DEPLOY_DIR_BOOTSTRAP}/${HOST_DISTRO}-${HOST_ARCH}.lock"
> >>>    
> >>>    require isar-bootstrap.inc
> >>> +# We only build debian host buildchroot environments
> >>> +DISTRO_APT_KEYS = ""
> >>
> >>   From the first glance this modification limits functionality.
> >> It looks like a hack and I would suggest to avoid this modification.
> > 
> > Well it is a fix and that limited functionality was already present but
> > just implicit, hidden behind some bug and the cleanup just made it
> > appear.
> 
> 
> Could you please point to this hidden, implicit place where mentioned 
> bug persists?

The HOST_DISTRO is set to 'debian-stretch' in
isar-bootstrap-helper.bbclass (included by isar-bootstrap-host.bb)
results in isar-bootstap-host only bootstrapping debian-stretch
repositories, since the 'HOST_DISTRO_APT_SOURCES' (set in
isar-bootstrap.inc) variable only points to 'debian-stretch.list'.

Yes that is quite a mess of spaghetti code, which this patch set is
trying to sort out somewhat and also probably why this patch set now
reveals some hidden bugs or limitations like this.

A patch later in this patch series sets 'HOST_DISTRO' to 'DISTRO' per
default. But that only opens the possibility to use other debian
versions (buster) for buildchroot-host, not allowing non-debian distros.
So the implicit limitation is somewhat loosened with this patch series.

> And bootstrapping itself (function isar_bootsrap in isar-bootstrap.inc) 
> differs only by passing extra '--arch' to target DISTRO_ARCH. Nothing 
> regarding

Well 'isar-bootstrap-host' does contain some issues that needs fixing but
this is not in scope of this patch series, which focuses mainly on
the rootfs creation process and only secondary on the isar-bootstrap*
stuff.

> >> Some time ago I thought about introduction of HOST_DISTRO_APT_KEYS to
> >> avoid confusion between target and host apt keys.
> > 
> > Good idea. But that would be a new feature/improvement.
> 
> Yes. But your series is also improvement, isn't?

With that reasoning you could also say that my patch series should fix
every issue in existence because that might be an 'improvement'.

Fixing the world is not in scope of this patch set.

> I need more arguments for introduction of this limitation.

Again, that limitation is already present. I don't get why you are
often so sure of yourself, especially about code you have not written
or worked with intensively.

Claudius

--
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

           PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                             Keyserver: hkp://pool.sks-keyservers.net