Note: lists.yoctoproject.org will be down for maintenance on Monday, September 26th, starting at 9AM Pacific Time (4PM Monday September 26, 2022 UTC), for approximately one hour.
- Yocto Project Status 9 August 2022 (WW32)
Yocto Project Status 9 August 2022 (WW32)
Current Dev Position: YP 4.1 M3
Next Deadline: 22nd August 2022 YP 4.1 M3 Build
Next Team Meetings:
YP 3.1.18 was released
YP 4.0.3 is due to build this week but we need the glibc and kernel reproducibility fixes first
Major changes to the rust toolchain build process were merged and this enables target rust, cross SDK and automated SDK testing. Sadly some issues remain and are stopping enabling the tests by default.
We have finally tracked down and worked out a fix for the kernel reproducibility issue which appeared in recent 5.15 stable updates. It was a config option which changed depending on whether /bin/sh was dash or bash.
The 5.19 kernel uprev is nearly ready to merge as the final build issues look to have been addressed.
The base glibc 2.36 patches have merged but not the actual upgrade yet.
We had some infrastructure issues over the weekend which impacted the autobuilder. Combined with a number of complex patch submissions, this has meant there are patches backlogged.
A number of new CVEs appeared in master this week so help would be much appreciated in addressing those.
The debug file mapping issues are stalled due to developer bandwidth limitations.
Ways to contribute:
YP 4.1 Milestone Dates:
YP 4.1 M3 build date 2022/08/22
YP 4.1 M3 Release date 2022/09/02
YP 4.1 M4 build date 2022/10/03
YP 4.1 M4 Release date 2022/10/28
Upcoming dot releases:
YP 3.1.18 Release date 2022/08/05
YP 4.0.3 build date 2022/08/08
YP 4.0.3 Release date 2022/08/19
YP 3.1.19 build date 2022/08/29
YP 3.1.19 Release date 2022/09/09
YP 4.0.4 build date 2022/09/19
YP 4.0.4 Release date 2022/09/30
YP 3.1.20 build date 2022/10/10
YP 3.1.20 Release date 2022/10/21
YP 4.0.5 build date 2022/10/31
YP 4.0.5 Release date 2022/11/11
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]