From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7003728059744387072 X-Received: by 2002:a7b:c005:: with SMTP id c5mr10473445wmb.59.1630917708123; Mon, 06 Sep 2021 01:41:48 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:c789:: with SMTP id l9ls579881wrg.1.gmail; Mon, 06 Sep 2021 01:41:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwiwZ7TCNr8hBNPLdNGIGOt3NXxWEMTxXo/m4AJN2Z3vUuqyf5SMQ5m0yNsfeLWuf+SjQTQ X-Received: by 2002:adf:dd51:: with SMTP id u17mr12053746wrm.432.1630917707215; Mon, 06 Sep 2021 01:41:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1630917707; cv=none; d=google.com; s=arc-20160816; b=xLJnUSTzuUzL+ahIC9RzFxwqAn26tt4ZnffFbXZMhhA5dt7VdHMiu8tnBrebdkpJSJ rrbCsSyeuDzg3WTOnX4wECppCdL8OTooG3/djktoHb1kwuAQzhPUFX59A0Sv+qRF5aaw 9SAZvUPKOQzig2/FVIQMMUh6s9gW7Tr9aMO9Cy3HeilrEL2WiipqeyZROKxRyYpbU4g5 mFnMeRyoOj7Jtz7/SqasC1FVW18/GvaPPPjTSRcLHBNgj7Rjh/pIeO4yINhP7dlWL/va by6yDAZF7Bzv6MtyT31yZfgKxySSdJqXDTGUewHaZSajHXL2Gnm6FHwzsSCOHN8TeBXx 064g== 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; bh=P4xYQDaeo+VcEWxP3gJvn7G9/TPTSQodfk9ElCT9r3o=; b=ydaKDyavPwGwgNmeSY6XdJC6MO1GZ/k64zKDF1HnNzALCBDlNgGyKwLRcsjf2UdAoO jdI25gAHEHWRRn/6+d8eP1jPcZCwPlRoYq9samhUXaS+dydrkFYtJv3CnXdg2SxHIXFr kygFje/CvucGhpoofH3Wcucl6zBUFTk3p80K7XJtpkn7MYmTeefumZoq/ktChwBPfcCt kVMrIp3V0YV6rhwCw058P3oSH16OdqTMziIoohKshe0SSHYe0Ihtb63P8epauUMr57i4 S6W1VGE/dbj0qQinpz8Hnuwd8myxa1eyp9cBdfwxI89neBwuPRLwzLe35SEC5AbrS2PU m/vw== 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id i7si48053wrn.2.2021.09.06.01.41.47 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Sep 2021 01:41:47 -0700 (PDT) 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id 1868fkWM014533 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 6 Sep 2021 10:41:46 +0200 Received: from md1za8fc.ad001.siemens.net ([139.25.0.59]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id 1868fkKG020329; Mon, 6 Sep 2021 10:41:46 +0200 Date: Mon, 6 Sep 2021 10:41:45 +0200 From: Henning Schild To: Cc: , , , Subject: Re: [isar] reproducible build failures Message-ID: <20210906104145.305cf2fd@md1za8fc.ad001.siemens.net> In-Reply-To: References: X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: /XbSkRSmhM3Z Am Fri, 3 Sep 2021 15:19:21 +0000 schrieb : > 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Fcip-project%2Fcip-core%2Fisar-cip-core%2F-%2Fissues%2F12&data=04%7C01%7Cde173c00-e982-4fda-8644-47edf4671d63%40ad011.siemens.com%7C186fea861bb04bae174708d96eee3bfb%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637662792787877923%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=ofcsE0TXKbwL%2FPUTD2hAEQWvOLXNRFrIvunSOblUAho%3D&reserved=0 > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Fcip-project%2Fcip-core%2Fisar-cip-core%2F-%2Fissues%2F13&data=04%7C01%7Cde173c00-e982-4fda-8644-47edf4671d63%40ad011.siemens.com%7C186fea861bb04bae174708d96eee3bfb%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637662792787877923%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=M7pZHme2TzX7ZhNbaZW%2BKn26K65ZnKFW4BvnQJldLnw%3D&reserved=0 > > 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 I was wondering why only one package is affected here, it should be more. Turns out that isar-exclude-docs might be a little to thorough. I sent a patch for that [PATCH 3/3] isar-exclude-docs: include "native" package changelogs And "[PATCH 1/3] debianize: make changelog date reproducible" makes sure we always use the same date while still allowing user control and prepending to upstream without "going back in time". Henning > 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Filbers%2Fisar%2Fblob%2Fmaster%2Fmeta%2Fclasses%2Fdebianize.bbclass%23L34&data=04%7C01%7Cde173c00-e982-4fda-8644-47edf4671d63%40ad011.siemens.com%7C186fea861bb04bae174708d96eee3bfb%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637662792787877923%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=sSB%2BhM1xQauyMIju%2FlJ0GsgdBXYds2C61qpUoQPwuQw%3D&reserved=0 > ) > > 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Filbers%2Fisar%2Fblob%2Fmaster%2Fmeta%2Fclasses%2Fimage.bbclass%23L183&data=04%7C01%7Cde173c00-e982-4fda-8644-47edf4671d63%40ad011.siemens.com%7C186fea861bb04bae174708d96eee3bfb%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637662792787877923%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=kUZoEeqRwUQWk8jZQ%2Bp6t3zO4czouhLQjGKh9RPB8kc%3D&reserved=0 > 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. > > Thanks, > Venkata.