From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6607733288662466560 X-Received: by 2002:a7b:c00f:: with SMTP id c15-v6mr1220849wmb.7.1540816084233; Mon, 29 Oct 2018 05:28:04 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:82ce:: with SMTP id e197-v6ls681557wmd.7.canary-gmail; Mon, 29 Oct 2018 05:28:03 -0700 (PDT) X-Google-Smtp-Source: AJdET5fYIYf/1S0JMvbwI8K640i3SZ1gTt8D85srMiJY/1EDNHY5VSgWH7AqNMGNKdUMFMaptRyx X-Received: by 2002:a1c:3a84:: with SMTP id h126-v6mr2183541wma.14.1540816083745; Mon, 29 Oct 2018 05:28:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540816083; cv=none; d=google.com; s=arc-20160816; b=gMFvwOj+d4813aqojnZ0+19zeXcwiFyYv4qjPF1grxBZ6tWhAiDveMZyNIMqJ+HFGC 66JIct9cdLdxD6SM1a370m3fbeia8cYAjnV5FawlUsxih+YX3zzvGd5khneVjaSJ0K9v FWCEaelXq7Avz+zZziELm3XdueVw5EOlqpbVDF7UFF/jkSEmaziLgthQGNrN/8I3unrW bpl5jyoOCG11EorNkWrJsGfeLNm5+ES+TTNl+pkGIvMZpBUej/peLd4t0qqvCW9ABm8I 3ITnDzeUL3y91Btm4/bHx4Mh4EmdWrDimk8y6UspUSdECS1KXYSull3PQMm9pet3u133 jsVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=pBQ3eH2TIJjRu7d8stXXiRBgaOoQtMndDLKI43r1XxE=; b=Ky5Ay/yo7Q4LCOKtjZlvFSSh15VwwJQfgrvBwrZzSVVjaKQbNISYmbwcj8G+GBfBU6 N1j7y9eh66hMH8QpvKmiv7ETfZ7XiUI6v2ydYwMur0h5rFeU+ug1OsCDw/AMaSHq6Ho3 clg1/KVfKBlScy/deCcvjD/pyF0j6nVGT8nt9hzKiW0WV8zAYI/VadErqS/ZBiBlNwqn XU4W4YMFHA4Vvor6MGQPSG8f102lSFBhEr+4V5hDTl6EhVi8HyBBUPjryKtM+G57ytvv rx/oGeD8/4cmz2BKiJsd0I+/lwd7pUG13W+DU2/ojjJIEHWpASxYXX6di5FYNFvvMGvE lY5Q== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id z129-v6si303392wmc.0.2018.10.29.05.28.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Oct 2018 05:28:03 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w9TCS1UB010477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 29 Oct 2018 13:28:02 +0100 Received: from yssyq.m.ilbers.de (localhost [127.0.0.1]) by yssyq.m.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPS id w9TCS16M017352 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 29 Oct 2018 13:28:01 +0100 Received: (from ibr@localhost) by yssyq.m.ilbers.de (8.15.2/8.15.2/Submit) id w9TCS0pE017351 for isar-users@googlegroups.com; Mon, 29 Oct 2018 13:28:00 +0100 Date: Mon, 29 Oct 2018 13:28:00 +0100 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH v2 00/10] Introduce local apt repo to cache upstream debian packages for offline usage Message-ID: <20181029122800.GD6306@yssyq.m.ilbers.de> Mail-Followup-To: isar-users@googlegroups.com References: <20181011165305.1622-1-mosipov@ilbers.de> <20181023181456.6d9c6a59@md1pvb1c.ad001.siemens.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181023181456.6d9c6a59@md1pvb1c.ad001.siemens.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-TUID: L1KSF0KzUc2f On Tue, Oct 23, 2018 at 06:14:56PM +0200, Henning Schild wrote: > i am kind of missing some context here. Is this really just a cache to > remove deb fetching from the build and allow offline builds? Or is this > somehow targeting reproducable builds? > > If the latter is true i would like to see a summary of the earlier > discussions, a detailed description of what is happening and why. Yes, this is just a cache to allow offline builds. And yes, this is a small step 0 towards reproducibility. As I see it, previous discussions boil down to: 1. Doing automatic reproducibility right is complex and should be done in steps. 2. Initial caching is a low-hanging fruit that can be addressed now and is better than nothing. This series provides (2). For (1), I suggest to introduce a mechanism first. It should be usable manually. It should start from minimal essential use cases (initial creation) and be possibly extended to further use cases (update all, update single, update single with deps, remove, etc.) as necessary. If desired, we could look at optionally building it into the workflow of Isar after the mechanism stabilizes (with policies such as automatically fetch on the first build, update on every build, etc.). We can provide more details along the way. On a related note, we've discussed these issues at ELCE. libapt and python-apt seem to be what we need for the implementation. With kind regards, Baurzhan.