Re: [OE-core][PATCH 1/2] ffmpeg: fix for CVE-2022-3964

Sure Ross, will make sure to add CVE tag in the patch header. Do I need to send again this patch with CVE tag ? Best Regards, Narpat From: Ross Burton Sent: Monday, November 28, 2022 11:04:15 PM To: Mali, Narpat Cc: openembedded-core@lists.openembedded.org ; P

[oe-core][PATCHv6] gcr: add recipe for gcr-4, needed to build with gtk4

- gcr-3 recipe is still needed for gnome projects that stick to gtk+3, rename to gcr3. - Move gtk4 recipe from meta-gnome Signed-off-by: Markus Volk --- ...-add-options-to-set-ssh-binary-paths.patch | 60 ...ectly-handle-disabled-ssh_agent-opti.patch | 49 ++ ...build-fix-one-par

[OE-core] Current high bug count owners for Yocto Project 4.2

All, Below is the list as of top 31 bug owners as of the end of WW48 of who have open medium or higher bugs and enhancements against YP 4.2. There are 104 possible work days left until the final release candidates for YP 4.2 needs to be released. Who Count michael.opdenac...@bootlin.com 35

Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.21.rc1)

Hi All, QA for yocto-3.1.21.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 === Summary No high milestone defects. No new issue found. Thanks, Jing Hui >

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

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 triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc

[OE-core] [PATCH] iputils: update to 20221126

From: Petr Vorel This release removed: ninfod, rarpd, rdisc. Remove also related, not yet upstreamed patch. License-Update: ninfod, rarpd, rdisc and switch to SPDX identifier. Signed-off-by: Petr Vorel Signed-off-by: Alexandre Belloni --- .../0001-rarpd-rdisc-Drop-PrivateUsers.patch | 27 --

[OE-core] [PATCH] bitbake.conf: Simplify CACHE setting

A long time ago the bitbake cache didn't use hashes in it's filename and hence values such as MACHINE were needed in the path to the cache file so that when switching MACHINE, a new cache wasn't always parsed. Times have moved on, we have a hash which represents the configuration and the caches ar

Re: [oe-core][PATCHv5] gcr: add recipe for gcr-4, needed to build with gtk4

On Mon, Nov 28 2022 at 09:57:31 PM +0100, Alexander Kanavin wrote: Please test your oe-core patches with a setup that includes only oe-core and no other layers. Then you'd immediately see that the new gcr recipe won't build. I even noticed it because I built core-image-sato for qemumips64 to

Re: [OE-core] [PATCH][master] go: Update patch due to build errors

Will do. Thanks. On 11/28/2022 15:26, Alexander Kanavin wrote: Ok then you need to place all of this and the bug link into the commit message, and then you can run the reproducibility test locally, no? Alex On Mon, 28 Nov 2022 at 22:22, Denys Dmytriyenko wrote: On Mon, Nov 28, 2022 at 09

Re: [OE-core] [PATCH][master] go: Update patch due to build errors

Ok then you need to place all of this and the bug link into the commit message, and then you can run the reproducibility test locally, no? Alex On Mon, 28 Nov 2022 at 22:22, Denys Dmytriyenko wrote: > > On Mon, Nov 28, 2022 at 09:58:43PM +0100, Alexander Kanavin wrote: > > What build errors is t

Re: [OE-core] [PATCH][master] go: Update patch due to build errors

On Mon, Nov 28, 2022 at 09:58:43PM +0100, Alexander Kanavin wrote: > What build errors is this addressing and how can they be observed? https://bugzilla.yoctoproject.org/show_bug.cgi?id=14976 > On Mon, 28 Nov 2022 at 21:46, Ryan Eatmon via lists.openembedded.org > wrote: > > > > The previous ve

Re: [OE-core] [PATCH][master] go: Update patch due to build errors

Apologies. I'll happily submit a patch v2 that further explains it if we want to move forward with this patch. There was a discussion back in September related to some of the TI machines and the riscv64 machine failing with a panic on recipes in meta-virtualization that use go. https://list

Re: [OE-core] [PATCH][master] go: Update patch due to build errors

