public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: venkata.pyla@toshiba-tsip.com
To: isar-users@googlegroups.com
Cc: venkata pyla <venkata.pyla@toshiba-tsip.com>,
	henning.schild@siemens.com, jan.kiszka@siemens.com,
	dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: [isar 0/1] Fix non-reproducible issue due to localepurge
Date: Sun, 10 Apr 2022 22:32:28 +0530	[thread overview]
Message-ID: <20220410170229.6369-1-venkata.pyla@toshiba-tsip.com> (raw)

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.

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(-)

-- 
2.20.1



             reply	other threads:[~2022-04-10 17:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10 17:02 venkata.pyla [this message]
2022-04-10 17:02 ` [isar 1/1] image-locales-extension: Do localepurge configuration after installation venkata.pyla
2022-04-11 10:53 ` [isar 0/1] Fix non-reproducible issue due to localepurge Henning Schild
2022-04-11 13:14   ` 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=20220410170229.6369-1-venkata.pyla@toshiba-tsip.com \
    --to=venkata.pyla@toshiba-tsip.com \
    --cc=dinesh.kumar@toshiba-tsip.com \
    --cc=henning.schild@siemens.com \
    --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