public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: <Adithya.Balakumar@toshiba-tsip.com>
To: <amikan@ilbers.de>, <florian.bezdeka@siemens.com>,
	<venkata1.pyla@toshibaap.onmicrosoft.com>,
	<felix.moessbauer@siemens.com>, <isar-users@googlegroups.com>,
	<ubely@ilbers.de>
Cc: <jan.kiszka@siemens.com>, <kazuhiro3.hayashi@toshiba.co.jp>,
	<dinesh.kumar@toshiba-tsip.com>, <venkatapyla4@gmail.com>
Subject: RE: [PATCH 3/5] wic: use E2FSPROGS_FAKE_TIME and hash_seed to generate reproducible ext4 images
Date: Wed, 13 Mar 2024 10:01:07 +0000	[thread overview]
Message-ID: <TYCPR01MB9669B38183C90BC9B47B3858C42A2@TYCPR01MB9669.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <ae651d5f-697b-43c9-be69-22814be95fc4@ilbers.de>

Hello Anton,

Hope this message finds you well.

Just wanted to follow up on a previous mail regarding wic and other related updates from openembedded-core. You had mentioned about the updates from openembedded-core to be handled right after the release of ISAR v0.10

Would like to understand if there are any plans for wic and other related updates from openembedded-core.

Thanks and Regards,
Adithya Balakumar

-----Original Message-----
From: Anton Mikanovich <amikan@ilbers.de> 
Sent: Thursday, December 28, 2023 3:40 PM
To: Florian Bezdeka <florian.bezdeka@siemens.com>; pyla venkata(TSIP TMIEC ODG Porting) <Venkata.Pyla@toshiba-tsip.com>; felix.moessbauer@siemens.com; isar-users@googlegroups.com; Uladzimir Bely <ubely@ilbers.de>
Cc: jan.kiszka@siemens.com; hayashi kazuhiro(林 和宏 DME ○DIG□MPS○MP4) <kazuhiro3.hayashi@toshiba.co.jp>; dinesh kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; venkatapyla4@gmail.com; balakumar adithya(TSIP TEUR) <Adithya.Balakumar@toshiba-tsip.com>
Subject: Re: [PATCH 3/5] wic: use E2FSPROGS_FAKE_TIME and hash_seed to generate reproducible ext4 images

28/12/2023 10:47, Florian Bezdeka wrote:
> On Thu, 2023-12-28 at 06:02 +0000, Venkata.Pyla@toshiba-tsip.com wrote:
>> This patch [1] has been merged now in upstream OE-core,
>>   now the required patches should be taken to ISAR, is there any timeline to bring the OE-core changes to ISAR or should we apply the required changes to ISAR manually?
>>
>> [1] 
>> https://github.com/openembedded/openembedded-core/commit/bb822ab75de0
>> 020572058090439b93cc56bbf7e0
> That's great! Thanks for taking care.
>
> I added two guys from Ilbers, maybe they have an update pending 
> already or can comment on the timeline. Anton, Uladzimir any comments?
>
> In general it's a good idea to come up with a patch to speed things up.
>
> The last update was done in 64af29bcc4b0 ("wic: Update to the latest 
> revision"). Might be used as inspiration.
>
> Florian
Hello,

We are going to make v0.10 release soon and probably can take care of externals (like WIC, OE libs and Bitbake) update right after that.

  reply	other threads:[~2024-03-13 10:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHaKSPYp2dXzOOhJUivzLFOKAgd4rF2a70A>
2023-12-07 15:41 ` [PATCH 0/5] Make ext4 images reproducible venkata.pyla
2023-12-07 15:41   ` [PATCH 1/5] linux-module: Use debug-prefix-map to build modules deterministically venkata.pyla
2023-12-08 10:27     ` MOESSBAUER, Felix
2023-12-07 15:41   ` [PATCH 2/5] wic: Set file system uuid to ext4 partitions venkata.pyla
2023-12-07 15:41   ` [PATCH 3/5] wic: use E2FSPROGS_FAKE_TIME and hash_seed to generate reproducible ext4 images venkata.pyla
2023-12-08 10:33     ` MOESSBAUER, Felix
2023-12-08 18:14       ` Venkata.Pyla
2023-12-09 11:07         ` Florian Bezdeka
2023-12-12 14:06           ` Venkata.Pyla
2023-12-28  6:02             ` Venkata.Pyla
2023-12-28  8:47               ` Florian Bezdeka
2023-12-28 10:10                 ` Anton Mikanovich
2024-03-13 10:01                   ` Adithya.Balakumar [this message]
2024-03-13 16:00                     ` Anton Mikanovich
2024-03-14  4:37                       ` Adithya.Balakumar
2024-04-25  6:24                       ` MOESSBAUER, Felix
2024-04-25  6:30                         ` Jan Kiszka
2024-04-25  7:02                           ` MOESSBAUER, Felix
2024-04-26  8:58                         ` Anton Mikanovich
2024-04-23  9:17     ` MOESSBAUER, Felix
2024-07-05 12:13       ` Adithya Balakumar
2024-07-08 10:43         ` 'MOESSBAUER, Felix' via isar-users
     [not found]           ` <CAM=oSXcw+sH3VYsstvDmRbLTK-H0ncFEbuqOhG2R0_P4bUYXjw@mail.gmail.com>
2024-07-08 11:12             ` Adithya.Balakumar
2023-12-07 15:41   ` [PATCH 4/5] wic: honor the SOURCE_DATE_EPOCH in case of updated fstab venkata.pyla
2023-12-07 15:41   ` [PATCH 5/5] wic: make ext2/3/4 images reproducible venkata.pyla
2023-12-08 10:29   ` [PATCH 0/5] Make ext4 " MOESSBAUER, Felix
2023-12-08 18:12     ` Venkata.Pyla

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=TYCPR01MB9669B38183C90BC9B47B3858C42A2@TYCPR01MB9669.jpnprd01.prod.outlook.com \
    --to=adithya.balakumar@toshiba-tsip.com \
    --cc=amikan@ilbers.de \
    --cc=dinesh.kumar@toshiba-tsip.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kazuhiro3.hayashi@toshiba.co.jp \
    --cc=ubely@ilbers.de \
    --cc=venkata1.pyla@toshibaap.onmicrosoft.com \
    --cc=venkatapyla4@gmail.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