From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6506467811408216064 X-Received: by 10.46.34.2 with SMTP id i2mr131198lji.44.1514988226081; Wed, 03 Jan 2018 06:03:46 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.20.11 with SMTP id u11ls3748654ljd.9.gmail; Wed, 03 Jan 2018 06:03:45 -0800 (PST) X-Google-Smtp-Source: ACJfBosZ++opGqNS4vRfBqjLXY+sjN3s3D/736NeOpcoKXEK0N/zS4FYUX+TQFqaLbnbA0TtUbF1 X-Received: by 10.25.24.24 with SMTP id o24mr77070lfi.35.1514988225673; Wed, 03 Jan 2018 06:03:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1514988225; cv=none; d=google.com; s=arc-20160816; b=XnvVcMjviL8xXUPVFEDX9ej+SjwUbxX6EUSQO/Ba9dDKtndNp2mLJwgApU9pPEA1WQ E8W9fzQEYOwJZCJs3EuUJhNXQMhwO3m0uWBmAtqncKWtRyFkJ8II5cFINz7lawHKJjbA WuzweLZMtiuPJn0vyC6QpxqAqa7C2czSVZPEdASrSamXdW8FZZ9e4OnF1EfY/myfsueO 3P2Ex3/KKSUfMOKGoh43h3+syLwMRjK+T+BBJp39/lDV+bd1TQdT9v/q72i9Lm0gDKfX 0tuQWwJxP/y8/NO1cdYnF0T1Wur/dTQYWqXREWY2thQFaVYQn0NjTl1JgKBcnBs537hN ZuYw== 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=KvNZdHCQUaTOpr6IgnqKBWa4wTRE5fygHB5UzkLOudw=; b=BmEJQ2fsUCYtZ0IVIdJcQYqpDI2gEmU0qzgMoLadhXCOEB7C0JGQ4xaJxjSeOw/COF KhYIneIo2fcXNU6fCbMW6gUebFuLsllqBRQB/NAnuA3302qvK6PWfAjvKkbq3ajW40G4 d5W9lsqLv9mqAGbq02RvAQE15gGCy2MKUo23GOyr9M1LoUAdvn5towcTTcGTZZm4NuH4 17fITcQ6THn8yyscLoDXTCYqYpxUdiJ4N6UYcyuiNnaNyoPAJZSsJm82hLM+QqRvqJ4p C1ATDVZL3vQnkvCjl+lSo3B6N5ThnCMQRZP516O5L6M6S2z8iJwm4hEdgS1/K0ACIA5e nCpA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id 64si122822ljz.5.2018.01.03.06.03.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jan 2018 06:03:45 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w03E3iYC000893 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 3 Jan 2018 15:03:45 +0100 Received: from mmd1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40] (may be forged)) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id w03E3i31019160; Wed, 3 Jan 2018 15:03:44 +0100 Date: Wed, 3 Jan 2018 15:03:44 +0100 From: Henning Schild To: Jan Kiszka Cc: Alexander Smirnov , Subject: Re: [RFC][PATCH 0/6] Isar build reproducibility Message-ID: <20180103150344.3bab5d01@mmd1pvb1c.ad001.siemens.net> In-Reply-To: References: <20180102145744.21814-1-asmirnov@ilbers.de> <20180103144945.017b062a@mmd1pvb1c.ad001.siemens.net> 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: M2NfCNA76KDZ Am Wed, 3 Jan 2018 14:54:10 +0100 schrieb Jan Kiszka : > 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. Not sure what you are talking about, but there will be two repos. "base-apt" which will contain all .debs from repos we fed into the first multistrap - presumably official Debian mirrors. But all of the partitial mirrors merged into one repo. And the second one "Isar" which will contain what came out of dpdk.bbclass or dpdk-raw.bblass recipes. Henning > Jan >