package_rpm: set clamp_mtime_to_source_date_epoch to 0
PATCH 1/1 package_rpm: set clamp_mtime_to_source_date_epoch to 0
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.
--- meta/classes-global/package_rpm.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/classes-global/package_rpm.bbclass +1 -1
@@ -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}'"
Signature · 1 line
2.34.1
Quoted 3 lines · Bin Lan via lists.openembedded.org
warning: %clamp_mtime_to_source_date_epoch is deprecated, please use %build_mtime_policy
This change sets
clamp_mtime_to_source_date_epochto 0 indo_package_rpm()to remove the warning.
But does this change introduce issues? This was originally set for a reason, what was the reason? Should it be replaced with built_mtime_policy as suggested?
meta/classes-global/package_rpm.bbclass python do_package_rpm () { · line 702
Quoted 2 lines
meta/classes-global/package_rpm.bbclass +1
-1- cmd = cmd + " --define 'clamp_mtime_to_source_date_epoch 1'" + cmd = cmd + " --define 'clamp_mtime_to_source_date_epoch 0'"
Alex