[OE-core] [PATCH] libinput: remove obsolete touchpad patch

This patch was a temporal workaround needed with 4.1 kernels. Remove it. Signed-off-by: Jose Alarcon --- ...ics-need-to-fake-new-touches-on-TRIPLETAP.patch | 72 -- meta/recipes-graphics/wayland/libinput_1.8.1.bb| 1 - 2 files changed, 73

[OE-core] [PATCH] gpg_sign: depress the owership warnings on homedir

A gpg command, e.g, called by get_gpg_version(), may trigger such a warning: gpg: WARNING: unsafe ownership on homedir '/home/user/.gnupg' This sort of warning is harmless so it can be depressed through specifying --no-permission-warning. Signed-off-by: Jia Zhang ---

Re: [OE-core] [PATCH] gpg_sign: depress the owership warnings on homedir

Sorry plz ignore this patch. I will send a new one. Jia On 08/24/2017 11:19 AM, Jia Zhang wrote: A gpg command, e.g, called by get_gpg_version(), may trigger such a warning: gpg: WARNING: unsafe ownership on homedir '/home/user/.gnupg' This sort of warning is harmless so it can be depressed

[OE-core] [PATCH] gpg_sign: depress the owership warnings on homedir

A gpg command, e.g, called by get_gpg_version(), may trigger such a warning: gpg: WARNING: unsafe ownership on homedir '/home/user/.gnupg' This sort of warning is harmless so it can be depressed through specifying --no-permission-warning. Signed-off-by: Jia Zhang ---

Re: [OE-core] [oe] State of bitbake world, Failed tasks 2017-08-19

