From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7003728059744387072 X-Received: by 2002:a2e:918e:: with SMTP id f14mr3481016ljg.357.1630686660549; Fri, 03 Sep 2021 09:31:00 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:3e17:: with SMTP id l23ls1348976lja.3.gmail; Fri, 03 Sep 2021 09:30:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyCrb4Ysotm/vHB2Krj6ftw+OqIMMC7uLD3yHf8tbBrsIw0PhsuklsZWzlYy13PPP3bCa6e X-Received: by 2002:a05:651c:54d:: with SMTP id q13mr1361544ljp.526.1630686659219; Fri, 03 Sep 2021 09:30:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1630686659; cv=none; d=google.com; s=arc-20160816; b=ql7DDLuwFKrNdvkB0oB/SheSHfMlQLe+lTREQyihUJOZ8yABJFB/fKy/sj/AEmzTCQ xm/qWHa/XDWsK3gVp47+6BLCTwijlgDxay4x1mXCruKBYpj8M91F+2MJx4fpOsPWPrvd +ZWK3qD+oru6MY8swKUbC1ycXt6jQUJzNXgAIyQWIn+sygq7DCjwe+SFs2cvr9dvoiIB wDOqtd37jUX8XocBKVjpK6nTo50arpMiKck4yjQZLQC48k3SAFqYXu6pZuxdMMAHxJgB 9th19dZ65maSIf5U9NJIhFvrn3J2vRujx67Q0yo8pNu11Y+UN7hAb+2ilqu2+GHeDWf6 l9ig== 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; bh=XhIllv6pmqZPZA3lkQaFPQM1cS8JUnMWupf0/LhypJY=; b=iySCzMygOp5fxqtJlk6u9094GBJ1Mc+GHqjpUOGHlWp1pksKA4EYqJ4epFIpNMh1jI qycCPElj94cfRifhM8NJL9b4Kp/i7BHRZ/FuPkDooyLs4s80jGGOAqhiYlO+aNqE2LyQ D9Zq6pnPMMuAV7+LbU6+MF7VM0ACPPCuc62ifnz5Oj4bR2Ys1PK0MRzMIFrgaBTk+6aJ /L5Ec2lkC+iBxU57K34qkDr1CrvX3R3UJchIC4LtmBn7SbJiZEtJde17jDTrpLs668zn 0SGF+MLwoy3ZuiR6nzJRtWZ/glJ8NKdwXAWE5DPKYvxVcS7vjEngKQCco3xTJjCS1zRE dNMg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from gecko.sbs.de (gecko.sbs.de. [194.138.37.40]) by gmr-mx.google.com with ESMTPS id h2si233849lft.5.2021.09.03.09.30.58 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Sep 2021 09:30:59 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) client-ip=194.138.37.40; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id 183GUvfj005548 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 3 Sep 2021 18:30:57 +0200 Received: from [139.25.68.37] ([139.25.68.37]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 183GUu2u029997; Fri, 3 Sep 2021 18:30:56 +0200 Subject: Re: [isar] reproducible build failures To: Venkata.Pyla@toshiba-tsip.com, isar-users@googlegroups.com Cc: henning.schild@siemens.com, daniel.sangorrin@toshiba.co.jp, dinesh.kumar@toshiba-tsip.com References: From: Jan Kiszka Message-ID: <35ce019c-004a-4b36-e5a5-3401717f7f34@siemens.com> Date: Fri, 3 Sep 2021 18:30:56 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: jLlFCHx3KTB3 Hi Venkata, please avoid HTML emails on mailing lists. On 03.09.21 17:19, Venkata.Pyla@toshiba-tsip.com wrote: > Hi, > > I am using isar system in isar-cip-core project [1] where I found some > reproducible failures, which may be good to fix in the isar system. > I am not good in modifying the isar system, so could you please guide me > to fix these problems? > > Here are the steps to check the reproducible failures in isar-cip-core > project: > https://gitlab.com/cip-project/cip-core/isar-cip-core/-/issues/12 > > https://gitlab.com/cip-project/cip-core/isar-cip-core/-/issues/13 > > > I also verified the reproducibility in the isar system and found similar > failures that are copied below: > ============================================== > tmp/gpghomefHv8eRhk43/ > tmp/gpghomefHv8eRhk43/private-keys-v1.d/ > usr/share/doc/hello/changelog.Debian.gz > var/cache/debconf/config.dat > var/cache/debconf/config.dat-old > var/cache/ldconfig/aux-cache > var/lib/dpkg/info/enable-fsck.md5sums > var/lib/dpkg/info/example-raw.md5sums > var/lib/dpkg/info/hello.md5sums > var/lib/dpkg/info/isar-disable-apt-cache.md5sums > var/lib/dpkg/info/isar-exclude-docs.md5sums > var/lib/dpkg/info/sshd-regen-keys.md5sums > var/lib/initramfs-tools/4.19.0-17-amd64 > var/lib/systemd/catalog/database > var/log/alternatives.log > var/log/bootstrap.log > var/log/dpkg.log > var/log/apt/history.log > var/log/apt/term.log > ============================================== > > Steps to check reproducible failures in isar > ==================================== > $ . isar-init-build-env ../build1 && bitbake mc:qemuamd64-buster-tgz:isar-image-base > $  . isar-init-build-env ../build2 && bitbake mc:qemuamd64-buster-tgz:isar-image-base > $ mkdir -p rootfs1 rootfs2 > $ tar -xzvf ./build1/tmp/deploy/images/qemuamd64/isar-image-base-debian-buster-qemuamd64.tar.gz -C ./rootfs1/ > $ tar -xzvf ./build2/tmp/deploy/images/qemuamd64/isar-image-base-debian-buster-qemuamd64.tar.gz -C ./rootfs2/ > $ rsync -nrclv ./rootfs1/ ./rootfs2/ > difference.txt > ====================================   >   > From the reproducible failures I found there are three different areas > to fix these problem > 1.       Changelog file generation, which is embedding the build time > date value at here > (https://github.com/ilbers/isar/blob/master/meta/classes/debianize.bbclass#L34 > > ) > 2.       Log files generated by different application, which are adding > build time values, I think we can remove these files if it is not > required after build. ( I tried at here > https://github.com/ilbers/isar/blob/master/meta/classes/image.bbclass#L183 > > but it did not work) > 3.       Cache and temporary files, I think we can delete these files also. > > Please guide me to fix these issues. > Did you also cross-check what https://wiki.debian.org/ReproducibleInstalls suggests? Then maybe start with the [isar-]bootstrap. Hook into https://github.com/ilbers/isar/blob/03124cca669f50b682336a0bdf4ede5a4238e144/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc#L232 to perform cleanups. Using SOURCE_DATE_EPOCH as control over timestamps might be an interface worth to explore. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux