public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: <Venkata.Pyla@toshiba-tsip.com>
To: <felix.moessbauer@siemens.com>, <isar-users@googlegroups.com>
Cc: <jan.kiszka@siemens.com>, <daniel.bovensiepen@siemens.com>,
	<henning.schild@siemens.com>
Subject: RE: [PATCH 00/11] Make rootfs build reproducible
Date: Wed, 11 Jan 2023 09:04:27 +0000	[thread overview]
Message-ID: <OSYPR01MB5542CB01CEB09589B58DC493A4FC9@OSYPR01MB5542.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20230111041140.3460393-1-felix.moessbauer@siemens.com>



>-----Original Message-----
>From: isar-users@googlegroups.com <isar-users@googlegroups.com> On
>Behalf Of Felix Moessbauer
>Sent: 11 January 2023 09:41
>To: isar-users@googlegroups.com
>Cc: jan.kiszka@siemens.com; daniel.bovensiepen@siemens.com;
>henning.schild@siemens.com; pyla venkata(TSIP TMIEC ODG Porting)
><Venkata.Pyla@toshiba-tsip.com>; Felix Moessbauer
><felix.moessbauer@siemens.com>
>Subject: [PATCH 00/11] Make rootfs build reproducible
>
>This series finally makes the rootfs generation bit-reproducible from debian
>bullseye on. Parts of it have already been sent as individual patches. However,
>image reproducibility can only be achived once all parts are reproducible itself.
>By that, these patches are included in this series as well.
>
>With this series, the following parts are now fully reproducible.
>This has been tested on the isar-image-base target.
>
>- custom initramfs (creation and updates)
>- debian initramfs (only updates are relevant)
>- custom kernel (debian kernel is reproducible itself)
>- rootfs itself
>- tar file generation (<image>.tar)
>- ext4 generation (only from bookworm on, more tests needed)
>
>Other parts that are still not reproducible are:
>
>- WIC (should be solved in OE already)
>- containers (untested yet)

This is great work, thank you.

>
>Best regards,
>Felix Moessbauer
>Siemens AG
>
>Felix Moessbauer (10):
>  fix rebuild of rootfs_finalize task
>  rootfs postprocess: clean python cache
>  remove non-portable ldconfig aux-cache
>  generate deterministic clear-text password hash
>  update debian initramfs in deterministic mode
>  create custom initramfs in deterministic mode
>  make deb_add_changelog idempotent
>  deb_add_changelog: set timestamp to valid epoch
>  deb_add_changelog: use SOURCE_DATE_EPOCH
>  make custom linux-image bit-by-bit reproducible
>
>venkata pyla (1):
>  image.bbclass: fix non-reproducible file time-stamps inside rootfs
>
> meta-isar/conf/local.conf.sample              | 10 +++++++++
> meta/classes/debianize.bbclass                | 22 +++++++++++++------
> meta/classes/image-account-extension.bbclass  | 10 ++++++++-
> meta/classes/image.bbclass                    | 21 ++++++++++++++++--
> meta/classes/initramfs.bbclass                |  5 +++++
> meta/classes/rootfs.bbclass                   | 13 +++++++++++
> .../linux/files/debian/isar/build.tmpl        |  1 +
> .../linux/files/debian/rules.tmpl             | 14 +++++++++++-
> meta/recipes-kernel/linux/linux-custom.inc    |  2 ++
> 9 files changed, 87 insertions(+), 11 deletions(-)
>
>--
>2.34.1
>
>--
>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/20230111041140.3460393-1-
>felix.moessbauer%40siemens.com.

      parent reply	other threads:[~2023-01-11  9:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  4:11 Felix Moessbauer
2023-01-11  4:11 ` [PATCH 01/11] fix rebuild of rootfs_finalize task Felix Moessbauer
2023-01-11  4:11 ` [PATCH 02/11] image.bbclass: fix non-reproducible file time-stamps inside rootfs Felix Moessbauer
2023-01-11  4:11 ` [PATCH 03/11] rootfs postprocess: clean python cache Felix Moessbauer
2023-01-11  8:06   ` Henning Schild
2023-01-11  8:23     ` Moessbauer, Felix
2023-01-11 12:47       ` Henning Schild
2023-01-11 13:18         ` Moessbauer, Felix
2023-01-11 13:23           ` Jan Kiszka
2023-01-11  4:11 ` [PATCH 04/11] remove non-portable ldconfig aux-cache Felix Moessbauer
2023-01-11  8:19   ` Henning Schild
2023-01-11  8:31     ` Moessbauer, Felix
2023-01-11 12:52       ` Henning Schild
2023-01-11  4:11 ` [PATCH 05/11] generate deterministic clear-text password hash Felix Moessbauer
2023-01-11  8:21   ` Henning Schild
2023-01-11  4:11 ` [PATCH 06/11] update debian initramfs in deterministic mode Felix Moessbauer
2023-01-11  8:23   ` Henning Schild
2023-01-11  8:39     ` Moessbauer, Felix
2023-01-11 12:55       ` Henning Schild
2023-01-11  4:11 ` [PATCH 07/11] create custom " Felix Moessbauer
2023-01-11  4:11 ` [PATCH 08/11] make deb_add_changelog idempotent Felix Moessbauer
2023-01-11  4:11 ` [PATCH 09/11] deb_add_changelog: set timestamp to valid epoch Felix Moessbauer
2023-01-11  4:11 ` [PATCH 10/11] deb_add_changelog: use SOURCE_DATE_EPOCH Felix Moessbauer
2023-01-11  8:49   ` Henning Schild
2023-01-11  9:06     ` Moessbauer, Felix
2023-01-11  4:11 ` [PATCH 11/11] make custom linux-image bit-by-bit reproducible Felix Moessbauer
2023-01-11  6:51 ` [PATCH 00/11] Make rootfs build reproducible Jan Kiszka
2023-01-11  9:04 ` Venkata.Pyla [this message]

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=OSYPR01MB5542CB01CEB09589B58DC493A4FC9@OSYPR01MB5542.jpnprd01.prod.outlook.com \
    --to=venkata.pyla@toshiba-tsip.com \
    --cc=daniel.bovensiepen@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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