[OE-core] [PATCH 06/14] devtool: upgrade: fix moving version-specific files directory

We were trying to move this from the current directory instead of the path. Let's just use shutil.move() instead of shelling out to mv. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/upgrade.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[OE-core] [PATCH 09/14] devtool: upgrade: fix several issues with extraction of new source

Fix several issues when extracting the new version source over the top of the old one (when the recipe is not fetching from a git repo): * Delete the old source first so we ensure files deleted in the new version are deleted. This also has the side-effect of fixing any issues where files

[OE-core] [PATCH 13/14] oe-selftest: devtool: rework devtool upgrade test

* Use a more real-world test of a recipe pointing to a remote file * The cleanup tracking / teardown commands need to be added towards the top, or they won't have the desired effect of cleaning up if the test fails. * Check that a versioned subdirectory gets renamed to match the new version

[OE-core] [PATCH 14/14] oe-selftest: devtool: add an additional test for devtool upgrade

Add a test for devtool upgrade with a recipe pointing to a git repository, since this uses several different code paths. Signed-off-by: Paul Eggleton --- .../devtool/devtool-upgrade-test2_git.bb | 18 +++

[OE-core] [PATCH 10/14] devtool: upgrade: eliminate unnecessary datastore copy

We aren't modifying the datastore copy here, so we don't need a copy at all. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/upgrade.py | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/scripts/lib/devtool/upgrade.py

[OE-core] [PATCH 08/14] devtool: upgrade: fix constructing new branch from tarball releases

When we do an upgrade from one tarball version to another we want to: 1) Check out the old version as a new branch 2) Record the changes between the old and new versions as a commit 3) Check out the old version with patches applied 4) Rebase that onto the new branch Where we went wrong was step

[OE-core] [PATCH 07/14] devtool: upgrade: fix renaming of recipe if PV is not in name

If the actual value of PV isn't in the name of the recipe (for example, a git or svn recipe) there's no point trying to rename it. Additionally, we already have the original filename, there's no need to guess it - just pass it in. Signed-off-by: Paul Eggleton ---

[OE-core] [PATCH 05/14] devtool: upgrade: fix version argument checking

For recipes that specify SRCREV, the code here wasn't quite doing the right thing. If the recipe has a SRCREV then that needs changing on upgrade, so ensure that the user specifies it. If it doesn't, then it'll be "INVALID" not None since the former is the actual default, so handle that properly

[OE-core] [PATCH 11/14] devtool: upgrade: drop PR on upgrade

The PR value should be reset to the default when upgrading, so we need to drop it from the newly created file. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/upgrade.py | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git

[OE-core] [PATCH 12/14] devtool: upgrade: print new recipe name

Make this consistent with "devtool add" so that the user knows where to find the new recipe. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/upgrade.py | 1 + 1 file changed, 1 insertion(+) diff --git a/scripts/lib/devtool/upgrade.py

[OE-core] [PATCH 01/14] devtool: add: tweak auto-determining name failure message

As suggested by Khem Raj. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/standard.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py index daf18c9..bcf6520 100644 ---

[OE-core] [PATCH 03/14] devtool: upgrade: make source tree path optional

Make devtool upgrade consistent with devtool add/modify in defaulting to sources/ under the workspace if no source tree path is specified. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/upgrade.py | 22 +++--- 1 file changed, 15

[OE-core] [PATCH 02/14] devtool: modify: fix source tree default name when mapping virtuals

If you for example ran devtool modify virtual/libusb0 without specifying a source tree path, the default was /sources/virtual/libusb0 which isn't correct - it should be using the mapped name i.e. libusb-compat (in the default OE-Core configuration). Reorder some of the code to ensure that the

[OE-core] [PATCH 04/14] devtool: upgrade: drop superfluous call to validate_pn

The recipename argument to devtool upgrade specifies an existing recipe, so by definition the name will be valid (or it won't exist) - we don't need to validate it ourselves, that's only needed for situations like in devtool add where we're creating a new recipe. Signed-off-by: Paul Eggleton

[OE-core] [PATCH 00/14] devtool upgrade fixes

I had occasion to look at devtool upgrade recently and found quite a number of issues. Fix those, improve the tests and fix a couple of minor things in devtool add and devtool modify as well. The following changes since commit 205b446f3fc4a9885179a66a8dab9d81bcc63dca: uclibc: Do not use

[OE-core] [PATCH 3/3] core-tools-profile: add lttng tools for aarch64

Signed-off-by: Tudor Florea --- meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb | 4 1 file changed, 4 deletions(-) diff --git a/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb

[OE-core] [PATCH 2/3] lttng-ust: add support for aarch64_be

Signed-off-by: Tudor Florea --- .../lttng-ust-add-support-for-aarch64_be.patch | 17 + meta/recipes-kernel/lttng/lttng-ust_git.bb | 4 +++- 2 files changed, 20 insertions(+), 1 deletion(-) create mode 100644

[OE-core] [PATCH 1/3] liburcu: add support for aarch64_be

Signed-off-by: Tudor Florea --- .../liburcu/liburcu/0002-Support-for-aarch64_be.patch | 19 +++ meta/recipes-support/liburcu/liburcu_0.9.1.bb | 1 + 2 files changed, 20 insertions(+) create mode 100644

Re: [OE-core] [PATCH 1/7] ffmpeg: update to 2.8.6

Fails to build for qemuarm when thumb is enabled. Why was: ARM_INSTRUCTION_SET = "arm" removed in http://git.openembedded.org/openembedded-core/commit/?id=77dbf07293df15cd5473422abd678930d6277bb0 without checking if it works? | {standard input}: Assembler messages: | {standard input}:288:

[OE-core] [fido][PATCH 00/11] Fido Security fixes #2

From: Armin Kuster please consider these changes for the next fido update. This is to meet our obligation for Yocto compatibility The following changes since commit 9037f2c7c797367c2d09b87f344ecf749d28cb41: gdk-pixbuf: Security fix CVE-2015-7674 (2016-02-22 19:08:53

Re: [OE-core] [PATCHv2 2/2] testimage.bbclass: reuse generic test suites

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I tested this with builds in my workstation and (local, internal) autobuilder, where TEST_SUITES is *not* specified in local.conf, so the TEST_SUITES are taken from the DEFAULT_TEST_SUITES variable for each image, which makes the tests work for the

Re: [OE-core] [PATCHv2 2/2] testimage.bbclass: reuse generic test suites

Hi Franco, how did you test this? what is the behavior you get with these defaults instead of how's behaving now? See comments below. On Tue, 2016-02-23 at 09:14 +, Alex Franco wrote: > Modify existing default test suites to reuse the new > generic test suites. > > Related to [YOCTO #8410]

Re: [OE-core] [PATCH 1/2] oe-core: Update alternatives of man pages

On 23 February 2016 at 11:47, wrote: > +ALTERNATIVE_${PN}-doc += "eject.1 su.1" > WARNING: util-linux-2.27.1-r0 do_package: util-linux: alternative target (/usr/share/man/man1/su.1 or /usr/share/man/man1/su.1.util-linux) does not exist, skipping... WARNING:

[OE-core] OE Changelog since 2016-02-14 until 2016-02-21

Changelog since 2016-02-14 until 2016-02-21. 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:

[OE-core] [PATCH 2/2] harfbuzz: add explicit dependency on fontconfig

The fontconfig dependency was previously met indirectly (via cairo). Signed-off-by: Andre McCurdy --- meta/recipes-graphics/harfbuzz/harfbuzz_1.2.1.bb | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git

[OE-core] [PATCH 1/2] harfbuzz: update 1.2.0 -> 1.2.1

Overview of changes leading to 1.2.1 Friday, February 23, 2016 - CoreText: Fix bug with wrong scale if font scale was changed later. https://github.com/libass/libass/issues/212 - CoreText: Drastically speed up font initialization. - CoreText: Fix tiny leak.

Re: [OE-core] [PATCH] base.bbclass wipe ${S} before unpacking source

On 23 February 2016 at 18:01, Christopher Larson wrote: > db isn't the only recipe doing that. The fetcher unpack method knows where > it's unpacking to, I think if anyone should be clearing out the destination > first, it should. If that's true for tarballs, I agree. I

Re: [OE-core] [PATCH] base.bbclass wipe ${S} before unpacking source

On Tue, Feb 23, 2016 at 6:55 AM Burton, Ross wrote: > > On 23 February 2016 at 11:36, Markus Lehtonen < > markus.lehto...@linux.intel.com> wrote: > >> Make sure that we have a pristine source tree after do_unpack. >> > > Interestingly this fails on db-native rebuild for

[OE-core] [PATCHv2 1/2] testimage.bbclass: add generic, image test suites

Add generic test suites MINTESTSUITE, NETTESTSUITE, DEVTESTSUITE to group common test suites. Add DEFAULT_TEST_SUITES_pn- variables for: * core-image-minimal-dev * core-image-full-cmdline * core-image-x11 * core-image-lsb * core-image-lsb-dev New default test suites use generic test

[OE-core] [PATCHv2 2/2] testimage.bbclass: reuse generic test suites

Modify existing default test suites to reuse the new generic test suites. Related to [YOCTO #8410] Signed-off-by: Alex Franco --- meta/classes/testimage.bbclass | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git

[OE-core] [PATCHv2 0/2] testimage: add/modify DEFAULT_TEST_SUITES

- Add generic variables to reuse values in default test suites - Add more default test suites variables - Modify existing test suites to use generic vars when possible [YOCTO #8410] Alex Franco (2): testimage.bbclass: add generic, image test suites testimage.bbclass: reuse generic test

Re: [OE-core] [PATCH 1/1] useradd_base.bbclass: fix simultaneous with flock

On 23 February 2016 at 17:01, Burton, Ross wrote: > The *amazing* BB_VERBOSE_LOGS option (set to 1 in local.conf to get all > shell scripts to do set -x) tells me this is due to missing quotes around > the opts assignment: > Why do some of the opts assignments just do

Re: [OE-core] [PATCH 1/1] useradd_base.bbclass: fix simultaneous with flock

On 23 February 2016 at 16:29, Burton, Ross wrote: > I got an error when openssh's do_install was running useradds to the > sysroot: > > | DEBUG: Executing shell function useradd_sysroot > | Running useradd commands... > | >

Re: [OE-core] [PATCH 1/1] useradd_base.bbclass: fix simultaneous with flock

On 23 February 2016 at 02:45, wrote: > When perform useradd during populate sysroot, it locks files passwd.lock > and group.lock at same time. And then it meets a dead lock issue > randomly. > > Use flock to reslove it by using an universal lock file for all the > user

Re: [OE-core] [PATCH] argp-standalone: make it available for non-musl systems too

Hi Khem, On Tue, Feb 23, 2016 at 10:40:28AM -0500, Khem Raj wrote: >Uclibc has its own argp implemented as libuargp so please use that you dont >need yet another implementation >>On Feb 23, 2016 10:18 AM, "Maxin B. John" wrote: >> >>Without this, uclibc build of rng-tools

[OE-core] [fido][PATCH 0/7] fido Security fixes pull request

From: Armin Kuster Please consider these for the next fido This is to meet our obligation for Yocto compatibility The following changes since commit 06d9c894636352a6c93711c7284d02b0c794a527: libbsd: Security fix CVE-2016-2090 (2016-02-18 11:03:10 +) are available

Re: [OE-core] [PATCH] argp-standalone: make it available for non-musl systems too

On 23 February 2016 at 15:40, Khem Raj wrote: > Uclibc has its own argp implemented as libuargp so please use that you > dont need yet another implementation > So the proper fix is to change rng-tools so it doesn't depend on argp-standalone on uclibc I guess. Ross --

Re: [OE-core] [PATCH] argp-standalone: make it available for non-musl systems too

Uclibc has its own argp implemented as libuargp so please use that you dont need yet another implementation On Feb 23, 2016 10:18 AM, "Maxin B. John" wrote: > Without this, uclibc build of rng-tools will fail with this error: > > ERROR: Nothing PROVIDES 'argp-standalone' >

[OE-core] [PATCH] fontconfig: Don't add font directories from host

* when enabled, configure check for "fonts" directory existence in following directories: /usr/X11R6/lib/X11 /usr/X11/lib/X11 /usr/lib/X11 on _host_ system and if it exists it adds element to /etc/fonts/fonts.conf * update_font_cache postinst will then fail if host system has e.g.

[OE-core] [PATCH] argp-standalone: make it available for non-musl systems too

Without this, uclibc build of rng-tools will fail with this error: ERROR: Nothing PROVIDES 'argp-standalone' (but rng-tools_5.bb DEPENDS on or otherwise requires it) ERROR: argp-standalone was skipped: incompatible with host x86_64-poky-linux-uclibc (not in COMPATIBLE_HOST) ERROR: Required build

Re: [OE-core] [PATCH] add tunings for 32-bit ARMv8-a

On Tue, Feb 16, 2016 at 05:20:20PM +0100, Martin Jansa wrote: > On Tue, Feb 16, 2016 at 06:08:45PM +0200, Dragomir Daniel wrote: > > > > > > On 02/16/2016 04:54 PM, Martin Jansa wrote: > > > On Tue, Feb 16, 2016 at 04:28:38PM +0200, Daniel Dragomir wrote: > > >> From: Cristian Bercaru

[OE-core] Debugging using sysroots and GDB

Hi Everybody Currently debugging using sysroots seems to work as long as the work folder containing the original source is available. Once this work dir is gone the debugger is no longer able to find the source code. This is especially confusing if some packages are taken from sstate and

Re: [OE-core] [PATCH] base.bbclass wipe ${S} before unpacking source

On 23 February 2016 at 11:36, Markus Lehtonen < markus.lehto...@linux.intel.com> wrote: > Make sure that we have a pristine source tree after do_unpack. > Interestingly this fails on db-native rebuild for me, as db is playing games with S (it's not the top of the tarball). I had a look at the

[OE-core] [PATCH V2] musl: Upgrade to 1.1.14

There has been regressions seen in 1.1.13 hence a quick 1.1.14 release is made license checksum changed due to updates to authors/contributors list here is the list of all changes between 1.1.13 and 1.1.14 http://git.musl-libc.org/cgit/musl/log/?qt=range=v1.1.13..v1.1.14 Signed-off-by: Khem

Re: [OE-core] [PATCH 2/2] oe-core: Update alternatives of info pages

On 23 February 2016 at 11:47, wrote: > From: Guojian Zhou > > Update alternatives of info pages in several packages. > > Signed-off-by: Guojian Zhou > Presumably these files are all identical, so would it be

[OE-core] [PATCH 2/2] oe-core: Update alternatives of info pages

From: Guojian Zhou Update alternatives of info pages in several packages. Signed-off-by: Guojian Zhou --- meta/recipes-devtools/autoconf/autoconf.inc | 6 +- meta/recipes-devtools/binutils/binutils.inc | 7 +++

[OE-core] [PATCH 1/2] oe-core: Update alternatives of man pages

From: Guojian Zhou Update alternatives of man pages between util-linx and shadow packages. Signed-off-by: Guojian Zhou --- meta/recipes-core/util-linux/util-linux.inc | 3 +++ meta/recipes-extended/shadow/shadow.inc | 4 +++- 2 files

[OE-core] [PATCH] Wipe ${S} before unpacking sources

It would seem reasonable that do_unpack() always results in a pristine source tree. This patch causes ${S} to be removed before unpacking sources. I didn't quite understand what kind of "investigation" the following code comment in do_unpack() was referring to: # TODO: Investigate if we can

[OE-core] [PATCH] base.bbclass wipe ${S} before unpacking source

Make sure that we have a pristine source tree after do_unpack. [YOCTO #9064] Signed-off-by: Markus Lehtonen --- meta/classes/base.bbclass | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/meta/classes/base.bbclass

Re: [OE-core] [PATCH v6 0/4] IPK signing for the gpg_sign module

Hi, Resending as my I got a strange "Only members may post to the list." error yesterday... On Fri, 2016-02-19 at 17:45 +0200, Ioan-Adrian Ratiu wrote: > This patch series extends the gpg_sign module to support ipk signing. > > v6 implements Markus' feedback. The most notable change is the >

Re: [OE-core] [PATCH v6 2/4] gpg_sign: detach_sign: fix gpg > 2.1 STDIN file descriptor

Hi, Resending as my I got a strange "Only members may post to the list." error yesterday... On Fri, 2016-02-19 at 17:43 +0200, Ioan-Adrian Ratiu wrote: > Starting from v2.1 passing passwords directly to gpg does not work > anymore [1], instead a loopback interface must be used otherwise > gpg

Re: [OE-core] [PATCH v6 1/4] gpg_sign: add local ipk package signing functionality

Hi, Resending as my I got a strange "Only members may post to the list." error yesterday... On Fri, 2016-02-19 at 17:43 +0200, Ioan-Adrian Ratiu wrote: > Implement ipk signing inside the sign_ipk bbclass using the gpg_sign > module and configure signing similar to how rpm does it. sign_ipk >

[OE-core] [PATCH v2] libdrm: fix build with uclibc

Fix 'O_CLOEXEC' undeclared error with uclibc Signed-off-by: Maxin B. John --- .../drm/libdrm/fix_O_CLOEXEC_undeclared.patch | 24 ++ meta/recipes-graphics/drm/libdrm_2.4.66.bb | 1 + 2 files changed, 25 insertions(+) create mode 100644

Re: [OE-core] [PATCH] libdrm: fix build with uclibc

Hi Ross, >On Tue, Feb 23, 2016 at 09:25:01AM +, Burton, Ross wrote: > >>On 23 February 2016 at 09:12, Maxin B. John wrote: >> >> ++#ifndef _GNU_SOURCE >> ++#define _GNU_SOURCE >> ++#endif >#including config.h is probably a better fix, as that already defines

Re: [OE-core] [PATCH] libdrm: fix build with uclibc

On 23 February 2016 at 09:12, Maxin B. John wrote: > ++#ifndef _GNU_SOURCE > ++#define _GNU_SOURCE > ++#endif > #including config.h is probably a better fix, as that already defines GNU_SOURCE. Ross -- ___ Openembedded-core

[OE-core] [PATCH] libdrm: fix build with uclibc

Fix 'O_CLOEXEC' undeclared error with uclibc Signed-off-by: Maxin B. John --- .../drm/libdrm/fix_O_CLOEXEC_undeclared.patch | 26 ++ meta/recipes-graphics/drm/libdrm_2.4.66.bb | 1 + 2 files changed, 27 insertions(+) create mode 100644