[OE-core] [PATCH 0/1] packagefeed-stability.bbclass: cleansstate should remove pkgs from deploy dir

The following changes since commit c86bf80abd87acb0da5860806822c64ec9dee089: oeqa.buildperf: use oe.path.remove() (2016-08-17 10:35:27 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rt/feed http://cgit.openembedded.org/cgit.cgi/openembed

[OE-core] [PATCH 1/1] packagefeed-stability.bbclass: cleansstate should remove pkgs from deploy dir

"bitbake recipe -ccleansstate" should remove binary pkgs from deploy dir as normal cleansstate does without packagefeed-stability.bbclass. Signed-off-by: Robert Yang --- meta/classes/packagefeed-stability.bbclass | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/classes/

[OE-core] [PATCH 7/8] qemuboot.bbclass: add it for runqemu

It saves vars in ${DEPLOY_DIR_IMAGE}/qemuboot.py, and runqemu will import it. The bsp which can be boot by runqemu will inherit it. Signed-off-by: Robert Yang --- meta/classes/qemuboot.bbclass | 59 +++ 1 file changed, 59 insertions(+) create mode 100644

[OE-core] [PATCH 1/8] qemu.inc: inherit qemu-boot.bbclass

All qemu boards should be able to boot by runqemu. Signed-off-by: Robert Yang --- meta/conf/machine/include/qemu.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/conf/machine/include/qemu.inc b/meta/conf/machine/include/qemu.inc index f44dbe6..2bc4dc2 100644 --- a/meta/conf/machin

[OE-core] [PATCH 0/8] runqemu: refactor it and remove machine knowledge

Previously, runqemu had hard coded machine knowledge, which limited its usage, for example, qemu can boot genericx86, but runqemu can't, we need edit runqemu/runqemu-internal a lot if we want to boot genericx86. Now bsp conf files can set vars to make it can be boot by runqemu, and qemuboot.bbclas

[OE-core] [PATCH 6/8] qemuppc.conf: set vars for runqemu

Signed-off-by: Robert Yang --- meta/conf/machine/qemuppc.conf | 6 ++ 1 file changed, 6 insertions(+) diff --git a/meta/conf/machine/qemuppc.conf b/meta/conf/machine/qemuppc.conf index bf0038d..dbadf5a 100644 --- a/meta/conf/machine/qemuppc.conf +++ b/meta/conf/machine/qemuppc.conf @@ -11,3

[OE-core] [PATCH 5/8] arch-mips.inc: set vars for runqemu

Both qemumips and qemumips64 can use these info to boot, so set these info in arch-mips.inc. Signed-off-by: Robert Yang --- meta/conf/machine/include/mips/arch-mips.inc | 6 ++ 1 file changed, 6 insertions(+) diff --git a/meta/conf/machine/include/mips/arch-mips.inc b/meta/conf/machine/inc

[OE-core] [PATCH 8/8] runqemu: refactor it and remove machine knowledge

Previously, runqemu had hard coded machine knowledge, which limited its usage, for example, qemu can boot genericx86, but runqemu can't, we need edit runqemu/runqemu-internal a lot if we want to boot genericx86. Now bsp conf files can set vars to make it can be boot by runqemu, and qemuboot.bbclas

[OE-core] [PATCH 2/8] arm: set vars for runqemu

These info are from old runqemu. Signed-off-by: Robert Yang --- meta/conf/machine/include/tune-cortexa8.inc | 4 meta/conf/machine/qemuarm.conf | 5 + 2 files changed, 9 insertions(+) diff --git a/meta/conf/machine/include/tune-cortexa8.inc b/meta/conf/machine/include/tun

[OE-core] [PATCH 4/8] arch-x86.inc: set vars for runqemu

These vars will be used by qemuboot.class, all the x86 and x86-64 bsps can be boot by runqemu in theory, so add the settings to arch-x86.inc. Signed-off-by: Robert Yang --- meta/conf/machine/include/x86/arch-x86.inc | 15 +++ 1 file changed, 15 insertions(+) diff --git a/meta/conf/m

[OE-core] [PATCH 3/8] qemuarm64.conf: set vars for runqemu

Signed-off-by: Robert Yang --- meta/conf/machine/qemuarm64.conf | 9 + 1 file changed, 9 insertions(+) diff --git a/meta/conf/machine/qemuarm64.conf b/meta/conf/machine/qemuarm64.conf index f59fb15..fd73583 100644 --- a/meta/conf/machine/qemuarm64.conf +++ b/meta/conf/machine/qemuarm64.c

[OE-core] [PATCH] libdrm: 2.4.68 -> 2.4.70

Upgrade libdrm from 2.4.68 to 2.4.70. Signed-off-by: Dai Caiyun --- meta/recipes-graphics/drm/libdrm/fix_O_CLOEXEC_undeclared.patch | 2 +- meta/recipes-graphics/drm/{libdrm_2.4.68.bb => libdrm_2.4.70.bb} | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) rename meta/recipes-graphics/d

