Bug 13755

Summary: binutils-doc man pages have build timestamp encoded in them
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Joshua Watt <JPEWhacker>
Component: coreAssignee: Trevor Gamblin <tvgamblin>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: alex.kanavin, meta.mr.watcher, meta.watcher, randy.macleod
Version: unspecified   
Target Milestone: 3.1 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Joshua Watt 2020-01-26 04:00:55 UTC
The binutils man pages appear to have the build timestamp encoded in them. See: https://autobuilder.yocto.io/pub/repro-fail/build-st-12270/
Comment 1 Alexander Kanavin 2020-01-31 14:51:37 UTC
The timestamp is taken from SOURCE_DATE_EPOCH, so the difference comes from that variable not being set deterministically. In my local testing I reliably get 2019-12-08 (the date of the last git commit), so can't reproduce the situation where it would be something else :(
Comment 2 Joshua Watt 2020-01-31 14:55:50 UTC
OK, thanks. I think we might be able to close this as a duplicate of https://bugzilla.yoctoproject.org/show_bug.cgi?id=13763 then
Comment 3 Alexander Kanavin 2020-01-31 15:35:02 UTC
I am not sure this one is a duplicate. The 'wrong' timestamp here is not zero, but the current time.
Comment 4 Alexander Kanavin 2020-01-31 15:42:36 UTC
What I suspect happens here is old version of pod2man from the host is used. It started honoring SOURCE_DATE_EPOCH only in the beginning of 2016, and we use distros (everyone's favorite centos 7) that predate that.
Comment 6 Alexander Kanavin 2020-02-07 20:42:41 UTC
Patch is merged into master