What build errors is this addressing and how can they be observed? Alex On Mon, 28 Nov 2022 at 21:46, Ryan Eatmon via lists.openembedded.org wrote: > > The previous version of this patch was a little too zealous in > cleaning up the envvironment. Some of the variable impacted > by the filerComp

Re: [oe-core][PATCHv5] gcr: add recipe for gcr-4, needed to build with gtk4

If we want to keep epiphany/webkit in core, then yes, we need gtk4 in it too. Epiphany master has already landed the gtk4 port, but there's no tagged release yet. Please test your oe-core patches with a setup that includes only oe-core and no other layers. Then you'd immediately see that the new g

Re: [oe-core][PATCHv5] gcr: add recipe for gcr-4, needed to build with gtk4

On Mon, Nov 28 2022 at 07:21:25 PM +0100, Alexandre Belloni via lists.openembedded.org wrote: Don't you need to also add gtk4 to oe-core? If this decision is final, I will send the patch for it tomorrow morning. At the moment I am not at home. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive al

[OE-core] [PATCH][master] go: Update patch due to build errors

The previous version of this patch was a little too zealous in cleaning up the envvironment. Some of the variable impacted by the filerCompilerFlags() function require at least one value to remain in the array. In this case, the values for ccExe, cxxExe, and fcExe require a value or it results in

[OE-core] [PATCH 4/4][kirkstone] tiff: add CVE tag to b258ed69a485a9cfb299d9f060eb2a46c54e5903.patch

* according to https://bugzilla.redhat.com/show_bug.cgi?id=2118863 this commit should be the fix for CVE-2022-2868 * resolves false-possitive entry in: https://lists.yoctoproject.org/g/yocto-security/message/705 CVE-2022-2868 (CVSS3: 8.1 HIGH): tiff https://web.nvd.nist.gov/view/vuln/detai

[OE-core] [PATCH] musl: Update to latest on tip of trunk

Brings following changes * 8f925945 fix return value of gethostby{name[2],addr} with no result but no error * 63402be2 clean up dns_parse_callback * 0a7b4323 dns response handling: don't treat too many addresses as an error * 41603c77 dns response handling: ignore presence of wrong-type RRs * cf7

[OE-core] [PATCH][kirkstone 2/3] tiff: fix a number of CVEs

From: Ross Burton Backport fixes from upstream for the following CVEs: - CVE-2022-3599 - CVE-2022-3597 - CVE-2022-3626 - CVE-2022-3627 - CVE-2022-3570 - CVE-2022-3598 Signed-off-by: Ross Burton Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie Signed-off-by: Martin Jansa --- ..

[OE-core] [PATCH][kirkstone 1/3] tiff: refresh with devtool

* so that they can be easily and cleanly applied with "git am" * manually fix CVE-2022-2953.patch commit message not to use UTF-8 quotes and replace it with human readable text from original commit: https://gitlab.com/libtiff/libtiff/-/commit/8fe3735942ea1d90d8cef843b55b3efe8ab6feaf Signed-of

[OE-core] [PATCH][kirkstone 3/3] tiff: Security fix for CVE-2022-3970

From: "Qiu, Zheng" This patch contains a fix for CVE-2022-3970 Reference: https://nvd.nist.gov/vuln/detail/CVE-2022-3970 https://security-tracker.debian.org/tracker/CVE-2022-3970 Patch generated from : https://gitlab.com/libtiff/libtiff/-/commit/227500897dfb07fb7d27f7aa570050e62617e3be Signed-

[OE-core] [kirkstone][PATCH v2] tiff: Security fix for CVE-2022-3970

This patch contains a fix for CVE-2022-3970 Reference: https://nvd.nist.gov/vuln/detail/CVE-2022-3970 https://security-tracker.debian.org/tracker/CVE-2022-3970 Patch generated from : https://gitlab.com/libtiff/libtiff/-/commit/227500897dfb07fb7d27f7aa570050e62617e3be Upstream-Status: Accepted S

Re: [OE-core] [kirkstone][PATCH] tiff: Security fix for CVE-2022-3970

On Mon, Nov 28, 2022 at 7:47 AM Qiu, Zheng wrote: > > This patch contains a fix for CVE-2022-3970 > > Reference: > https://nvd.nist.gov/vuln/detail/CVE-2022-3970 > https://security-tracker.debian.org/tracker/CVE-2022-3970 > > Patch generated from : > https://gitlab.com/libtiff/libtiff/-/commit/227

Re: [oe-core][PATCHv5] gcr: add recipe for gcr-4, needed to build with gtk4

Don't you need to also add gtk4 to oe-core? I guess without that this will never pass the autobuilders On 28/11/2022 17:13:19+0100, Markus Volk wrote: > gcr-3 recipe is still needed for gnome projects that stick to gtk+3, rename > to gcr3. > > Signed-off-by: Markus Volk > --- > ...-add-option

[OE-core] [kirkstone][PATCH] tiff: Security fix for CVE-2022-3970

This patch contains a fix for CVE-2022-3970 Reference: https://nvd.nist.gov/vuln/detail/CVE-2022-3970 https://security-tracker.debian.org/tracker/CVE-2022-3970 Patch generated from : https://gitlab.com/libtiff/libtiff/-/commit/227500897dfb07fb7d27f7aa570050e62617e3be Upstream-Status: Accepted S

Re: [OE-core][PATCH 1/2] ffmpeg: fix for CVE-2022-3964

Can you put a CVE tag in the patch header alongside your Upstream-Status and Signed-off-by? We need this to track in an automated way that this patch deals with a specific CVE. eg CVE: CVE-2022-3964 Ross > On 23 Nov 2022, at 14:20, Narpat Mali via lists.openembedded.org > wrote: > > A vuln

Re: [oe-core][PATCHv4] gcr: add recipe for gcr-4, needed to build with gtk4

Am Mo, 28. Nov 2022 um 17:12:53 +0100 schrieb Alexander Kanavin : There might be more pieces in core, not sure. While updating this, I also ran 'grep -r 'gcr ' .' in ./meta and ./meta-openembedded. Epiphany was the only gcr user in core. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messag

Re: [OE-core] [PATCH RFC] base: Switch to use addpylib directive

On Mon, 2022-11-28 at 21:00 +0530, Vishal Bhoj wrote: > > > On Mon, 28 Nov 2022 at 20:14, Richard Purdie > wrote: > > On Mon, 2022-11-28 at 19:29 +0530, Vishal Bhoj wrote: > > > I get the below backtrace with this patch on master-next. The > > > same > > > patchset works fine on debian-11. Are t

Re: [oe-core][PATCHv4] gcr: add recipe for gcr-4, needed to build with gtk4

Am Mo, 28. Nov 2022 um 17:13:09 +0100 schrieb Alexander Kanavin : *adjusted to gcr3. Thoght i also sent a patch for epiphany that does that adjustment, but maybe i forgot. I've sent a v5 because i had a typo in the gpg_path. Hopefully its good like it is now -=-=-=-=-=-=-=-=-=-=-=- Links

[oe-core][PATCHv5] gcr: add recipe for gcr-4, needed to build with gtk4

gcr-3 recipe is still needed for gnome projects that stick to gtk+3, rename to gcr3. Signed-off-by: Markus Volk --- ...-add-options-to-set-ssh-binary-paths.patch | 60 +++ ...ectly-handle-disabled-ssh_agent-opti.patch | 49 +++ ...build-fix-one-parallel-build-failure

Re: [oe-core][PATCHv4] gcr: add recipe for gcr-4, needed to build with gtk4

*adjusted to gcr3. Alex On Mon, 28 Nov 2022 at 17:12, Alexander Kanavin wrote: > > It's me again :) > I think epiphany is going to fail unless adjusted to gcr. There might > be more pieces in core, not sure. Yes it's annoying to wait for webkit > to build before you can test that. > > Alex > > O

Re: [oe-core][PATCHv4] gcr: add recipe for gcr-4, needed to build with gtk4

It's me again :) I think epiphany is going to fail unless adjusted to gcr. There might be more pieces in core, not sure. Yes it's annoying to wait for webkit to build before you can test that. Alex On Mon, 28 Nov 2022 at 17:08, Markus Volk wrote: > > gcr-3 recipe is still needed for gnome projec

[oe-core][PATCHv4] gcr: add recipe for gcr-4, needed to build with gtk4

gcr-3 recipe is still needed for gnome projects that stick to gtk+3, rename to gcr3. Signed-off-by: Markus Volk --- ...-add-options-to-set-ssh-binary-paths.patch | 60 +++ ...ectly-handle-disabled-ssh_agent-opti.patch | 49 +++ ...build-fix-one-parallel-build-failure

Re: [oe-core][PATCHv3] gcr: add recipe for gcr-4, needed to build with gtk4

Yes, otherwise I'm fine with it :) Alex On Mon, 28 Nov 2022 at 16:29, Markus Volk wrote: > > I know that ;) > > Just sent to see, if it would be ok for you like it is. I'll send the patch > upstream. > > Am Mo, 28. Nov 2022 um 16:21:35 +0100 schrieb Alexander Kanavin > : > > On Mon, 28 Nov 20

Re: [OE-core] [PATCH RFC] base: Switch to use addpylib directive

On Mon, 28 Nov 2022 at 20:14, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Mon, 2022-11-28 at 19:29 +0530, Vishal Bhoj wrote: > > I get the below backtrace with this patch on master-next. The same > > patchset works fine on debian-11. Are there any specific versions of > > pack

Re: [oe-core][PATCHv3] gcr: add recipe for gcr-4, needed to build with gtk4

I know that ;) Just sent to see, if it would be ok for you like it is. I'll send the patch upstream. Am Mo, 28. Nov 2022 um 16:21:35 +0100 schrieb Alexander Kanavin : On Mon, 28 Nov 2022 at 16:11, Markus Volk > wrote: +Upstream-Status: Pending Please submit upstr

Re: [oe-core][PATCHv3] gcr: add recipe for gcr-4, needed to build with gtk4

On Mon, 28 Nov 2022 at 16:11, Markus Volk wrote: > +Upstream-Status: Pending Please submit upstream first and include the link to the submission. I'm highly allergic to 'Pending' without a reason. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online

[oe-core][PATCHv3] gcr: add recipe for gcr-4, needed to build with gtk4

gcr-3 recipe is still needed for gnome projects that stick to gtk+3, rename to gcr3. Signed-off-by: Markus Volk --- ...-add-options-to-set-ssh-binary-paths.patch | 60 +++ ...ectly-handle-disabled-ssh_agent-opti.patch | 49 +++ ...build-fix-one-parallel-build-failure

Re: [OE-core] [meta-oe][PATCH] opencv: follow changed name license_flags_accepted

Wrong mailinglist for a meta-openembedded batch. I resent it to the correct ML. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#173921): https://lists.openembedded.org/g/openembedded-core/message/173921 Mute This Topic: https://lists.openembedded.or

Re: [OE-core] [PATCH RFC] base: Switch to use addpylib directive

On Mon, 2022-11-28 at 19:29 +0530, Vishal Bhoj wrote: > I get the below backtrace with this patch on master-next. The same > patchset works fine on debian-11. Are there any specific versions of > packages that need to be installed as  dependency ? > > Tested on host os: ubuntu-18.04/ubuntu-20.04

Re: [OE-core] [PATCH] linux-yocto: enable strict kernel module signing by default

On Mon, Nov 28, 2022 at 09:03:04AM -0500, Bruce Ashfield wrote: > On Mon, Nov 28, 2022 at 2:12 AM Mikko Rapeli wrote: > > > > On Sat, Nov 26, 2022 at 10:06:57PM -0500, Bruce Ashfield wrote: > > > On Fri, Nov 25, 2022 at 10:54 AM Mikko Rapeli > > > wrote: > > > > > > > > It's a good default and u

Re: [OE-core] [PATCH] linux-yocto: enable strict kernel module signing by default