[OE-core] [PATCH] gdk-pixbuf: 2.34.0 -> 2.35.3

Upgrade gdk-pixbuf from 2.34.0 to 2.35.3. Signed-off-by: Wang Xin --- .../gdk-pixbuf/{gdk-pixbuf_2.34.0.bb => gdk-pixbuf_2.35.3.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-gnome/gdk-pixbuf/{gdk-pixbuf_2.34.0.bb => gdk-pixbuf_2.35.3.bb} (96%) diff

[OE-core] [PATCH] glib-2.0: 2.48.1 -> 2.48.2

1) Upgrade glib-2.0 from 2.48.1 to 2.48.2. 2) Modify Enable-more-tests-while-cross-compiling.patch, since the data has changed. Signed-off-by: Wang Xin --- .../glib-2.0/glib-2.0/Enable-more-tests-while-cross-compiling.patch | 2 +- meta/recipes-core/glib-2.0/{glib-2.0_2.48.1.bb => glib-2.0_2.

[OE-core] [PATCH V2] bash: fix run-intl ptest failed

1. Filter the extra white space in intl.right When the sub-test unicode2.sub of intl.tests executed, it produced compact results without extra white space, compared to intl.right, it failed. So we need to filter the extra white space in intl.right. Import this patch for intl.right

[OE-core] [PATCH] kexec-tools: 2.0.12 -> 2.0.13

Upgrade kexec-tools from 2.0.12 to 2.0.13. Signed-off-by: Dai Caiyun --- .../kexec/{kexec-tools_2.0.12.bb => kexec-tools_2.0.13.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-kernel/kexec/{kexec-tools_2.0.12.bb => kexec-tools_2.0.13.bb} (88%) diff

[OE-core] [PATCH V5] rootfs.py: allow removal of unneeded packages

Paul and I had a discussion about this a couple weeks ago. We want to allow for the removal of certain packages, regardless of the image features containing "read-only-rootfs". For example, if something has a runtime dependency on update-rc.d or shadow, we need a way to remove these packages regar

[OE-core] [PATCH V5] rootfs.py: allow removal of unneeded packages

Current functionality allows for the removal of certain packages based on the read-only image feature. This patch extends this functionality by adding the FORCE_RO_REMOVE variable, which will remove these packages regardless of any image features. [ YOCTO #9491 ] Signed-off-by: Stephano Cetola -

[OE-core] [PATCH 1/2] oeqa/sdkext: Adds test cases for devtool extensible SDK

Adds test cases in order to increase devtool verification. The changes cover add, reset, build make, build cmake, extend autotools recipe creation, kernel module and node.js. Signed-off-by: Francisco Pedraza --- meta/lib/oeqa/sdkext/devtool.py| 90 -- .../

[OE-core] [PATCH 2/2] oeqa/selftest Adds eSDK test cases to devtool verification.

The covered functions are, install libraries headers, image generation binary feeds and sdk update devtool. Signed-off-by: Francisco Pedraza --- meta/lib/oeqa/selftest/eSDK.py | 147 + 1 file changed, 147 insertions(+) create mode 100644 meta/lib/oeqa/se

Re: [OE-core] [PATCH] testimage: allow using kvm when running qemux86* machines

On 08/16/2016 06:08 PM, Bill Randle wrote: > Using kvm can provide significant speedups when running qemux86* machines > on an x86* host. Enabled by using the new QEMU_USE_KVM variable. > > [YOCTO #9298] > > Signed-off-by: Bill Randle Acked-by: Aníbal Limón > --- > meta/lib/oeqa/targetcontro

Re: [OE-core] [PATCH] mmc-utils: update to latest git revision

Hi, 2016-08-08 19:25 GMT+09:00 Burton, Ross : > > On 8 August 2016 at 11:09, Nobuhiro Iwamatsu wrote: >> >> mmc-utils will change the revision of Git in version 0.1. We are using >> the now of any revision in PV, >> we do not know from version of package. >> Because I want to be seen that this re

[OE-core] [PATCH v2 0/1] wget: Add --ssh-askpass support

This adds the --ssh-askpass=COMMAND option which is disabled by default. --use-askpass=COMMAND will request the username and password for a given URL by executing the external program COMMAND. If COMMAND is left blank, then the external program in the environment variable WGET_ASKPASS will be use

[OE-core] [PATCH v2 1/1] wget: Add --ssh-askpass support

This adds the --ssh-askpass=COMMAND option which is disabled by default. --use-askpass=COMMAND will request the username and password for a given URL by executing the external program COMMAND. If COMMAND is left blank, then the external program in the environment variable WGET_ASKPASS will be use

Re: [OE-core] [oe-core][PATCH 1/1] systemd-compat-units: pkg_postinst() does not work

On Mon, 2016-08-15 at 16:04 -0700, Joe Slater wrote: > The test for various files is wrong and will always be > true, even if init.d does not exist. > > Exit if init.d does not exist, and correctly test for > file existence otherwise. > > Signed-off-by: Joe Slater > --- > meta/recipes-core/syst

[OE-core] [PATCH] kernel-module-split.bbclass: no need for running depmod

With the recent changes, executing depmod is not needed anymore. This simplifies and remove a lot of unnecessary code. Signed-off-by: André Draszik --- meta/classes/kernel-module-split.bbclass | 67 +--- 1 file changed, 1 insertion(+), 66 deletions(-) diff --git a/m

[OE-core] [PATCH 1/2] module.bbclass: use Module.symvers for dependants

When compiling multiple external kernel modules, where one depends on the other, there are two problems at the moment: 1) we get compile time warnings from the kernel build system due to missing symbols (from modpost). 2) Any modules generated are missing dependency information (in the .modin

[OE-core] [PATCH 0/2] fixing kernel module cross-recipe dependency

Hi, In a situation where multiple external kernel modules are built from multiple independent recipes, we currently don't generate correct runtime dependencies of the packages created. This (small) series of patches attempts to address this. It's working well for me but there'll likely be cases

[OE-core] [PATCH 2/2] kernel-module-split.bbclass: generate dependencies across recipes

The information retrieved via depmod is incomplete with regards to kernel modules that are dependencies, in particular where two kernel modules are build from different source trees / recipes, which leads to incomplete dependency information for packages created. So far, our packages created didn'

Re: [OE-core] [PATCH] dbus: 1.10.8 -> 1.11.2

On Thu, 2016-04-28 at 16:37 +0300, Dai Caiyun wrote: Upgrade dbus from 1.10.8 to 1.11.2. You might want to update the date/time of the machine you used to post your patches. With a date of April 28, your email could easily be missed by someone sorting and reading messages by date. -Bill

[OE-core] Problem building eglibc

I previously posted this issue: --- On Aug 16, 2016, at 12:53 PM, kyle.un...@l-3com.com wrote: Folks, I am having a problem doing the 'bitbake -c do_populate_sdk fsl-image-full'

Re: [OE-core] what means IMAGE_ROOTFS_EXTRA_SPACE_append += "+ 3000000"?

On 17/08/2016 16:01, Robert P. J. Day wrote: as in, what's with the "+" in that "+ 300" value? i've never seen that before, and i took a quick look under classes/ to try to figure out what's happening, but i'm still confused. you're reading too much into this "+ 300" will append th

Re: [OE-core] subtle weirdness when you combine "_append" with "+="?

On Wed, 17 Aug 2016, Ulf Magnusson wrote: > On Wed, Aug 17, 2016 at 3:21 PM, Robert P. J. Day > wrote: > > On Tue, 16 Aug 2016, Khem Raj wrote: > > > > ... big snip ... > > > >> the _append/_prepend in conjunction with += is a undocumented > >> behavior however, I do not see it as much a side

[OE-core] [PATCH] unfs3: Simplify simultaneous usage of "_append" and "+="

Signed-off-by: Robert P. J. Day --- for pedantic consistency, i also removed the *trailing* space from the libtirpc line, since subsequent appends should be responsible for adding the necessary leading space. i wonder if that will break anything... diff --git a/meta/recipes-devtools/unfs3/un

Re: [OE-core] subtle weirdness when you combine "_append" with "+="?

On Wed, Aug 17, 2016 at 3:21 PM, Robert P. J. Day wrote: > On Tue, 16 Aug 2016, Khem Raj wrote: > > ... big snip ... > >> the _append/_prepend in conjunction with += is a undocumented >> behavior however, I do not see it as much a side effect. But in >> future bitbake may silently change its beh

[OE-core] what means IMAGE_ROOTFS_EXTRA_SPACE_append += "+ 3000000"?

as in, what's with the "+" in that "+ 300" value? i've never seen that before, and i took a quick look under classes/ to try to figure out what's happening, but i'm still confused. this is all in aid of the aforementioned "+=" cleanup, and i can see some inconsistency as to whether there

Re: [OE-core] npm.bbclass

On 17 August 2016 at 13:40, Paul Eggleton wrote: > Hey Chris, long time! > Hey :) > On Wed, 17 Aug 2016 11:11:13 Brendan Le Foll wrote: > > >- Is there a reason to split the package like it does? Node projects > > >tend to have huge dependency trees, it makes updating and > distributin

Re: [OE-core] subtle weirdness when you combine "_append" with "+="?

On Tue, 16 Aug 2016, Khem Raj wrote: ... big snip ... > the _append/_prepend in conjunction with += is a undocumented > behavior however, I do not see it as much a side effect. But in > future bitbake may silently change its behavior, so I agree its > always good to stay in safe waters. so j

Re: [OE-core] npm.bbclass

Hey Chris, long time! On Wed, 17 Aug 2016 11:11:13 Brendan Le Foll wrote: > >- Is there a reason to split the package like it does? Node projects > >tend to have huge dependency trees, it makes updating and distributing > >node-based applications a bit of a chore if they end up split i

[OE-core] [PATCH] busybox: Backport makefile fix from upstream

This at least partially addresses one of the build races we've seen on the autobuilder in busybox. Its a straightforward backport from upstream. Signed-off-by: Richard Purdie diff --git a/meta/recipes-core/busybox/busybox/makefile-fix-backport.patch b/meta/recipes-core/busybox/busybox/makefile

[OE-core] [PATCH] gobject-introspection: Ensure prelink config file exists to avoid build failures

gobject-introspection relies upon prelink-rtld. In order to function correctly, we generate an ld.so.conf file which is generated before users of prelink-rtld are called. There is currently a race in gobject-introspection since the configuration file may not have been created. This adds in code t

[OE-core] [PATCH V3] bootchart2: fixes a BOOTLOG_DEST typo

From: Ming Liu A flaw was observed in bootchartd that BUILDLOG_DEST should actually be BOOTLOG_DEST, this seems to be a typo or mix-up which has been fixed in upstream. Cherry pick the fix since bootchart2 0.14.8 is still the newest release so far. Signed-off-by: Ming Liu --- ...ed-Missing-de

Re: [OE-core] [PATCH v2] u-boot.inc: Enable out-of-tree builds

On Tue, Aug 16, 2016 at 7:40 PM, Burton, Ross wrote: > > On 16 August 2016 at 23:00, Otavio Salvador > wrote: >> >> But you removed the suffix from the binaries it seems > > Just double-checked the diff, I think the line wrapping is making you think > that. Or, paste the hunk that is broken plea

[OE-core] [PATCH 1/2] alsa-lib: 1.1.1 -> 1.1.2

Changelog: http://www.alsa-project.org/main/index.php/Changes_v1.1.1_v1.1.2 Removed upstreamed patch: 0001-pcm_plugin-fix-appl-pointer-not-correct-when-mmap_co.patch Rebased avoid-including-sys-poll.h-directly.patch Signed-off-by: Tanu Kaskinen --- ...fix-appl-pointer-not-correct-when-mmap_co.

[OE-core] [PATCH 2/2] alsa-utils: 1.1.1 -> 1.1.2

Changelog: http://www.alsa-project.org/main/index.php/Changes_v1.1.1_v1.1.2 The FFT code in alsabat changed from double precision to single precision floating point numbers, which is why the fftw dependency changed to fftwf. Signed-off-by: Tanu Kaskinen --- .../{alsa-utils-scripts_1.1.1.bb => a

[OE-core] [PATCH 0/2] Update alsa recipes

The following changes since commit c86bf80abd87acb0da5860806822c64ec9dee089: oeqa.buildperf: use oe.path.remove() (2016-08-17 10:35:27 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib tanuk/updates http://cgit.openembedded.org/cgit.cgi/op

[OE-core] [PATCH] Fix S4U2Self KDC crash when anon is restricted

This is CVE-2016-3120 The validate_as_request function in kdc_util.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.13.6 and 1.4.x before 1.14.3, when restrict_anonymous_to_tgt is enabled, uses an incorrect client data structure, which allows remote authenticated users

Re: [OE-core] npm.bbclass

On Tue, Aug 16, 2016 at 05:41:28PM +0100, Christopher Lord wrote: >I've been using npm.bbclass with various node projects we're working on >in the Connected Devices team at Mozilla, and had some >questions/comments about behaviour (note that I'm basing this off of >ostro master, whi

[OE-core] [PATCH v2] bind: 9.10.3-P3 -> 9.11.0b2

1) Upgrade bind from 9.10.3-P3 to 9.11.0b2. 2) Delete some patchers, since they are no use. bind-confgen-build-unix.o-once.patch CVE-2016-1285.patch CVE-2016-1286_1.patch CVE-2016-1286_2.patch CVE-2016-2088.patch 3) Modify LIC_FILES_CHKSUM, since the date in it has been changed,

Re: [OE-core] [PATCH 07/10] tslib: remove recipe

Hi Ross, On Tue, Aug 16, 2016 at 10:39:55PM +0100, Burton, Ross wrote: >Hi Maxin, > >This breaks meta-qt4 which currently just depends on oe-core. > Haven't noticed this before. Thanks for sharing this info. >Can you see if we can make qt4-embedded have a configurable dependency >on tslib which

[OE-core] [PATCH] dbus: 1.10.8 -> 1.10.10

Upgrade dbus from 1.10.8 to 1.10.10. Signed-off-by: Dai Caiyun --- meta/recipes-core/dbus/{dbus-test_1.10.8.bb => dbus-test_1.10.10.bb} | 4 ++-- meta/recipes-core/dbus/{dbus_1.10.8.bb => dbus_1.10.10.bb} | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) rename meta/recipes-c

[OE-core] [PATCH v2] adwaita-icon-theme: 3.18.0 -> 3.20

Upgrade adwaita-icon-theme from 3.18.0 to 3.20. Signed-off-by: Wang Xin --- .../{adwaita-icon-theme_3.18.0.bb => adwaita-icon-theme_3.20.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-gnome/gnome/{adwaita-icon-theme_3.18.0.bb => adwaita-icon-theme_3.20.b

[OE-core] [PATCH] adwaita-icon-theme: 3.18.0 -> 3.20

Upgrade adwaita-icon-theme from 3.18.0 to 3.20. Signed-off-by: Wang Xin --- .../{adwaita-icon-theme_3.18.0.bb => adwaita-icon-theme_3.20.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-gnome/gnome/{adwaita-icon-theme_3.18.0.bb => adwaita-icon-theme_3.20.b

[OE-core] [PATCH 1/1] grub: fix load module all_video failed

While using oe-core toolchain to strip grub module 'all_video.mod', it stripped symbol table: -- root@localhost:~# objdump -t all_video.mod all_video.mod: file format elf64-x86-64 SYMBOL TABLE: no symbols -- It caused grub to load module all_video failed. (This module

[OE-core] [PATCH 0/1] grub: fix load module all_video failed

The following changes since commit 6b66e9317f4ec3a69f98f29836aafa35b52f3fc7: Allow for simultaneous do_rootfs tasks with rpm (2016-08-12 15:25:22 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib hongxu/fix-grub http://cgit.openembedded.o

[OE-core] [PATCH] dbus-test: 1.10.8 -> 1.11.2

Upgrade dbus-test from 1.10.8 to 1.11.2. Signed-off-by: Dai Caiyun --- meta/recipes-core/dbus/{dbus-test_1.10.8.bb => dbus-test_1.11.2.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-core/dbus/{dbus-test_1.10.8.bb => dbus-test_1.11.2.bb} (93%) diff --git a/me

Re: [OE-core] [PATCH] dbus: 1.10.8 -> 1.11.2

On 28 April 2016 at 16:37, Dai Caiyun wrote: > Upgrade dbus from 1.10.8 to 1.11.2. > 1.11 is the development branch, we should not upgrade to it without a really good reason. Also, is there something wrong with your date settings? The date header is from April. Jussi > Signed-off-by: Dai Cai

Re: [OE-core] [PATCH] dropbear/init: Allow extra arguments for key generation

Ping!Any comments?On 09-08-16 13:36, Mike Looijmans wrote:> This patch adds DROPBEAR_RSAKEY_ARGS and DROPBEAR_DSSKEY_ARGS optional> parameters to /etc/default/dropbear. The contents are simply passed to> the 'dropbearkey' program when generating a host key.>> The default keysize for RSA is curren