From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6656673633724792832 X-Received: by 2002:adf:dece:: with SMTP id i14mr1203454wrn.3.1551780698841; Tue, 05 Mar 2019 02:11:38 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:2d06:: with SMTP id t6ls268721wmt.10.gmail; Tue, 05 Mar 2019 02:11:38 -0800 (PST) X-Google-Smtp-Source: APXvYqy5UXdmDqIgf/rcS6KqS2AmDgQoXUNLioq5fU/UL3TWJZOpuuBuR8aGw7cDBQKkWPYLoUN4 X-Received: by 2002:a1c:a702:: with SMTP id q2mr254583wme.0.1551780698446; Tue, 05 Mar 2019 02:11:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551780698; cv=none; d=google.com; s=arc-20160816; b=uJgVFNGSw5jGDGJbQlncILBgodFavxxiTGYTDG7SdB8YInWHAAjvOT7aCdJeGLU2hr hNBmtPM4YUkqJkzKcXCddWglGgmqiFVOXrfnI/+4GzEkqHqvNnCOtCutl2CSRtT1hkYm liIZ0nw17YWm63u+sCfiL5fHVI622u0OL83843Bw3piTm3Fzt9oT5NQsU+1yubXITVMn aLpYVtzkEzqrcoCpTa9nac4vRL1g2ZLtbbgshwU8A89JModyYfG6jFR3dorKQNtsNlLL J15137GLKghBVSPLfJObyadwxFnByKM4DrFC50Xapuxly8RgYHgrhgoICawi0/3FiW2r 5mxA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=mMNogDNMTqhbV2hS5prGHLkWGLJgK/UJAply4xs0qC4=; b=JipOj8krSN2T8q/Dvw86GXeD2pXwZ5kbYe93uBCr/uHdhGndMSDggXY/1KyHYyBn0z 87kGYz3mE9j3XJyEPmZLJ4bi0Z9wnkp8QDBXMsVgu2AJXWTZAlelneIN1GZ/lhq8ed5a KBQDF3yabLDjQQma70XgzsNQ8fm9lU8vysUQoADtR/jq43xe6j2vuoBGKbia8w2xGvTo NUF8vo0OecPyPMLXCjQdhZjLlf6ReEMoJcgkMrpIHGIYrOGmzI7QJ6lXGhO1yA7ZdYqv Lt81fNKtGB+CaZMCuA+kJ1N9pdu4fSaLjvbG0hYlnPVUb5Tt7jjL9JIwz/0GDv3stF1M whGw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id 109si262020wrb.0.2019.03.05.02.11.38 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Mar 2019 02:11:38 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@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 henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x25ABbnP029652 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 5 Mar 2019 11:11:37 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.69.211]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x25ABbGi030949; Tue, 5 Mar 2019 11:11:37 +0100 Date: Tue, 5 Mar 2019 11:11:37 +0100 From: Henning Schild To: Jan Kiszka Cc: Subject: Re: [PATCH] dpkg-base: apt-get "update" before "source" Message-ID: <20190305111137.7cfccea1@md1za8fc.ad001.siemens.net> In-Reply-To: References: <20190211093324.1444-1-henning.schild@siemens.com> <20190211103526.3d92babf@md1za8fc.ad001.siemens.net> <0ff54328-5b30-e645-619e-0eaac9c184b5@siemens.com> <20190226160013.59c4ad3e@md1za8fc.ad001.siemens.net> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: H5D0DO/XFXJ2 Am Tue, 26 Feb 2019 16:03:42 +0100 schrieb Jan Kiszka : > On 26.02.19 16:00, Henning Schild wrote: > > Am Mon, 11 Feb 2019 13:53:07 +0100 > > schrieb Jan Kiszka : > > > >> On 11.02.19 10:35, [ext] Henning Schild wrote: > >>> Here i see an often repeating pattern. That "apt-get update" is > >>> now present in many entry points to the buildchroot. > >>> I guess we should factor it out and put it into a central place. > >>> And the rule of thumb probably is ... whenever you use anything > >>> apt, apt-get update before you do ... > >> > >> If you are only talking about updating our locally maintained repo > >> (like below), that is fine to factor out and reuse. However, we > >> must not update against public repos after the initial pulling, in > >> order to ensure we have a consistent package set along the whole > >> build. > > > > I think that is actually not true. The whole process is an "eventual > > consistency" topic. Say one of your package compiles for 2 > > weeks ... > > Then you will not be able to work. This is no realistic scenario. Sure, just trying to stress the point that your local view of your mirror can expire any time. ( 2 weeks or 2 minutes ... ) > > you would never be able to build a buster image. And in fact, no > > matter how long the time windows is. You can always hit the point > > where a file that should be there according to your view of the > > repo, can not be downloaded anymore .... in which case you need to > > "update/upgrade". > > > > So i tend to believe that we should always "apt-get update" without > > restrictions. For people that truly care about having a > > reproducible > > Nope, we won't do that - unless we have a stable (versioned and > frozen) repo. This does not apply to upstream Debian, so the current > pattern is the way to go: single update for a single build. Several updates would most likely be a noop anyways but ensure that every "apt-get install" will succeed. We do have the cache and everyone can have a versioned and frozen repo. I just started this topic again because Andreas introduced a full "apt-get update" to deal with the gpg topic. Henning > Jan >