From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6506467811408216064 X-Received: by 10.80.201.7 with SMTP id o7mr650815edh.3.1514987652366; Wed, 03 Jan 2018 05:54:12 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.241.28 with SMTP id w28ls12875917edl.0.gmail; Wed, 03 Jan 2018 05:54:11 -0800 (PST) X-Google-Smtp-Source: ACJfBovsz3CcITN9xeY4N3hZPYcA8t/OOeVk4G6GOvYLzpTspBDw3p0mws9h3R6jXHQTOUszWYHF X-Received: by 10.80.163.200 with SMTP id t8mr649012edb.1.1514987651811; Wed, 03 Jan 2018 05:54:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1514987651; cv=none; d=google.com; s=arc-20160816; b=q8VgHbsIaaOcOMDlIPfMmGeHOI27DBv0vpspibgkBU6zgwB5SXHPml1zzTHyCyfC+D mAeF0VNkD88GCGXdZGRwYvrXzbMaV3Bq6gjlJtnRSPxvEzk0aXykhMP8k+q3j6AxWTFc AK+joK8eCmN1RovcIqHTWZQq96ZyX6xadXlQrQEKL/L9+dsI9VQOxAnSZtYxj1hlXQLg LvXanay/QKSTTqLc+Bq5fs4RkG0lq/gZXCA3UHxOohdVX95Qla38TBJdVwcQwC7cYSb7 5K0e1mx79PUXyMbwW23Lz2dpgy6SxRLHNlmJyp3vRVLr8cmHK3SCssJpLQxQwsI3f0bz GRrQ== 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:cc:to:subject :arc-authentication-results; bh=dJWOhxscQXjFF/037C0fiYsYt1Nwff2DbfcNy7Y1lJA=; b=kxN+8zZAigZQSy6XdY8ni2+PIrtZx9MbnQS5+dIQgb9oeWHgIF+xA3QPjQKYCETN0E EZs/5IDkabmkMFH15rJaT6ZFDyA3cd6W7uV244vXbAItzSuLH9d+mXB2MmNrzCZugGxf jiA31ylVCgKGV+WTqoE/XyBfjTs0EENNycyEySjagrXWUvNoiDE14Alj63Wqh+Q2iR51 hNX/FWkSEHJjsfI5ft7tZCiEbmkSFAtiUtkigIe9+688ufJi5gLSysK2SatQlKieIBfl 7/xxUHgeskIgcHdEy/IdinEuoJHX2aJYKkdQTJSwgMi1Jx0FqCtk3FMGzmytzuaKpycI 3gYw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id h45si164336eda.2.2018.01.03.05.54.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jan 2018 05:54:11 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id w03DsADc032552 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 3 Jan 2018 14:54:11 +0100 Received: from md1f2u6c.ww002.siemens.net (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w03DsASW027829; Wed, 3 Jan 2018 14:54:10 +0100 Subject: Re: [RFC][PATCH 0/6] Isar build reproducibility To: "[ext] Henning Schild" , Alexander Smirnov Cc: isar-users@googlegroups.com References: <20180102145744.21814-1-asmirnov@ilbers.de> <20180103144945.017b062a@mmd1pvb1c.ad001.siemens.net> From: Jan Kiszka Message-ID: Date: Wed, 3 Jan 2018 14:54:10 +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: <20180103144945.017b062a@mmd1pvb1c.ad001.siemens.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: vpSVhDAxL6QM On 2018-01-03 14:49, [ext] Henning Schild wrote: > Am Tue, 2 Jan 2018 17:57:38 +0300 > schrieb Alexander Smirnov : > >> Hello all, >> >> this series proposes the way how build reproducibility could be >> implemented in Isar. General idea is to get the list of all the >> necessary packages for build, fetch them and create local repo, that >> will be used for further builds/ >> >> Briefly speeking, it works like the following: >> >> 1. User sets the list of images that should be 'reproducible' in >> BASE_APT_IMAGES variable in local.conf file. > > I am with Jan here, i would prefer an all or nothing approach. > >> 2. Based on the list of images above, Isar will derive all the >> run-time and build dependencies for these images. >> >> 3. Using multistrap, Isar will fetch the list of packages and create >> base-apt local repository. >> >> 4. Now buildchroot and image root filesystems are generated using >> base-apt. > > Patch5 makes base-apt and Isar the only repos for a rootfs/buildchroot. > How do images, not using BASE_APT, get packages that are not cached? > Another reason to split the caching and local redistribution repo that will be filled by local builds from this mirroring and pinning repo. For archiving purposes, there than later be some tool/task to export both into a single repo, but we need a separation during builds. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux