From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7026732926060462080 X-Received: by 2002:a2e:a885:: with SMTP id m5mr1190425ljq.166.1636039504961; Thu, 04 Nov 2021 08:25:04 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a19:c74d:: with SMTP id x74ls604103lff.3.gmail; Thu, 04 Nov 2021 08:25:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx9wEKL5Y5UsPt/GEP3rwuNtLmlIRC0eZ3fFibJ6n7bzPLMOMmjRV3hI9Cho4kQoeaaM5sL X-Received: by 2002:a05:6512:1023:: with SMTP id r3mr49297018lfr.47.1636039503817; Thu, 04 Nov 2021 08:25:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1636039503; cv=none; d=google.com; s=arc-20160816; b=Yo331iLM/o/quzJYq4u7POXJtssHF3HQNG7TDmxV3PhZo8uoZ4JFRUgJnVQwfNM7cA rwoUVQlR3qYHLyYuWRkq2qhlGjLYFkWtvzjcHMaMrh5etoZy6HPeixhhpoRzzazrsMAx 7d5QuGwqmNfIjAj5akbnzh+QUq2UMLADMF1N762p7Vm14Ricf/XR33g7fkAFDDV1SsSX Bz69d1BQaRRE3x3GFlz0oJ1c3+AWBpqoUxj+lOl3HxDN00Dp2Mi2SBNrUHPKU1H1kw7e gZtbhguFPZQo2eJB7TO/7RyVhU1jAZIwcuIRKGzTEqfsNIbMVBSpN7Ui5wMHv/0fmoIx fMwQ== 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; bh=18PyawG/i5krRkWkKDZGoPtiB8zTFoU2toSUnWp7XtE=; b=egSWR74BgA5mzRFElYbV8TvgnNZIh9YLr3+gUJ6O/wsaGLgDiJO0k6m2ZR8DfDFrd6 HUo/NbYyX8vw1Vpdk51kuoKXtOtxok6CnyvLB1VjM6Ul58rFrNhjpDwRcTw3iI4T0BsI Ni4CP+y+b08fZIAYJlnOERT6kDk3NZtiUAiqnOYhb81wTtTH2FojjtPnZFKGZ17ehrY/ qgjU47cxmCXeVMq/QRrMQdYLrz+s1zkq0Q2QUajEXsxIuGHYCMnFfvsO6hOrnpfKq9TZ uGlNjwQwDfM8bliL8iTZhlkxkdQOTk0g0ylM2AJIcGJoBUg1w8SXYR1REsBKC+KjhraS LYvg== 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id f9si305918ljj.4.2021.11.04.08.25.03 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Nov 2021 08:25:03 -0700 (PDT) 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=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 1A4FP2GC019014 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 4 Nov 2021 16:25:03 +0100 Received: from [139.22.45.19] ([139.22.45.19]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 1A4FP2eu006756; Thu, 4 Nov 2021 16:25:02 +0100 Subject: Re: RFC: add maximum debootstrap storing time, or check for updates and invalidate To: Henning Schild , isar-users@googlegroups.com References: <20211104161227.49668f09@md1za8fc.ad001.siemens.net> From: Jan Kiszka Message-ID: Date: Thu, 4 Nov 2021 16:25:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <20211104161227.49668f09@md1za8fc.ad001.siemens.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: njc4y1qLIq4A On 04.11.21 16:12, Henning Schild wrote: > Hi, > > Isar does have the problem that a debootstrap does the only real > "apt-get update". That is in fact intentional but can lead to the > situation where an outdated chrootfs can break a build. I.e. apt-get > wants to install a package in a version that is not available upstream > anymore. > > Now when this happens is impossible to say. It depends on the amount of > packages one has, maybe the distro one is using (sid moving faster than > oldstable), and frozen custom mirror never moving. > > With local builds people usually clean all, and for sstate people will > also have to find their own way of dealing with it. But one could say > ... it is becoming more of a problem. Not something to not merge the > sstate changes for, but something to think about for the future. > > My current idea would be to introduce > DISTRO_MAX_CHROOT_AGE?="3d" > > anon python function > if /var/..apt/ older than DISTRO_MAX_AGE > cleanall bootstrap recipe, or somehow enforce re-run > > An alternative (maybe better) would be to say > > check_for_updates after rootfs_install > copy rootfs to rootfs_tmp > chroot rootfs_tmp > apt-get update > if "apt-get upgrade is not empty" > bbwarn(image lacking some updates that meanwhile have been > published) > cleanall bootstrap recipe > if ISAR_BE_STRICT_ABOUT_THAT=true > fail > It's all a trade-off: The above will only run when redoing a rootfs, not when the buildchroot is considered "done" while a dependency installation later on may still fail. And running such a check on every rebuild, even when you only want to build a single package, not a complete image, may take too much time. I agree that some update check could be valuable, provided its controllable whether it is executed or not. And bonus for a simpler way of triggering the invalidation of all bootstrap tasks, faster than "rm -rf tmp". Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux