[OE-core] [oe-core][PATCH V2] recipetool: fixed uncaught NameError exception

From: Sarah Marsh When packaging a node application, a `NameError` can be thrown in create_npm.py if an optional npm dependency does not support Linux. Signed-off-by: Sarah Marsh --- scripts/lib/recipetool/create_npm.py | 1 + 1 file changed, 1 insertion(+) diff --git a/scripts/lib/recipetoo

Re: [OE-core] [PATCH 1/2] qemu: fix CVE-2017-16845

On 2018年04月26日 04:10, Martin Jansa wrote: FWIW: in http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu I have WIP qemu upgrade to 2.12.0 which includes this fix as well. Got it, thanks //Hongxu On Tue, Apr 24, 2018 at 9:37 AM, Hongxu Jia

[OE-core] ✗ patchtest: failure for `NameError` is currently thrown in create_npm.py

== Series Details == Series: `NameError` is currently thrown in create_npm.py Revision: 1 URL : https://patchwork.openembedded.org/series/11926/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have bee

[OE-core] [PATCH] `NameError` is currently thrown in create_npm.py

From: Sarah Marsh This happens if an optional npm dependency does not support Linux. Signed-off-by: Sarah Marsh --- scripts/lib/recipetool/create_npm.py | 1 + 1 file changed, 1 insertion(+) diff --git a/scripts/lib/recipetool/create_npm.py b/scripts/lib/recipetool/create_npm.py index fb57e7

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On 04/25/2018 12:54 PM, Martin Jansa wrote: On Thu, Jun 15, 2017 at 05:37:50PM +0100, Burton, Ross wrote: On 15 June 2017 at 17:17, Martin Kelly wrote: I am no expert, but running qemu -cpu help just says: kvm32 - "Common 32-bit KVM processor" kvm64 - "Common 64-bit KVM processor" My best g

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

There are actually 3 we need to consider for lowest common denominator. The one we build for, the one we build on and the one where we will run the qemu in the end. I mean the core2duo is probably best match for core2-64 DEFAULT used by qemux86-64 MACHINE. But it's not good match to emulate with

[OE-core] ✗ patchtest: failure for Only add uninative and checksum if inherited uninative class

== Series Details == Series: Only add uninative and checksum if inherited uninative class Revision: 1 URL : https://patchwork.openembedded.org/series/11924/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several te

[OE-core] [PATCH] Only add uninative and checksum if inherited uninative class

The checksum value is only calculated if the uninative class is inherited, so check for inherit before adding it to local.conf Signed-off-by: Jeremy Puhlman --- meta/classes/populate_sdk_ext.bbclass | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/meta/classes/populate_sd

Re: [OE-core] [PATCH 1/2] qemu: fix CVE-2017-16845

FWIW: in http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu I have WIP qemu upgrade to 2.12.0 which includes this fix as well. On Tue, Apr 24, 2018 at 9:37 AM, Hongxu Jia wrote: > During Qemu guest migration, a destination process invokes ps2 > post_load function. In that, i

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On Thu, Jun 15, 2017 at 05:37:50PM +0100, Burton, Ross wrote: > On 15 June 2017 at 17:17, Martin Kelly wrote: > > > I am no expert, but running qemu -cpu help just says: > > > > kvm32 - "Common 32-bit KVM processor" > > kvm64 - "Common 64-bit KVM processor" > > > > My best guess is that, running

[OE-core] [PATCH] mesa: Upgrade 17.3.8 -> 18.0.1

This includes changes from Mesa 18.0.0 and 18.0.1 releases. Mesa 18.0.0 is a new development release and 18.0.1 is a bug-fix release. You can find release notes here: - https://mesa3d.org/relnotes/18.0.0.html - https://mesa3d.org/relnotes/18.0.1.html Remove patch 0001-st-dri-Initialise-modi

[OE-core] ✗ patchtest: failure for Backports for morty (rev3)

== Series Details == Series: Backports for morty (rev3) Revision: 3 URL : https://patchwork.openembedded.org/series/8870/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the propo

[OE-core] ✗ patchtest: failure for Backports for pyro (rev4)

== Series Details == Series: Backports for pyro (rev4) Revision: 4 URL : https://patchwork.openembedded.org/series/8739/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the propos

Re: [OE-core] [PATCH][RFC] sstate: allow specifying indirect dependencies to exclude from sysroot

I realise that this is basically working around the fact that -native recipes don't get any RDEPENDS treatment AFAICS, except that RDEPENDS == DEPENDS, which is what I want to avoid, at least in certain cases... I guess if computing proper RDEPENDS for -native recipes was easy, it would have been

Re: [OE-core] [meta-networking][rocko][PATCH 1/2] kernel_wireless_regdb: Add class for embedding regulatory data into the kernel

Please don't cross-post this to multiple repository lists. meta-networking only exists in meta-openembedded, therefore this patch only needs to be sent to openembedded-devel. -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

[OE-core] [OE-Core][PATCH v2] tzdata: fix a typo.

Signed-off-by: Kevin Carli --- meta/recipes-extended/tzdata/tzdata_2018d.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-extended/tzdata/tzdata_2018d.bb b/meta/recipes-extended/tzdata/tzdata_2018d.bb index ec24f44962..f7fce80b75 100644 --- a/meta/recipes-exten

[OE-core] [PATCH][RFC] sstate: allow specifying indirect dependencies to exclude from sysroot

From: André Draszik Currently, a dependency on any -native recipe will pull in all dependencies of that -native recipe in the recipe sysroot. This behaviour might not always be wanted, e.g. when that -native recipe depends on build-tools that are not relevant for the current recipe. This change

[OE-core] ✗ patchtest: failure for "[meta-networking,rocko] kernel..." and 1 more

== Series Details == Series: "[meta-networking,rocko] kernel..." and 1 more Revision: 1 URL : https://patchwork.openembedded.org/series/11907/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

[OE-core] ✗ patchtest: failure for tzdata: fix a typo

== Series Details == Series: tzdata: fix a typo Revision: 1 URL : https://patchwork.openembedded.org/series/11906/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed ser

[OE-core] [rocko][PATCH 1/2] Revert "waf.bbclass: explicitly pass bindir and libdir if supported"

* this doesn't work correctly as discussed in: http://lists.openembedded.org/pipermail/openembedded-commits/2018-January/218460.html * some of the issues were fixed in master since then but not all, so revert it until it's completely resolved This reverts commit eac21f981337bfaddb2d67161a1ff0

[OE-core] [rocko][PATCH 2/2] scripts/test-dependencies.sh: remove

* with RSS used in pyro this script isn't very useful anymore * RSS makes sure that the dependencies are almost always deterministic the only case known to me where dependencies are different based on what was already built in TMPDIR are runtime dependencies resolved by shlibs code in package

[OE-core] [pyro][PATCH 3/3] scripts/test-dependencies.sh: remove

* with RSS used in pyro this script isn't very useful anymore * RSS makes sure that the dependencies are almost always deterministic the only case known to me where dependencies are different based on what was already built in TMPDIR are runtime dependencies resolved by shlibs code in package

[OE-core] [rocko][PATCH 0/2] Backports for rocko

The following changes since commit 1b18cdf6b8bdb00ff5df165b9ac7bc2b10c87d57: libvorbis: CVE-2018-5146 (2018-03-31 14:17:16 +0100) are available in the Git repository at: git://git.openembedded.org/openembedded-core-contrib jansa/rocko-backports http://cgit.openembedded.org/openembedded-co

[OE-core] [pyro][PATCH 1/3] sstate-sysroot-cruft.sh: Extend the whitelist

* add more php5 entries Signed-off-by: Martin Jansa --- scripts/sstate-sysroot-cruft.sh | 2 ++ 1 file changed, 2 insertions(+) diff --git a/scripts/sstate-sysroot-cruft.sh b/scripts/sstate-sysroot-cruft.sh index b6166aa1b2..d9917f5152 100755 --- a/scripts/sstate-sysroot-cruft.sh +++ b/scripts/

[OE-core] [pyro][PATCH 2/3] sstate-diff-machines.sh: Replace MACHINE_ARCH only at the beginning and separated with dash

* I had some components where the MACHINE name was also included in PV of allarch recipe which was tripping the script into saying that they have different signatures (because for one MACHINE was the string in PV replaced with 'MACHINE' and not for other MACHINEs Signed-off-by: Martin Jansa

[OE-core] [pyro][PATCH 0/3] Backports for pyro

The following changes since commit f8cc08fc7db26241d996ac710484d559eff5f9c0: distcc: Change SRC_URI (2018-04-02 17:09:07 +0100) are available in the Git repository at: git://git.openembedded.org/openembedded-core-contrib jansa/pyro-backports http://cgit.openembedded.org/openembedded-core-

[OE-core] [morty][PATCH 1/3] sstate-sysroot-cruft.sh: Extend the whitelist

* add more php5 entries Signed-off-by: Martin Jansa --- scripts/sstate-sysroot-cruft.sh | 2 ++ 1 file changed, 2 insertions(+) diff --git a/scripts/sstate-sysroot-cruft.sh b/scripts/sstate-sysroot-cruft.sh index b6166aa1b2..d9917f5152 100755 --- a/scripts/sstate-sysroot-cruft.sh +++ b/scripts/

[OE-core] [morty][PATCH 3/3] test-dependencies.sh: remove /sysroots* between component builds

* glibc is now the only component in morty release which is using TMPDIR/sysroots-components (normally used only after RSS): oe-core$ git grep "\${STAGING_DIR}-components" meta/recipes-core/glibc/glibc-locale.inc:LOCALETREESRC = "${STAGING_DIR}-components/${PACKAGE_ARCH}/glibc-stash-locale"

[OE-core] [morty][PATCH 2/3] sstate-diff-machines.sh: Replace MACHINE_ARCH only at the beginning and separated with dash

* I had some components where the MACHINE name was also included in PV of allarch recipe which was tripping the script into saying that they have different signatures (because for one MACHINE was the string in PV replaced with 'MACHINE' and not for other MACHINEs Signed-off-by: Martin Jansa

[OE-core] [morty][PATCH 0/3] Backports for morty

The following changes since commit 7b7cbba0bb93893029118e5798ec5831838a5bd9: sanity.bbclass: Improved error message (2018-04-05 15:22:59 +0100) are available in the Git repository at: git://git.openembedded.org/openembedded-core-contrib jansa/morty-backports http://cgit.openembedded.org/o

Re: [OE-core] [OE-Core][PATCH] tzdata: fix a typo

Hi Kevin, Thank you for this patch! A couple nitpics, however... On Wed 2018-04-25 @ 03:31:42 PM, Kevin Carli wrote: > Change-Id: I57f17f13aba2a2d26b9f6b72214563a86725def9 This isn't relevant to openembedded, please remove > Signed-off-by: Kevin Carli > --- > meta/recipes-extended/tzdata/tzda

[OE-core] [PATCH] base: improve do_unpack[cleandirs] logic

If a recipe sets S to ${WORKDIR}/ then the S != WORKDIR test doesn't work as expected. Use os.path.samefile() instead of string comparisons to do the right thing. Signed-off-by: Ross Burton --- meta/classes/base.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/cl

Re: [OE-core] GCC 8 hosts

Hi Joshua, I do now, they're in poky-contrib:ross/gcc8. The commit messages need rewriting before merging to master. Ross On 25 April 2018 at 14:05, Joshua Watt wrote: > On Wed, 2018-04-25 at 13:11 +0100, Burton, Ross wrote: >> Hi, >> >> Just thought I'd say that GCC 8 is going to start appear

Re: [OE-core] [meta-networking][rocko][PATCH 1/2] kernel_wireless_regdb: Add class for embedding regulatory data into the kernel

On Wed, Apr 25, 2018 at 3:47 PM, Krzysztof Kozlowski wrote: > Small embedded systems might: > 1. Want to get rid of daemons as much as possible (therefore be built >without CRDA), > 2. Not receive user-space incremental updates but an entire system >upgrade (with kernel). > > Add class ker

[OE-core] [meta-networking][rocko][PATCH 2/2] wireless-regdb: Bump version to latest upstream 2017.12.23

Bump the wireless-regdb recipe to use newest wireless regulatory database. Signed-off-by: Krzysztof Kozlowski --- .../{wireless-regdb_2016.06.10.bb => wireless-regdb_2017.12.23.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta-networking/recipes-connectivity/wireless

[OE-core] [meta-networking][rocko][PATCH 1/2] kernel_wireless_regdb: Add class for embedding regulatory data into the kernel

Small embedded systems might: 1. Want to get rid of daemons as much as possible (therefore be built without CRDA), 2. Not receive user-space incremental updates but an entire system upgrade (with kernel). Add class kernel_wireless_regdb which allows in such cases to embed the wireless regula

[OE-core] [OE-Core][PATCH] tzdata: fix a typo

Change-Id: I57f17f13aba2a2d26b9f6b72214563a86725def9 Signed-off-by: Kevin Carli --- meta/recipes-extended/tzdata/tzdata_2018c.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-extended/tzdata/tzdata_2018c.bb b/meta/recipes-extended/tzdata/tzdata_2018c.bb index c

Re: [OE-core] GCC 8 hosts

On Wed, 2018-04-25 at 13:11 +0100, Burton, Ross wrote: > Hi, > > Just thought I'd say that GCC 8 is going to start appearing in the > wild, I believe the first distro to ship with it will be Fedora 28. > As usual there are changes in behaviour so there are several > problems. > So far I've identif

[OE-core] GCC 8 hosts

Hi, Just thought I'd say that GCC 8 is going to start appearing in the wild, I believe the first distro to ship with it will be Fedora 28. As usual there are changes in behaviour so there are several problems. So far I've identified the following issues: * Python 2 crashes on startup * Kernel too

[OE-core] loopback interface not brought up on 'ifup -a' automatically

Hi, I am building an image using rocko branch and installing ifupdown package: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/ifupdown/ifupdown_0.8.16.bb?h=rocko If there is no loopback definition in /etc/network/interfaces file, then "ifup -a" brings lo interface up auto

[OE-core] sdk compiler output usable during build?

Hi, Quick question - is the sdk compiler supposed to be able to create executables that can be executed while the sdk package build is ongoing? Reason I'm asking is that my package nativesdk build errors out saying 'C compiler cannot create executables'. Reason for that seems to be that the outpu

[OE-core] [PATCH v3] toolchain-scripts: preserve host path in environment setup script

The environment setup script generated in the build directory sets the PATH variable by expanding ${PATH} which would have host paths filtered. Sourcing this script to run runqemu will not work as it complains host stty (/bin/stty) cannot be found. To resolve this, the script no longer expands ${P

[OE-core] [PATCH v2 8/8] gstreamer1.0: upgrade other packages to 1.14.0

From: Kai Kang Upgrade following packages from 1.12.4 to 1.14.0: * gstreamer1.0-omx * gstreamer1.0-python * gstreamer1.0-rtsp-server * gstreamer1.0-vaapi Signed-off-by: Kai Kang --- .../{gstreamer1.0-omx_1.12.4.bb => gstreamer1.0-omx_1.14.0.bb} | 4 ++-- .../{gstreamer1.0-python_1.12.4.b

[OE-core] [PATCH v2 4/8] gstreamer1.0-plugins-ugly: 1.12.4 -> 1.14.0

From: Kai Kang Upgrade gstreamer1.0-plugins-ugly from 1.12.4 to 1.14.0. * move packageconfigs 'lame', 'mpg123' and configure options '--disable-twolame' to -good that plugins have been moved to -good Signed-off-by: Kai Kang --- meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-ugly.inc

[OE-core] [PATCH v2 6/8] gstreamer1.0-libav: 1.12.4 -> 1.14.0

From: Kai Kang Upgrade gstreamer1.0-libav from 1.12.4 to 1.14.0. * remove 0001-hevcpred_msa.c-Fix-build-by-Including-libavcodec-hev.patch which has been fixed by upstream * add patch to fix host contamination Signed-off-by: Kai Kang --- ...a.c-Fix-build-by-Including-libavcodec-hev.patch | 3

[OE-core] [PATCH v2 7/8] gst-validate: 1.12.4 -> 1.14.0

From: Kai Kang Upgrade gst-validate from 1.12.4 to 1.14.0: * fix out of source tree build error Signed-off-by: Kai Kang --- .../gstreamer/gst-validate/out-of-tree-build.patch | 28 ++ ...t-validate_1.12.4.bb => gst-validate_1.14.0.bb} | 8 --- 2 files changed, 33 inse

[OE-core] [PATCH v2 5/8] gstreamer1.0-plugins-good: 1.12.4 -> 1.14.0

From: Kai Kang Upgrade gstreamer1.0-plugins-good from 1.12.4 to 1.14.0. * add packageconfig 'gtk' and configure option '--disable-qt' from -bad * add packageconfig 'lame', 'mpg123' and configure option '--disable-twolame' from -ugly * remove configure option '--disable-sunaudio' since plugin s

[OE-core] [PATCH v2 2/8] gstreamer1.0-plugins-base: 1.12.4 -> 1.14.0

From: Kai Kang Upgrade gstreamer1.0-plugins-base from 1.12.4 to 1.14.0. * add packageconfigs 'wayland', 'opengl', 'egl' and 'wayland' and configure option '--disable-cocoa' from -bad that related plugins have been moved from -bad to -base * backport patch to fix compile error: Couldn't find

[OE-core] [PATCH v2 3/8] gstreamer1.0-plugins-bad: 1.12.4 -> 1.14.0

From: Kai Kang Upgrade gstreamer1.0-plugins-bad from 1.12.4 to 1.14.0. * GStreamer OpenGL integration library is moved to -base, so move packageconfigs 'opengl', 'egl' and 'gles2' to -base * move packageconfig 'wayland' to -base * move configure option '--disable-cocoa' to -base * move package

[OE-core] [PATCH v2 1/8] gstreamer1.0: 1.12.4 -> 1.14.0

From: Kai Kang Upgrade gstreamer1.0 from 1.12.4 to 1.14.0. Signed-off-by: Kai Kang --- .../gstreamer/{gstreamer1.0_1.12.4.bb => gstreamer1.0_1.14.0.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-multimedia/gstreamer/{gstreamer1.0_1.12.4.bb => gstreamer

[OE-core] [PATCH v2 0/8] gstreamer1.0: 1.12.4 -> 1.14.0

From: Kai Kang V2: * Update patch format of out-of-tree-build.patch * Do add and remove patches which are moved from -bad to -base in 2 seperate commits The following changes since commit da3625c52e1ab8985fba4fc3d133edf92142f182: build-appliance-image: Update to sumo head revision (2018-04-2

[OE-core] ✗ patchtest: failure for gstreamer1.0: 1.12.4 -> 1.14.0

== Series Details == Series: gstreamer1.0: 1.12.4 -> 1.14.0 Revision: 1 URL : https://patchwork.openembedded.org/series/11903/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the