public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
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: Thu, 14 Apr 2022 10:08:17 +0200	[thread overview]
Message-ID: <20220414100817.61afa3b9@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <TYBPR01MB5549CA9893844B4AFD6C921CA4EC9@TYBPR01MB5549.jpnprd01.prod.outlook.com>

Am Wed, 13 Apr 2022 12:15:47 +0000
schrieb <Venkata.Pyla@toshiba-tsip.com>:

> Hi Henning Schild,
> 
> Thank you for the comments.
> 
> Please find my comments inline.
> 
> >-----Original Message-----
> >From: isar-users@googlegroups.com <isar-users@googlegroups.com> On
> >Behalf Of Henning Schild
> >Sent: 11 April 2022 16:24
> >To: pyla venkata(TSIP) <Venkata.Pyla@toshiba-tsip.com>
> >Cc: isar-users@googlegroups.com; jan.kiszka@siemens.com; dinesh
> >kumar(TSIP) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林
> >和宏 □SWC◯ACT) <kazuhiro3.hayashi@toshiba.co.jp>
> >Subject: Re: [isar 0/1] Fix non-reproducible issue due to localepurge
> >
> >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.  
> 
> Yes I agree with you, Ideally this should be fixed from each package
> if they have such non-reproducible behaviour.

I would want to bet that there are some packages which show similar
problems directly from upstream, but likely more in downstream isar
layers. Because a debian package on its own will simply bring its
default config, every deviation will come from something else ... like
ansible, puppet, isar ... 

> I reported a bug today in the Debian package bug-tracking system,
> though I don’t have solution for that, but I want to start discussion
> and get some solution going forward.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009639

I am not sure that is a valid debian but either, they could just tell
you to install first and configure later. The non default config is not
coming from debian.

> Meanwhile we can use this trick to bypass non-reproducible problem,
> what's your opinion?

I would prefer a way/idea to deal with such problems in
general. Like a quality checker script that would warn about a
populated conf cache, or a postprocess rule to clear the cache.

That would be a real good thing, while your patch is only a workaround
for an exotic potential problem most people do not really care too much
about.
We know anyways that an isar build is never 100% reproducible ... just
try a wic run and binary diff the resulting images instead of diffing
the files on mounted partitions.

regards,
Henning

> >
> >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(-) 
> >
> >--
> >You received this message because you are subscribed to the Google
> >Groups "isar-users" group.
> >To unsubscribe from this group and stop receiving emails from it,
> >send an email to isar-users+unsubscribe@googlegroups.com.
> >To view this discussion on the web visit
> >https://groups.google.com/d/msgid/isar-
> >users/20220411125354.7ecbe49c%40md1za8fc.ad001.siemens.net.  
> 


  reply	other threads:[~2022-04-14  8:08 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 ` [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 [this message]
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=20220414100817.61afa3b9@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=Venkata.Pyla@toshiba-tsip.com \
    --cc=dinesh.kumar@toshiba-tsip.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