On Mon, Nov 28, 2022 at 2:12 AM Mikko Rapeli wrote: > > On Sat, Nov 26, 2022 at 10:06:57PM -0500, Bruce Ashfield wrote: > > On Fri, Nov 25, 2022 at 10:54 AM Mikko Rapeli > > wrote: > > > > > > It's a good default and used in many Linux distributions. > > > Did not test out of tree modules if the

Re: [OE-core] [PATCH RFC] base: Switch to use addpylib directive

Hi, I get the below backtrace with this patch on master-next. The same patchset works fine on debian-11. Are there any specific versions of packages that need to be installed as dependency ? Tested on host os: ubuntu-18.04/ubuntu-20.04 tuxbake@b8b6586bfb2c:/source/source/poky/build$ bitbake -e

Re: [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4

Am Mo, 28. Nov 2022 um 14:13:36 +0100 schrieb Alexander Kanavin : We have plenty of options everywhere that are disabled specifically because there is no easy way to activate them. Fair enough. I've sent a v3 that completely removes the ssh_agent settings and includes your patch -=-=-=-=-=-

[oe-core][PATCHv3] gcr: add recipe for gcr-4, needed to build with gtk4

gcr-3 recipe is still needed for gnome projects that stick to gtk+3, rename to gcr3. Signed-off-by: Markus Volk --- ...ectly-handle-disabled-ssh_agent-opti.patch | 49 ++ ...build-fix-one-parallel-build-failure.patch | 0 ...1d02bb0148ca787ac4aead164d7c8ce2c4d8.patch | 0 .../

Re: [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4

It won’t if you add the patch. I have tested that: https://git.yoctoproject.org/poky-contrib/commit/?h=akanavin/package-version-updates-later (That’s a wip commit just to be aware of issues) We have plenty of options everywhere that are disabled specifically because there is no easy way to activat

Re: [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4

Am Mo, 28. Nov 2022 um 12:45:54 +0100 schrieb Alexander Kanavin : For gcr I suppose we can just disable the ssh stuff if it's not strictly required. I've noticed that you sent a patch to gcr that would fix it but 4.0.0 will presumably still search for the external ssh programs even if ssh_age

Re: [OE-core] [PATCH] linux-yocto: enable strict kernel module signing by default

On 28 Nov 2022, at 11:12, Mikko Rapeli via lists.openembedded.org wrote: > > Thus I don't think signed kernel modules can ever be stripped by > package.py or package.bbclass. It sounds like only option is to install > modules without stripping and signing to debug packages and then install > the

Re: [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4

For gcr I suppose we can just disable the ssh stuff if it's not strictly required. Alex On Mon, 28 Nov 2022 at 12:42, Markus Volk wrote: > > Am Mo, 28. Nov 2022 um 12:28:31 +0100 schrieb Alexander Kanavin > : > > This needs to be explained. And we need to find a better way to do it, > preferab

Re: [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4

Am Mo, 28. Nov 2022 um 12:28:31 +0100 schrieb Alexander Kanavin : This needs to be explained. And we need to find a better way to do it, preferably one that is acceptable upstream. Now thats somehow problematic. I had this issue also with seahorse, that wants to know at build time what targets

Re: [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4

Ah is it the same issue? Then please backport. https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/114 Alex On Mon, 28 Nov 2022 at 12:28, Alexander Kanavin via lists.openembedded.org wrote: > > On Mon, 28 Nov 2022 at 12:22, Markus Volk wrote: > > > +do_configure:prepend() { > > +sed -i "s|s

Re: [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4

On Mon, 28 Nov 2022 at 12:22, Markus Volk wrote: > +do_configure:prepend() { > +sed -i "s|ssh_add_path = find_program('ssh-add', required: > get_option('ssh_agent')).full_path()|ssh_add_path = '${bindir}/ssh-add'|" > ${S}/meson.build > +sed -i "s|ssh_agent_path = find_program('ssh-agent

Re: [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4

libsecret dependency has been moved to PACKAGECONFIG since its only needed for the 'ssh_agent' added the ssh_agent service files to FILES:${PN} to avoid an error if ssh_agent PACKAGECONFIG is selected: ERROR: gcr-4.0.0-r0 do_package: QA Issue: gcr: Files/directories were installed but not sh

[oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4

gcr-3 recipe is still needed for gnome projects that stick to gtk+3, rename to gcr3. Signed-off-by: Markus Volk --- ...build-fix-one-parallel-build-failure.patch | 0 ...1d02bb0148ca787ac4aead164d7c8ce2c4d8.patch | 0 .../gcr/{gcr_3.40.0.bb => gcr3_3.40.0.bb} | 8 ++- meta/recipes-gnome/

Re: [OE-core] [PATCH] linux-yocto: enable strict kernel module signing by default

Hi, On Sun, Nov 27, 2022 at 06:47:30PM +, Jack Mitchell wrote: > On 27/11/2022 03:34, Bruce Ashfield wrote: > > On Fri, Nov 25, 2022 at 11:11 AM Jack Mitchell wrote: > > > > > > On 25/11/2022 15:54, Mikko Rapeli wrote: > > > > It's a good default and used in many Linux distributions. > > > >

[OE-core] [PATCH v2 3/3] selftest/runqemu: reenable the nfs rootfs test

With the previous fixes the test can be run again, and it doesn't need all those extra steps. Runqemu takes care of everything automatically now. Signed-off-by: Alexander Kanavin --- meta/lib/oeqa/selftest/cases/runqemu.py | 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) di

[OE-core] [PATCH v2 1/3] qemu-helper: depend on unfs3 and pseudo directly

The eliminates having to do extra steps (e.g. meta-ide-support) when booting an image with a nfs mount as rootfs - startng runqemu with a nfs mount starts to 'just work' after building an image. Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/qemu/nativesdk-qemu-helper_1.0.bb | 2 +-

[OE-core] [PATCH v2 2/3] runqemu: do not hardcode the ip address of the nfs server when using tap

Rather, set it similarly to the overall network config. Signed-off-by: Alexander Kanavin --- scripts/runqemu | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/runqemu b/scripts/runqemu index 7bd9465593..04728673de 100755 --- a/scripts/runqemu +++ b/scripts/runqemu @@

Re: [OE-core] [PATCH] yocto-check-layer: add option to skip sublayer

On Mon, 2022-11-28 at 16:16 +0800, Yu, Mingli wrote: > From: Mingli Yu > > When do yocto compliance for a layer which contains many sublayers, > we may just want to check the top-level layer, so add one option to > achieve this. > > Before the patch: > $ yocto-check-layer-wrapper ../layers/met

Re: [OE-core] [PATCH 1/3] qemu-helper: depend on unfs3 and pseudo directly

On Mon, 2022-11-28 at 10:54 +0100, Alexander Kanavin wrote: > On Mon, 28 Nov 2022 at 00:58, Richard Purdie > wrote: > > NFS isn't really a dependency of qemu though. The thinking here was > > that you could boot a real board onto an NFS mount from your local > > system for development purposes. Th

Re: [OE-core] [PATCH 1/3] qemu-helper: depend on unfs3 and pseudo directly

On Mon, 28 Nov 2022 at 00:58, Richard Purdie wrote: > NFS isn't really a dependency of qemu though. The thinking here was > that you could boot a real board onto an NFS mount from your local > system for development purposes. That is why it was being included as > an SDK tool. > > Perhaps we shoul

Re: [OE-Core][master][langdale][kirkstone][PATCH v2] rng-tools: backport patch to adjust jitterentropy library to timeout/fail on long delay

On Sun, 27 Nov 2022 at 14:39, Xiangyu Chen wrote: > * add libgcc in RDEPENDS flag to solve testing failed in > core-image-full-cmdline > +RDEPENDS:${PN} = "libgcc" This needs to be better investigated first. The change looks like solving the symptom, but not the actual issue. Alex -=-=-=-=-=

[OE-core] [PATCH] yocto-check-layer: add option to skip sublayer

From: Mingli Yu When do yocto compliance for a layer which contains many sublayers, we may just want to check the top-level layer, so add one option to achieve this. Before the patch: $ yocto-check-layer-wrapper ../layers/meta-cloud-services --dependency ../layers/meta-openembedded ../layers