Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *openssh* to *9.0p1* has Succeeded. Next steps: - apply the patch: git am

From: Suhrid_S <suhrid.subramaniam@...> clinfo 2.2.18.04.06 released April 2018 does not show correct information pertaining to OpenCL 3.0 released Sept 2020. It shows version as `2.0` or

From: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@...> - gcc 12 is in RC stages. - Add patch to re-shuffle include of sched.h to fix build on musl Signed-off-by: Bernhard Rosenkränzer

From: Kai Kang <kai.kang@...> It duplicates udevadm in systemd recipe to make it could run update_udev_hwdb with multilib enabled. Since systemd last update, it deploys a shared library

This isn't quite the right approach, we should probably skip parsing of glibc- tests if ptests aren't in DISTRO_FEATURES? Cheers, Richard

wrote: This hasn't happened in the past as we've had no good way to notify users of the change and it would likely break existing BSPs. We do at least have some mechanism for deprecating and warning

This includes a fix for CVE-2022-24765 Signed-off-by: Richard Purdie <richard.purdie@...> --- meta/recipes-devtools/git/{git_2.35.1.bb => git_2.35.2.bb} | 2 +- 1 file changed, 1

Some of the flags listed here do change the output and hence do need to be included in task checksums. This means we start including the following flags in function/task/variable checksums: type,

The license in this code is listed as MIT and whilst it is compatible with and usable as MIT, it actually looks like HPND. Clarify the license field accordingly. Signed-off-by: Richard Purdie

With the fix for #8621, cleandirs is now applied to autotools_do_install and this results in a lot of the install targets to be removed. Ensure cleandirs isn't set for

The current default DISTRO_FEATURES does not support ptest. Hence, the following error is generated during "bitbake glibc-tests". ERROR: glibc-tests-2.35-r0 do_package: QA Issue:

I agree, and this would allow to simplify documentation too. Markus, would you like to submit a patch to openembedded-core? Good catch by the way! Thanks Michael. -- Michael Opdenacker,

Having looked at a few SPDX licenses, I think this looks like HPND: https://spdx.org/licenses/HPND.html I suspect the license set in the recipeutils-test is there for testing purposes and not as a

I had tried building these three fixes but it looks like they are causing a ptest to fail in libxml-parser-perl for

Here is the COPYING: Copyright © 2013 Keith Packard Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided

Hello, The following two recipes use the similar sources, but their LICENSE are different in the recipe: meta-selftest/recipes-test/recipeutils/recipeutils-test_1.2.bb SRC_URI =

The graphics option auto detection logic added in 7f78bb7a was not checking if the publicvnc option had been specified, meaning that it would be ignored and the auto detection result used instead. Add

An attempt to disable the use of syslog() was made in commit 8f181686 (shadow-native: Simplify and fix syslog disable patch). However, because the code checks if USE_SYSLOG is defined rather than

The systemd bluetooth service failed to start. Add a workaround for this whilst the final fix is discussed upstream, https://github.com/bluez/bluez/issues/329. Signed-off-by: Richard Purdie