> -Original Message- > From: openembedded-devel-boun...@lists.openembedded.org > [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of > Martin Jansa > Sent: Tuesday, August 22, 2017 21:20 > To: Patches and discussions about the oe-core layer; openembedded-devel >

[OE-core] [PATCH v2] webkitgtk: disable gobject-introspection on armv7a

From: Jackie Huang Disable gobject-introspection on armv7a and armv7ve to avoid do_compile failure: | qemu: uncaught target signal 11 (Segmentation fault) - core dumped | Segmentation fault Signed-off-by: Jackie Huang ---

[OE-core] [PATCH v3] devtool/standard: set a preferred provider when adding a new recipe with devtool

From: Juan M Cruz Alcaraz A recipe added with "devtool add" requires to be able to take precedence on recipes previously defined with PREFERRED_PROVIDER. By adding the parameter "--provides" to "devtool add" it is possible to specify an element to be

[OE-core] [PATCH] initramfs-framework/setup-live: quote bootparam_root variable

When bootparam_root was empty the if statement would resolve into invalid syntax instead of short circuiting after the -z, causing a boot failure. Signed-off-by: California Sullivan --- I stupidly didn't test an empty root parameter with my previous patch and

Re: [OE-core] [PATCH] boost: add python to default PACKAGECONFIG options

On 08/22/2017 09:26 PM, Randy MacLeod wrote: > On 2017-08-22 03:55 PM, Richard Purdie wrote: >> On Tue, 2017-08-22 at 12:51 -0700, Andre McCurdy wrote: >>> On Tue, Aug 22, 2017 at 12:42 AM, >>> wrote: From: Jackie Huang

Re: [OE-core] [PATCH 4/7] json-glib: convert to meson build

> -inherit gnomebase gettext lib_package gobject-introspection gtk-doc manpages > +inherit gnomebase-meson lib_package gobject-introspection gtk-doc manpages gettext is dropped, does it mean that it was not needed? > > -PACKAGECONFIG[manpages] = "--enable-man >

[OE-core] [PATCH] acl_2.25: improve reproducibility

Remove all host build references from the acl-ptest package. Signed-off-by: Juro Bystricky --- meta/recipes-support/attr/acl_2.2.52.bb | 5 + 1 file changed, 5 insertions(+) diff --git a/meta/recipes-support/attr/acl_2.2.52.bb

[OE-core] [PATCH] attr: improve reproducibility

Remove all host build references from the attr-ptest package. Signed-off-by: Juro Bystricky --- meta/recipes-support/attr/attr.inc | 6 ++ 1 file changed, 6 insertions(+) diff --git a/meta/recipes-support/attr/attr.inc b/meta/recipes-support/attr/attr.inc index

Re: [OE-core] [PATCH v2] kernel-yocto: relax BSP definition test

On Wed, Aug 23, 2017 at 8:20 PM, Bruce Ashfield < bruce.ashfi...@windriver.com> wrote: > commit 44aea7b873 [kernel-yocto: ensure that only valid BSPs are built] > introduced a new check to ensure that a valid BSP definition was found, > rather than building something that 'closely' matched the

Re: [OE-core] [PATCH 0/2] poky: update default kernel to 4.12 and lsb to 4.9

ignore this! misfire of my script to send the updated BSP test. Bruce On Wed, Aug 23, 2017 at 2:54 PM, Bruce Ashfield < bruce.ashfi...@windriver.com> wrote: > Hi all, > > To match the pull request to oe-core that adds the 4.12 kernel and removes > the 4.1 kernel these two patches bump the

[OE-core] [PATCH v2] kernel-yocto: relax BSP definition test

commit 44aea7b873 [kernel-yocto: ensure that only valid BSPs are built] introduced a new check to ensure that a valid BSP definition was found, rather than building something that 'closely' matched the current MACHINE. This check breaks valid configurations which do not have a bsp definition but

Re: [OE-core] [PATCH] kernel-yocto: relax BSP definition test

On 08/23/2017 03:07 PM, Andre McCurdy wrote: On Wed, Aug 23, 2017 at 11:54 AM, Bruce Ashfield wrote: commit 44aea7b873 [kernel-yocto: ensure that only valid BSPs are built] introduced a new check to ensure that a valid BSP definition was found, rather than

Re: [OE-core] [PATCH 1/7] meson: add a recipe and class from meta-oe

> + > +inherit setuptools3 > + > +RDEPENDS_${PN} = "ninja python3-core python3-modules" > + if (python3) modules depends on core, I believe core can be dropped from RDEPENDS > +BBCLASSEXTEND = "native" > -- > 2.14.1 > -- ___ Openembedded-core

Re: [OE-core] [PATCH] kernel-yocto: relax BSP definition test

On Wed, Aug 23, 2017 at 11:54 AM, Bruce Ashfield wrote: > commit 44aea7b873 [kernel-yocto: ensure that only valid BSPs are built] > introduced a new check to ensure that a valid BSP definition was found, > rather than building something that 'closely' matched the

Re: [OE-core] [PATCH] ca-certificates: prevent executing update-ca-certificates from host system

On 8/23/17 5:44 AM, Richard Purdie wrote: > On Wed, 2017-08-23 at 14:07 +0200, Andrej Valek wrote: >> I have found out that even master with HOSTTOOLS does not fix my >> problem. >> We use ASSUME_PROVIDED for ca-certificates-native due to corporate >> environment CAs. >> Since

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On 08/23/2017 02:31 PM, Denys Dmytriyenko wrote: On Sun, Aug 20, 2017 at 10:58:21PM -0400, Bruce Ashfield wrote: There was a bug in the search routines responsible for locating BSP definitions which returned a valid match if only the ktype matched. This meant that someone looking for

[OE-core] [PATCH] kernel-yocto: relax BSP definition test

commit 44aea7b873 [kernel-yocto: ensure that only valid BSPs are built] introduced a new check to ensure that a valid BSP definition was found, rather than building something that 'closely' matched the current MACHINE. This check breaks valid configurations which do not have a bsp definition but

[OE-core] [PATCH 0/2] poky: update default kernel to 4.12 and lsb to 4.9

Hi all, To match the pull request to oe-core that adds the 4.12 kernel and removes the 4.1 kernel these two patches bump the default kernel to 4.12 and also update LSB to use the 4.9 kernel. Build and boot testing was performed on all qemu architectures. Cheers, Bruce The following changes

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On Sun, Aug 20, 2017 at 10:58:21PM -0400, Bruce Ashfield wrote: > There was a bug in the search routines responsible for locating > BSP definitions which returned a valid match if only the ktype > matched. > > This meant that someone looking for "qemux86foo" (which is an > invalid definition)

Re: [OE-core] [PATCH 7/7] sysprof: convert to meson build

On Wed, Aug 23, 2017 at 10:06 AM, Alexander Kanavin wrote: > Drop autotools-specific patches. > > Rename polkit packageconfig option to sysprofd as 'polkit' does not > at all match what is happening. > > Remove --enable-compiler-warnings, as the equivalent in

Re: [OE-core] Fwd: kernel-yocto class requires BSP definition now

On Wed, Aug 23, 2017 at 1:18 PM, Andrei Gherzan wrote: > On Wed, Aug 23, 2017 at 6:08 PM, Bruce Ashfield > wrote: > >> >> >> On Wed, Aug 23, 2017 at 1:01 PM, Andrei Gherzan >> wrote: >> >>> On Wed, Aug 23, 2017 at 5:54 PM, Bruce

Re: [OE-core] Fwd: kernel-yocto class requires BSP definition now

On Wed, Aug 23, 2017 at 6:08 PM, Bruce Ashfield wrote: > > > On Wed, Aug 23, 2017 at 1:01 PM, Andrei Gherzan wrote: > >> On Wed, Aug 23, 2017 at 5:54 PM, Bruce Ashfield < >> bruce.ashfi...@windriver.com> wrote: >> >>> Already discussed with Khem and

Re: [OE-core] pkgconfig vs pkgconf

On 8/23/17 11:57 AM, Khem Raj wrote: > > On Wed, Aug 23, 2017 at 9:19 AM Mark Hatle > wrote: > > On 8/23/17 10:46 AM, Mark Hatle wrote: > > As of this morning, I'm not getting a warning about a preferred > provider being > >

[OE-core] [PATCH 5/7] libepoxy: convert to meson build

Signed-off-by: Alexander Kanavin --- meta/recipes-graphics/libepoxy/libepoxy_1.4.3.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/meta/recipes-graphics/libepoxy/libepoxy_1.4.3.bb b/meta/recipes-graphics/libepoxy/libepoxy_1.4.3.bb

[OE-core] [PATCH 6/7] libinput: convert to meson build

Drop autotools-specific patch. Drop libunwind option, as it is only used if tests are enabled (and they're unconditionally not enabled). Signed-off-by: Alexander Kanavin --- .../0001-tools-Fix-race-in-autotools-install.patch | 37 --

[OE-core] [PATCH 4/7] json-glib: convert to meson build

Note that meson flags for gobject introspection and gtk-doc appear to be non-standardized; going forward we should devise a common way to deal with it. Signed-off-by: Alexander Kanavin --- ...ble-gobject-introspection-when-cross-comp.patch | 32

[OE-core] [PATCH 2/7] gnomebase.bbclass: split into autotools and meson versions

gnomebase.bbclass unfortunately hardcodes the autotools inherit, so we have to introduce gnomebase-nobuildsystem.bbclass where the common bits between autotools and meson classes can be placed. Signed-off-by: Alexander Kanavin ---

[OE-core] [PATCH 3/7] gtk-doc.bbclass: add all directories where .so files are found to library search path

This should reduce the need to manually specify the path in recipes. Signed-off-by: Alexander Kanavin --- meta/classes/gtk-doc.bbclass | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/classes/gtk-doc.bbclass b/meta/classes/gtk-doc.bbclass index

[OE-core] [PATCH 1/7] meson: add a recipe and class from meta-oe

The original recipe has been provided and improved by: Ross Burton Ricardo Ribalda Delgado Adam C. Foltzer Peter Kjellerstedt Linus Svensson I have added a couple patches

[OE-core] [PATCH 0/7] Introduce meson build system

This patch series introduces meson recipe and class (that recipes should inherit in order to be built with meson). It also converts a few recipes from autotools to meson to establish that things basically work. Note that I haven't tackled the bigger items: gstreamer family of recipes, systed and

Re: [OE-core] Fwd: kernel-yocto class requires BSP definition now

On Wed, Aug 23, 2017 at 1:01 PM, Andrei Gherzan wrote: > On Wed, Aug 23, 2017 at 5:54 PM, Bruce Ashfield < > bruce.ashfi...@windriver.com> wrote: > >> Already discussed with Khem and Richard in the original >> thread. >> >> I'm sending another patch shortly to back this off to

Re: [OE-core] Fwd: kernel-yocto class requires BSP definition now

On Wed, Aug 23, 2017 at 5:54 PM, Bruce Ashfield < bruce.ashfi...@windriver.com> wrote: > Already discussed with Khem and Richard in the original > thread. > > I'm sending another patch shortly to back this off to a note/warning. > > That is nice but wouldn't that clutter the build logs for no

Re: [OE-core] pkgconfig vs pkgconf

On Wed, Aug 23, 2017 at 9:19 AM Mark Hatle wrote: > On 8/23/17 10:46 AM, Mark Hatle wrote: > > As of this morning, I'm not getting a warning about a preferred provider > being > > typo.. 'I'm -NOW- getting a warning' > > sorry for the confusion... > > > necessary to

Re: [OE-core] Fwd: kernel-yocto class requires BSP definition now

Already discussed with Khem and Richard in the original thread. I'm sending another patch shortly to back this off to a note/warning. Bruce On 08/23/2017 12:48 PM, Andrei Gherzan wrote: (Resending this from the yocto mailing list) Hello all, Since... commit

[OE-core] Fwd: kernel-yocto class requires BSP definition now

(Resending this from the yocto mailing list) Hello all, Since... commit b6f78c7a27d6d3acae63cf1fdb7b56c11c919830 Author: Bruce Ashfield Date: Sun Aug 20 22:58:21 2017 -0400 kernel-yocto: ensure that only valid BSPs are built There was a bug in the

Re: [OE-core] pkgconfig vs pkgconf

On 8/23/17 10:46 AM, Mark Hatle wrote: > As of this morning, I'm not getting a warning about a preferred provider being typo.. 'I'm -NOW- getting a warning' sorry for the confusion... > necessary to differentiate between pkgconfig and pkgconf. > > I've set the following to make it "go away".

Re: [OE-core] Change to kernel.bbclass broke kernel build when gcc does not support -ffile-prefix-map

> From: Bystricky, Juro [mailto:juro.bystri...@intel.com] > > Yes, the issue was reported by others as well, it should be fixed by this > patch: > > https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=master- > next=2b7646a113cca7698d8484fe14bdbb8683a5f8ab > > > From: Andrew Goodbody

[OE-core] [PATCH] vulkan: Only build when 'vulkan' distro flag is set

Only build with the vulkan distro flag is set. (References to this flag were found in the mesa recipe.) In addition, only set the RRECOMEMND to mesa, if 'opengl' flag is set. Mesa required opengl distro flag to build. Signed-off-by: Mark Hatle ---

[OE-core] [PATCH] vulkan distro flag update

I'm not sure if this is right or not, but it resolves the failures I was getting after updating oe this morning. I was attempting to run the yocto project compliant script, which runs bitbake -S none world. The results of this were an error that vulkan needed 'mesa-vulkan-drivers'. Looking at

[OE-core] pkgconfig vs pkgconf

As of this morning, I'm not getting a warning about a preferred provider being necessary to differentiate between pkgconfig and pkgconf. I've set the following to make it "go away". But I assume we need to set a default somewhere in the system... PREFERRED_PROVIDER_pkconfig = "pkgconfig"

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On Wed, Aug 23, 2017 at 7:58 AM, Richard Purdie wrote: > On Wed, 2017-08-23 at 10:42 -0400, Bruce Ashfield wrote: >> On 08/23/2017 10:40 AM, Khem Raj wrote: >> > >> > On Wed, Aug 23, 2017 at 5:37 AM, Bruce Ashfield >> > wrote: >>

Re: [OE-core] ✗ patchtest: failure for do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev6)

On Wed, 2017-08-23 at 13:04 +, Patchwork wrote: > == Series Details == > > Series: do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev6) > Revision: 6 > URL : https://patchwork.openembedded.org/series/6525/ > State : failure > > == Summary == > > > Thank you for submitting this

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On 08/23/2017 10:58 AM, Richard Purdie wrote: On Wed, 2017-08-23 at 10:42 -0400, Bruce Ashfield wrote: On 08/23/2017 10:40 AM, Khem Raj wrote: On Wed, Aug 23, 2017 at 5:37 AM, Bruce Ashfield wrote: On 08/22/2017 11:40 PM, Khem Raj wrote: On Sun, Aug 20,

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On Wed, 2017-08-23 at 10:42 -0400, Bruce Ashfield wrote: > On 08/23/2017 10:40 AM, Khem Raj wrote: > > > > On Wed, Aug 23, 2017 at 5:37 AM, Bruce Ashfield > > wrote: > > > > > > On 08/22/2017 11:40 PM, Khem Raj wrote: > > > > > > > > > > > > On Sun, Aug 20, 2017

