[OE-core] [PATCH] e2fsprogs 1.43 -> 1.43.3

Upgrade e2fsprogs from 1.43 to 1.43.3 Signed-off-by: Zheng Ruoqin --- .../e2fsprogs/{e2fsprogs_1.43.bb => e2fsprogs_1.43.3.bb}| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/e2fsprogs/{e2fsprogs_1.43.bb =>

[OE-core] [PATCH 1/1] selftest/bbtests.py: update test_bitbake_g()

Add tests: bitbake -g world bitbake -g world -cfetchall I saw they were failed in the past. Signed-off-by: Robert Yang --- meta/lib/oeqa/selftest/bbtests.py | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git

[OE-core] [PATCH 0/1] selftest/bbtests.py: update test_bitbake_g()

The following changes since commit 91f856426c7523e1ebdf6d6f93f5fa7e509d6e49: oeqa/utils/commands.py: Fix get_bb_vars() when called without arguments (2016-12-14 16:14:59 +) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/test

[OE-core] [PATCH] sudo: 1.8.17p1 -> 1.8.18p1

Upgrade sudo from 1.8.17p1 to 1.8.18p1. Signed-off-by: Huang Qiyu --- meta/recipes-extended/sudo/{sudo_1.8.17p1.bb => sudo_1.8.18p1.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/sudo/{sudo_1.8.17p1.bb =>

Re: [OE-core] [PATCH] glibc: add -fno-builtin-strlen when not using -O2

On 2016-12-13 04:16 AM, Andre McCurdy wrote: On Mon, Dec 12, 2016 at 9:14 PM, Huang, Jie (Jackie) wrote: From: Andre McCurdy [mailto:armccu...@gmail.com] For reference, here's the patch I've been using. It's a slightly more generic fix than the one in the KDE bug

Re: [OE-core] [PATCH] fontconfig: Fix namespace conflicts with glibc

On Mon, Dec 12, 2016 at 9:47 AM, Khem Raj wrote: > > On Dec 12, 2016, at 4:45 AM, Burton, Ross wrote: > > Has fallout, for example libxft: > > | ../../libXft-2.3.2/src/xftfreetype.c:675:43: error: ‘FC_CHAR_WIDTH’ > undeclared (first use in this

[OE-core] [PATCH V2] fontconfig: Fix namespace conflicts with glibc

glibc 2.25 will come with TS 18661-1 macro definitions in limits.h which ends with following errors | ../../fontconfig-2.12.1/src/fcmatch.c:324:63: error: 'PRI_CHAR_WIDTH_STRONG' undeclared here (not in a function) | #define FC_OBJECT(NAME, Type, Cmp) { FC_##NAME##_OBJECT, Cmp,

Re: [OE-core] [PATCH] lttng-ust: Patch python shebang appropriately for native builds

On Wed, Dec 14, 2016 at 1:38 PM, Phil Blundell wrote: > If we are building a native package then ${bindir}/python3 is not guaranteed > to be available, and if it is available then it is probably a directory not a > file. In either case, attempting to use it as an interpreter will

[OE-core] [PATCH] nspr: set correct version in pkg-config file

while we are at it clean up sed Signed-off-by: Andreas Müller --- meta/recipes-support/nspr/nspr/nspr.pc.in | 2 +- meta/recipes-support/nspr/nspr_4.13.1.bb | 11 +++ 2 files changed, 8 insertions(+), 5 deletions(-) diff --git

[OE-core] [PATCH] lttng-ust: Patch python shebang appropriately for native builds

If we are building a native package then ${bindir}/python3 is not guaranteed to be available, and if it is available then it is probably a directory not a file. In either case, attempting to use it as an interpreter will not end well. Let's use ${bindir}/nativepython instead. Signed-off-by:

[OE-core] [PATCH 2/4] scripts: remove True option to getVar calls

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?\(( ?[^,()]*), True\) Signed-off-by: Joshua Lock ---

[OE-core] [PATCH 3/4] meta: remove True option to getVarFlag calls

getVarFlag() now defaults to expanding by default, thus remove the True option from getVarFlag() calls with a regex search and replace. Search made with the following regex: getVarFlag ?\(( ?[^,()]*, ?[^,()]*), True\) Signed-off-by: Joshua Lock ---

[OE-core] [PATCH 0/4] Remove True option to getVar[Flag] calls

getVar() and getVarFlag() now default to expanding by default, thus remove the True option from calls to both with a regex search and replace. (Note: this series is relative to ross/mut3) The following changes since commit d17879fdbc46e2cf10f724d3fbcf1b09d4e1bc7b: uninative: rebuild uninative

[OE-core] [PATCH 4/4] scripts: remove True option to getVarFlag calls

getVarFlag() now defaults to expanding by default, thus remove the True option from getVarFlag() calls with a regex search and replace. Search made with the following regex: getVarFlag ?\(( ?[^,()]*, ?[^,()]*), True\) Signed-off-by: Joshua Lock ---

Re: [OE-core] multiconfig + siteinfo.bbclass

On Wed, 2016-12-14 at 16:37 +0100, Patrick Ohly wrote: > Hello! > > While trying out a multiconfig with two configurations (one for MACHINE > = intel-corei7-64, one for quark) in custom Ostro derivative I got an > error while parsing recipes: > [...] > > However, I can't reproduce this with

[OE-core] [PATCH v2 1/3] wic: Add --exclude-path option to rootfs source plugin.

It will omit the given path from the resulting partition, and if the given path ends in a slash, it will only delete the content, and keep the directory. Since mkfs only accepts whole directories as input, we need to copy the rootfs directory to the workdir so that we can selectively delete files

[OE-core] [PATCH v2 2/3] Add e2tools recipe, in order to test contents of images.

Signed-off-by: Kristian Amlie --- meta/recipes-devtools/e2tools/e2tools-native_0.0.16.bb | 17 + 1 file changed, 17 insertions(+) create mode 100644 meta/recipes-devtools/e2tools/e2tools-native_0.0.16.bb diff --git

[OE-core] [PATCH v2] wic: Add --exclude-path option to rootfs source plugin.

Alright, this took a bit longer than I expected, I had to learn a bit about the test framework in OpenEmbedded. But here is the updated patch with additional patches enabling tests. Two things I'm a bit unsure about: I had to add a path to the wic python script in order to use the

[OE-core] [PATCH v2 3/3] selftest/wic: Add tests for --exclude-dir option.

Based partially on an earlier patch by Maciej Borzecki. Signed-off-by: Kristian Amlie --- meta/lib/oeqa/selftest/wic.py | 106 +- 1 file changed, 105 insertions(+), 1 deletion(-) diff --git a/meta/lib/oeqa/selftest/wic.py

Re: [OE-core] [PATCH 1/1] oeqa/utils/commands.py: Fix get_bb_vars() when called without arguments

On 12/14/2016 10:04 AM, Lopez, Mariano wrote: On 12/14/2016 10:01 AM, Leonardo Sandoval wrote: On 12/14/2016 01:45 AM, mariano.lo...@linux.intel.com wrote: From: Mariano Lopez Commit 9d55e9d489cd78be592fb9b4d6484f9060c62fdd broke calling get_bb_vars()

Re: [OE-core] [PATCH 1/1] oeqa/utils/commands.py: Fix get_bb_vars() when called without arguments

On 12/14/2016 10:01 AM, Leonardo Sandoval wrote: On 12/14/2016 01:45 AM, mariano.lo...@linux.intel.com wrote: From: Mariano Lopez Commit 9d55e9d489cd78be592fb9b4d6484f9060c62fdd broke calling get_bb_vars() when called without arguments. This fix this

Re: [OE-core] [PATCH][busybox] Add comments to separate Runit from SELinux content in defconfig

I've fixed it in when merging, but please don't put 'busybox' in square brackets as git-apply will strip anything in those out when it applies the patch. Ross On 14 December 2016 at 15:01, Robert P. J. Day wrote: > > There is no break in busybox's "defconfig" file to

Re: [OE-core] [PATCH 1/1] oeqa/utils/commands.py: Fix get_bb_vars() when called without arguments

On 12/14/2016 01:45 AM, mariano.lo...@linux.intel.com wrote: From: Mariano Lopez Commit 9d55e9d489cd78be592fb9b4d6484f9060c62fdd broke calling get_bb_vars() when called without arguments. This fix this issue. Signed-off-by: Mariano Lopez

[OE-core] [PATCH 1/1] oeqa/utils/commands.py: Fix get_bb_vars() when called without arguments

From: Mariano Lopez Commit 9d55e9d489cd78be592fb9b4d6484f9060c62fdd broke calling get_bb_vars() when called without arguments. This fix this issue. Signed-off-by: Mariano Lopez --- meta/lib/oeqa/utils/commands.py | 3 ++- 1 file

[OE-core] multiconfig + siteinfo.bbclass

Hello! While trying out a multiconfig with two configurations (one for MACHINE = intel-corei7-64, one for quark) in custom Ostro derivative I got an error while parsing recipes: ERROR:

[OE-core] [PATCH][busybox] Add comments to separate Runit from SELinux content in defconfig

There is no break in busybox's "defconfig" file to show where Runit settings suddenly morph into SELinux settings, so add some comments. Signed-off-by: Robert P. J. Day --- diff --git a/meta/recipes-core/busybox/busybox/defconfig

Re: [OE-core] [PATCH 1/2] grub_git: extend recipe for proper target deployment

Hi Ross, >> +RDEPENDS_${PN}_class-target = "diffutils freetype" > Does this really need to be class-target-specific? Without the class-target override I get ERROR: Nothing RPROVIDES 'diffutils-native' (but virtual:native:/data/amd_yocto/poky/meta/recipes-bsp/grub/grub_git.bb RDEPENDS on or

Re: [OE-core] [PATCH V3 0/4] Persistent /var/log support

On Wed, 2016-12-14 at 17:08 +0800, Chen Qi wrote: > Changes since V2: > Use boolean value consistently. Update the comments to fit the use of boolean > value. Looks good to me now. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an

Re: [OE-core] [PATCH] selftest/wic: extending test coverage for WIC script options

On Tue, Dec 13, 2016 at 06:24:57PM -0600, Jair Gonzalez wrote: > Hi Ed, > > Thank you for your response and suggestions. Below are my comments. > > > > +@testcase(1557) > > > +def test_listed_images_help(self): > > > +"""Test wic listed images help""" > > > +output =

Re: [OE-core] [PATCH v5 0/6] wic: bugfixes & --fixed-size support, tests, oe-selftest: minor fixes

On Tue, Dec 13, 2016 at 7:53 PM, Ed Bartosh wrote: > On Tue, Dec 13, 2016 at 09:07:30AM +0100, Maciej Borzęcki wrote: >> On Thu, Nov 24, 2016 at 8:08 AM, Maciej Borzecki >> wrote: >> > v5 of a patch series previously posted here [1]. >> >

[OE-core] opinions on enabling busybox's "runit" implementation to control some services?

colleague needs "runit" to control one or more services that have historically been managed that way, so a couple questions: 1) anyone with experience with busybox's implementation of runit? does it work properly? does it play nicely with others? 2) is runit actually necessary, or would it be

Re: [OE-core] [PATCH V2 4/6] runqemu: support mutiple qemus running when nfs

On 12/06/2016 04:55 PM, Robert Yang wrote: Fixed: * In build1: $ runqemu nfs qemux86-64 In build2: $ runqemu nfs qemux86-64 It would fail before since the port numerbs and conf files are conflicted, now make runqemu-export-rootfs work together with runqemu to fix the problem. *

[OE-core] [PATCH V3 1/4] bitbake.conf: add VOLATILE_LOG_DIR variable

The default value is "yes" which results in the /var/log being a link pointing to /var/volatile/log which is on tmpfs. Setting valid boolean false value ('no', 'n', 'false', 'f', '0') would make /var/log to be a directory on persistent storage. [YOCTO #6132] Signed-off-by: Chen Qi

[OE-core] [PATCH V3 3/4] initscripts: support persistent /var/log

Respect VOLATILE_VAR_LOG variable so that if it's set to any valid boolean false value, we could have persistent /var/log on the final image. [YOCTO #6132] Signed-off-by: Chen Qi --- meta/recipes-core/initscripts/initscripts-1.0/volatiles | 1 -

[OE-core] [PATCH V3 4/4] package.bbclass: support persistent /var/log

Add a new file, fs-perms-persistent-log.txt, which treats /var/log as a directory instead of a link. Modify package.bbclass to use this file if VOLATILE_LOG_DIR is set to boolean false value. [YOCTO #6132] Signed-off-by: Chen Qi --- meta/classes/package.bbclass

[OE-core] [PATCH V3 2/4] base-files: respect VOLATILE_LOG_DIR

Respect VOLATILE_LOG_DIR variable. In this way, if the user overrides this variable to be any valid boolean false value, /var/log on the final image would reside on persistent storage. [YOCTO #6132] Signed-off-by: Chen Qi ---

[OE-core] [PATCH V3 0/4] Persistent /var/log support

Changes since V2: Use boolean value consistently. Update the comments to fit the use of boolean value. The following changes since commit d62f18c39bc0ed3b0f5ac8465b393c15f2143ecf: targetloader.py: drop test for ClassType (2016-12-12 15:16:39 +) are available in the git repository at:

[OE-core] [PATCH 0/1] devtool: package: don't try to initialise tinfoil twice

This patch is on top of the tinfoil2 set but doesn't actually require it - it fixes an issue that's been there for a while, it just slowed things down a bit instead of failing as it does with tinfoil2. The following changes since commit 2eea6a65b009e9d47c03b7d82d2699f88228fc62: oe-selftest:

[OE-core] [PATCH 1/1] devtool: package: don't try to initialise tinfoil twice

setup_tinfoil() already calls prepare(), we don't need to call it again ourselves and doing so with tinfoil2 results in "ERROR: Only one copy of bitbake should be run against a build directory". Calling prepare() twice should probably still be allowed, so that ought to be fixed separately, but in

Re: [OE-core] [PATCH V2 1/8] populate_sdk_ext.bbclass: break the long lines

Hi Ulf, On 12/14/2016 04:02 PM, Ulf Magnusson wrote: I'm not a big fan of those run-on lines either, so thanks. Some superficial comments: On Wed, Dec 14, 2016 at 8:24 AM, Robert Yang wrote: Make it easier to read and maintain. [YOCTO #10647] Signed-off-by:

Re: [OE-core] [PATCH V2 1/8] populate_sdk_ext.bbclass: break the long lines

I'm not a big fan of those run-on lines either, so thanks. Some superficial comments: On Wed, Dec 14, 2016 at 8:24 AM, Robert Yang wrote: > Make it easier to read and maintain. > > [YOCTO #10647] > > Signed-off-by: Robert Yang > --- >