Re: [OE-core] [RFC PATCH 0/8] [WIP] runqemu/runqemu-internal: refactor it

On 05/20/2016 10:31 AM, Robert Yang wrote: Hi Nathan, Thanks, but I'm sorry to say that this is only a RFC, we may change it a lot, I will talk with RP, and let you when we have progresses. Oonce we change it a lot, for example, change runqemu to use python rather than shell script, your

Re: [OE-core] [RFC PATCH 0/8] [WIP] runqemu/runqemu-internal: refactor it

Hi Nathan, Thanks, but I'm sorry to say that this is only a RFC, we may change it a lot, I will talk with RP, and let you when we have progresses. // Robert On 05/19/2016 10:57 PM, Nathan Rossi wrote: On Tue, May 10, 2016 at 6:13 PM, Robert Yang wrote: Hello,

Re: [OE-core] PRServer's problem

On 05/19/2016 06:17 PM, Richard Purdie wrote: On Thu, 2016-05-19 at 18:12 +0800, Robert Yang wrote: On 05/19/2016 05:45 PM, Richard Purdie wrote: To be really clear, OE-Core will not have a different signature policy on release branches since that differing policy would break user

[OE-core] [PATCH] coreutils: Fix rootfs creation errors

1) error: file /usr/share/man/man1/su.1 from install of shadow-doc-4.2.1 conflicts with file from package coreutils-doc-6.9-r5 2) error: file /usr/share/man/man1/hostname.1 from install of net-tools-doc conflicts with file from package coreutils-doc-6.9-r5 3) error: file

[OE-core] [PATCH] net-tools: Fix rootfs creation errors

1) error: file /usr/share/man/man1/hostname.1 from install of net-tools-doc conflicts with file from package coreutils-doc-6.9-r5 2) error: file /usr/share/man/man1/hostname.1 from install of net-tools-doc conflicts with file from package coreutils-doc-8.25 Signed-off-by:

[OE-core] [PATCH] shadow: Fix rootfs creation errors

error: file /usr/share/man/man1/su.1 from install of shadow-doc-4.2.1 conflicts with file from package coreutils-doc-6.9-r5 Signed-off-by: Dai Caiyun --- meta/recipes-extended/shadow/shadow.inc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff

[OE-core] [PATCH Jethro v2] gdb: Backport patch to changes with AVX and MPX

The current MPX target descriptions assume that MPX is always combined with AVX, however that's not correct. We can have machines with MPX and without AVX; or machines with AVX and without MPX. This patch adds new target descriptions for machines that support both MPX and AVX, as duplicates of

[OE-core] [PATCH Krogoth v2] gdb: Backport patch to changes with AVX and MPX

The current MPX target descriptions assume that MPX is always combined with AVX, however that's not correct. We can have machines with MPX and without AVX; or machines with AVX and without MPX. This patch adds new target descriptions for machines that support both MPX and AVX, as duplicates of

[OE-core] [PATCH 0/1] [PATCHV2] gdb: Backport 7.12 features supporting AVX and MPX

The current MPX target descriptions assume that MPX is always combined with AVX, however that's not correct. We can have machines with MPX and without AVX; or machines with AVX and without MPX. This patch adds new target descriptions for machines that support both MPX and AVX, as duplicates of

[OE-core] [PATCH 1/1] gdb: Backport patch to changes with AVX and MPX

The current MPX target descriptions assume that MPX is always combined with AVX, however that's not correct. We can have machines with MPX and without AVX; or machines with AVX and without MPX. This patch adds new target descriptions for machines that support both MPX and AVX, as duplicates of

Re: [OE-core] [PATCH v3 4/6] bmap-tools: generate standalone script

On Thu, May 19, 2016 at 2:50 PM, Alexander Kanevskiy wrote: > On Thu, May 19, 2016 at 5:54 PM, Christopher Larson > wrote: > >> On Thu, May 19, 2016 at 7:19 AM, Alexander Kanevskiy >> wrote: >> >>> On Wed, May 4, 2016 at 9:55 PM, Christopher

Re: [OE-core] [PATCH v3 4/6] bmap-tools: generate standalone script

On Thu, May 19, 2016 at 5:54 PM, Christopher Larson wrote: > On Thu, May 19, 2016 at 7:19 AM, Alexander Kanevskiy wrote: > >> On Wed, May 4, 2016 at 9:55 PM, Christopher Larson >> wrote: >> >>> Yeah, putting it there does require

Re: [OE-core] [PATCH 1/1] gdb: 7.11 backport of 7.12 avx/mxp support

> On May 19, 2016, at 1:17 PM, bavery wrote: > > Signed-off-by: bavery > --- > meta/recipes-devtools/gdb/gdb-common.inc |2 +- > meta/recipes-devtools/gdb/gdb/0011-avx_mpx.patch | 2503 ++ > 2 files changed, 2504

[OE-core] [PATCH 0/1] [PATCH] gdb: Backport 7.12 features supporting AVX and MPX

This patch brings in features from gdb 7.12 so that an Intel core that supports MPX but not AVX will work as will the converse. Previous versions assumed that if MPX was supported AVX was as well. -brian avery Changelog details of this patch: 2016-02-25 Marcin Kościelnicki

[OE-core] [PATCH 1/1] gdb: 7.11 backport of 7.12 avx/mxp support

Signed-off-by: bavery --- meta/recipes-devtools/gdb/gdb-common.inc |2 +- meta/recipes-devtools/gdb/gdb/0011-avx_mpx.patch | 2503 ++ 2 files changed, 2504 insertions(+), 1 deletion(-) create mode 100644

[OE-core] [PATCH] scripts/bitbake-whatchanged: migrate from optparse to argparse

The script bitbake-whatchanged uses optparse library, which is deprecated since python 2.7. This migrates to argparse library. [Yocto #9634] Signed-off-by: Humberto Ibarra --- scripts/bitbake-whatchanged | 32 1 file changed, 12

[OE-core] nss postinst requires nss-native during rootfs generation

We've recently added nss to our image and have started to see rootfs generation anomalies. We use IMAGE_FEATURES = "read-only-rootfs" so postinsts run at rootfs generation time. nss's postinst calls shlibsign. Under normal circumstances with read-only-rootfs, this appears to come from nss-native

Re: [OE-core] [PATCH v1] runqemu: Add suport for qemuzynqmp

On Thu, May 12, 2016 at 2:37 PM, Alistair Francis wrote: > Signed-off-by: Alistair Francis Ping! > --- > scripts/runqemu | 9 - > scripts/runqemu-internal | 21 + > 2 files changed, 29

Re: [OE-core] [PATCH] bluez5: move btmgmt to common READLINE section

On 19 May 2016 at 16:32, Nicolas Dechesne wrote: > i haven't seen any feedback on this one, and I don't see it in -next.. > It's in mut and I should be sending a consolidated pull soon. Ross -- ___ Openembedded-core

Re: [OE-core] [PATCH] bluez5: move btmgmt to common READLINE section

hi there, On Mon, May 2, 2016 at 5:56 PM, Nicolas Dechesne wrote: > Upstream in 5.33 btmgmt was moved from experimental to common READLINE > section, > in commit e4f0c5582f1fe3451d5588243adba9de1ed68b80, but this was never updated > in the recipe. > > Signed-off-by:

Re: [OE-core] [RFC PATCH 0/8] [WIP] runqemu/runqemu-internal: refactor it

On Tue, May 10, 2016 at 6:13 PM, Robert Yang wrote: > Hello, > > This is still WIP, I send this out to make sure that I won't walk on > wrong way too far. Please feel free to give any comments. Hi Robert, This is great! So I went ahead and tested out converting the

Re: [OE-core] [PATCH v3 4/6] bmap-tools: generate standalone script

On Thu, May 19, 2016 at 7:19 AM, Alexander Kanevskiy wrote: > On Wed, May 4, 2016 at 9:55 PM, Christopher Larson > wrote: > >> >> > >>> > Also, the convention is to add do_deploy before do_build, not before >>> > do_package, otherwise do_deploy's checksum is

Re: [OE-core] [oe-core PATCH v8 13/13] core-image-weston: If X11 is enabled, add XWayland support

On 18 May 2016 at 22:35, Otavio Salvador wrote: > As discussed on IRC, instead of XTerm - which is not included on > OE-Core - we could use Xeyes as an utility to show it is working. What > do you think? Do you want me to send a v9 changing it or do you change >

Re: [OE-core] [PATCH v3 4/6] bmap-tools: generate standalone script

On Wed, May 4, 2016 at 9:55 PM, Christopher Larson wrote: > > > >> > Also, the convention is to add do_deploy before do_build, not before >> > do_package, otherwise do_deploy's checksum is included int he checksums >> of >> > do_package and subsequent tasks, even though its

Re: [OE-core] [PATCH 4/4] ghostscript: fix upstream check

On 19 May 2016 at 14:43, Maxin B. John wrote: > +UPSTREAM_CHECK_URI = " > https://github.com/ArtifexSoftware/ghostpdl-downloads/releases; > #9573 reports that the current SRC_URI doesn't work either, so you change the SRC_URI to their new download URIs and see if we still

[OE-core] [PATCH 2/4] freetype: fix upstream check

Provide UPSTREAM_CHECK_URI and UPSTREAM_CHECK_REGEX for proper upstream check. Signed-off-by: Maxin B. John --- meta/recipes-graphics/freetype/freetype_2.6.3.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/recipes-graphics/freetype/freetype_2.6.3.bb

[OE-core] [PATCH 4/4] ghostscript: fix upstream check

Ghostscript releases from version 9.19 have been moved to GitHub. Update UPSTREAM_CHECK_URI to fix upstream check. Signed-off-by: Maxin B. John --- meta/recipes-extended/ghostscript/ghostscript_9.18.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git

[OE-core] [PATCH 3/4] libgudev: fix upstream check

Provide UPSTREAM_CHECK_URI and UPSTREAM_CHECK_REGEX to fix upstream check. Signed-off-by: Maxin B. John --- meta/recipes-gnome/libgudev/libgudev_230.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-gnome/libgudev/libgudev_230.bb

[OE-core] [PATCH 1/4] package_regex.inc: remove deprecated file

Remove this file as it has been deprecated in the previous release. New entries should be added to recipes itself. Signed-off-by: Maxin B. John --- meta/classes/distrodata.bbclass| 1 - meta/conf/distro/include/package_regex.inc | 22 -- 2

Re: [OE-core] [PATCH 0/7][python3] buildtools-tarball: replace python with python3

On 05/19/2016 03:19 PM, Alexander Kanavin wrote: On 05/18/2016 10:43 AM, Robert Yang wrote: Robert Yang (7): python3-smmap: add it for python3-gitdb python3-async: add it for python3-gitdb python3-gitdb: add it for python3-git python3-git: add it for buildtools-tarball You can

Re: [OE-core] [PATCH 5/7] buildtools-tarball: remove nativesdk-python-pexpect

On 05/18/2016 10:43 AM, Robert Yang wrote: It was added for testing, and not needed any more after: meta/recipes-core/meta/buildtools-tarball.bb | 1 - 1 file changed, 1 deletion(-) Same thing: if the pexpect recipe is not needed by anything, then remove it. Alex --

Re: [OE-core] [PATCH 0/7][python3] buildtools-tarball: replace python with python3

On 05/18/2016 10:43 AM, Robert Yang wrote: Robert Yang (7): python3-smmap: add it for python3-gitdb python3-async: add it for python3-gitdb python3-gitdb: add it for python3-git python3-git: add it for buildtools-tarball You can remove the Python 2 versions at the same time.

[OE-core] [PATCH] mesa-demos: provide option for disabling GLX demos

There are platforms that default to EGL only configurations in which case the GLX applications are not required at all. Allow the user to control generation of these demos as needed through a configure switch. Signed-off-by: Awais Belal ---

Re: [OE-core] PRServer's problem

On Thu, 19 May 2016 11:37:03 Joshua G Lock wrote: > On Thu, 2016-05-19 at 18:12 +0800, Robert Yang wrote: > > On 05/19/2016 05:45 PM, Richard Purdie wrote: > > > Users are free to set their own policies, the system was designed > > > to do > > > that. If WindRiver wants to have a much more

[OE-core] [PATCH] kernel: moves KERNEL_SRC_PATH to bitbake.conf

From: Ming Liu "/usr/src/kernel" is being hard-coded in multiple recipes so far, move its definition to bitbake.conf. Signed-off-by: Ming Liu --- meta/classes/kernel.bbclass | 4

[OE-core] [PATCH 2/2] zip: update SRC_URI

The infozip FTP server appears to have been taken down, so change the SRC_URI to point at their SourceForge project. Also as the SRC_URI can't be generated from the version and there is no other user of the .inc, merge the .bb and .inc together. [ YOCTO #9655 ] Signed-off-by: Ross Burton

[OE-core] [PATCH 1/2] unzip: update SRC_URI

The infozip FTP server appears to have been taken down, so change the SRC_URI to point at their SourceForge project. [ YOCTO #9655 ] Signed-off-by: Ross Burton --- meta/recipes-extended/unzip/unzip_6.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [OE-core] PRServer's problem

On Thu, 2016-05-19 at 18:12 +0800, Robert Yang wrote: > > On 05/19/2016 05:45 PM, Richard Purdie wrote: > > Users are free to set their own policies, the system was designed > > to do > > that. If WindRiver wants to have a much more permissive policy, I'm > > more than happy for them to do so. >

Re: [OE-core] PRServer's problem

On Thu, May 19, 2016 at 05:45:11PM +0800, Robert Yang wrote: > Hi Martin, > > On 05/19/2016 04:47 PM, Martin Jansa wrote: > > As the commit says, small change in package.bbclass also causes all > > packages to > > be recreated with PR bump even when the content is most likely the same. > > That

Re: [OE-core] PRServer's problem

On Thu, 2016-05-19 at 18:12 +0800, Robert Yang wrote: > On 05/19/2016 05:45 PM, Richard Purdie wrote: > > To be really clear, OE-Core will not have a different signature > > policy > > on release branches since that differing policy would break user > > expectations and also wouldn't get tested

Re: [OE-core] PRServer's problem

On 05/19/2016 05:45 PM, Richard Purdie wrote: The bottom line is that the system is setup to be sensitive to changes. Where we've had cases where we haven't reacted to changes, people have complained and we've ended up making sure we do react to them. The patch you reference was one such case

[OE-core] Wic and "live" images

Greetings, I am trying to learn "wic" and have been confused as how to create a "live" style image. I am following "http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html#creating-partitioned-images; but am getting confused on the target to use to create the a file system that has

Re: [OE-core] PRServer's problem

The bottom line is that the system is setup to be sensitive to changes. Where we've had cases where we haven't reacted to changes, people have complained and we've ended up making sure we do react to them. The patch you reference was one such case where users complained we didn't react enough.

Re: [OE-core] PRServer's problem

Hi Martin, On 05/19/2016 04:47 PM, Martin Jansa wrote: As the commit says, small change in package.bbclass also causes all packages to be recreated with PR bump even when the content is most likely the same. That is another case we need work on. Fixing bug in gcc may at least provide

Re: [OE-core] PRServer's problem

On Thu, 2016-05-19 at 10:47 +0200, Martin Jansa wrote: > As the commit says, small change in package.bbclass also causes all > packages to be recreated with PR bump even when the content is most > likely the same. > > Fixing bug in gcc may at least provide different binaries so it might > be

Re: [OE-core] PRServer's problem

As the commit says, small change in package.bbclass also causes all packages to be recreated with PR bump even when the content is most likely the same. Fixing bug in gcc may at least provide different binaries so it might be useful to upgrade them on target (or at least distinguish if they were

Re: [OE-core] [PATCH 1/1] webkitgtk: turn off JIT on armv4 and armv7a

On 2016-05-19 07:42, Khem Raj wrote: On May 18, 2016, at 10:38 PM, Robert Yang wrote: On 05/19/2016 01:28 PM, Khem Raj wrote: On May 18, 2016, at 8:16 PM, Gary Thomas wrote: On 2016-05-18 22:07, Khem Raj wrote: On Wed, May 18, 2016 at

Re: [OE-core] [PATCH 2/5] systemd: Create missing sysusers offline

On Thu, 2016-05-19 at 08:36 +0100, Richard Purdie wrote: > On Tue, 2016-05-17 at 21:40 -0700, Khem Raj wrote: > > Some system users which are needed by systemd components were > > missing > > create these users knobbed with relevant packageconfig > > > > Signed-off-by: Khem Raj

Re: [OE-core] [PATCH v4 0/2] Yocto Bug #6945

Ping. On 05/12/2016 05:48 PM, zhe...@windriver.com wrote: > From: He Zhe > > This has been reviewed several rounds and no more comments are provided so > far. > Here are the brief history. More details can be found in the previous threads. > > v1 to v2: > - Change

Re: [OE-core] [PATCH 2/5] systemd: Create missing sysusers offline

On Tue, 2016-05-17 at 21:40 -0700, Khem Raj wrote: > Some system users which are needed by systemd components were missing > create these users knobbed with relevant packageconfig > > Signed-off-by: Khem Raj > --- > meta/recipes-core/systemd/systemd_229.bb | 8 +++- > 1