Re: [OE-core] ✗ patchtest: failure for staging: add missing import errno to staging_populate_sysroot_dir

On Wed, 2017-08-23 at 14:03 +, Marko, Peter wrote: > >* Issue Series does not apply on top of target branch > >[test_series_merge_on_head] > > Suggested fixRebase your series on top of targeted branch > > Targeted branch master (currently at b1e482ae20) > > Richie is

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On 08/23/2017 10:40 AM, Khem Raj wrote: On Wed, Aug 23, 2017 at 5:37 AM, Bruce Ashfield wrote: On 08/22/2017 11:40 PM, Khem Raj wrote: On Sun, Aug 20, 2017 at 7:58 PM, Bruce Ashfield wrote: There was a bug in the search routines

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On Wed, Aug 23, 2017 at 5:37 AM, Bruce Ashfield wrote: > On 08/22/2017 11:40 PM, Khem Raj wrote: >> >> On Sun, Aug 20, 2017 at 7:58 PM, Bruce Ashfield >> wrote: >>> >>> There was a bug in the search routines responsible for locating >>>

Re: [OE-core] ✗ patchtest: failure for staging: add missing import errno to staging_populate_sysroot_dir

>* Issue Series does not apply on top of target branch >[test_series_merge_on_head] > Suggested fixRebase your series on top of targeted branch > Targeted branch master (currently at b1e482ae20) Richie is faster than patchwork :-) Master head commit b1e482ae20 is actually

Re: [OE-core] [PATCH 0/3] Restructure python2 and python3 packaging system

On Thu, 2017-08-17 at 10:11 -0700, Alejandro Hernandez wrote: > Alejandro Hernandez (3): >   python: Restructure python packaging and replace it with > autopackaging >   python3: fix RDEPENDS on several recipes, due to non-existent > python3 > packages >   python3: Restructure python3

Re: [OE-core] do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature.

On 23/08/17 14:46, Richard Purdie wrote: > On Wed, 2017-08-23 at 14:39 +0200, Kristian Amlie wrote: >> I don't understand why I'm getting patch failures. This is rebased to >> cutting edge master. Trying one more time... > > Its because you're patching documentation which is maintained in a >

Re: [OE-core] [PATCH v5] do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature.

On 23/08/17 14:47, Richard Purdie wrote: > On Wed, 2017-08-23 at 14:39 +0200, Kristian Amlie wrote: >> From: Kristian Amlie >> >> This is a direct followup from the earlier f6a064d969f414 commit in >> wic. It works more or less the same way: The variable specifies a >>

Re: [OE-core] [PATCH V2 6/9] core/target/ssh.py: replace decode errors

On Tue, 2017-08-22 at 22:55 +1200, Paul Eggleton wrote: > On Tuesday, 22 August 2017 1:23:10 PM NZST Robert Yang wrote: > > > > There might be wild strings when read from target (especially when > > reading ptest results), replace the errors to avoid breaking the > > test. > > > > Fixed: (Not

[OE-core] ✗ patchtest: failure for staging: add missing import errno to staging_populate_sysroot_dir

== Series Details == Series: staging: add missing import errno to staging_populate_sysroot_dir Revision: 1 URL : https://patchwork.openembedded.org/series/8447/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response.

[OE-core] ✗ patchtest: failure for do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev6)

