Yocto 5.3 (whinlatter) migration: CI and recipe updates#276
Conversation
Yocto 5.3 (whinlatter) warns on assignments without whitespace around the = operator. Fix PARALLEL_MAKEINST="" and PACKAGE_ARCH="all" across mono and nuget recipes. Ref: https://docs.yoctoproject.org/dev/migration-guides/migration-5.3.html Ref: #275 Co-authored-by: Cursor <cursoragent@cursor.com>
…COMPAT Yocto 5.3 (whinlatter) no longer maintains release branches in the poky repository. Replace the single poky clone with individual clones of: - bitbake (branch 2.16) - openembedded-core (branch whinlatter) - meta-yocto (branch whinlatter) Update oe-init-build-env path and TEMPLATECONF to use the new layout. Move meta-openembedded under layers/ for consistency. Also update LAYERSERIES_COMPAT from styhead to whinlatter. Ref: https://docs.yoctoproject.org/dev/migration-guides/migration-5.3.html Ref: #275 Co-authored-by: Cursor <cursoragent@cursor.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Co-authored-by: Alex Lennon <ajlennon@dynamicdevices.co.uk>
Make the meta-openembedded step self-contained so a clean workspace still works if clone order changes. Co-authored-by: Alex Lennon <ajlennon@dynamicdevices.co.uk>
Yocto 5.3 errors when recipes set S = "${UNPACKDIR}/git" because
oe-core bitbake.conf now sets S from BB_GIT_DEFAULT_DESTSUFFIX.
This unblocks mono-native do_unpack on the whinlatter CI branch.
Co-authored-by: Alex Lennon <ajlennon@dynamicdevices.co.uk>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 2eb825b. Configure here.
| @@ -1,3 +1 @@ | |||
| S = "${UNPACKDIR}/git" | |||
There was a problem hiding this comment.
Mono git source path wrong
High Severity
Removing the S = "${UNPACKDIR}/git" override from mono-6.12.0.206.inc leaves S at mono-6.xx.inc's tarball path (${UNPACKDIR}/mono-6.12.0) while mono_6.12.0.206.bb and mono-native_6.12.0.206.bb fetch from git. Configure and patch steps then target the wrong directory and CI mono builds fail.
Reviewed by Cursor Bugbot for commit 2eb825b. Configure here.
| SRCREV= "e272a2c006211b6b03be2ef5bbb9e3f8fefd0768" | ||
| SRC_URI = "git://github.com/mono/xsp.git;branch=main;protocol=https \ | ||
| " | ||
|
|
There was a problem hiding this comment.
mono-xsp git wrong S
Medium Severity
Dropping the git-specific S override in mono-xsp_git.bb leaves S from mono-xsp-3.x.inc as ${UNPACKDIR}/xsp-${PV} for a tarball layout, while this recipe's SRC_URI uses the git fetcher. Builds of mono-xsp_git point at a path that does not match the unpacked repository.
Reviewed by Cursor Bugbot for commit 2eb825b. Configure here.
2 participants
Summary
Migrate meta-mono to support Yocto 5.3 (whinlatter). The poky repository no longer maintains release branches from whinlatter onwards, requiring a new CI setup approach.
oe-init-build-envandTEMPLATECONFpaths=inPARALLEL_MAKEINSTandPACKAGE_ARCHassignments (5 files) to suppress whinlatter warningsLAYERSERIES_COMPATupdated fromstyheadtowhinlatterReferences
Test plan
Made with Cursor
Note
Medium Risk
CI now fetches and initializes Yocto from multiple upstream repos (instead of
poky), so failures are most likely due to branch/path mismatches or layer ordering; recipe changes are formatting-only but can affect parsing under newer BitBake.Overview
Updates the project to target Yocto 5.3
whinlatterby switchingLAYERSERIES_COMPAT_monoand adjusting CI to build/test against thewhinlatterbranch.The GitHub Actions workflow stops cloning
pokyand instead clonesbitbake,openembedded-core, andmeta-yoctointo alayers/layout, updatesTEMPLATECONF/oe-init-build-envpaths accordingly, and limits the build matrix towhinlatteronx86-64andarm64.Separately, recipe metadata is normalized for
whinlatterparsing (whitespace around=), includingPARALLEL_MAKEINSTin Mono include files andPACKAGE_ARCHinnuget.inc.Written by Cursor Bugbot for commit 863f4db. This will update automatically on new commits. Configure here.