From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6669723628337102848 X-Received: by 2002:a2e:4504:: with SMTP id s4mr12860074lja.150.1553513430906; Mon, 25 Mar 2019 04:30:30 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:9e17:: with SMTP id e23ls595138ljk.12.gmail; Mon, 25 Mar 2019 04:30:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqxGDuC8ne4yicOsUXJOKkETcUEZJeQSllophUcKqU0tem0NZ47SSlu6vmleG+9EGV205Qjp X-Received: by 2002:a2e:2f06:: with SMTP id v6mr12918404ljv.139.1553513430429; Mon, 25 Mar 2019 04:30:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553513430; cv=none; d=google.com; s=arc-20160816; b=y3NuyhhNtv+Xuu6FjMw2V52JVWfdYuDZRdN2SVu10lIcNNM/YLo98OpAXDOSZijEEb jzmF2iy3tyPkMgf6YngzG7R45kcyp53a1qis1iTPCEhzGB9lzYb+3ktQpnwc7rULl3i7 QgSYZFYwJtVEdlAjv2OoWM13Z3ovHKv2I3HxPSwmHjV9ZqO9tLGqKPY9Odx/DOKhIuCg +QTsMvlw2fMgPEd+TU9gnixLqgqbhEtqMtdipvGG60SJvMY7ZGDQ+ikUFtzY5gPArQJ6 OzC/MAQQnfvVNgYfko5HOLVSNplvw5+gw2WPeCXqSdWDmGtQMzi07/U1/tGNSkRqXkrY C+kA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:content-description :mime-version:references:message-id:subject:cc:to:from:date; bh=5PGNucfMTe/aivV06bE+viYA6wuPAVOwJCdb7fLrxS4=; b=W0at9yz1b6mFdbFuE3j2/6Blle/Ww2RwblwldcZiPygG3tSmkpB2HYpNke/6RUaWPt BMMcP0KuK8YJtreG93qOlhf5LBASSJOtndYa5peESVFwSp6fdD+jAjfH7bcKoGdiZNmH A4aMnUmvq0qXvMN61pqTgyFIt+joPf/G9dvN3hFZ1tekssbdBYHWwsTqIbgAJjdVBs86 KmWBCB+ppzzw0bT4byZ/RNPyaGuB84e4CEYJGPR5TxPyKtRwPobVwNTqJTekwvZ4UxRA TbuY7LtOxt1dpZzVVd77OZjonJuyQjYnpV5hXmHxLz74/ga13osO7a7yRaYj+saiI/Ge kndA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of andreas.reichel.ext@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=andreas.reichel.ext@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id a22si100661lfl.3.2019.03.25.04.30.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Mar 2019 04:30:30 -0700 (PDT) Received-SPF: pass (google.com: domain of andreas.reichel.ext@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of andreas.reichel.ext@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=andreas.reichel.ext@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id x2PBUTA0025329 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 25 Mar 2019 12:30:29 +0100 Received: from iiotirae (golem.ppmd.siemens.net [139.25.69.17]) by mail2.sbs.de (8.15.2/8.15.2) with SMTP id x2PBUTaO021611; Mon, 25 Mar 2019 12:30:29 +0100 Date: Mon, 25 Mar 2019 12:28:35 +0100 From: Andreas Reichel To: "Maxim Yu. Osipov" Cc: isar-users@googlegroups.com Subject: Re: [PATCH v8 0/7] Fix usage of additional apt keys and repos Message-ID: <20190325112835.GA4930@iiotirae> References: <20190321151526.12001-1-andreas.reichel.ext@siemens.com> <20190325101939.GA11173@iiotirae> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: message Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) X-TUID: c/IYqrLkN9PV On Mon, Mar 25, 2019 at 11:35:33AM +0100, Maxim Yu. Osipov wrote: > On 3/25/19 11:19 AM, Andreas Reichel wrote: > > > Not working yet: > > > qemuarm64-stretch with BASE_REPO_KEY and do_cache_base_repo > > > > > > | gpgme gave error GPGME:54: Unusable secret key > > > > > > I have created a keypair inside the build container and exported the > > > public key to a file "blabla.key". Then I set > > > > > > BASE_REPO_KEY = "file:///build/blabla.key" > > > > > > Any idea? > > > > > There was actually no problem anymore. The KEY had to be in the gpg key > > ring which was expected by the normal user in /tmp/tmpb6et85_1/.gnupg, not > > /home/builder/.gnupg. After readding the secrect key for the normal > > build user, it worked. > > > > I have just triggered a CI build on ilbers-ci. After that is green, > > you can apply my patchset. > > Just FYI: > > I test patchsets independently before applying them into the tree. > > Meanwhile I encourage people to use CI build before sending patchset to the > mailing list (if this is not RFC) to avoid unnecessary patchsets iterations. > > > The automated CI test procedure consists actually from the two steps: > > 1) "fast" CI build/smoke test (by passing the key '-f' to corresponding > ci_build.sh and vm_smoke_test scripts) - it tests cross compilation for > three supported stretch QEMU targets and one de0-nano-soc target. > > 2) "standard" CI build - it tests native build for the almost full set > of QEMU targets. > > > If the new feature is added to the ISAR it's always desirable to add > corresponding test case into the CI. > In this case it means we/I should add a test case where the docker upstream repo is added and an image with docker is built. Let's say it is a generalization of an existing feature :) Regards, Andreas > > Regards, > Maxim. > > > > > Regards > > Andreas > > > > > Signed-off-by: Andreas Reichel > > > > > > Andreas Reichel (7): > > > 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 keyrings > > > If we use a custom keyring debootstrap may fall to https > > > raspbian-jessie: Use DISTRO_BOOTSTRAP_KEYS > > > docs: Update user_manual.md > > > > > > doc/user_manual.md | 7 +- > > > meta-isar/conf/distro/raspbian-jessie.conf | 2 +- > > > .../conf/multiconfig/qemuamd64-buster.conf | 1 - > > > .../conf/multiconfig/qemuamd64-jessie.conf | 1 - > > > meta/conf/bitbake.conf | 1 + > > > .../isar-bootstrap/isar-bootstrap-host.bb | 4 +- > > > .../isar-bootstrap/isar-bootstrap-target.bb | 4 +- > > > .../isar-bootstrap/isar-bootstrap.inc | 95 +++++++++++++------ > > > 8 files changed, 79 insertions(+), 36 deletions(-) > > > > > > -- > > > 2.21.0 > > > > > > > > -- > 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 -- Andreas Reichel Dipl.-Phys. (Univ.) Software Consultant Andreas.Reichel@tngtech.com, +49-174-3180074 TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082