[1/4] update source date epoch fallback to cover all distro versions

Message ID 20261113151058.1542335-2-felix.moessbauer@siemens.com
State Under Review
Headers show
Series A couple of fixes for snapshot handling on ubuntu | expand

Commit Message

Felix Moessbauer Nov. 13, 2026, 3:10 p.m. UTC
We update it to cover debian forky and ubuntu resolute, which otherwise
are not yet known to the snapshot mirrors. Normally, the users would set
it anyways to a reasonable date, but for CI testing we need a stable
baseline that works.

The new timestamp has been chosen arbitrarily and points to roughly the
time this commit was authored.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/conf/bitbake.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Patch

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index c31719b8..f51e1e68 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -142,7 +142,7 @@  export PERL_HASH_SEED = "0"
 export SOURCE_DATE_EPOCH ?= "${@get_source_date_epoch_value(d)}"
 # A SOURCE_DATE_EPOCH of '0' might be misinterpreted as no SDE
 # Isar: set value to date of latest release
-SOURCE_DATE_EPOCH_FALLBACK ??= "1709565251"
+SOURCE_DATE_EPOCH_FALLBACK ??= "1794563711"
 # Debian snapshots
 ISAR_USE_APT_SNAPSHOT ??= "0"
 ISAR_APT_RETRIES ??= "${@'10' if bb.utils.to_boolean(d.getVar('ISAR_USE_APT_SNAPSHOT')) else '3'}"