From: Henning Schild <henning.schild@siemens.com>
To: venkata.pyla@toshiba-tsip.com
Cc: isar-users@googlegroups.com, jan.kiszka@siemens.com,
dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: Re: [isar 0/1] Fix non-reproducible issue due to localepurge
Date: Mon, 11 Apr 2022 12:53:54 +0200 [thread overview]
Message-ID: <20220411125354.7ecbe49c@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220410170229.6369-1-venkata.pyla@toshiba-tsip.com>
Am Sun, 10 Apr 2022 22:32:28 +0530
schrieb venkata.pyla@toshiba-tsip.com:
> From: venkata pyla <venkata.pyla@toshiba-tsip.com>
>
> Hello all,
>
> Replying to this mail conversation,
> (https://groups.google.com/g/isar-users/c/JCgpWU_pFJU/m/IwlYTmzQBQAJ)
>
> For the problem "debconf cache non-reproducible", I figured out a
> solution in isar system itself.
Generating configuration items and placing them before a package gets
installed is very common. It is not only done by Isar but very likely
by many packages in debian that cater for other packages.
What you are suggesting is not a generic solution to "debconf cache"
being non-reproducible. It is just a quirk to hide the problem in that
one case for that one package.
Maybe the cache just needs to be excluded from the image, or cleaned or
whatever.
And i guess we should have some infrastructure in Isar to find
"non-reproducible" build issues also available for any layers. Because
layers is where the real complexity is, not those relatively boring
example images you find in isar.
regards,
Henning
> The problem is that, in isar system, in-order to remove unwanted
> locales from the system image, it is installing the localepurge
> package after its configuration is copied,
> due to this when the package post-installation script triggered the
> ucf check, it creates a debconf cache entry with the new configuration
> change (which is non-reproducible).
>
> This would be avoided if localpurge package is installed first and
> then copy required configuration to remove unwanted to locales from
> the system image.
>
> Created below patch to fix non-reproducible problem, please review
> and provide your feedback.
>
> venkata pyla (1):
> image-locales-extension: Do localepurge configuration after
> installation
>
> meta/classes/image-locales-extension.bbclass | 33
> ++++++++++---------- 1 file changed, 17 insertions(+), 16 deletions(-)
>
next prev parent reply other threads:[~2022-04-11 10:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 17:02 venkata.pyla
2022-04-10 17:02 ` [isar 1/1] image-locales-extension: Do localepurge configuration after installation venkata.pyla
2022-04-11 10:53 ` Henning Schild [this message]
2022-04-11 13:14 ` [isar 0/1] Fix non-reproducible issue due to localepurge Jan Kiszka
2022-04-13 12:15 ` Venkata.Pyla
2022-04-14 8:08 ` Henning Schild
2022-04-14 15:38 ` Jan Kiszka
2022-05-06 9:45 ` [isar][RFC] rootfs: clean debconf cache files venkata.pyla
2022-05-10 7:19 ` Venkata.Pyla
2022-06-08 14:40 ` Venkata.Pyla
2022-06-10 7:41 ` Anton Mikanovich
2022-06-16 3:54 ` Venkata.Pyla
2022-06-16 4:36 ` [PATCH] " venkata.pyla
2022-09-26 9:03 ` Anton Mikanovich
2022-06-09 6:04 ` [isar][RFC] " Jan Kiszka
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=20220411125354.7ecbe49c@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=venkata.pyla@toshiba-tsip.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