Bug 16278 - colord compile fails with SOURCE_DATE_EPOCH="0"
Summary: colord compile fails with SOURCE_DATE_EPOCH="0"
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: oe-core other (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: 0.0.0
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2026-05-04 21:13 UTC by Michael Mitchell
Modified: 2026-05-07 14:47 UTC (History)
2 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 Michael Mitchell 2026-05-04 21:13:19 UTC
solution for bbappend in an alternative layer; this comes when meta-updater is setting global SOURCE_DATE_EPOCH to 0.

# colord's cd_create_profile native tool rejects SOURCE_DATE_EPOCH=0 with
# "$SOURCE_DATE_EPOCH invalid 0". Override it with a valid positive epoch
# (1980-01-01 UTC) which satisfies the g_ascii_strtoull != 0 check.
do_compile:prepend() {
    export SOURCE_DATE_EPOCH="315532800"
}
Comment 1 Michael Mitchell 2026-05-04 21:15:25 UTC
found first with scarthgap
Comment 2 Randy MacLeod 2026-05-07 14:44:01 UTC
We think that setting SOURCE_DATE_EPOCH to 0 or 1 is not sensible 
and known to be problematic. Don't do that.

It's not an oe-core issue.
Comment 3 Tim Orling 2026-05-07 14:47:30 UTC
https://github.com/uptane/meta-updater/issues/96