public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 1/4] update source date epoch fallback to cover all distro versions
Date: Fri, 13 Nov 2026 16:10:55 +0100	[thread overview]
Message-ID: <20261113151058.1542335-2-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20261113151058.1542335-1-felix.moessbauer@siemens.com>

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(-)

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'}"
-- 
2.55.0

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20261113151058.1542335-2-felix.moessbauer%40siemens.com.

  reply	other threads:[~2026-11-13 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 15:10 [PATCH 0/4] A couple of fixes for snapshot handling on ubuntu 'Felix Moessbauer' via isar-users
2026-11-13 15:10 ` 'Felix Moessbauer' via isar-users [this message]
2026-11-13 15:10 ` [PATCH 2/4] fix(resolute-arm64): use official mirror instead of ports 'Felix Moessbauer' via isar-users
2026-11-16  9:51   ` 'Moessbauer, Felix' via isar-users
2026-11-13 15:10 ` [PATCH 3/4] ubuntu: add default snapshot entry for ports 'Felix Moessbauer' via isar-users
2026-11-13 15:10 ` [PATCH 4/4] testsuite: check if all ubuntu targets can be bootstrapped 'Felix Moessbauer' via isar-users

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261113151058.1542335-2-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox