From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517546778931232768 X-Received: by 10.80.202.11 with SMTP id d11mr13215165edi.9.1517485233823; Thu, 01 Feb 2018 03:40:33 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.182.240 with SMTP id f45ls4290216ede.1.gmail; Thu, 01 Feb 2018 03:40:33 -0800 (PST) X-Google-Smtp-Source: AH8x224MExlqjDbJ8zD4I5i6y6Yu2NN/abOptRY35IIXLU+Ski/Ub9lYbVzPQ0qArbjRLX4OqXbz X-Received: by 10.80.204.74 with SMTP id n10mr1020658edi.12.1517485233074; Thu, 01 Feb 2018 03:40:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517485233; cv=none; d=google.com; s=arc-20160816; b=gKGoUCh2I7N8DJRddObMbnYTrG9i8hH6GJMma4NZbO4ujKqf9iJpGbEV5SLsEnINvv 2FtgaH5MuHeTFNsvlMqMwOn0s7kxh33BvYnbSaA60N/Lti7rUc6Df/o+312VAlTCj5Ul Df0DpGs7/6KnRmHUEFqPUiufkQ0KGFDYmaNwM5iTRKNx/P/xG76J3TL708Cg+339V6nb 2cKjMkQdPc87zAC4VpVq/4kAWcOEVYRjyzsG45DAlbz7gV60D6whU8cd5IoYVcu4BCBp 0tt8Cz20pk7km+FCpyqa7qfCjzSrIn3bcpaslgkZHHGkdaSqZkTfrONtK/turugbPd2i sCfw== 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:from:references:to:subject :arc-authentication-results; bh=SF1bb46UibV2kRO+3a02RrRIlaVNLBpmU6+kjc0lnV8=; b=uKQKG1wJshSCWm+Ewwj9FgVoVZKp4f8HlVvsj5OM/wl17aAzZlhBbuXySLgriZcWk/ jR4M6LWOrEOqGNPK6+7MF0EiCmdDYjSkKPzNxARCb60CENo/sjlzOrCKRK2FXp0C347L QUqCu1o4XloMJ4bGPtyzB7KvpGOe2wzj7dGNX+1ZEOTQzmWSXu+i2qOfDQfOuA+tLEni 5bxCsWqedVhMvs2tigc2nZz1CJULZgfxZ40lftRmQ6JhIRakbgyGYhvCVH1unwDGIByE 0n0GQivp97hgCURS4g7exnpRpmYOhEdiqxQAEMWA3VYeNg1xKOKHec+rEr7W1PWntVpp f11g== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id z17si1806721edz.1.2018.02.01.03.40.32 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 03:40:33 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@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 jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w11BeWrI028837 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Feb 2018 12:40:32 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id w11BeWbQ022377; Thu, 1 Feb 2018 12:40:32 +0100 Subject: Re: [PATCH 3/4] build.sh: Update apt sources To: Alexander Smirnov , isar-users@googlegroups.com References: <20180201112944.7877-1-asmirnov@ilbers.de> <20180201112944.7877-4-asmirnov@ilbers.de> From: Jan Kiszka Message-ID: Date: Thu, 1 Feb 2018 12:40:30 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <20180201112944.7877-4-asmirnov@ilbers.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: piDLArszjoDB On 2018-02-01 12:29, Alexander Smirnov wrote: > Trigger apt sources update before building the package to be sure that > we are in sync with isar-apt content. > > Signed-off-by: Alexander Smirnov > --- > meta/recipes-devtools/buildchroot/files/build.sh | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/meta/recipes-devtools/buildchroot/files/build.sh b/meta/recipes-devtools/buildchroot/files/build.sh > index 77e0fdd..5c59193 100644 > --- a/meta/recipes-devtools/buildchroot/files/build.sh > +++ b/meta/recipes-devtools/buildchroot/files/build.sh > @@ -3,6 +3,9 @@ > # This software is a part of ISAR. > # Copyright (C) 2015-2017 ilbers GmbH > > +# Make sure that we have latest isar-apt content > +apt-get update > + Can we confine this to the isar-apt repo? Or is there no risk that an upstream repo update will result in a buildchroot change that is inconsistent with an earlier build stage? Jan > # Go to build directory > cd $1 > > -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux