From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517546778931232768 X-Received: by 10.28.15.145 with SMTP id 139mr3565424wmp.27.1517490810758; Thu, 01 Feb 2018 05:13:30 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.223.187.140 with SMTP id q12ls1777165wrg.9.gmail; Thu, 01 Feb 2018 05:13:29 -0800 (PST) X-Google-Smtp-Source: AH8x225RFaLnQ30YP1iHSs+edFYiJQJ0jAH2sOL+U1hWcH0O1jYkOnafHrrEras353BwN47DkLLj X-Received: by 10.28.128.79 with SMTP id b76mr2997786wmd.30.1517490809523; Thu, 01 Feb 2018 05:13:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517490809; cv=none; d=google.com; s=arc-20160816; b=K77h8au4/CsGSozW/ZFbvHgcuTpsiSFObyLhturYO3uzT988hekkZ1dpUNqJB19Rtn RQ+52plSH7g8kD5fpYvIBptPBqr//97BNeEzdK6uNxDKEPw1pwUL+Ln84qAf0d5qWaSU lKpbaBZmzGCt3M+wtX8MPlsp3hE0ZOUvpAp04+h5TKZUo5pEzPiyVzaEx3SA60mCYy+K S/zgP4vAoOLycwSBveXs6efF1hT67OMVWomiAI0ECAc/7sFbKKMC1BI5Fyth1UMhptz6 ZubmlYdNGb5RrEAomycjMPSsz6Ipyxcgc43R5nlEVkQ7qdqhcFHHrhY8BxGIDxkEuBtU SgBg== 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=9GhmJs70tI2ZyfaSjxU89UEiskISMgP5dm3Cc/iBjaU=; b=NodvaU9im7g9iTvVpUBih+mP4YbLUA/bEPTlPJDy08IS1HPgTKbcueQCp9LuCyZb++ cb0zERuGemAo0PyFgOL02OjLslhJ4rv8wp1oX7+ZFWjV/CwApbsd/4J0vOFuL0gWWCqL auyh39Ukr3JGBRsSiC8fLR0qXWxzPXTVLuzN7OhHuB9yqIWISZECcw7TUOrtcF+3FreE iSZsnWDrEsgwFciGWkWfjYztPPkL82Ak0CnufVn8vxlfqjeIDrrnYXh/+/2cT5gtUdGq RoId7zj5inGHIiop/NBDacNbeAhAhFTR0BrGjwkUsZMGFmHo8APe5s8rBvzJwDqNMndL N9zQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id s81si193174wmd.2.2018.02.01.05.13.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 05:13:29 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w11DDS0U003890 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Feb 2018 14:13:29 +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 w11DDSCF012946; Thu, 1 Feb 2018 14:13:28 +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> <6a256d50-9bd9-cad6-e4d6-9fabf19570d8@ilbers.de> From: Jan Kiszka Message-ID: Date: Thu, 1 Feb 2018 14:13:27 +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: <6a256d50-9bd9-cad6-e4d6-9fabf19570d8@ilbers.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: ZofG3W0UE8n+ On 2018-02-01 12:48, Alexander Smirnov wrote: > On 02/01/2018 02:40 PM, Jan Kiszka wrote: >> 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? > > That's a good point, I've already checked it, it seems to be possible like: > > sudo apt-get update -o Dir::Etc::sourcelist="sources.list.d/${source}" \ > -o Dir::Etc::sourceparts="-" -o APT::Get::List-Cleanup="0" > > [https://askubuntu.com/questions/65245/apt-get-update-only-for-a-specific-repository] > > > But I decided that it makes no sense, because target image will be > generated later and use upstream apt. So if something has been changed > during buildchroot operating, this will affect target image anyway. buildchroot shall not deviate from target rootfs. We will eventually (rather sooner than later) have to provide it for SDK use, and than you definitely don't want surprises, but actually already earlier. > > Again I think this should be handled outside buildchroot by caching > upstream apts. Well, do you plan to /always/ cache them? Last time I asked you said we need both cases, cached and "live" ;). But even when live, we must keep things atomic over a single build at least. So, if you can avoid pulling from upstream here, please add that. We can still drop it again when the external infrastructure can always guarantee atomicity in the repo state. Thanks, Jan