From: Anton Mikanovich <amikan@ilbers.de>
To: Venkata.Pyla@toshiba-tsip.com, isar-users@googlegroups.com
Cc: henning.schild@siemens.com, jan.kiszka@siemens.com,
dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: Is it safe to remove debconf cache files in isar system
Date: Fri, 17 Dec 2021 19:56:37 +0300 [thread overview]
Message-ID: <1a3ee03f-4749-859e-c6cb-7eb3e8cc11bc@ilbers.de> (raw)
In-Reply-To: <OSYPR01MB554254B35D37230B04195ED4A4779@OSYPR01MB5542.jpnprd01.prod.outlook.com>
16.12.2021 10:47, Venkata.Pyla@toshiba-tsip.com wrote:
> Hi,
>
> I am working to fix some reproducible build failures in isar system, as part of this I wanted to know some ideas to fix it.
>
> I am checking the reproducible failures as below:
> $ cd 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
>
> Below is one reproducible problem I picked:
> In debconf db file the contents were different after two subsequent builds,
>
> Part of the debconf db file where the difference is found (/var/cache/debconf/config.dat)
> Build1:
> Name: ucf/changeprompt
> Template: ucf/changeprompt
> Value: keep_current
> Owners: ucf
> Variables:
> BASENAME = locale.nopurge
> FILE = /etc/locale.nopurge
> NEW = /etc/locale.nopurge.29308
>
> Build2:
> Name: ucf/changeprompt
> Template: ucf/changeprompt
> Value: keep_current
> Owners: ucf
> Variables:
> BASENAME = locale.nopurge
> FILE = /etc/locale.nopurge
> NEW = /etc/locale.nopurge.19132
>
> The probable solution I am thinking of is:
> 1. remove the debconf cache files (rm -f /var/cache/debconf/*)
> 2. Fix the debconf in such a way it generates same package configuration on every build
>
> The first solution is easy, but I am worried if those package configuration files maybe required in future when the package is updating
> The second solution would need more investigation at debconf package side.
>
> Any ideas or suggestion would be very grateful.
>
> Thanks,
> Venkata.
>
Because both questions are not really Isar-related, but more
Debian-related, maybe it's better to duplicate them on
debian-user@lists.debian.org ?
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2021-12-17 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 7:47 Venkata.Pyla
2021-12-17 16:56 ` Anton Mikanovich [this message]
2022-02-14 19:35 ` Venkata.Pyla
2022-02-15 16:13 ` Baurzhan Ismagulov
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=1a3ee03f-4749-859e-c6cb-7eb3e8cc11bc@ilbers.de \
--to=amikan@ilbers.de \
--cc=Venkata.Pyla@toshiba-tsip.com \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=henning.schild@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
/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