public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: venkata.pyla@toshiba-tsip.com, isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, henning.schild@siemens.com,
	kazuhiro3.hayashi@toshiba.co.jp, dinesh.kumar@toshiba-tsip.com
Subject: Re: [PATCH 0/2] Test for verifiying reproducible images
Date: Wed, 28 Dec 2022 11:40:06 +0300	[thread overview]
Message-ID: <78ac2552-aafa-10a9-e157-06aece3b7d83@ilbers.de> (raw)
In-Reply-To: <20221219144147.31245-1-venkata.pyla@toshiba-tsip.com>

19.12.2022 17:41, venkata.pyla@toshiba-tsip.com wrote:
> From: venkata pyla <venkata.pyla@toshiba-tsip.com>
>
> Hi,
>
> The below patch set will add the test for verifying the rootfs images
> are reproducible, it will help to identify the reproducible problems
> and also can verify the fixes that solves the problem.
>
> Please check if this can add to the isar testsuite and eventually helps
> to verify the reproducible problems in isar.
>
> Looking forward for your feedback.
>
> Thanks,
> Venkata.
>
> venkata pyla (2):
>    cibuilder.py: Add source_date_epoch to build configuration
>    repro-build-test.py: Test to check images are reproducible
>
>   testsuite/cibuilder.py        |  5 ++-
>   testsuite/repro-build-test.py | 68 +++++++++++++++++++++++++++++++++++
>   2 files changed, 72 insertions(+), 1 deletion(-)
>   create mode 100755 testsuite/repro-build-test.py
>
Applied to next, thanks.


  reply	other threads:[~2022-12-28  8:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  8:25 [PATCH] image.bbclass: set file timestamps inside the rootfs and initramfs image venkata.pyla
2022-11-07  8:50 ` Moessbauer, Felix
2022-11-09  6:56   ` Venkata.Pyla
2022-11-07  8:53 ` Henning Schild
2022-11-09  9:27   ` Venkata.Pyla
2022-11-10  7:12     ` Henning Schild
2022-11-20  7:53       ` [PATCH] scripts/repro-test.sh: script to test reproducibility of Isar image venkata.pyla
2022-11-22  7:28         ` Anton Mikanovich
2022-11-22  8:49           ` Venkata.Pyla
2022-12-19 14:41             ` [PATCH 0/2] Test for verifiying reproducible images venkata.pyla
2022-12-28  8:40               ` Anton Mikanovich [this message]
2023-01-02  6:24                 ` [PATCH] repro-build-test.py: Fix date_epoch time contains byte character b'' venkata.pyla
2023-01-11  5:42                   ` Uladzimir Bely
2022-12-19 14:41             ` [PATCH 1/2] cibuilder.py: Add source_date_epoch to build configuration venkata.pyla
2022-12-19 14:41             ` [PATCH 2/2] repro-build-test.py: Test to check images are reproducible venkata.pyla
2023-01-07  0:01               ` Henning Schild
2022-11-21  5:16       ` [PATCH] image.bbclass: set file timestamps inside the rootfs and initramfs image Venkata.Pyla
2022-11-10  9:52 ` Balasubramanian Sundaram
2022-11-10 10:03   ` Anton Mikanovich
2022-11-10 10:17     ` Balasubramanian Sundaram
2022-11-10 10:19       ` Balasubramanian Sundaram
2022-11-10 10:27       ` Anton Mikanovich
2022-11-10 10:51         ` Balasubramanian Sundaram
2022-11-10 16:30           ` Henning Schild
2022-11-10 17:05             ` Henning Schild

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=78ac2552-aafa-10a9-e157-06aece3b7d83@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