Re: [OE-core] [PATCH] oeqa/selftest/cases/devtool.py: avoid .pyc race

On Mon, Sep 28, 2020 at 9:32 PM Tim Orling wrote: > > From: Tim Orling > > In certain conditions, most likely under heavy load on the > AutoBuiler, the prebuilt .pyc files are attempting to be > executed before they have been completely copied. Avoid > this by not copying the .pyc files (nor the

[OE-core] [PATCH] systemd: Use ROOTPREFIX without suffixed slash in systemd.pc.in

Signed-off-by: Khem Raj --- ...se-ROOTPREFIX-without-suffixed-slash.patch | 37 +++ meta/recipes-core/systemd/systemd_246.6.bb| 1 + 2 files changed, 38 insertions(+) create mode 100644 meta/recipes-core/systemd/systemd/0001-systemd.pc.in-use-ROOTPREFIX-without-suffixed-sla

[OE-core] [PATCH] harfbuzz: Refresh patch

Because two modifications conflict in the patch, do_patch will make an error when using patch as a patchtool. Signed-off-by: Zang Ruochen --- .../harfbuzz/harfbuzz/version-race.patch | 76 +++ 1 file changed, 26 insertions(+), 50 deletions(-) diff --git a/meta/recipes-grap

Re: [OE-core] [meta-oe][PATCH v4 6/6] tunes/armv8: move to a new location

Em ter., 29 de set. de 2020 às 21:38, Jon Mason escreveu: > > On Tue, Sep 29, 2020 at 5:58 PM Khem Raj wrote: > > > > Lets not do it. For couple of reasons, > > > > There are BSPs including these include files which are using same > > branch across multiple yocto releases, this will break them >

Re: [OE-core] [PATCH] bash: fix CVE-2019-18276

On Tue, Sep 29, 2020 at 6:21 PM Mittal, Anuj wrote: > > On Mon, 2020-09-28 at 20:45 -0700, Khem Raj wrote: > > On Mon, Sep 28, 2020 at 8:27 AM Khem Raj wrote: > > > On Wed, Sep 23, 2020 at 11:00 PM Yu, Mingli < > > > mingli...@windriver.com> wrote: > > > > Hi Anuj, > > > > > > > > On 9/24/20 10:5

Re: [OE-core] [PATCH] bash: fix CVE-2019-18276

On Mon, 2020-09-28 at 20:45 -0700, Khem Raj wrote: > On Mon, Sep 28, 2020 at 8:27 AM Khem Raj wrote: > > On Wed, Sep 23, 2020 at 11:00 PM Yu, Mingli < > > mingli...@windriver.com> wrote: > > > Hi Anuj, > > > > > > On 9/24/20 10:50 AM, Anuj Mittal wrote: > > > > Hi Mingli, > > > > > > > > On Thu,

Re: [OE-core] [meta-oe][PATCH v4 6/6] tunes/armv8: move to a new location

On Tue, Sep 29, 2020 at 5:58 PM Khem Raj wrote: > > Lets not do it. For couple of reasons, > > There are BSPs including these include files which are using same > branch across multiple yocto releases, this will break them > files under include/ are common at arch level, this moved the > CPU imple

[OE-core] OpenEmbedded Happy Hour September 30 9pm/2100 UTC

Just a reminder about our upcoming OpenEmbedded Happy Hour on September 30 for Oceania/Asia timezones @ 2100/9pm UTC (5pm EDT): https://www.openembedded.org/wiki/Calendar https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+September+30&iso=20200930T21 -- Denys -=-

[OE-core] [PATCH] oeqa/selftest/devtool: Add sync call to test teardown

Devtool tests are heavy on IO and if bitbake can't write out its caches, we see timeouts. Call "sync" around the tests to ensure the IO queue doesn't get too large, taking any IO hit here rather than in bitbake shutdown. Signed-off-by: Richard Purdie --- meta/lib/oeqa/selftest/cases/devtool.py |

Re: [OE-core] [PATCH 1/2] bjam-native: don't do debug builds

On Tue, 2020-09-29 at 23:16 +0100, Ross Burton wrote: > Previously this recipe was changed to do debug builds because > otherwise insane > warns that the binary is already stripped. > > However, debug builds for boost.build also pass -O0. It turns out > that given > how large Boost is (or, how ba

[OE-core] [PATCH 1/2] bjam-native: don't do debug builds

Previously this recipe was changed to do debug builds because otherwise insane warns that the binary is already stripped. However, debug builds for boost.build also pass -O0. It turns out that given how large Boost is (or, how bad boost.build is) doing a release build with -O3 knocks a third off

[OE-core] [PATCH 2/2] boost: move the build directory outside of S

Instead of manually creating and deleting build directories, follow the idioms by setting B to WORKDIR/build, setting do_configure[cleandirs], and using ${B} where appropriate. Signed-off-by: Ross Burton --- meta/recipes-support/boost/boost.inc | 12 +--- 1 file changed, 9 insertions(+),

Re: [OE-core] [meta-oe][PATCH v4 6/6] tunes/armv8: move to a new location

Lets not do it. For couple of reasons, There are BSPs including these include files which are using same branch across multiple yocto releases, this will break them files under include/ are common at arch level, this moved the CPU implementation ( cortex* ) under it, seems odd and even more odd wh

[OE-core] [PATCH] systemd: Drop 0023-Fix-field-efi_loader_entry_one_shot_stat-has-incompl.patch

This patch is no longer needed as upstream has added including part of this include list, perhaps thats all is what was needed to make it portable Refresh 0001-Handle-missing-gshadow.patch Signed-off-by: Khem Raj --- .../systemd/0001-Handle-missing-gshadow.patch | 20 +--- ...ader_entry

[OE-core] [PATCH 2/2] Map license names PSF and PSFv2 to PSF-2.0

According to SDPX.org "Python License 2.0" is the overall Python license, which is comprised of several licenses. "Python Software Foundation License 2.0" is part of the complete Python license, but is also used independently by some projects. So far the license names PSF and PSFv2 found in LICENS

[OE-core] [PATCH 0/2] Map license names PSF and PSFv2 to PSF-2.0

According to SDPX.org "Python License 2.0" is the overall Python license, which is comprised of several licenses. "Python Software Foundation License 2.0" is part of the complete Python license, but is also used independently by some projects. So far the license names PSF and PSFv2 found in LICENS

[OE-core] [PATCH 1/2] Add license text for PSF-2.0

Signed-off-by: Mark Jonas --- meta/files/common-licenses/PSF-2.0 | 49 ++ 1 file changed, 49 insertions(+) create mode 100644 meta/files/common-licenses/PSF-2.0 diff --git a/meta/files/common-licenses/PSF-2.0 b/meta/files/common-licenses/PSF-2.0 new file mode 100644

Re: [OE-core] [PATCH 6/6] lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+ builds

On Tue, Sep 29, 2020 at 4:55 AM Bruce Ashfield wrote: > > Steve, > > Attached is the minimal backport that I was able to pull together. > Chuck that in the queue and you can take the latest 5.4.x -stable > updates. > > So it looks like we can get away without a version bump for now. > > It passed

Re: [OE-core] [PATCH 2/4] pseudo: Ignore mismatched inodes from the db

On Mon, 28 Sep 2020 22:42:18 +0100 "Richard Purdie" wrote: > It helps to know that! I wasn't sure if you'd hate the path filtering. It was on my to-do list at one point to be able to denote "the pseudo filesystem" in some way and just politely ignore everything outside it. And, possibly, switch

[OE-core] [PATCH 2/2] cve-check: add CVE_CHECK_REPORT_PATCHED variable to suppress reporting of patched CVEs

Default behavior is not changed. To suppress patched CVEs, set: CVE_CHECK_REPORT_PATCHED = "" Signed-off-by: Chris Laplante --- meta/classes/cve-check.bbclass | 38 -- 1 file changed, 22 insertions(+), 16 deletions(-) diff --git a/meta/classes/cve-check.

[OE-core] [PATCH 1/2] cve-check: introduce CVE_CHECK_RECIPE_FILE variable to allow changing of per-recipe check file

The addition of this variable also makes it possible to change the output suffix of the check files, e.g. in local.conf: CVE_CHECK_MANIFEST_append = ".txt" CVE_CHECK_RECIPE_FILE_append = ".txt" Signed-off-by: Chris Laplante --- meta/classes/cve-check.bbclass | 8 1 file changed, 4 inse

[OE-core] Yocto Project Status WW39'20

Current Dev Position: YP 3.2 M4 Next Deadline: YP 3.2 M4 Feature Freeze - Now Next Team Meetings: * Bug Triage meeting Thursday Oct. 1st at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Oct. 6th at 8am PDT (

Re: [OE-core] [PATCH 6/6] lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+ builds

Steve, Attached is the minimal backport that I was able to pull together. Chuck that in the queue and you can take the latest 5.4.x -stable updates. So it looks like we can get away without a version bump for now. It passed all my local testing, but let me know if it causes you issues. Bruce O

Re: [OE-core] [PATCH 2/2] meson: set correct cpu and cpu-family for multilib SDKs

On Fri, 2020-09-18 at 11:50 +0200, Christian Perkonig via lists.openembedded.org wrote: > meson use to cross compile a cross-file. This file is special for > every build environment. So if you have a multilib SDK for aarch64 > and arm the cpu_family and the cpu variable in the [HOST]-section > of

Re: [OE-core] [PATCH 1/2] meson: remove shell wrapper for meson

On Tue, 2020-09-29 at 08:33 +0200, Christian Perkonig via lists.openembedded.org wrote: > Can someone review the patches I don't doubt there is a problem here but simply reverting them is going to cause someone else a different problem for which the patch was originally added. Is there not a way