From: Bin Lan <bin.lan.cn@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][PATCH] package_rpm: set clamp_mtime_to_source_date_epoch to 0
Date: Fri, 3 Jan 2025 14:32:24 +0800 [thread overview]
Message-ID: <20250103063224.1988264-1-bin.lan.cn@windriver.com> (raw)
There is the following warning when the do_package_write_rpm task is executed
when bitbake linux-yocto:
warning: %clamp_mtime_to_source_date_epoch is deprecated, please use %build_mtime_policy
This change sets clamp_mtime_to_source_date_epoch to 0 in do_package_rpm() to remove the warning.
Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
---
meta/classes-global/package_rpm.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes-global/package_rpm.bbclass b/meta/classes-global/package_rpm.bbclass
index 3579d0d695..d7b57e301b 100644
--- a/meta/classes-global/package_rpm.bbclass
+++ b/meta/classes-global/package_rpm.bbclass
@@ -699,7 +699,7 @@ python do_package_rpm () {
cmd = cmd + " --define '_smp_ncpus_max 4'"
cmd = cmd + " --define '_source_payload %s'" % rpmbuild_compmode
cmd = cmd + " --define '_binary_payload %s'" % rpmbuild_compmode
- cmd = cmd + " --define 'clamp_mtime_to_source_date_epoch 1'"
+ cmd = cmd + " --define 'clamp_mtime_to_source_date_epoch 0'"
cmd = cmd + " --define 'use_source_date_epoch_as_buildtime 1'"
cmd = cmd + " --define '_buildhost reproducible'"
cmd = cmd + " --define '__font_provides %{nil}'"
--
2.34.1
next reply other threads:[~2025-01-03 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 6:32 Bin Lan [this message]
2025-01-03 10:24 ` [OE-core][PATCH] package_rpm: set clamp_mtime_to_source_date_epoch to 0 Alexander Kanavin
[not found] <18171B17FD27DA44.21892@lists.openembedded.org>
2025-01-03 7:32 ` Bin Lan
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=20250103063224.1988264-1-bin.lan.cn@windriver.com \
--to=bin.lan.cn@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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