13509 2019-09-10 21:04:50 +0000 reproducible QA: Fake time in the future for better reproducibility 2026-10-21 07:30:59 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple RESOLVED FIXED Medium enhancement 6.99 1 JPEWhacker unassigned mathieu.dubois-briand meta.mr.watcher meta.watcher randy.macleod sangeeta.jain mathieu.dubois-briand --- --- No (bug/feature does not impact docs) oldest_to_newest 84913 0 JPEWhacker 2019-09-10 21:04:50 +0000 The QA check should use 'faketime' or equivalent to fake the time in the future when building the second test build. This is in line with the debian reproducible build tests, and ensures recipes are not including timestamps. An ideal time to move the clock forward by might be 34308122 seconds. This is 397 days, 2 hours, 2 minutes, and 2 seconds in the future. This value has a few useful properties: * It is always at least one year ahead of the real time * It is always a different month than the real time * It is always a different day of the week than the real time * It is always a different day of the month * It is always a different hour of the day * It is always a different minute * It is always a different second The reason for always adding 2 instead of one is to account for any ambiguity related to leap year, leap seconds, DST, and leap minutes if they every become a thing. 97131 1 randy.macleod 2023-10-30 15:37:29 +0000 Build move to 5.0 -- ../Randy 98830 2 randy.macleod 2024-04-25 01:13:54 +0000 Bulk move of 5.0 medium importance issues to 5.99. Move to 5.1 if you want to actively work on an issue. 98852 3 randy.macleod 2024-04-25 01:23:09 +0000 Move to 5.99 since no one is actively working on this issue. Move to 5.x if you start on a task, please. 107140 4 mathieu.dubois-briand 2026-10-21 07:30:59 +0000 Implemented and merged: https://git.openembedded.org/openembedded-core/commit/?id=537ee506b3cfd6ecc53315759763bd25ab38f63a