== Series Details == Series: do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev6) Revision: 6 URL : https://patchwork.openembedded.org/series/6525/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several

Re: [OE-core] long (never ending?) do_install for adwaita-icon-theme

On 08/22/2017 09:46 PM, Trevor Woerner wrote: Do you have any kind of logs for when it happens? Unfortunately not, I'll try to keep some the next time it happens. But I have a suspicion it might be related to a build failure. Earlier today I was doing a build which failed in a recipe that

Re: [OE-core] [PATCH v5] do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature.

On Wed, 2017-08-23 at 14:39 +0200, Kristian Amlie wrote: > From: Kristian Amlie > > This is a direct followup from the earlier f6a064d969f414 commit in > wic. It works more or less the same way: The variable specifies a > list > of directories relative to the root of

Re: [OE-core] do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature.

On Wed, 2017-08-23 at 14:39 +0200, Kristian Amlie wrote: > I don't understand why I'm getting patch failures. This is rebased to > cutting edge master. Trying one more time... Its because you're patching documentation which is maintained in a separate repository. Separating that from the patch

Re: [OE-core] [PATCH] ca-certificates: prevent executing update-ca-certificates from host system

On Wed, 2017-08-23 at 14:07 +0200, Andrej Valek wrote: > I have found out that even master with HOSTTOOLS does not fix my > problem. > We use ASSUME_PROVIDED for ca-certificates-native due to corporate > environment CAs. > Since nativesdk-ca-certificates depends on ca-certificates-native > whichis

