From: <Venkata.Pyla@toshiba-tsip.com>
To: <isar-users@googlegroups.com>
Cc: <henning.schild@siemens.com>, <jan.kiszka@siemens.com>,
<daniel.sangorrin@toshiba.co.jp>, <dinesh.kumar@toshiba-tsip.com>
Subject: [isar] reproducible build failures
Date: Fri, 3 Sep 2021 15:19:21 +0000 [thread overview]
Message-ID: <OSYPR01MB5542D8A9E0471070B8CE773BA4CF9@OSYPR01MB5542.jpnprd01.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2592 bytes --]
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.
Thanks,
Venkata.
[-- Attachment #2: Type: text/html, Size: 9749 bytes --]
next reply other threads:[~2021-09-03 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 15:19 Venkata.Pyla [this message]
2021-09-03 16:30 ` Jan Kiszka
2021-09-03 17:10 ` Henning Schild
2021-09-06 4:57 ` Jan Kiszka
2021-09-06 8:41 ` Henning Schild
2021-09-14 7:29 ` Venkata.Pyla
2021-09-14 10:41 ` Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OSYPR01MB5542D8A9E0471070B8CE773BA4CF9@OSYPR01MB5542.jpnprd01.prod.outlook.com \
--to=venkata.pyla@toshiba-tsip.com \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox