[OE-core] [PATCH] image.bbclass: Always try to run populate-volatile.sh at rootfs time

Currently populate-volatile.sh will only run when "readonly-rootfs" is selected. Running this script is very useful even on read/write root filesystems, because it reduces the number of "fixup" actions at first boot of the device. That not only reduces boot time, it also reduces the flash space us

[OE-core] [PATCH] bash: append srcdir to run-ptest script

If srcdir is not set, we get below error while running ptest for bash on qemu target, -- snip -- root@qemux86:/usr/lib/bash/ptest# ./run-ptest /bin/sh: line 0: cd: /home/ajay/Downloads/poky-fido-13.0.0/build/tmp/work/i586-poky-linux/bash/4.3-r1/bash-4.3/tests: No such file or directory Makefile:

Re: [OE-core] [PATCH 3/4] nfs-utils: Upgrade 1.3.1 -> 1.3.2

On 12 August 2015 at 04:50, Khem Raj wrote: > >> On Aug 11, 2015, at 12:13 PM, Jussi Kukkonen >> wrote: >> >> Let "--enable-tirpc" be selected in configure by default: it is >> a requirement for ipv6 support. This should not grow a typical >> image size as libtirpc is a rpcbind dependency alread

Re: [OE-core] [oe-core][PATCH 1/1] common-glibc: define bash_cv_getcwd_malloc

> On Jul 21, 2015, at 10:39 AM, Joe Slater wrote: > > We do not want bash to use internal code for getcwd() because > it can fail in certain filesystem types. Trust that the function > in glibc is not "broken”. I would suggest to move this to bash recipe as CACHED_CONFIGUREVARS += “bash_cv_ge

Re: [OE-core] [PATCH 2/5] screen: Add version 4.3.1

On 11 August 2015 at 23:37, Otavio Salvador wrote: > On Tue, Aug 11, 2015 at 5:28 PM, Burton, Ross wrote: >> >> On 11 August 2015 at 20:54, Andre McCurdy wrote: >>> >>> > Is screen considered sufficiently core that we should maintain both >>> > GPLv2 >>> > and v3 recipes? I'm not convinced it i

Re: [OE-core] [PATCH 0/3] preserve xattrs in images