[OE-core] [PATCH] staging: add missing import errno to staging_populate_sysroot_dir

Fixes error "Exception: NameError: name 'errno' is not defined" during build-sysroots.bb:do_build_target_sysroot Signed-off-by: Marko, Peter --- meta/classes/staging.bbclass | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/classes/staging.bbclass

Re: [OE-core] do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature.

I don't understand why I'm getting patch failures. This is rebased to cutting edge master. Trying one more time... -- Kristian -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

[OE-core] [PATCH v5] do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature.

From: Kristian Amlie This is a direct followup from the earlier f6a064d969f414 commit in wic. It works more or less the same way: The variable specifies a list of directories relative to the root of the rootfs, and these directories will be excluded from the resulting

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On 08/22/2017 11:40 PM, Khem Raj wrote: On Sun, Aug 20, 2017 at 7:58 PM, Bruce Ashfield wrote: There was a bug in the search routines responsible for locating BSP definitions which returned a valid match if only the ktype matched. This meant that someone looking

[OE-core] [PATCH 1/2] recipetool: create: fix broken import in npm module

With "import oe" in create_npm.py you get "AttributeError: module 'oe' has no attribute 'package'" when it tries to call oe.package.npm_split_package_dirs(). Signed-off-by: Paul Eggleton --- scripts/lib/recipetool/create_npm.py | 2 +- 1 file changed, 1

[OE-core] [PATCH 2/2] recipetool: create: fix npm license code regression

OE-Core commit 1df60b09f7a60427795ec828c9c7180e4e52f98c caused a regression in npm handling since it still expected to be able to get the results of the license handling, but this no longer happens until after the npm plugin is called. Thus, call the license handling function ourselves here (which

[OE-core] [PATCH 0/2] recipetool npm regression fixes

Fixes for a couple of regressions caused by recent patches to recipetool. The following changes since commit f59e729f98ef9b506b0cfdc415567e03ec87f2a9: runqemu: Use virtio to mount cdrom drives (2017-08-23 12:06:46 +0100) are available in the git repository at:

Re: [OE-core] [PATCH] ca-certificates: prevent executing update-ca-certificates from host system

Hello Richard, I have found out that even master with HOSTTOOLS does not fix my problem. We use ASSUME_PROVIDED for ca-certificates-native due to corporate environment CAs. Since nativesdk-ca-certificates depends on ca-certificates-native which is not built, so it could not be found.

[OE-core] ✗ patchtest: failure for do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev5)

== Series Details == Series: do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev5) Revision: 5 URL : https://patchwork.openembedded.org/series/6525/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several

[OE-core] ✗ patchtest: failure for do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev4)

== Series Details == Series: do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev4) Revision: 4 URL : https://patchwork.openembedded.org/series/6525/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several

