| Summary: | binutils-doc man pages have build timestamp encoded in them | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Joshua Watt <JPEWhacker> |
| Component: | core | Assignee: | 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 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 :( 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 I am not sure this one is a duplicate. The 'wrong' timestamp here is not zero, but the current time. 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. Patch is merged into master |