On Tue, 2015-08-11 at 15:29 +0100, Burton, Ross wrote: > Hi Patrick, > > On 11 August 2015 at 09:44, Patrick Ohly > wrote: > The default does not get changed because supporting xattrs > causes a > certain overhead (need to build GNU tar, additional system > calls w

[OE-core] [PATCH v4] create-pull-request: cleanup bashisms

Made create-pull-request POSIX compatible: - Replaced /bin/bash -> /bin/sh in shebang. - Replaced usage of pushd/popd with generic shell commands. - Tested on zsh and dash. Signed-off-by: Ed Bartosh --- scripts/create-pull-request | 7 --- 1 file changed, 4 insertions(+), 3 deletion

Re: [OE-core] [PATCH 3/3] mtd-utils: keep xattr support enabled

On Tue, 2015-08-11 at 15:33 +0100, Burton, Ross wrote: > > On 11 August 2015 at 09:45, Patrick Ohly > wrote: > -EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' > 'CFLAGS=${CFLAGS} -I${S}/include -DWITHOUT_XATTR' 'BUILDDIR= > ${S}'" > +EXTRA_OEMAKE = "'CC=$

Re: [OE-core] [PATCH v4] create-pull-request: cleanup bashisms

On Wed, Aug 12, 2015 at 2:33 AM, Ed Bartosh wrote: > Made create-pull-request POSIX compatible: >- Replaced /bin/bash -> /bin/sh in shebang. >- Replaced usage of pushd/popd with generic shell commands. >- Tested on zsh and dash. thanks for doing this. > > Signed-off-by: Ed Bartosh >

[OE-core] making /var/log persistent

I'm trying to make /var/log persistent and I'm having trouble. I've made a bbappend to base_files which contains: dirs755_append = " \ /var/log \ " volatiles = "tmp" Looking in the resulting image, /var/log is indeed now a directory and not a symlink to volatile storage, however when

Re: [OE-core] making /var/log persistent

On 08/12/2015 06:29 PM, Jack Mitchell wrote: I'm trying to make /var/log persistent and I'm having trouble. I've made a bbappend to base_files which contains: dirs755_append = " \ /var/log \ " volatiles = "tmp" Looking in the resulting image, /var/log is indeed now a directory and no

[OE-core] shell script guidelines in oe-core? (was Re: [PATCH v4] create-pull-request: cleanup bashisms)

Sorry to hijack the thread but... On Wed, Aug 12, 2015 at 12:33:31PM +0300, Ed Bartosh wrote: > Made create-pull-request POSIX compatible: >- Replaced /bin/bash -> /bin/sh in shebang. >- Replaced usage of pushd/popd with generic shell commands. >- Tested on zsh and dash. This reminded

[OE-core] [PATCH] gnu-efi: BBCLASSEXTEND to native

Sbsigntool depends on gnu-efi and we need sbsigntool-native to do some signing, so extend gnu-efi to support that. Signed-off-by: Koen Kooi --- meta/recipes-bsp/gnu-efi/gnu-efi_3.0.2.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-bsp/gnu-efi/gnu-efi_3.0.2.bb b/meta/recip

[OE-core] OE Changelog since 2015-08-02 until 2015-08-09

Changelog since 2015-08-02 until 2015-08-09. Projects included in this report: bitbake: git://git.openembedded.org/bitbake openembedded-core: git://git.openembedded.org/openembedded-core meta-openembedded: git://git.openembedded.org/meta-openembedded meta-angstrom: git://github.com/Angstrom-distr

Re: [OE-core] [PATCH 2/2] base.bbclass/blacklist.bbclass: remove doc item when d.getVarFlags()

On Tue, Aug 11, 2015 at 11:13 PM, Robert Yang wrote: > > > On 08/11/2015 08:45 PM, Otavio Salvador wrote: >> >> On Thu, Jul 30, 2015 at 12:18 PM, Robert Yang >> wrote: >>> >>> The FOO[doc] is set in meta/conf/documentation.conf, we need remove it >>> from d.getVarFlags()'s return dict when it cau

[OE-core] [PATCH][RESEND] adt-installer: use DEPLOY_DIR in ANT_DEPLOY expansion

Currently adt-installer uses "${TMPDIR}/deploy/sdk/" as a deployment dir. This doesn't interact well with DEPLOY_DIR reassignment. So let's use "${DEPLOY_DIR}/sdk/" instead. Signed-off-by: Dmitry Eremin-Solenikov --- meta/recipes-devtools/installer/adt-installer_1.0.bb | 2 +- 1 file changed, 1

Re: [OE-core] [PATCH 2/2] base.bbclass/blacklist.bbclass: remove doc item when d.getVarFlags()

On Wednesday 12 August 2015 10:45:29 Otavio Salvador wrote: > On Tue, Aug 11, 2015 at 11:13 PM, Robert Yang wrote: > > On 08/11/2015 08:45 PM, Otavio Salvador wrote: > >> On Thu, Jul 30, 2015 at 12:18 PM, Robert Yang > >> > >> wrote: > >>> The FOO[doc] is set in meta/conf/documentation.conf, we

Re: [OE-core] [PATCH 2/2] base.bbclass/blacklist.bbclass: remove doc item when d.getVarFlags()

On Wed, Aug 12, 2015 at 11:04 AM, Paul Eggleton wrote: > On Wednesday 12 August 2015 10:45:29 Otavio Salvador wrote: >> On Tue, Aug 11, 2015 at 11:13 PM, Robert Yang > wrote: >> > On 08/11/2015 08:45 PM, Otavio Salvador wrote: >> >> On Thu, Jul 30, 2015 at 12:18 PM, Robert Yang >> >> >> >> wrote

Re: [OE-core] [PATCH] nettle: clean up license information

Hi, I realise I'm a bit late (with the commit in master already) but I'm looking at upgrading this recipe and had some questions on this patch and the recipe in general. On 9 August 2015 at 08:28, Armin Kuster wrote: > adding the license definitions on the few packages that > deviate from the ov

Re: [OE-core] [PATCH 0/3] preserve xattrs in images

Is there something here that enables the tar-replacement-native? Or is the user just expected to know they need it? If you look at meta/classes/sanity.bbclass, there is already a tar check for a specific old version that can't handle overwriting symlinks properly. It should be possible to check

Re: [OE-core] [PATCH 0/3] preserve xattrs in images

On Wed, 2015-08-12 at 09:34 -0500, Mark Hatle wrote: > Is there something here that enables the tar-replacement-native? Or is the > user > just expected to know they need it? The user is supposed to ensure that it gets depended on if (and only if) needed. I gave the following usage instructions

[OE-core] [PATCH] qemu: upgrade to 2.4.0

All CVE patches removed, included in release. Signed-off-by: Cristian Iorga --- ...f-modified-PCI-CFG-contents-CVE-2015-4103.patch | 140 --- ...o-control-MSI-mask-register-CVE-2015-4104.patch | 194 --- ...-MSI-X-limit-error-messages-CVE-2015-4105.patch | 90 --- ...s-t

Re: [OE-core] meta-gplv2? [Was Re: parted_1.8.6.bb: add parted that not GPLv3]

On 8/11/15 3:36 PM, Burton, Ross wrote: > > On 11 August 2015 at 16:46, Khem Raj > wrote: > > can we freeze this thread please. > > > Or more usefully, reboot it. Philip, you're turning into Koen! Alex, if > someone on this list asks what Poky is, 99% of the ti

Re: [OE-core] [PATCH 5/8] Extensible SDK: allow for installation without preparing build system

Hi Chris / Qi, On Monday 10 August 2015 08:39:01 Christopher Larson wrote: > On Sun, Aug 9, 2015 at 8:18 PM, Chen Qi wrote: > > When publishing SDK, what we want is basically its metadata and sstate > > cache objects. We don't want the SDK to be prepared with running bitbake > > as it takes time

Re: [OE-core] [PATCH 6/8] oe-publish-sdk: add script

Hi Qi, A couple of issues noted below. On Monday 10 August 2015 11:18:04 Chen Qi wrote: > Add a script to publish extensible SDK to a specified destination. > > oe-publish-sdk > > Signed-off-by: Chen Qi > --- > scripts/oe-publish-sdk | 124 > +

[OE-core] [PATCH] systemd: update SRC_URI

Upstream has moved git hosts, so update the SRC_URI appropriately. [ YOCTO #8181 ] Signed-off-by: Ross Burton --- meta/recipes-core/systemd/systemd_219.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/systemd/systemd_219.bb b/meta/recipes-core/systemd/sy

Re: [OE-core] [PATCH 8/8] devtool: add sdk.py plugin

On Monday 10 August 2015 11:18:06 Chen Qi wrote: > E.g. > devtool sdk-update /mnt/sdk-repo/ > devtool sdk-update http://mysdkhost/sdk As noted by Chris we definitely need a better commit message here. > +logger.debug("Updating meta data via git ...") > +ret = subprocess.call("rm -

Re: [OE-core] [PATCH 0/8] Extensible SDK fixes

On Monday 10 August 2015 11:17:58 Chen Qi wrote: > The following changes since commit 288c76a41aebaf54c7fca3782160830df462b9e4: > > builder: Fix multilib compile failure (2015-08-03 07:15:47 +0100) > > are available in the git repository at: > > git://git.openembedded.org/openembedded-core-c

Re: [OE-core] [oe-core][PATCH 1/1] common-glibc: define bash_cv_getcwd_malloc

On 12 August 2015 at 08:49, Khem Raj wrote: > I would suggest to move this to bash recipe as > > CACHED_CONFIGUREVARS += “bash_cv_getcwd_malloc=yes” > > so other libcs can also benefit. > Don't we then have to trust that all libcs are not broken, or is the bash getcwd implementation *that bad*?

Re: [OE-core] [oe-core][PATCH 1/1] common-glibc: define bash_cv_getcwd_malloc

On Wed, Aug 12, 2015 at 9:46 AM, Burton, Ross wrote: > Don't we then have to trust that all libcs are not broken, or is the bash > getcwd implementation *that bad*? we already know it fails in some cases but nothing of such sort is reported with libc implementations. That doesnt mean they cant be

Re: [OE-core] shell script guidelines in oe-core? (was Re: [PATCH v4] create-pull-request: cleanup bashisms)

On Wed, Aug 12, 2015 at 2:49 AM, wrote: > This reminded me of the problems I've seen with various oe-core shell scripts: > they are missing systematic error handling. > > IMO using bash and 'set -euxo pipefail' are a good approach to catch errors > early in shell scripts. Manually checking for $?

Re: [OE-core] shell script guidelines in oe-core? (was Re: [PATCH v4] create-pull-request: cleanup bashisms)

On Wed, Aug 12, 2015 at 9:56 AM, Khem Raj wrote: > On Wed, Aug 12, 2015 at 2:49 AM, wrote: > > This reminded me of the problems I've seen with various oe-core shell > scripts: > > they are missing systematic error handling. > > > > IMO using bash and 'set -euxo pipefail' are a good approach to

Re: [OE-core] shell script guidelines in oe-core? (was Re: [PATCH v4] create-pull-request: cleanup bashisms)

On Wed, Aug 12, 2015 at 10:46 AM, Christopher Larson wrote: > On Wed, Aug 12, 2015 at 9:56 AM, Khem Raj wrote: > >> On Wed, Aug 12, 2015 at 2:49 AM, wrote: >> > This reminded me of the problems I've seen with various oe-core shell >> scripts: >> > they are missing systematic error handling. >>

[OE-core] [PATCH] qemu-native: Add debugging when qemu fails with qemu_cpu_kick_thread

We are expecting some random failures in QEMU runs one of this is related to qemu_cpu_kick_thread that ends on exit(1) on qemu. To improve debug information add patch that prints the backtrace and the status of qemu cpu. [YOCTO #8143] Signed-off-by: Aníbal Limón --- meta/recipes-devtools/qemu/

[OE-core] [PATCH 1/6] qemurunner.py: Add method run_serial

From: Mariano Lopez The only need for the console before this patch was to check if the target has booted. This allows to send commands to the terminal. This new method is based on the method with the same name of the QemuTinyRunner class. The difference here is it will remove the command and th

[OE-core] [PATCH 0/6] Allow to dump commands from serial console when a test fails

From: Mariano Lopez These changes allows to run commands on the qemu serial console when a test fails. Right now the tests are hardcoded but the idea is to be able to customize them. qemurunner.py: Added and tunned run_serial method to allow to run serial commands on the target oetest.py: Added

[OE-core] [PATCH 6/6] oetest.py: Don't wait to write dump files

From: Mariano Lopez This allows to write the dump files immediately after get the data from the target. Before this, it would run all the commands and write the files. The old behavior could cause no log written at all if the serial console gets stuck. Signed-off-by: Mariano Lopez --- meta/lib

[OE-core] [PATCH 5/6] oetest.py: Added method tearDown for oeRuntimeTest

From: Mariano Lopez The tearDown method is triggered when a tests ends it doesn't matter if fails or succeeds. Inside this method added an evalution to check if fails and then run some commands in the target to get the data for later debugging. [YOCTO #8118] Signed-off-by: Mariano Lopez --- m

[OE-core] [PATCH 2/6] qemurunner.py: Added login to start method

From: Mariano Lopez This adds the automatic login after the target finished booting. If the automatic login fails it won't stop the target or any test, it would only send a log to the file. [YOCTO #8118] Signed-off-by: Mariano Lopez --- meta/lib/oeqa/utils/qemurunner.py | 11 +++ 1 fi

[OE-core] [PATCH 3/6] qemurunner.py: Added raw mode in run_serial

From: Mariano Lopez Raw mode allows to send the command without sending 'echo $?' for validation; Also this doesn't remove the command or the prompt from the output returned. In raw mode validation is done if there is output. This raw mode would be useful for validate the prompt when a user logs

[OE-core] [PATCH 4/6] qemurunner.py: Performance improvements in run_serial

From: Mariano Lopez This allow to search for the prompt after a command is run so it can avoid waiting for the timeout. Also corrected identation issues [YOCTO #8118] Signed-off-by: Mariano Lopez --- meta/lib/oeqa/utils/qemurunner.py | 20 1 file changed, 12 insertions(+

[OE-core] [PATCH] rpm: opendb before rpmverifyscript to avoid null point input

If the command is "rpm -V" and the return value of (headerIsEntry(h, RPMTAG_VERIFYSCRIPT) || headerIsEntry(h, RPMTAG_SANITYCHECK)) located in /lib/verify.c is true, it will call rpmpsmStage function(rpmVerifyScript->rpmpsmScriptStage->rpmpsmStage) and occur segment fault because of null point(rp

[OE-core] [PATCH] u-boot.inc: Add UBOOT_BINARY sym links for UBOOT_CONFIG types

An additional use case of UBOOT_CONFIG is when a machine has applicability to boards of the same architecture but different in other ways to require a different UBOOT_BINARY build. The UBOOT_CONFIG default value can be a list of these board types. For example: UBOOT_CONFIG ??= "boardA boardB"

Re: [OE-core] shell script guidelines in oe-core? (was Re: [PATCH v4] create-pull-request: cleanup bashisms)

On Wed, Aug 12, 2015 at 10:51:26AM -0700, Christopher Larson wrote: > That reminds me, there's a shell portability issue / standards-complaince > issue that's not identified by shellcheck. Typically, to negate a bracket > expression in a regular expression, one uses ^, e.g. [^a-z] is everything >