The ca-certificates package encodes timestamps in resulting deb files. See: https://autobuilder.yocto.io/pub/repro-fail/build-st-12270/
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?
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.
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
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.
This is a duplicate of 13763 and was fixed with it. *** This bug has been marked as a duplicate of bug 13763 ***