Skip to content

[Backport kirkstone-next] greengrass-lite: upgrade 2.3.2 -> 2.3.3#15146

Merged
rpcme merged 4 commits intokirkstone-nextfrom
backport-15145-to-kirkstone-next
Mar 9, 2026
Merged

[Backport kirkstone-next] greengrass-lite: upgrade 2.3.2 -> 2.3.3#15146
rpcme merged 4 commits intokirkstone-nextfrom
backport-15145-to-kirkstone-next

Conversation

@aws-iot-embedded-linux-ci
Copy link
Copy Markdown
Collaborator

Description

Backport of #15145 to kirkstone-next.

@rpcme
Copy link
Copy Markdown
Member

rpcme commented Mar 2, 2026

Added version-upgrade label to unblock auto-approval

Copy link
Copy Markdown
Member

@rpcme rpcme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving: All CI checks passing, version-upgrade label added

@rpcme rpcme enabled auto-merge March 2, 2026 14:57
@thomas-roos
Copy link
Copy Markdown

grep -q ${SRCREV_sdk} ${S}/fc_deps.json || bbfatal "ERROR: dependency version mismatch, please update 'SRCREV_sdk'!"
need to be removed, as in the fc deps file is still the tag name and that seems to not supported in kirkstone

Kirkstone requires fixed commit hashes for SRCREV, but the upstream
fc_deps.json uses tag 'v0.4.1'. The recipe's verification check fails
because it looks for the commit hash in fc_deps.json.

Add a patch to update fc_deps.json to use the commit hash that v0.4.1
points to (9487b56479ebc20a67bb9dce9b3a3dfb58f91cb9).

Fixes: #15146
@rpcme
Copy link
Copy Markdown
Member

rpcme commented Mar 9, 2026

Root Cause Fixed

The build was failing because of a mismatch between the recipe and upstream's fc_deps.json:

  • Recipe SRCREV_sdk: 9487b56479ebc20a67bb9dce9b3a3dfb58f91cb9 (commit hash - required by Kirkstone)
  • Upstream fc_deps.json: "rev": "v0.4.1" (tag name)
  • Verification check: Looks for exact match of SRCREV in fc_deps.json → FAILS

Solution

Added patch 0001-kirkstone-fc_deps-use-commit-hash-for-gg_sdk.patch that updates fc_deps.json to use the commit hash instead of the tag.

This is kirkstone-specific because:

  • Kirkstone requires fixed commit hashes for SRCREV (Yocto policy)
  • Newer releases (scarthgap, whinlatter) accept tags
  • The verification logic in the recipe requires an exact match

The patch is marked Upstream-Status: Inappropriate [kirkstone-specific] since upstream correctly uses tags.

Build tests should now pass. ✅

@rpcme rpcme added this pull request to the merge queue Mar 9, 2026
Merged via the queue into kirkstone-next with commit 6d3942e Mar 9, 2026
7 checks passed
@rpcme rpcme deleted the backport-15145-to-kirkstone-next branch March 9, 2026 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport version-upgrade Automated Version Upgrade

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants