Yocto Project - Recent changes [en]

2026 Yocto Project Weekly Status Archive

2026-04-14T14:47:32Z

Yocto Project Status 7 April 2026

@@ Line 1: / Line 1: @@
 == Yocto Project Status 7 April 2026 ==
 Current Dev Position: YP 6.0 M3<br/>
@@ Line 68: / Line 128: @@
 '''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
 https://wiki.yoctoproject.org/wiki/TSC<br/>
 == Yocto Project Status 31 March 2026 ==
 Current Dev Position: YP 6.0 M3<br/>

Weekly Status

2026-04-14T14:47:00Z

Yocto Project Status 7 April 2026

← Older revision		Revision as of 14:47, 14 April 2026
Line 1:		Line 1:
	== Yocto Project Status 7 April 2026 ==		== Yocto Project Status 14 April 2026 ==
	Current Dev Position: YP 6.0 M3<br/>		Current Dev Position: YP 6.0 M4<br/>
	Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>		Next Deadline: YP 6.0 M4 Build Date 2026-04-20<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday Apr. ~~9th~~ 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday Apr. 16th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday Apr. ~~7th~~ 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday Apr. 14th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday Apr. ~~9th~~ 10am GMT and Monday Apr. ~~13th~~ 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday Apr. 16th 10am GMT and Monday Apr. 20th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

	'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 5.3.~~3 was~~ released.		*YP 5.0.17 is due to be released
	*YP 5.0~~.17~~ is in QA		*YP 6.0 M3 is in QA
	*YP 6.0 M3 is ~~the feature freeze~~ for ~~6.0 which is our next LTS.~~		*YP 4.0.35 is queued for QA
	*~~YP 6~~.~~0 M3 is now due to build however there~~ are ~~still key changes missing~~.		*We have converted over to sbom-cve-check and dropped cve-check. This has caused a significant increase in CVEs reported, these are being triaged.
	*Issues with pending work needed:		*Issues with pending work needed:
	**Converting scripts/run-cvecheck to sbom-cve-check
	**32bit x86 kvm seemingly broken with certain CPU features (#16074)		**32bit x86 kvm seemingly broken with certain CPU features (#16074)
	**~~Failure~~ to ~~generate regression reports in release builds~~ (~~need tags~~)		**Reports of pseudo errors on Fedora 44 beta related to openat2()
	**~~Ubuntu 26.04 support~~ (~~need worker adding for testing~~)		**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
	*~~Issues that have patches ready to merge:~~		**Meta-oe cve layer filtering under new tooling (metrics script tweak?)
	**DISTRO_FEATURES defaults improvements.		**Reprodicubility issues with strace/apr-util after gnulib macro changes (patches in testing)
	**~~Fixing yocto-check-layer to work~~ with -~~-machines~~		*There was disruption to git services last week due to scraping attacks against the servers. This resulted in connection issues whilst those were mitigated, particularly the git protocol access.
	**RHEL 9 xattrs/~~selinux~~/~~tar issue~~		git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
	**Splitting wic into an external tool.		*The recent wic changes will need wic support files to be placed in files/wic within layers going forwards.
	**RHEL 10/~~openSUSE Leap 16~~.~~0 support~~
	*Issues that need investigation
	**Reports of pseudo errors on Fedora 44 beta
	*The ~~proposed~~ wic changes will need wic support files to be placed in files/wic within layers going forwards.
	*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.		*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
	*~~We are aware of our git hosting giving 502 Bad Gateway errors,~~ this ~~is being investigated~~		*The final kirkstone build has taken place and we’re no longer planning to merge patches on this branch.
	*~~The CFP~~ for the ~~Yocto Project Workshop at Embedded Recipes 2026 closes today: https://pretalx~~.~~com/yocto-embedded-recipes-2026/cfp~~		*If you have any final patches for whinlatter, please get these sent to the list ASAP.

	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 43:		Line 38:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2797~~ (last week ~~2814~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2777 (last week 2797) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1060~~ (last week ~~1062~~)		**Total patches found: 1072 (last week 1060)
	**Patches in the Pending State: ~~148~~ (14%) [last week 148 (14%)]		**Patches in the Pending State: 147 (14%) [last week 148 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

	'''YP 6.0 Milestone Dates:'''<br/>		'''YP 6.0 Milestone Dates:'''<br/>
	*YP 6.0 M3 ~~Build Date 2026-03-23~~		*YP 6.0 M3 in QA.
	*YP 6.~~0 M3 Release Date 2026-04-08~~
	*YP 6.0 M4 Build Date 2026-04-13		*YP 6.0 M4 Build Date 2026-04-13
	*YP 6.0 M4 Release Date 2026-05-04		*YP 6.0 M4 Release Date 2026-05-04

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.3.3 was released.		*YP 5.0.17 is in review.
	*YP 5.0.17 is in QA.		*YP 4.0.35 is in QA.
	*YP 4.0.35
	**Build Date 2026-04-06
	**Release Date 2026-04-22
	*YP 5.3.4		*YP 5.3.4
	**Build Date 2026-04-20		**Build Date 2026-04-20

TipsAndTricks/GentooLinux-RequiredPackagesforYoctoBuildHost

2026-04-13T07:49:02Z

Gentoo Linux - Required Packages for Yocto Build Host - creation page

New page

== Gentoo Linux - Required Packages for Yocto Build Host ==

The following packages are required to build a Yocto image on Gentoo Linux.
Note that several third-party guides reference incorrect package atoms —
the verified atoms are listed below.

<pre>
emerge -av \
dev-vcs/git \
dev-lang/python:3.11 \
dev-python/pip \
dev-util/diffstat \
app-admin/chrpath \
sys-apps/texinfo \
dev-libs/glib \
sys-apps/file \
app-arch/xz-utils \
sys-libs/zlib \
dev-build/cmake \
dev-lang/perl \
app-misc/screen \
app-shells/bash \
sys-process/lsof \
app-arch/cpio \
app-arch/tar \
sys-apps/util-linux \
sys-apps/gawk \
net-misc/socat
</pre>

=== Common mistakes in third-party guides ===

Several widely referenced guides list incorrect Gentoo package atoms that do
not exist in the Portage tree. Use the following verified atoms instead:

* <code>app-admin/chrpath</code> — not <code>dev-util/chrpath</code> or <code>app-text/chrpath</code>
* <code>app-arch/cpio</code> — not <code>dev-util/cpio</code>
* <code>dev-build/cmake</code> — not <code>dev-util/cmake</code>

=== Python version compatibility ===

Prefer <code>dev-lang/python:3.11</code> or <code>dev-lang/python:3.12</code>.
Python 3.13 may cause issues with Scarthgap and Nanbield releases.

''Verified on Gentoo Linux (OpenRC, amd64), Portage tree April 2026.''

TipsAndTricks

2026-04-13T07:48:15Z

Requirement Gentoo for Yocto Build Host

← Older revision		Revision as of 07:48, 13 April 2026
Line 62:		Line 62:
	* [[TipsAndTricks/DebuggingOddFailure]] (RP)		* [[TipsAndTricks/DebuggingOddFailure]] (RP)
	* [[TipsAndTricks/UnconventionalImages]] (Ross)		* [[TipsAndTricks/UnconventionalImages]] (Ross)
			* [[TipsAndTricks/GentooLinux-RequiredPackagesforYoctoBuildHost]] (Aurelien)

	== Finished Articles ==		== Finished Articles ==
	* [[TipsAndTricks/Packaging Prebuilt Libraries \| Packaging Prebuilt Libraries]] (Ross and Henry)		* [[TipsAndTricks/Packaging Prebuilt Libraries \| Packaging Prebuilt Libraries]] (Ross and Henry)
	* [[TipsAndTricks/NPM \| Packaging Node.js Projects]] (Brendan and Henry)		* [[TipsAndTricks/NPM \| Packaging Node.js Projects]] (Brendan and Henry)

User talk:Aurelien DESBRIERES

2026-04-13T06:35:42Z

Welcome!

New page

'''Welcome to ''Yocto Project''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 06:35, 13 April 2026 (UTC)

User:Aurelien DESBRIERES

2026-04-13T06:35:42Z

Creating user page for new user.

New page

I like Rolling release and I like embedded things :)

User:Aurelien DESBRIERES

2026-04-13T06:35:41Z

User account Aurelien DESBRIERES was created by MichaelHalstead and password was sent by email

2026 Yocto Project Weekly Status Archive

2026-04-07T14:44:31Z

Yocto Project Status 31 March 2026

@@ Line 1: / Line 1: @@
 == Yocto Project Status 31 March 2026 ==
 Current Dev Position: YP 6.0 M3<br/>
@@ Line 74: / Line 143: @@
 '''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
 https://wiki.yoctoproject.org/wiki/TSC<br/>
 == Yocto Project Status 24 March 2026 ==
 Current Dev Position: YP 6.0 M3<br/>

Weekly Status

2026-04-07T14:44:14Z

Yocto Project Status 31 March 2026

← Older revision		Revision as of 14:44, 7 April 2026
Line 1:		Line 1:
	== Yocto Project Status ~~31 March~~ 2026 ==		== Yocto Project Status 7 April 2026 ==
	Current Dev Position: YP 6.0 M3<br/>		Current Dev Position: YP 6.0 M3<br/>
	Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>		Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday Apr. ~~2nd~~ 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday Apr. 9th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~31st Mar~~. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday Apr. 7th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday Apr. ~~2nd~~ 10am GMT and Monday Apr. ~~6th~~ 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday Apr. 9th 10am GMT and Monday Apr. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

	'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 4.0.34 was released.		*YP 5.3.3 was released.
	*YP 5.3.3 is ~~approved for release.~~		*YP 5.0.17 is in QA
	*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.		*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
	*YP 6.0 M3 is now due to build however there are still key changes missing.		*YP 6.0 M3 is now due to build however there are still key changes missing.
	*Issues ~~still~~ pending:		*Issues with pending work needed:
	**Splitting wic into an external tool.
	**Converting scripts/run-cvecheck to sbom-cve-check		**Converting scripts/run-cvecheck to sbom-cve-check
			**32bit x86 kvm seemingly broken with certain CPU features (#16074)
			**Failure to generate regression reports in release builds (need tags)
			**Ubuntu 26.04 support (need worker adding for testing)
			*Issues that have patches ready to merge:
	**DISTRO_FEATURES defaults improvements.		**DISTRO_FEATURES defaults improvements.
			**Fixing yocto-check-layer to work with --machines
	**RHEL 9 xattrs/selinux/tar issue		**RHEL 9 xattrs/selinux/tar issue
	**~~How to improve DEBUG_BUILD?~~		**Splitting wic into an external tool.
	**RHEL 10/openSUSE Leap 16.0~~/Ubuntu 26.04~~ support		**RHEL 10/openSUSE Leap 16.0 support
	*Issues that ~~are mostly known quantities still needing work:~~		*Issues that need investigation
	**x86 kvm seemingly broken with certain CPU features (#16074)		**Reports of pseudo errors on Fedora 44 beta
	**Failure to generate regression reports in release builds		*The proposed wic changes will need wic support files to be placed in files/wic within layers going forwards.
	**~~Fixing yocto-check-layer to work with --machines (many fixes merged)~~
	*Issues that were resolved this week:
	**Sbom-cve-check added
	**Replacement of ~~runtlp with kirk (Thanks Daniel!)~~
	**bitbake-setup vscode integration
	**Fedora ~~43 selftest failures~~
	**Reconciling poky and OE-Core defaults templates.
	*We have rationalized the tags in ~~various project repositories, more information can be found here: https:/~~/~~lists.openembedded.org/g/openembedded-architecture/message/2312 Whilst controversial, this will make the tag list much easier to understand for users, guide users to use the right tags~~ going ~~forward and remove confusion about whether any tags were “missed”, at the expense that some CI setups may need adjusting short term~~.
	*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.		*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
	*The CFP ~~closing date~~ for the Yocto Project Workshop at Embedded Recipes 2026 ~~has been extended until April 7th, please submit a proposal if you’d like to present~~: https://pretalx.com/yocto-embedded-recipes-2026/cfp		*We are aware of our git hosting giving 502 Bad Gateway errors, this is being investigated
			*The CFP for the Yocto Project Workshop at Embedded Recipes 2026 closes today: https://pretalx.com/yocto-embedded-recipes-2026/cfp

	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 46:		Line 43:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2814~~ (last week ~~2819~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2797 (last week 2814) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1062~~ (last week ~~1072~~)		**Total patches found: 1060 (last week 1062)
	**Patches in the Pending State: 148 (14%) [last week ~~151~~ (14%)]		**Patches in the Pending State: 148 (14%) [last week 148 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

Line 59:		Line 56:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 4.0.34 was released.		*YP 5.3.3 was released.
	*YP 5.3.3 ~~ready for release~~.		*YP 5.0.17 is in QA.
	*YP 5.0.17 ~~Build Date 2026-03-30~~		*YP 4.0.35
	*YP 5.0.~~17 Release Date 2026-04-15~~		**Build Date 2026-04-06
	*YP 4.0.35 Build Date 2026-04-06		**Release Date 2026-04-22
	*~~YP 4.0.35~~ Release Date 2026-04-22		*YP 5.3.4
	*YP 5.3.4 ~~Build Date 2026-04-20~~		**Build Date 2026-04-20
	*~~YP 5.3.4 Release Date 2026-05-06~~		**Release Date 2026-05-06
	*~~YP 5.0.18~~ Build Date 2026-04-27		*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
	*~~YP 5.0.18~~ Release Date 2026-05-13
	*~~YP 5.0.19 Build Date 2026-05-26~~
	*YP 5.0.~~19 Release Date 2026-06-05~~

	'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>		'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

Release calendar

2026-04-07T12:16:16Z

Created page with "== Planned release dates == Release dates have been planned through April 2027. Dates will be reviewed in '''''July 2026''''' and revised if needed. === 5.0 "scarthgap" series === * 5.0.18: w/c 2026-05-25 * 5.0.19: w/c 2026-07-13 * 5.0.20: w/c 2026-08-31 * 5.0.21: w/c 2026-10-19 * 5.0.22: w/c 2026-12-14 * 5.0.23: w/c 2027-01-25 * 5.0.24: w/c 2027-03-08 * 5.0.25: w/c 2027-04-19 === 6.0 "wrynose" series === * 6.0.0: w/c 2026-05-04 * 6.0.1: w/c 2026-06-01 * 6.0.2: w/c..."

New page

== Planned release dates ==

Release dates have been planned through April 2027. Dates will be reviewed in '''''July 2026''''' and revised if needed.

=== 5.0 "scarthgap" series ===

* 5.0.18: w/c 2026-05-25
* 5.0.19: w/c 2026-07-13
* 5.0.20: w/c 2026-08-31
* 5.0.21: w/c 2026-10-19
* 5.0.22: w/c 2026-12-14
* 5.0.23: w/c 2027-01-25
* 5.0.24: w/c 2027-03-08
* 5.0.25: w/c 2027-04-19

=== 6.0 "wrynose" series ===

* 6.0.0: w/c 2026-05-04
* 6.0.1: w/c 2026-06-01
* 6.0.2: w/c 2026-07-06
* 6.0.3: w/c 2026-08-24
* 6.0.4: w/c 2026-10-12
* 6.0.5: w/c 2026-12-07
* 6.0.6: w/c 2027-01-18
* 6.0.7: w/c 2027-03-01
* 6.0.8: w/c 2027-04-12

=== 6.1 series ===

* 6.1 M1: w/c 2026-06-22
* 6.1 M2: w/c 2026-08-03
* 6.1 M3: w/c 2026-09-14
* 6.1.0: w/c 2026-11-02
* 6.1.1: w/c 2026-11-30
* 6.1.2: w/c 2027-01-04
* 6.1.3: w/c 2027-02-22
* 6.1.4: w/c 2027-04-05

=== 6.2 series ===

* 6.2 M1: w/c 2026-12-21
* 6.2 M2: w/c 2027-02-01
* 6.2 M3: w/c 2027-03-15
* 6.2.0: w/c 2027-05-03

== Notes ==

* All dates are '''''week commencing''''', the exact day the release is published depends on TSC availability to approve releases and time taken to upload release artefacts.

* Releases will be built 10-14 days before the target release date to give time for QA and review.

* We aim for 6-7 weeks between releases in each series, occasionally there will be an 8 week gap due to things like Christmas/New Year vacations.

* We aim for 4 weeks between .0 and .1 releases to allow us to get any necessary fixes out for the new series.