From: Anton Mikanovich <amikan@ilbers.de>
To: venkata.pyla@toshiba-tsip.com
Cc: isar-users@googlegroups.com, henning.schild@siemens.com,
jan.kiszka@siemens.com, dinesh.kumar@toshiba-tsip.com,
kazuhiro3.hayashi@toshiba.co.jp
Subject: Re: [PATCH] rootfs: clean debconf cache files
Date: Mon, 26 Sep 2022 12:03:47 +0300 [thread overview]
Message-ID: <5b55ac47-302d-242d-d235-2abe5d877a64@ilbers.de> (raw)
In-Reply-To: <20220616043657.3750-1-venkata.pyla@toshiba-tsip.com>
16.06.2022 07:36, venkata.pyla@toshiba-tsip.com wrote:
> From: venkata pyla <venkata.pyla@toshiba-tsip.com>
>
> Cleaning the debconf cache files for the purpose of generating
> reproducible system image.
>
> The debconf cache database sometime generates with non-reproducible
> contents because of some packages behaviour (e.g: localepurge), reported
> this to package bug tracking system[1], but because this problem is not
> with one particular package and can happen with other packages also,
> this should be solved in common place to address reproducibility
> problem, discussing with Reproducible-builds community[2] to find some
> common solution for this problem.
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009639
> [2] https://lists.reproducible-builds.org/pipermail/rb-general/2022-April/002546.html
>
> Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com>
> Suggested-by: Henning Schild <henning.schild@siemens.com>
Applied to next, thanks.
Sorry for delay, it looks like we've lost this patch after the latest
release.
next prev parent reply other threads:[~2022-09-26 9:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 17:02 [isar 0/1] Fix non-reproducible issue due to localepurge 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
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 [this message]
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=5b55ac47-302d-242d-d235-2abe5d877a64@ilbers.de \
--to=amikan@ilbers.de \
--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 \
--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