From: <Venkata.Pyla@toshiba-tsip.com>
To: <jan.kiszka@siemens.com>, <isar-users@googlegroups.com>
Cc: <amikan@ilbers.de>, <henning.schild@siemens.com>,
<kazuhiro3.hayashi@toshiba.co.jp>,
<dinesh.kumar@toshiba-tsip.com>
Subject: RE: [PATCH] image.bbclass: fix non-reproducible file time-stamps inside rootfs image
Date: Tue, 3 Jan 2023 05:54:41 +0000 [thread overview]
Message-ID: <OSYPR01MB5542143CC70D494D0937E929A4F49@OSYPR01MB5542.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <f5a8e3e8-30ad-9039-836f-5ce42b25567f@siemens.com>
>-----Original Message-----
>From: isar-users@googlegroups.com <isar-users@googlegroups.com> On Behalf
>Of Jan Kiszka
>Sent: 02 January 2023 21:03
>To: pyla venkata(TSIP TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>tsip.com>; isar-users@googlegroups.com
>Cc: amikan@ilbers.de; henning.schild@siemens.com; hayashi kazuhiro(林 和宏
>□SWC◯ACT) <kazuhiro3.hayashi@toshiba.co.jp>; dinesh kumar(TSIP
>TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>
>Subject: Re: [PATCH] image.bbclass: fix non-reproducible file time-stamps inside
>rootfs image
>
>On 02.01.23 15:58, venkata.pyla@toshiba-tsip.com wrote:
>> From: venkata pyla <venkata.pyla@toshiba-tsip.com>
>>
>> As part of reproducible-build work, the rootfs images generated on
>> same source should be identical between two builds.
>>
>> In this commit it tries to solve one of the non-reproducible problem
>> i.e. the rootfs file time-stamps generated during build time are not
>> reproducible, it uses one of the solution provided in the debian
>> live-build image project (refer [1]), it fixes by finding all the
>> files/folders that are gernerated newly and set the time-stamp
>> provided by `SOURCE_DATE_EPOCH` environment variable.
>>
>> [1] https://salsa.debian.org/live-team/live-build/-/merge_requests/218
>>
>
>Just out of curiosity: How does Yocto address this?
Yocto also does similar approach as debian live-build but in yocto it set the timestamp `REPRODUCIBLE_TIMESTAMP_ROOTFS` to all the rootfs files
See the reference code https://github.com/yoctoproject/poky/blob/master/meta/classes-recipe/image.bbclass#L673
whereas in debian live-build it assumes the files from the debian packages are reproducible so only the newly changed or created files are set to the timestamp `SOURCE_DATE_EPOCH`
>
>Jan
>
>> Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com>
>> ---
>> meta/classes/image.bbclass | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
>> index 813e1f3..f592a12 100644
>> --- a/meta/classes/image.bbclass
>> +++ b/meta/classes/image.bbclass
>> @@ -430,6 +430,15 @@ do_rootfs_finalize() {
>> "${ROOTFSDIR}/etc/apt/sources.list.d/bootstrap.list"
>>
>> rm -f "${ROOTFSDIR}/etc/apt/sources-list"
>> +
>> + # Set same time-stamps to the newly generated file/folders in the
>> + # rootfs image for the purpose of reproducible builds.
>> + test ! -z "${SOURCE_DATE_EPOCH}" && \
>> + find ${ROOTFSDIR} -newermt \
>> + "$(date -d@${SOURCE_DATE_EPOCH} '+%Y-%m-%d %H:%M:%S')" \
>> + -printf "%y %p\n" \
>> + -exec touch '{}' -h -d@${SOURCE_DATE_EPOCH} ';'
>> +
>> EOSUDO
>> }
>> addtask rootfs_finalize before do_rootfs after do_rootfs_postprocess
>
>--
>Siemens AG, Technology
>Competence Center Embedded Linux
>
>--
>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/f5a8e3e8-30ad-9039-836f-
>5ce42b25567f%40siemens.com.
next prev parent reply other threads:[~2023-01-03 5:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 14:58 venkata.pyla
2023-01-02 15:32 ` Jan Kiszka
2023-01-03 5:54 ` Venkata.Pyla [this message]
2023-01-02 16:44 ` Henning Schild
2023-01-03 8:05 ` Jan Kiszka
2023-01-03 18:51 ` Henning Schild
2023-01-03 14:10 ` Venkata.Pyla
2023-01-03 19:05 ` Henning Schild
2023-01-04 7:54 ` Venkata.Pyla
2023-01-04 9:29 ` Henning Schild
2023-01-04 13:48 ` Venkata.Pyla
2023-01-04 13:53 ` Henning Schild
2023-01-04 14:35 ` Jan Kiszka
2023-01-04 14:50 ` Venkata.Pyla
2023-01-04 15:07 ` Henning Schild
2023-01-04 15:34 ` Venkata.Pyla
2023-01-05 6:18 ` [PATCH v2 0/1] Fix for reproducible build issue venkata.pyla
2023-01-05 6:18 ` [PATCH v2 1/1] image.bbclass: fix non-reproducible file time-stamps inside rootfs venkata.pyla
2023-01-05 8:19 ` Henning Schild
2023-01-05 9:50 ` Moessbauer, Felix
2023-01-05 17:05 ` Henning Schild
2023-01-06 2:08 ` Moessbauer, Felix
2023-01-05 13:52 ` Venkata.Pyla
2023-01-05 15:12 ` [PATCH v3 0/1] Fix for reproducible build issue venkata.pyla
2023-01-05 15:12 ` [PATCH v3 1/1] image.bbclass: fix non-reproducible file time-stamps inside rootfs venkata.pyla
2023-01-06 9:45 ` Moessbauer, Felix
2023-01-06 10:17 ` Venkata.Pyla
2023-01-05 16:49 ` [PATCH v2 " Henning Schild
2023-01-04 15:01 ` [PATCH] image.bbclass: fix non-reproducible file time-stamps inside rootfs image Henning Schild
2023-01-04 15:27 ` 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=OSYPR01MB5542143CC70D494D0937E929A4F49@OSYPR01MB5542.jpnprd01.prod.outlook.com \
--to=venkata.pyla@toshiba-tsip.com \
--cc=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 \
/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