public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Adithya Balakumar <Adithya.Balakumar@toshiba-tsip.com>,
	isar-users@googlegroups.com, amikan@ilbers.de
Cc: kazuhiro3.hayashi@toshiba.co.jp, dinesh.kumar@toshiba-tsip.com,
	shivanand.kunijadar@toshiba-tsip.com,
	sai.sathujoda@toshiba-tsip.com
Subject: Re: [PATCH v1 0/1] Set hash-seed for empty ext partition
Date: Tue, 25 Jun 2024 09:37:53 +0200	[thread overview]
Message-ID: <2f491241-dbff-4af1-8f41-8dd141211d47@siemens.com> (raw)
In-Reply-To: <20240625065032.595783-1-Adithya.Balakumar@toshiba-tsip.com>

On 25.06.24 08:50, Adithya Balakumar wrote:
> ext filesystems require a hash_seed to generate deterministic directory 
> indexes for reproducible builds. This is handled by wic in the case where 
> the rootfs plugin is used but this not handled in the case when an empty 
> ext4 partition is deployed.
> 
> This patch is also shared with openembedded-core and also accepted. 
> Upstream commit: 0202fb594fb05098cb8d8b6088e63beb40b5906e
> 
> Adithya Balakumar (1):
>   wic/partition.py: Set hash_seed for empty ext partition
> 
>  scripts/lib/wic/partition.py | 37 ++++++++++++++++++++++--------------
>  1 file changed, 23 insertions(+), 14 deletions(-)
> 

Shouldn't we sync to a wic revision >= the one containing this?

Jan

-- 
Siemens AG, Technology
Linux Expert Center


  parent reply	other threads:[~2024-06-25  7:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25  6:50 Adithya Balakumar
2024-06-25  6:50 ` [PATCH v1 1/1] wic/partition.py: Set hash_seed " Adithya Balakumar
2024-06-25  7:37 ` Jan Kiszka [this message]
2024-06-25 13:09   ` [PATCH v1 0/1] Set hash-seed " Anton Mikanovich
2024-06-25 14:30     ` Jan Kiszka
2024-06-26  4:35       ` Adithya.Balakumar

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=2f491241-dbff-4af1-8f41-8dd141211d47@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Adithya.Balakumar@toshiba-tsip.com \
    --cc=amikan@ilbers.de \
    --cc=dinesh.kumar@toshiba-tsip.com \
    --cc=isar-users@googlegroups.com \
    --cc=kazuhiro3.hayashi@toshiba.co.jp \
    --cc=sai.sathujoda@toshiba-tsip.com \
    --cc=shivanand.kunijadar@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