From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6690944878080163840 X-Received: by 2002:a7b:c549:: with SMTP id j9mr5976501wmk.114.1558508139261; Tue, 21 May 2019 23:55:39 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a5d:66ce:: with SMTP id k14ls335908wrw.4.gmail; Tue, 21 May 2019 23:55:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqwpOcovNIj4RM9UnQlABMARL9wSY6AIp+tq3k9BplYCyLtA3CvaAWTjck1AnsqyUdb4PpxA X-Received: by 2002:a5d:4cc4:: with SMTP id c4mr41170431wrt.164.1558508138849; Tue, 21 May 2019 23:55:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558508138; cv=none; d=google.com; s=arc-20160816; b=LQpSMXSOlps620srsaxqku58MSzZliWJw8twiPd2+G2YjZ1f5JF0D7ohq5WXLxASkG AZVzE1mB/GY3ABqlAut1fwARQGh+8GlBZBf9dkxTajVpCji4WzuVt5LhMpRgL6TJS7qE uQmesM8pPvAyOgoz49c8iFfdBBOmO2RnKmcgkBVYdD/wquuz1pgaWlfSBiPeOBickviP VH+P76DN4trG4SPjFHqwCB06kHUq+TAX33dQkI20s97pZ/0wtCCwrP2aEige4gBrWxPB UdY6ETpv6LtN7PdsZKEEAyjYSCfMbIrc6fH7UGOe9H9nzuoyEwgmuFeMdqOhoalW+sct 6RMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:organization:from:references:cc:to :subject; bh=+pFC7kw9MRljGnOblq+U987tSxdBBtY9Dr/aHyeABug=; b=CU5MkueHnj9Ews6sS+Km5ro7zmC5Dcfo3RXIKuXhJEpvppHYB84m1xlGlkIVOiUl69 Ue8eQaaTvJ7zYlaoqNVEzfTXX27cHez6B8rjEyGKkDIZDUMrFHrFPWU6Ue0h5AoQGtjx PLuHXqPsUrWGlBDRKyuhbc2cmUZsi7UrsQv9LIZygtBvnnwUwqO+ODw8Q+0u9PQ8Q/G9 A+CJMUDTxhn2InX3/JjK0riRzTeFAC8Lc+7y4cqnT8yapElS7q9mMCgWBIpeIH4C83Eq Iqf71y+SsgFD57ChrL7MjwFhRI1me494qZdVGZDYkQ93ovkgGnVWKpbFvjkeCEXtvQ9e +HiQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of mosipov@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=mosipov@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id i17si414449wrn.5.2019.05.21.23.55.38 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 21 May 2019 23:55:38 -0700 (PDT) Received-SPF: pass (google.com: domain of mosipov@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mosipov@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=mosipov@ilbers.de Received: from [192.168.1.29] (115.165-131-109.adsl-dyn.isp.belgacom.be [109.131.165.115] (may be forged)) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id x4M6tYNi003284 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 22 May 2019 08:55:35 +0200 Subject: Re: [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage To: Claudius Heine , Jan Kiszka , isar-users@googlegroups.com Cc: Claudius Heine References: <20190515101149.22187-1-claudius.heine.ext@siemens.com> <20190515101149.22187-2-claudius.heine.ext@siemens.com> <3745f4ba-e3c9-4d59-22e4-9746c6497f6b@siemens.com> From: "Maxim Yu. Osipov" Organization: ilbers GmbH Message-ID: Date: Wed, 22 May 2019 08:55:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: VFA1NSmsmkoL On 5/22/19 8:37 AM, Claudius Heine wrote: > Hi Jan, > > On 21/05/2019 18.56, Jan Kiszka wrote: >> On 15.05.19 12:11, [ext] claudius.heine.ext@siemens.com wrote: >>> From: Claudius Heine >>> >>> isar-bootstrap-host only supports bootstrapping Debian root file >>> systems. Therefore deactivate any DISTRO_BOOTSTRAP_KEYS from other >>> distributions. >> >> Actually not totally true, as I just realized: What about >> bootstrapping the buildchroot from a custom debian repo that was >> differently signed (e.g. because it is a condensed version of >> upstream)? Seems we do need HOST_DISTRO_BOOTSTRAP_KEYS, right? > > You are right, I haven't considered that case. Well, the next task on > the todo list should probably be to refactor and streamline the > isar-bootstrap, and especially the host bootstrap process and fix those > kind of issues while doing that. > > There are a lot of possible customization options gained if the current > giant bootstrap function would be split up, similar to how the rootfs > system works in the pre-processing patchset. > > Maybe it makes sense to also start renaming "host" and "target" to be > compatible with the gcc nomenclature [1] in that patchset. I am a bit > reluctant to do so, because of the breakage involved. But the further we > wait, to more stuff will break downstream. > > The plan would be to rename all occurrences of "host" to "build" and > "target" to "host". That would lead to the following recipe changes: > "buildchroot-host" -> "buildchroot-build" > "buildchroot-target" -> "buildchroot-host" > "isar-bootstrap-host" -> "isar-bootstrap-build" > "isar-bootstrap-target" -> "isar-bootstrap-host" > I am on the fence of that change. Correctness vs. no-breakage > > Any comments about that? I would prefer to avoid such a renaming taking into account needed efforts and possible confusion for current Isar users. Regards, Maixm. > Cheers, > Claudius > > [1] https://gcc.gnu.org/onlinedocs/gccint/Configure-Terms.html > >> >> Jan >> >>> >>> Signed-off-by: Claudius Heine >>> [Maxim: rebased] >>> Signed-off-by: Maxim Yu. Osipov >>> --- >>>   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 7ee4c61..5501e35 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_BOOTSTRAP_KEYS = "" >>>   inherit isar-bootstrap-helper >>>   do_generate_keyrings[stamp-extra-info] = "${DISTRO}-${DISTRO_ARCH}" >>> >> > -- Maxim Osipov ilbers GmbH Maria-Merian-Str. 8 85521 Ottobrunn Germany +49 (151) 6517 6917 mosipov@ilbers.de http://ilbers.de/ Commercial register Munich, HRB 214197 General Manager: Baurzhan Ismagulov