From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6669723628337102848 X-Received: by 2002:aa7:cfc3:: with SMTP id r3mr6300edy.1.1555073550277; Fri, 12 Apr 2019 05:52:30 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a50:f401:: with SMTP id r1ls1541114edm.8.gmail; Fri, 12 Apr 2019 05:52:29 -0700 (PDT) X-Google-Smtp-Source: APXvYqwp1C22fLY39hfZ8coHrglugnJnZmk7kWTKVUqeIb86nRTuMvbVv3feAbnIhgVaAHRrJVkJ X-Received: by 2002:a50:b104:: with SMTP id k4mr6193061edd.12.1555073549787; Fri, 12 Apr 2019 05:52:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555073549; cv=none; d=google.com; s=arc-20160816; b=SRM3VATSc2rBXWlzTkNKT77rF0sCLYJcEryM+IsEo3GyYHIdIlfMDSvZfDG7GmyHaJ ls6SrA5mNvF6h25h8HqJQr1KK/8LfBIEN1r0zPJM71Sg7QIkTRe9GgzXitg5pYHe7qrG F43lt5o3ikcl0Q8H0yP9GJeE/qYpfth449t7AByKlgwGALseiYIznl0SflLq2tMDDPK3 hqktjIG8DZ5FDreTHq2Mq89bhGYWwGnzzuQhEcRgQ29EI5ziyWsD2jf0mENmTk6IWbVO LDEt+tE+eExbrurXUWb0kmMVfzihOaKbsBLIryeEbjrQQcXfpCSbq0n8gsvX+plsAD+l WL6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=4qW4k0Zhb2ZZMt5LiDT1qzfyTC3nt/EVGHEZLNzLgBk=; b=SKQ1kLvPwsSaz2LucVIFbfQ7OEKr/ZaaBt5VsdSnb+T5TYrgCpn1i7vABfAtJDV302 ALljlDC4+82PQDTVOPIZdqscjxSaEY4h7O6fAFhqPRcBf9joYzutZYDLl86QV6AS+C2p ocGQceMxLCKkRu/9mk85xdNuneEc+NwNKRNMazJot78bkl3dEK172DC3C9wtPZyochOM 1ql9Ig+V4FW4mCQlXMF3X8bH4jWxV9frhVOcam4adUErZk/L/SAejMkpMt9yeMwtCAGW D4NBtPT6aj5+Sv85mank2KiL8AzQ9pmPHhxUNI2rVM/ogySQ31XFyRjC/3wA4Mb77rln gNaw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id a38si2113318edd.0.2019.04.12.05.52.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Apr 2019 05:52:29 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x3CCqTee010496 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 12 Apr 2019 14:52:29 +0200 Received: from md1za8fc.ad001.siemens.net ([139.25.68.211]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x3CCqTZw026851; Fri, 12 Apr 2019 14:52:29 +0200 Date: Fri, 12 Apr 2019 14:52:28 +0200 From: Henning Schild To: "Maxim Yu. Osipov" Cc: Andreas Reichel , Subject: Re: [PATCH v8 0/7] Fix usage of additional apt keys and repos Message-ID: <20190412145228.333bc3f5@md1za8fc.ad001.siemens.net> In-Reply-To: References: <20190321151526.12001-1-andreas.reichel.ext@siemens.com> <20190325101939.GA11173@iiotirae> <20190325112835.GA4930@iiotirae> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: O18MVK4/eJOU Am Mon, 25 Mar 2019 12:39:01 +0100 schrieb "Maxim Yu. Osipov" : > On 3/25/19 12:28 PM, Andreas Reichel wrote: > > 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. > > I hope that your feature is generic enough to add some simpler (not > docker) third party repo for testing purposes. On the repo level they probably all are equally "simple". However, i would not trust the docker one to work repeatedly and stable for all suites/arches. I know it provides broken init scripts, that suggest they do not do much more than "works for me" testing. This could be a better example: https://wiki.x2go.org/doku.php/wiki:repositories:debian Henning > Regards, > Maxim. > > > > 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 > > > >