From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6506467811408216064 X-Received: by 10.80.242.138 with SMTP id f10mr646235edm.11.1514987387522; Wed, 03 Jan 2018 05:49:47 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.208.199 with SMTP id g7ls12859250edf.7.gmail; Wed, 03 Jan 2018 05:49:47 -0800 (PST) X-Google-Smtp-Source: ACJfBotfRMdhM2mP0yYvzLIsrJd6dByp2ew7nVA4hPY/eHixbVjNE5QjUgqId4F+bMbZhJdQzpKq X-Received: by 10.80.230.25 with SMTP id y25mr646234edm.9.1514987387135; Wed, 03 Jan 2018 05:49:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1514987387; cv=none; d=google.com; s=arc-20160816; b=PaMp/4RcZtJjRqzrldQvyhBvsi9RQ42RUr2OEOlDZXfqCSqmH10BpucO2+LE5SsXpa Wp/v7I6cNIByZsJnlinM4xvJytLOX8i++CtRecsQtoYgyuBnkg7aXgMDA4gu1iSf2zWv nuvEHbTSQqhKpB5UqQRrx1LRxpCj4tfwHprxPyyH7RL+KUeRIWPRb+wlPuiqqC7j3bFk hgNx8OvBDt3R7bCJBlvJNIswySaDHzKS7VQl3u3fkU7JP+W46pU3k8itypAdtwR2OBgL vALHMNNeRovNYN/hih8gYXddQ7d7PYPemyttvO3uer00Q7zi67DO7LZPbidKem3CB6C4 zuXQ== 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:arc-authentication-results; bh=FHRiLTzmPli1XxHDY2HB9qDtp9K5B68/q4W3ObPZzcU=; b=EAAhvVKqZLBnochRoIe8G+IjLMYpHdYWcpLkcCsH+Wi6fjwDhpJhFe+QngzVGVDNWU aX2ZSubkTLbQDVUtWr2M3BRZJqdlsGJdLMOIyEmGqQw9soyq7pnPqBEkQpRlq/Ul+bZz PK14J3KjzHjjRKFAtRjuC2ba/+M9fdwAWK43gfFNoHso6yXi1V5koqm8RZdcwI/X3+BC 5Uj/ZYLtvkR7g4oIFNSKZURnY9QWmi+CFrSptJ9P5apSM7fKC7XxLejb/V7ePFpCyrc+ jluoVpD9aOdd0evom8rvoktJDZ0GfyIn6RdWYhaQG7JYzU7pMyMlt1IA3eE5Cj1tghX1 qBmg== 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 r58si167127eda.3.2018.01.03.05.49.47 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jan 2018 05:49:47 -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 mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w03Dnkg3022407 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 3 Jan 2018 14:49:46 +0100 Received: from mmd1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40] (may be forged)) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w03DnkO4005775; Wed, 3 Jan 2018 14:49:46 +0100 Date: Wed, 3 Jan 2018 14:49:45 +0100 From: Henning Schild To: Alexander Smirnov Cc: Subject: Re: [RFC][PATCH 0/6] Isar build reproducibility Message-ID: <20180103144945.017b062a@mmd1pvb1c.ad001.siemens.net> In-Reply-To: <20180102145744.21814-1-asmirnov@ilbers.de> References: <20180102145744.21814-1-asmirnov@ilbers.de> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: 5QktdCGI+1eY 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? > Some notes: > > 1. base-apt repository is mounted to buildchroot, so Isar packages are > able to install necessary deps via apt-get. > > 2. bitbake events are used to clean up buildchroot. I haven't found > another way how base-apt could be unmounted. So it's mounted once > before any package starts building and unmounted by bitbake event: > bb.event.BuildCompleted. > > This series works good with latest next. Any comments are welcome. > > Happy New Year 2018! :-) Same from me! Henning > With best regards, > Alex > > Alexander Smirnov (6): > base-apt: Introduce fetching upstream apt > base-apt: Add to pipeline > buildchroot: Switch to base-apt > buildchroot: Add mount/umount for 'base-apt' > image: Switch to base-apt > base-apt: Add possibility to reuse > > meta-isar/conf/local.conf.sample | 8 ++ > .../recipes-core/images/files/multistrap.conf.in | 18 +--- > meta-isar/recipes-core/images/isar-image-base.bb | 5 +- > meta/classes/dpkg-base.bbclass | 16 +++- > meta/classes/image.bbclass | 13 ++- > meta/classes/isar-events.bbclass | 21 +++++ > meta/conf/isar-bitbake.conf | 2 + > meta/recipes-devtools/base-apt/base-apt.bb | 97 > ++++++++++++++++++++++ .../base-apt/files/distributions.in > | 3 + .../base-apt/files/multistrap.conf.in | 28 +++++++ > meta/recipes-devtools/buildchroot/buildchroot.bb | 28 ++++++- > .../buildchroot/files/configscript.sh | 1 - > .../buildchroot/files/multistrap.conf.in | 18 +--- > 13 files changed, 217 insertions(+), 41 deletions(-) > create mode 100644 meta/classes/isar-events.bbclass > create mode 100644 meta/recipes-devtools/base-apt/base-apt.bb > create mode 100644 > meta/recipes-devtools/base-apt/files/distributions.in create mode > 100644 meta/recipes-devtools/base-apt/files/multistrap.conf.in >