From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6665315485307895808 X-Received: by 2002:a2e:9d93:: with SMTP id c19mr572367ljj.25.1551951378812; Thu, 07 Mar 2019 01:36:18 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:5551:: with SMTP id j78ls611749ljb.11.gmail; Thu, 07 Mar 2019 01:36:18 -0800 (PST) X-Google-Smtp-Source: APXvYqybalfUMsLsvxtUVCpWU0MwlY/+bkkvJX6QpQo7aj8GOtS9MbABOF9FnqE0AaE6agBva89D X-Received: by 2002:a2e:9ec6:: with SMTP id h6mr563369ljk.23.1551951378323; Thu, 07 Mar 2019 01:36:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551951378; cv=none; d=google.com; s=arc-20160816; b=EEGa9Dn0dot5pzG7uaABUC7gEw+pEnGcOEX4D4sE6qUW/LsBWvGA4gyfyTDCZ3i2pv RNlvQR+XmkxjG3UJc2CltAWQmkX3T17BCVtHG587TwJjYlHLONnmRd6bHdI5mEEwQYkI L/mJkMXOVIwU3Pz6wo/L8UKs0XAoVDnxXx5R3bNAqcqAbZgJwuzR/BmarHmdtVHX8GU8 pl94DqXiI5ZURsi7q8+kfFY+rKbq8+IBJAfJjyZ1eMR7LhRFh1GkbwgB7ptjOkmuL1eN V0G+iyxCkrixeoiL6h3szh5duyP9qMh56owR2WMtg9XRyLTb66jFhxzLRPcOS+Gg8d62 r5tQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:date:cc:to:from:subject:message-id; bh=j6ESPdvz34ZL8Ekw3LMVVfTP73BU4QBalErPdenC58M=; b=YxwHrhJn7lmH/0CiFoPN4uyfiiqQxWdyMEqZKy4kR+6F0YkfGUZIobzfKqZZvdHSZq Uq7uDIkGSdZnuvZGePyAUG0J1E5KmALvzAHGDOzyELpM5P0sDaKJlARPozNoesMVRda2 63So7uIRHP2ozSyNu3XX2A05cguzZ2acILCQHlEUN5vDaFw5ax5GnGUFh/ymO7ik+QPq XTKpIkzz7j2x3gzyVFBRlKQMQqxxNU7ZrET2vzE8hZDW4VkCdaYMA0vWO76wQZo4i1cQ k7nCR1USW5NJX1izxiW8JoxBy9mPYXp076ddogGI2IcTpVuz735z6gnkBGwERueEmOCL gOew== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id m65si131276lfm.1.2019.03.07.01.36.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Mar 2019 01:36:18 -0800 (PST) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id x279aHCi023744 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 7 Mar 2019 10:36:17 +0100 Received: from linux-ses-ext02.ppmd.siemens.net (linux-ses-ext02.ppmd.siemens.net [139.25.69.232]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x279aHlj019753; Thu, 7 Mar 2019 10:36:17 +0100 Message-ID: Subject: Re: [PATCH v3 5/6] Use all source lists in target root apt From: Claudius Heine To: "[ext] Henning Schild" , "[ext] Andreas J. Reichel" Cc: isar-users@googlegroups.com, "Kiszka, Jan (CT RDA IOT SES-DE)" Date: Thu, 07 Mar 2019 10:36:17 +0100 In-Reply-To: <20190306182754.7cb25c81@md1za8fc.ad001.siemens.net> References: <20190306162619.826-1-andreas.reichel.ext@siemens.com> <20190306162619.826-6-andreas.reichel.ext@siemens.com> <20190306182754.7cb25c81@md1za8fc.ad001.siemens.net> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-TUID: y2trBYWAIv1l Hi, On Wed, 2019-03-06 at 18:27 +0100, [ext] Henning Schild wrote: > Am Wed, 6 Mar 2019 17:26:17 +0100 > schrieb "[ext] Andreas J. Reichel" : > > > From: Andreas Reichel > > > > When we only use isar-apt.list, we cannot add additional > > repositories > > since they are listed in the bootstrap list only. > > As far as i understood some entries in the list are not "enabled" or > fully working before we added the key. The reasoning behind this > change > is somehow gpg ... and that needs to go in here. Because that is the > first violation of "we only update isar-apt". But the violation is so > early in the bootstrap that it is probably ok. I don't think so. That apt-get update is part of the isar-bootstrap- helper, so it will be called late when the image is build. That could cause conflicting versions between the buildchroot and the resulting image. The reason why the general apt-get update is called only in the isar- bootstrap recipe is so that there are no index conflicts between all images that base itself on the same isar-bootstrap rootfs. Claudius > > Henning > > > Signed-off-by: Andreas Reichel > > --- > > meta/classes/isar-bootstrap-helper.bbclass | 5 +---- > > 1 file changed, 1 insertion(+), 4 deletions(-) > > > > diff --git a/meta/classes/isar-bootstrap-helper.bbclass > > b/meta/classes/isar-bootstrap-helper.bbclass index 1f24037..f9e3fba > > 100644 --- a/meta/classes/isar-bootstrap-helper.bbclass > > +++ b/meta/classes/isar-bootstrap-helper.bbclass > > @@ -130,10 +130,7 @@ setup_root_file_system() { > > rm "$ROOTFSDIR/tmp/$kfn" > > done > > fi > > - sudo -E chroot "$ROOTFSDIR" /usr/bin/apt-get update \ > > - -o Dir::Etc::sourcelist="sources.list.d/isar-apt.list" \ > > - -o Dir::Etc::sourceparts="-" \ > > - -o APT::Get::List-Cleanup="0" > > + sudo -E chroot "$ROOTFSDIR" /usr/bin/apt-get update > > # Add multiarch for cross-target > > if [ "${ROOTFS_ARCH}" != "${DISTRO_ARCH}" ]; then > > sudo -E chroot "$ROOTFSDIR" /usr/bin/dpkg --add- > > architecture > > ${DISTRO_ARCH}