From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517546778931232768 X-Received: by 10.223.156.210 with SMTP id h18mr3880431wre.1.1517485710591; Thu, 01 Feb 2018 03:48:30 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.223.164.149 with SMTP id g21ls2305764wrb.1.gmail; Thu, 01 Feb 2018 03:48:30 -0800 (PST) X-Google-Smtp-Source: AH8x225Vb8zxiVl08Xa34fKx4wTrAXEgogDa9Nw2CPun3Id+zpXnzBCo6GQbVurnMw8Ozr6bzACF X-Received: by 10.223.196.13 with SMTP id v13mr547593wrf.22.1517485710193; Thu, 01 Feb 2018 03:48:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517485710; cv=none; d=google.com; s=arc-20160816; b=IxwUdN2Wyonr7rAGbMiyrD3xERGsgrC/OMoaY7GAVgboOwfEV9Hd2alCcyX6KfhujD /jcX5gFHtOYuva0Cg1lpA/yBo3Bdkf4nOaBuZSVJ3TEHsTysfl1DnJIPhQHmrcCkCrDX MnunuucdnpcRUyu7jOmQYM4WV3iX/i3T4DaIAKO3RwBR2OLYzqontBNL4c1464YkL+sd 1ylDE/CfSEODLReep4hdCybVejL/IKQrjgHfI8S+L/17T9f9Y4AJRviB/HExSnf3RRIS tC/gwlI1+mJu8clagTVSKxrL1KpNIewdIWOFM7GIdipNxyCj1a8sLCEN0jZOZFfymjFK PIYA== 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=Ct2HPOTPta2S9jhZwSZx2t6IPd/qjPZk3/OjU3B7Sb8=; b=mIgk7IYw9MhYthE3RwfHhq6nGVlFIQXWk1MXIREayuZ+oxbSCRkNaf1/RK806DnIi9 xGPKZoVTkfEqlrS9S0/Oad9X7gkjc3u9v4EHIhUiDZCcdIkHcwjh8RwUhKngrBCxJ+e+ 41QV+EV5ZZA/A9DaPmff+4ccLMt1C/GeafuYbVD2orgBSPcypnSRsP5T75fNSjQfliS+ JGKUNq/uY/7xNO4iYEuByy4SC7s+uO2fAScIg+X4H51YxNKbKoXt26jjeiqOq65e5FoU WE9DDgMp5lyRMGO5bKeb9T0WlHuNDMSMe4yH6xrmDZi4ZFNIs1X/s7r/aJTyBe2kN0A9 Inkg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id g70si87906wmc.3.2018.02.01.03.48.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 03:48:30 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Received: from [10.0.2.15] ([188.227.110.165]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w11BmQDe011633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 1 Feb 2018 12:48:28 +0100 Subject: Re: [PATCH 3/4] build.sh: Update apt sources To: Jan Kiszka , isar-users@googlegroups.com References: <20180201112944.7877-1-asmirnov@ilbers.de> <20180201112944.7877-4-asmirnov@ilbers.de> From: Alexander Smirnov Message-ID: <6a256d50-9bd9-cad6-e4d6-9fabf19570d8@ilbers.de> Date: Thu, 1 Feb 2018 14:48:21 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: xNSiDYPzARVg 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. Again I think this should be handled outside buildchroot by caching upstream apts. Alex