This version supports openssl 3.1 The maintainer changed his tag versions hence the different looking version. The maintainer also has stopped releasing tar files and asked we directly grab from git.

Current Dev Position: YP 4.3 M1 Next Deadline: 5th June 2023 YP 4.3 M1 build date Next Team Meetings: Bug Triage meeting Thursday June 1st 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0

I was just looking up the Yocto LTS and I found https://endoflife.date/yocto. It says: 3.1 'Dunfell' (LTS) Ends in 10 months (01 Apr 2024) 4.0 'Kirkstone' (LTS) Ends in 11 months (27 Apr 2024) Are the

Configuration error: | -- Configuring done (4.9s) | CMake Error in CMakeLists.txt: | Target "zephyr_interface" contains relative path in its | INTERFACE_INCLUDE_DIRECTORIES: | | "include-fixed" With G

The CVE product name for selinux-* package is (usually) the selinux (and not our recipe name), so use selinux as the default. See also: http://lists.openembedded.org/pipermail/openembedded-core/2017-J

From: Mikko Rapeli <mikko.rapeli@...> After latest changes to ${S}, parsec-service fails to apply systemd.patch: ERROR: parsec-service-1.2.0-r0 do_patch: Applying patch 'systemd.patch' on target direc

From: Mikko Rapeli <mikko.rapeli@...> Currently build fails with: | error: manifest path `/home/builder/build/tmp_qemuarm64/work/cortexa57-linux/parsec-tool/0.6.0-r0/cargo_home/bitbake/parsec-tool-0.6

All, YP M+ or high bugs which moved to a new milestone in WW21 Priority Bug ID Short Description Changer Owner Was Became High 15124 cmake-native fails to prepend c++ compiler after pulling the newest

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macleod@... 3 Grand Total 3 Thanks, Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 24

All, Below is the list as of top 34 bug owners as of the end of WW21 of who have open medium or higher bugs and enhancements against YP 4.3. There are 104 possible work days left until the final relea

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the

From: Mikko Rapeli <mikko.rapeli@...> After latest changes to ${S}, parsec-service fails to apply systemd.patch: ERROR: parsec-service-1.2.0-r0 do_patch: Applying patch 'systemd.patch' on target direc

From: Wang Mingyu <wangmy@...> Signed-off-by: Wang Mingyu <wangmy@...> --- .../xerces-j/{xerces-j_2.11.0.bb => xerces-j_2.12.0.bb} | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) rename re

Hi We are pleased to announce the Yocto Project 4.2.1 Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-4.2.1/poky-c5c69f78fc7ce4ba361363c14352e4264ce7813f.

Hi.. there Hope all are doing well I'm dealing with the Makefile based project, for which i have created the recipe file The file architecture of the recipes file is as follows, |---modem-api ├── file

Hi.. community Hope all are doing well I'm dealing with the Yocto hardknott with my Ubuntu host The Ubuntu version is Ubuntu 22.04.2 LTS During the building of the custom image, everything goes well u

Hello all, I'm trying to figure out how to set the `nodatacow` flag on a directory in a BTRFS image at build time. Normally this is done by running 'chattr +c <dir>'. Unfortunately, this doesn't seem

Hi, I'm using kirkstone and from time to time I'm getting pseudo abort on opencv. There are some topics already reported: https://lists.yoctoproject.org/g/yocto/topic/opencv_build_generates_pseudo/828

Hello, I am trying to get v4l_mem2mem in to ffmpeg. It does hardware h264 encoding on a RPI4 ffmpeg -encoders | grep h264 for example ffmpeg -f v4l2 -i /dev/video0 -v:c v4l_mem2mem out.mp4 would take

Hi All, QA for yocto-4.2.1.rc1 is completed. This is the full report for this release: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summ