From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6669723628337102848 X-Received: by 2002:a17:906:a18:: with SMTP id w24mr13616054ejf.94.1553510135688; Mon, 25 Mar 2019 03:35:35 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a50:9950:: with SMTP id l16ls1753359edb.3.gmail; Mon, 25 Mar 2019 03:35:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqy7jdFxIwFdLeA1Er4FcUrZ2a3V/C497ik3NlJtogjIMWJDuw3mgonZF0wYVjEkI5srLTSF X-Received: by 2002:a50:ec93:: with SMTP id e19mr16332610edr.169.1553510135169; Mon, 25 Mar 2019 03:35:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553510135; cv=none; d=google.com; s=arc-20160816; b=JPSrV7mdRgiq2QLSoFtqdQbYCErLEs8zBfPbbe9tFNNSSwLnOM4fHaA3exjPTQs5Nb +A7cghyOrr8pkjjFqNFvxnVIUW43uMz9qt6tBzRJ+nqO5jsmAZPrnTFpwidMOJyrl3TY 25qwb3VkQl3Q+4hirGH6EPFpVLUOjwF2sZI+o7rTox9IO6OU8eJZ7SqY4+yw5kiN4UYK dWzqSKwe1s8Q9LKEq+xAaI87EiqqLVIxbmKlSRfCV0Z7vydbnKwKLoY8LnMEF7ZhdnPl OuxsWFnBkEhwX4qiSc3uK5CmiUURyMIsVadUohFcocyGw3DJhZgN+iuUq5oxa+dfwwOM 5f1A== 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:to:subject; bh=WHi4WR71nK3L99nEomNVZ+UTBuZGbRLEv2hjuYrTKRg=; b=hAZu+KDiMDtg+Tj3HZCfTbBNzgvsmA5YhjxjtamlR6XAWzGz25Pj4T5CLnaHRX3/+Q 1XvA2E+WA6DmH+uNuLHZDUyfZexybl+LqlPNbVH/nNZLSz4M98iQlcXztc9aBA1lTMsf cWE65MYVDCtpPglYzASx12KZS0CE2JGZQBXSxZSHVnzR5VcJvr/Zurr1euvYSV9wH9Zq 0PoVpU5iMEn6orGwR/OIHZtQCSjpIx/eUuwvQToEOegKPwLrR1tvy96QQkzID/36eu0l V/8vOrgzPlssD+L46dENgrIza8ApgqllKVLWLEHN6ES6YxCn1mzOme6UG6Y87XxFbqA2 NBlw== 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 a5si880900edn.3.2019.03.25.03.35.35 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 25 Mar 2019 03:35:35 -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.50.164] (d51A48A80.access.telenet.be [81.164.138.128]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id x2PAZYgC017274 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 25 Mar 2019 11:35:34 +0100 Subject: Re: [PATCH v8 0/7] Fix usage of additional apt keys and repos To: Andreas Reichel , isar-users@googlegroups.com References: <20190321151526.12001-1-andreas.reichel.ext@siemens.com> <20190325101939.GA11173@iiotirae> From: "Maxim Yu. Osipov" Organization: ilbers GmbH Message-ID: Date: Mon, 25 Mar 2019 11:35:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: <20190325101939.GA11173@iiotirae> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: HcThV1RQUHQF 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. 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