[OE-core] [PATCH v4] do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature.

From: Kristian Amlie This is a direct followup from the earlier f6a064d969f414 commit in wic. It works more or less the same way: The variable specifies a list of directories relative to the root of the rootfs, and these directories will be excluded from the resulting

Re: [OE-core] do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature.

Ping, third rebase now! This is related to https://bugzilla.yoctoproject.org/show_bug.cgi?id=11688. -- Kristian -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

[OE-core] [PATCH v4] do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature.

From: Kristian Amlie This is a direct followup from the earlier f6a064d969f414 commit in wic. It works more or less the same way: The variable specifies a list of directories relative to the root of the rootfs, and these directories will be excluded from the resulting

[OE-core] ✗ patchtest: failure for libxml2: Fix CVE-2017-8872 (rev2)

== Series Details == Series: libxml2: Fix CVE-2017-8872 (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/7105/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on

[OE-core] [PATCH V2] libxml2: Fix CVE-2017-8872

fix global-buffer-overflow in htmlParseTryOrFinish (HTMLparser.c:5403) https://bugzilla.gnome.org/show_bug.cgi?id=775200 Here is the reproduce steps on ubuntu 16.04, use clang with "-fsanitize=address" ... export CC="clang" export CFLAGS="-fsanitize=address" ./configure --disable-shared make

Re: [OE-core] [PATCH] base.bbclass: trim duplicated whitespaces from BUILDCFG_VARS

Hi, Richard: OK, understood. So for this kind of issues, the BSP developers should pay attention by themselves not to introduce any duplicated whitespaces in their meta-xxx layers? //Ming Liu 2017-08-23 9:59 GMT+02:00 Richard Purdie : > On Wed, 2017-08-23

Re: [OE-core] [PATCH] boost: add python to default PACKAGECONFIG options

> -Original Message- > From: MacLeod, Randy > Sent: Wednesday, August 23, 2017 09:27 > To: Richard Purdie; Andre McCurdy; Huang, Jie (Jackie) > Cc: OE Core mailing list > Subject: Re: [OE-core] [PATCH] boost: add python to default PACKAGECONFIG > options > > On 2017-08-22 03:55 PM,

Re: [OE-core] [PATCH] base.bbclass: trim duplicated whitespaces from BUILDCFG_VARS

On Wed, 2017-08-23 at 09:57 +0200, Ming Liu wrote: > Yes, it's in master-next not in master branch, but wouldn't that mean > it's accepted as a proper fix, or? It means it was queued for testing, I've dropped it from master-next now as the comments from Chris still apply from last time. Cheers,

Re: [OE-core] [PATCH] base.bbclass: trim duplicated whitespaces from BUILDCFG_VARS

Hi, Yes, it's in master-next not in master branch, but wouldn't that mean it's accepted as a proper fix, or? //Ming Liu 2017-08-23 9:50 GMT+02:00 Richard Purdie : > On Wed, 2017-08-23 at 04:33 +0200, Ming Liu wrote: > > Hi, Andre: > > > > Arha, I did not

Re: [OE-core] [PATCH] base.bbclass: trim duplicated whitespaces from BUILDCFG_VARS

On Wed, 2017-08-23 at 04:33 +0200, Ming Liu wrote: > Hi, Andre: > > Arha, I did not know that when I was submitting the patch, may I know > why it's rejected at that moment? Since even with the alternative > fixes, the developers still could introduce duplicated whitespaces in > their BSP layers

[OE-core] [PATCH 1/2] oeqa/parselogs: Ignore device node warnings on mips

THe newner kernels have ope firmware support enabled which leads to warnings during boot on mips. These aren't interesting and we should ignore them. Signed-off-by: Richard Purdie --- meta/lib/oeqa/runtime/cases/parselogs.py | 2 ++ 1 file changed, 2

[OE-core] [PATCH 2/2] runqemu: Use virtio to mount cdrom drives

The IDE driver in the kernel is fragile and in 4.12 is causing backtraces. To unblock 4.12 kernel merging use the virtio CD driver instead to mount iso images which should be faster and more stable. Signed-off-by: Richard Purdie ---