Bug 13754 - ca-certificates encodes timestamp in package files
Summary: ca-certificates encodes timestamp in package files
Status: RESOLVED DUPLICATE of bug 13763
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: High normal
Target Milestone: 3.1 M3
Assignee: Joshua Watt
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-01-26 03:54 UTC by Joshua Watt
Modified: 2020-02-04 16:15 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Watt 2020-01-26 03:54:00 UTC
The ca-certificates package encodes timestamps in resulting deb files. See: https://autobuilder.yocto.io/pub/repro-fail/build-st-12270/
Comment 1 Alexander Kanavin 2020-01-31 13:41:43 UTC
I am not sure what happens here. The first build has timestamps dating to Jan 1 1970, the second to Jan 11 2019. The files are identical. After making a local build, I also get timestamps of Jan 11 2019 and debs identical to the second build. It doesn't seem like ca-certificates itself is doing anything particularly unusual.

Was there a time setting glitch on one of the builders perhaps, or something builder-specific that forced the reproducible class to fall back to 1970?
Comment 2 Alexander Kanavin 2020-01-31 14:53:05 UTC
Apparently the Jan 11 2019 is the date of the last git commit, so I am not sure how SOURCE_DATE_EPOCH became something else.
Comment 3 Joshua Watt 2020-01-31 14:55:11 UTC
Yes it appears to be that on the first build, SOURCE_DATE_EPOCH is erronously 0, see https://bugzilla.yoctoproject.org/show_bug.cgi?id=13763
Comment 4 Joshua Watt 2020-01-31 16:59:22 UTC
OK, I think I've convinced myself that this is indeed a duplicate of https://bugzilla.yoctoproject.org/show_bug.cgi?id=13754. The root cause is the same, WORKDIR get changed by anon python after attempt to read the SDE file, although in this case it is because of allarch.bbclass instead of AUTOINC.
Comment 5 Joshua Watt 2020-02-04 16:15:29 UTC
This is a duplicate of 13763 and was fixed with it.

*** This bug has been marked as a duplicate of bug 13763 ***