Re: [OE-core] [PATCH] lsb: Remove bashisms from the rc.d functions

On 04/08/2017 12:31 AM, Richard Purdie wrote: > On Fri, 2017-04-07 at 23:55 +0200, Marek Vasut wrote: >> This bashism prevents functions from working on systems without bash, >> ie. on systems with busybox shell or debian dash. Replace them with >> bourne-compatible command instead. > > Note that

Re: [OE-core] [PATCH] lsb: Remove bashisms from the rc.d functions

On Fri, 2017-04-07 at 23:55 +0200, Marek Vasut wrote: > This bashism prevents functions from working on systems without bash, > ie. on systems with busybox shell or debian dash. Replace them with > bourne-compatible command instead. Note that you'd code adds in a couple of forks for code which

[OE-core] ✗ patchtest: failure for lsb: Remove bashisms from the rc.d functions (rev2)

== Series Details == Series: lsb: Remove bashisms from the rc.d functions (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/6209/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have

Re: [OE-core] [PATCH 0/4] Use fixed DISTRO_FEATURES for native

On Fri, 2017-04-07 at 09:08 +0300, Jussi Kukkonen wrote: > Avoid signifant native task churn when DISTRO_FEATURES is changed > by defining a fixed DISTRO_FEATURES value (default is "") for native > recipes. > > The xorg changes are all removals of x11 requirements (that were not > real) from

[OE-core] [PATCH] lsb: Remove bashisms from the rc.d functions

This bashism prevents functions from working on systems without bash, ie. on systems with busybox shell or debian dash. Replace them with bourne-compatible command instead. Signed-off-by: Marek Vasut Cc: Ross Burton Cc: Richard Purdie

Re: [OE-core] [PATCH 2/4] no-static-libs: Add entry for ncurses

On Fri, 2017-04-07 at 10:42 -0700, Andre McCurdy wrote: > On Fri, Apr 7, 2017 at 9:41 AM, Richard Purdie > wrote: > > > > Yes, the option to disable static libraries in boost really is > boost or ncurses? ncurses. Its been a long day, I'll tweak the commit

[OE-core] [PATCH][morty] base-files: resize only serial tty's in profile

[Backported from master.] We don't want to run resize on non serial consoles. There's been an earlier attempt (6557787), so this builds upon that. The problem we're seeing is that if there is text buffered in the virtual console (like from a desperate user trying to enter login details), resize

[OE-core] [PATCH][krogoth] base-files: resize only serial tty's in profile

[Backported from master.] We don't want to run resize on non serial consoles. There's been an earlier attempt (6557787), so this builds upon that. The problem we're seeing is that if there is text buffered in the virtual console (like from a desperate user trying to enter login details), resize

Re: [OE-core] [PATCH 2/4] no-static-libs: Add entry for ncurses

On Fri, Apr 7, 2017 at 9:41 AM, Richard Purdie wrote: > Yes, the option to disable static libraries in boost really is boost or ncurses? > "--without-normal". Add this for ncurses and its variants. > > Signed-off-by: Richard Purdie

[OE-core] State of bitbake world, Failed tasks 2017-04-05

== Number of issues - stats == {| class='wikitable' !|Date !!colspan='3'|Failed tasks !!colspan='6'|Failed depencencies!!|Signatures !!colspan='14'|QA !!Comment |- || ||qemuarm ||qemux86 ||qemux86_64

[OE-core] [PATCH 2/4] no-static-libs: Add entry for ncurses

Yes, the option to disable static libraries in boost really is "--without-normal". Add this for ncurses and its variants. Signed-off-by: Richard Purdie --- meta/conf/distro/include/no-static-libs.inc | 4 1 file changed, 4 insertions(+) diff --git

Re: [OE-core] [PATCH v2 1/2] runqemu: Automatically add a TFTP directory for slirp boot

On Fri, Mar 31, 2017 at 10:07 AM, Alistair Francis wrote: > On Fri, Mar 24, 2017 at 1:38 PM, Alistair Francis > wrote: >> When booting QEMU with slirp networking we want to use QEMUs TFTP server >> to make the images in deploy accessible to the

Re: [OE-core] [morty][PATCH 1/1] packagegroup-core-standalone-sdk-target: add libssp

On 04/06/2017 07:38 PM, Paul Eggleton wrote: If you want to be able to use -fstack-protector then you need the runtime support - you can either write this yourself or use libssp supplied with GCC. If you're using GCC then it seems likely that you'd just be using libssp, so include in the SDK

[OE-core] [PATCH 3/4] ncurses: Drop incorrect option

The --disable-static option doesn't exist in ncurses. Its equivalent is --without-normal so remove the option which does nothing. Signed-off-by: Richard Purdie --- meta/recipes-core/ncurses/ncurses.inc | 1 - 1 file changed, 1 deletion(-) diff --git

[OE-core] [PATCH 4/4] uninative-flags.inc: Build binutils-native as pie

Some distros (ubuntu 16.10, debian-testing) default to gcc configured with --enable-default-pie (see gcc -v). This breaks e.g. prelink-native on a pie default system if binutils-native was built on a system which is not pie default We therefore enable pie unconditionally for native recipes where

[OE-core] [PATCH 1/4] selftest/sstatetests: Replace glibc-initial with linux-libc-headers

The intent in these tests was to find something early in the bootstrap process to run tests against which didn't require long build times. This breaks with the removal of the glibc-initial do_build target. Replacing it with linux-libc-headers seems like a good choice and simplifies the

[OE-core] [PATCH 5/5] yocto-compat-layer: test signature differences when setting MACHINE

Selecting a machine may only affect the signature of tasks that are specific to that machine. In other words, when MACHINE=A and MACHINE=B share a recipe foo and the output of foo, then both machine configurations must build foo in exactly the same way. Otherwise it is not possible to use both

[OE-core] [PATCH 3/5] yocto-compat-layer: include bitbake-diffsigs output

After filtering out potential false positives, it becomes feasible to include the output of bitbake-diffsigs for those tasks which definitely have a change. Depends on bitbake-diffsigs with the "--signature" parameter. Enhanced output now is: AssertionError: False is not true : Layer

[OE-core] [PATCH 4/5] yocto-compat-layer: also determine tune flags for each task

locked-sigs.inc groups tasks according to their tune flags (allarch, i586, etc.). Also retrieve that information while getting signatures, it will be needed to determine when setting a machine changes tasks that aren't machine-specific. Signed-off-by: Patrick Ohly ---

[OE-core] [PATCH 1/5] yocto-compat-layer: fix also other command invocations

In commit 5b9ac62ab535d, one place was fixed where a command was invoked such that failures caused double stack traces and stderr was lost. The same problem also occurs elsewhere, triggered for example by a layer with parsing problems. Now a new utility method is used instead of repeating the

[OE-core] [PATCH 2/5] yocto-compat-layer: limit report of signature changes

Typically a single change cascades through the entire task dependency chain. Developers had to figure that out themselves, based on hard to read and interpret output (not sorted, no indention, no explanations): $ yocto-compat-layer.py -n meta- ... AssertionError: True is not false :

[OE-core] [PATCH 0/5] [RFC] yocto-compat-layer: various enhancements + bitbake-diffsigs support

I started applying yocto-compat-layer to some real BSP layers and ran into some usability issues with the tool. I also didn't want to do the root cause analysis manually, so I automated the dependency analysis and the running of bitbake-diffsigs. This patch series is based on Mark's

Re: [OE-core] ✗ patchtest: failure for Set linux-firmware to correct license

On Fri, 2017-04-07 at 10:32 +, Patchwork wrote: > == Series Details == > > Series: Set linux-firmware to correct license > Revision: 1 > URL : https://patchwork.openembedded.org/series/6226/ > State : failure > > == Summary == > > > Thank you for submitting this patch series to

Re: [OE-core] [PATCH] selftest/recipetool: skip create_git in case x11 feature is not present

On Fri, 2017-04-07 at 08:57 +0300, Jussi Kukkonen wrote: > > > On 6 April 2017 at 19:41, > wrote: > From: Leonardo Sandoval > > > The unit test requires x11 as distro

Re: [OE-core] [PATCH 0/2] Fixes for building on Fedora 26 (Alpha)

On Fri, Apr 7, 2017 at 7:02 AM, Christopher Larson wrote: > > > On Thu, Apr 6, 2017 at 6:23 AM, Joshua Lock wrote: >> >> As Fedora 26 has a new gcc [1] and a new system pkg-config implementation >> [2] I >> wanted to do some testing on that host OS so

[OE-core] scripts/rpm2cpio.sh -- master version

The change to the rpm4 version of rpm2cpio.sh has triggered a problem on a few of our older build machines. Specifically: dd: invalid input flag: `skip_bytes' Try `dd --help' for more information. I was doing some investigation, and the line causing the issue is: dd if="$pkg" skip="$o"

Re: [OE-core] [PATCH 0/2] Fixes for building on Fedora 26 (Alpha)

On Thu, Apr 6, 2017 at 6:23 AM, Joshua Lock wrote: > As Fedora 26 has a new gcc [1] and a new system pkg-config implementation > [2] I > wanted to do some testing on that host OS so that we might be able to get > some > fixes in before Pyro/2.3 is released. > > The

[OE-core] [PATCH v2] python-pycurl: create python3-pycurl recipe

The python-pycurl recipe can be used with python2 only even though python3 is officially supported by upstream. Create python3-pycurl recipe enabling the pycurl module for python3. Signed-off-by: Dmitry Rozhkov --- Changes in v2: - redefine SECURITY_CFLAGS for

Re: [OE-core] [PATCH] openssl: Fix symlink creation

On Fri, Apr 07, 2017 at 02:27:45PM +0200, David Vincent wrote: > On jeudi 6 avril 2017 15:03:36 CEST Martin Jansa wrote: > > I still don't understand why not use standard update-alternatives and > > install another package with your favorite openssl.conf which has higher > > ALTERNATIVE_PRIORITY.

Re: [OE-core] [PATCH 4/4] native.bbclass: Use fixed DISTRO_FEATURES

On 7 April 2017 at 15:13, Richard Purdie wrote: > > > Also, one question. Does this have any effect on qemu-native? Does > > > qemu-native need/use x11 today? > > qemu itself does not use anything x11 since last year and the default > > native packageconfig is

Re: [OE-core] [PATCH] openssl: Fix symlink creation

On 7 April 2017 at 15:27, David Vincent wrote: > > On jeudi 6 avril 2017 15:03:36 CEST Martin Jansa wrote: > > I still don't understand why not use standard update-alternatives and > > install another package with your favorite openssl.conf which has higher > >

Re: [OE-core] [PATCH] openssl: Fix symlink creation

On jeudi 6 avril 2017 15:03:36 CEST Martin Jansa wrote: > I still don't understand why not use standard update-alternatives and > install another package with your favorite openssl.conf which has higher > ALTERNATIVE_PRIORITY. Why not, but maybe this

Re: [OE-core] [PATCH 4/4] native.bbclass: Use fixed DISTRO_FEATURES

On Fri, 2017-04-07 at 14:59 +0300, Jussi Kukkonen wrote: > On 7 April 2017 at 11:28, Richard Purdie ion.org> wrote: > > On Fri, 2017-04-07 at 09:09 +0300, Jussi Kukkonen wrote: > > > There seems to be no advantage to letting distro features affect > > > native

Re: [OE-core] [PATCH 4/4] native.bbclass: Use fixed DISTRO_FEATURES

On 7 April 2017 at 11:28, Richard Purdie wrote: > On Fri, 2017-04-07 at 09:09 +0300, Jussi Kukkonen wrote: > > There seems to be no advantage to letting distro features affect > > native builds. There is a significant disadvantage: a change to > >

[OE-core] [PATCH 3/3] scripts/oe-build-perf-report: improve guessing of args

Search remote branches, too, when finding the latest commit. Signed-off-by: Markus Lehtonen --- scripts/oe-build-perf-report | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/oe-build-perf-report b/scripts/oe-build-perf-report index

[OE-core] [PATCH 0/3] Fixes to build perf test reporting

Three miscellaneous one-liners fixing minor issues in build performance test reporting scripts. Markus Lehtonen (3): build-perf-test-wrapper.sh: support extra args for email script oe-build-perf-report-email.py: use proper fallback email address scripts/oe-build-perf-report: improve

[OE-core] [PATCH 2/3] oe-build-perf-report-email.py: use proper fallback email address

Use properly formatted fallback email address instead of just the username. Signed-off-by: Markus Lehtonen --- scripts/contrib/oe-build-perf-report-email.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[OE-core] [PATCH 1/3] build-perf-test-wrapper.sh: support extra args for email script

Make it possible to provide (extra) command line arguments to the oe-build-perf-test-email script via a new environment variable OE_BUILD_PERF_REPORT_EMAIL_EXTRA_ARGS. Signed-off-by: Markus Lehtonen --- scripts/contrib/build-perf-test-wrapper.sh | 2 +- 1 file

Re: [OE-core] [PATCH v2 0/3][YOCTO #11090] Set linux-firmware to correct license

Hi, On Fri, Apr 07, 2017 at 03:57:33AM -0700, wei.tee...@intel.com wrote: > From: "Ng, Wei Tee" > > These patches is to update the SRCREV of linux-firmware to the latest HEAD > and set thelicense file explicitly for linux-firmware-carl9170 to GPL-2. > > The SRCREV for

Re: [OE-core] [PATCH v3 4/8] logrotate: replace fedorahosted.org SRC_URI with github.com source

On Fri, 2017-04-07 at 09:10 +, Choong, Yin Thong wrote: > Is wired. I bitbake successful on my machine. bitbake logrotate > -ccleanall and bitbake logrotate. > In this case, I should submit my entire patch or only resubmit this > patch [PATCH v3 4/8] with cover letter? Please send just this

[OE-core] [PATCH v2 2/3] linux-firmware: Set the license for carl9170 to GPLv2

From: "Ng, Wei Tee" linux-firmwara-carl9170 was set to a wrong license string. Carl9170 firmware is bounded by GPLv2 via code inspection on linux firmware source tree. Hence we include GPLv2 in LICENSE field and set carl9170 firmware to the correct license. [YOCTO #11090]

[OE-core] [PATCH v2 3/3] linux-firmware: Fix build failure when update SRCREV to latest HEAD

From: "Chang, Rebecca Swee Fun" When we update the SRCREV to latest, we will encouter the following bitbake error. Build error message: | Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 | error: Arch dependent

[OE-core] [PATCH v2 1/3] linux-firmware: update to revision a4dde74b

From: "Ng, Wei Tee" -change in amdgpu firmware copyright year -change in radeon firmware copyright year -LICENCE.mwl8335 was removed in linux-firmware source tree -specify the copyright year for siano -change in qla2xxx firmware copyright year Signed-off-by: Ng, Wei Tee

[OE-core] [PATCH v2 0/3][YOCTO #11090] Set linux-firmware to correct license

From: "Ng, Wei Tee" These patches is to update the SRCREV of linux-firmware to the latest HEAD and set thelicense file explicitly for linux-firmware-carl9170 to GPL-2. The SRCREV for linux-firmware was updated to the latest in order to include the GPL-2 license file.

[OE-core] ✗ patchtest: failure for Set linux-firmware to correct license

== Series Details == Series: Set linux-firmware to correct license Revision: 1 URL : https://patchwork.openembedded.org/series/6226/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed

[OE-core] [PATCH 3/4] linux-firmware: Set the license for carl9170 to GPLv2

From: "Ng, Wei Tee" linux-firmwara-carl9170 was set to a wrong license string. Carl9170 firmware is bounded by GPLv2 via code inspection on linux firmware source tree. Hence we include GPLv2 in LICENSE field and set carl9170 firmware to the correct license. [YOCTO #11090]

[OE-core] [PATCH 4/4] linux-firmware: Fix build failure when update SRCREV to latest HEAD

From: "Chang, Rebecca Swee Fun" When we update the SRCREV to latest, we will encouter the following bitbake error. Build error message: | Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 | error: Arch dependent

[OE-core] [PATCH 1/4] bitbake: fetch2: Do not fail to create symbolic links if they already exist

From: Peter Kjellerstedt When the fetcher retrieves file:// URLs, there is no lock file being used. This means that in case two separate tasks (typically from two concurrent invocations of bitbake) want to download the same file:// URL at the same time, there is a

[OE-core] [PATCH 0/4][YOCTO #11090] Set linux-firmware to correct license

From: "Ng, Wei Tee" These patches is to update the SRCREV of linux-firmware to the latest HEAD and set the license file explicitly for linux-firmware-carl9170 to GPL-2.   The SRCREV for linux-firmware was updated to the latest in order to include the GPL-2 license file. The

Re: [OE-core] [PATCH 0/2] Fixes for building on Fedora 26 (Alpha)

On Thu, 2017-04-06 at 06:50 -0700, Khem Raj wrote: > On Thu, Apr 6, 2017 at 6:23 AM, Joshua Lock > wrote: > > As Fedora 26 has a new gcc [1] and a new system pkg-config > > implementation [2] I > > wanted to do some testing on that host OS so that we might be able > > to

[OE-core] [PATCH 8/8] runqemu: make use of two new vars

From: Chen Qi Make use of STAGING_DIR_TUNCTL_NATIVE and STAGING_DIR_QEMU_BINDIR_NATIVE to run correctly. In this way, runqemu would still work when 'rm_work' is enabled. [YOCTO #11266] [YOCTO #11193] Signed-off-by: Chen Qi --- scripts/runqemu |

[OE-core] [PATCH 7/8] qemuboot.bbclass: add two vars for use by runqemu

From: Chen Qi Add STAGING_DIR_TUNCTL_NATIVE and STAGING_DIR_QEMU_BINDIR_NATIVE so that runqemu could find 'tunctl' and 'qemu-xxx' binaries to run correctly. [YOCTO #11266] [YOCTO #11193] Signed-off-by: Chen Qi --- meta/classes/qemuboot.bbclass |

[OE-core] [PATCH 6/8] runqemu: do not rely on grepping images

Fixed when the image is large and not enough memory: grep: memory exhausted Aborted [YOCTO #11073] Signed-off-by: Robert Yang --- meta/classes/qemuboot.bbclass | 3 +++ scripts/runqemu | 19 +++ 2 files changed, 14 insertions(+), 8

[OE-core] [PATCH 5/8] runqemu: use realpath for imgdir

The DEPLOY_DIR_IMAGE maybe relative or absolute path since it can be read from env vars, so use realpath for both imgdir and DEPLOY_DIR_IMAGE when compare. Signed-off-by: Robert Yang --- scripts/runqemu | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[OE-core] [PATCH 2/8] runqemu: support env vars explicitly

Use self.env_vars to support get vars from environment explicity. The MACHINE, ROOTFS and KERNEL was supported by shell based runqemu, and the help text says support them from env vars, so add them back. [YOCTO #11141] Signed-off-by: Robert Yang --- scripts/runqemu |

[OE-core] [PATCH 3/8] runqemu: use self.rootfs to replace self.nfs_dir

We can use self.rootfs as self.nfs_dir when self.fstype is nfs, this can reduce the code's complexity and we can re-use the code of checking ROOTFS conflictions. Signed-off-by: Robert Yang --- scripts/runqemu | 28 +--- 1 file changed, 13

[OE-core] [PATCH 4/8] runqemu: run without arguments

Since we can get MACHINE and others from env vars and "bitbake -e", "runqemu" can work without any arguments. Signed-off-by: Robert Yang --- scripts/runqemu | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/runqemu b/scripts/runqemu index

[OE-core] [PATCH 0/8 V2] fixes for runqemu and runqemu + rm_work

* V2: - Fixed "ERROR - name 'p' is not defined" - Add Qi's patch. // Robert The following changes since commit 901659a51cd53625a93f57a9c5865e90a07ec09d: oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir (2017-04-06 10:13:34 +0100) are available in the git

[OE-core] [PATCH 1/8] runqemu: fix 2 typos

* "is it" -> "it is" * Remove ".qemuboot.conf =" in the error message which looked strange. Signed-off-by: Robert Yang --- scripts/runqemu | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/runqemu b/scripts/runqemu index

Re: [OE-core] [PATCH 0/6] fixes for runqemu

On 04/07/2017 07:54 AM, Richard Purdie wrote: On Wed, 2017-04-05 at 23:41 -0700, Robert Yang wrote: The following changes since commit 3a1cce659156ef2654a55a6e3c6922fa2dc780e4: glibc: fix nativesdk ldd RTLDLIST (2017-04-05 23:22:06 +0100) are available in the git repository at:

Re: [OE-core] [PATCH v3 4/8] logrotate: replace fedorahosted.org SRC_URI with github.com source

Is wired. I bitbake successful on my machine. bitbake logrotate -ccleanall and bitbake logrotate. In this case, I should submit my entire patch or only resubmit this patch [PATCH v3 4/8] with cover letter? Thanks and Regards Choong YinThong -Original Message- From: Richard Purdie

Re: [OE-core] [PATCH 4/4] native.bbclass: Use fixed DISTRO_FEATURES

On Fri, 2017-04-07 at 09:09 +0300, Jussi Kukkonen wrote: > There seems to be no advantage to letting distro features affect > native builds. There is a significant disadvantage: a change to > DISTRO_FEATURES will trigger a lot of unnecessary native tasks. In a > test like this: >   $ bitbake

Re: [OE-core] [PATCH 1/1] image.inc/qemu.inc: preserve directories to be used by runqemu

On 04/05/2017 07:22 PM, Richard Purdie wrote: On Wed, 2017-04-05 at 20:06 +1000, Nathan Rossi wrote: On 30 March 2017 at 15:12, Chen Qi wrote: The 'recipe-sysroot' and 'recipe-sysroot-native' directories need to be preserved for runqemu to work correctly. Otherwise,

[OE-core] [PATCH 1/2] qemuboot.bbclass: add two vars for use by runqemu

Add STAGING_DIR_TUNCTL_NATIVE and STAGING_DIR_QEMU_BINDIR_NATIVE so that runqemu could find 'tunctl' and 'qemu-xxx' binaries to run correctly. [YOCTO #11266] [YOCTO #11193] Signed-off-by: Chen Qi --- meta/classes/qemuboot.bbclass | 5 - 1 file changed, 4

[OE-core] [PATCH 2/2] runqemu: make use of two new vars

Make use of STAGING_DIR_TUNCTL_NATIVE and STAGING_DIR_QEMU_BINDIR_NATIVE to run correctly. In this way, runqemu would still work when 'rm_work' is enabled. [YOCTO #11266] [YOCTO #11193] Signed-off-by: Chen Qi --- scripts/runqemu | 10 -- 1 file changed, 8

[OE-core] [PATCH 0/2] Fix runqemu problem when 'rm_work' is enabled

The following changes since commit 633ad6c9f436f5d2b6ee1a005b697661a054a394: oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir (2017-04-06 10:13:39 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/runqemu_rm_work

Re: [OE-core] [PATCH 0/4] Fix some incorrect TARGET_-* flags

On Thu, 2017-04-06 at 14:09 +0200, liu.min...@gmail.com wrote: > From: Ming Liu > > I had found a lot of churn in sysroots when multiple MACHINEs are > sharing a same build folder, which is the case in my company, after > digging into it, I found it's caused by the

Re: [OE-core] [PATCH] python-pycurl: create python3-pycurl recipe

On Wed, 2017-04-05 at 10:01 +0300, Dmitry Rozhkov wrote: > The python-pycurl recipe can be used with python2 only even > though python3 is officially supported by upstream. > > Create python3-pycurl recipe enabling the pycurl module for > python3. This failed autobuilder tests:

Re: [OE-core] [PATCH v3 4/8] logrotate: replace fedorahosted.org SRC_URI with github.com source

On Thu, 2017-04-06 at 01:35 -0700, yin.thong.cho...@intel.com wrote: > From: Choong YinThong > > fedorahosted.org was retired on March 1st, 2017. This is to > update the SRC_URI to point to github.com. > > [YOCTO #11226] > > Signed-off-by: Choong YinThong

Re: [OE-core] [PATCH 2/3] yocto-compat-layer: limit report of signature changes

On Fri, 2017-04-07 at 08:38 +1200, Paul Eggleton wrote: > On Thursday, 6 April 2017 1:36:05 AM NZST you wrote: > >AssertionError: False is not true : Layer meta- changed 120 > > signatures, initial differences (first hash without, second with layer): > > BTW, rather than

[OE-core] [PATCH 2/4] mkfontscale: Remove x11 requirement

Build does not need libx11, so also does not need the distro feature. Signed-off-by: Jussi Kukkonen --- meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb

[OE-core] [PATCH 0/4] Use fixed DISTRO_FEATURES for native

Avoid signifant native task churn when DISTRO_FEATURES is changed by defining a fixed DISTRO_FEATURES value (default is "") for native recipes. The xorg changes are all removals of x11 requirements (that were not real) from recipes that have native versions. I added a configuration default in

[OE-core] [PATCH 4/4] native.bbclass: Use fixed DISTRO_FEATURES

There seems to be no advantage to letting distro features affect native builds. There is a significant disadvantage: a change to DISTRO_FEATURES will trigger a lot of unnecessary native tasks. In a test like this: $ bitbake core-image-minimal # append " systemd" to DISTRO_FEATURES $ bitbake

[OE-core] [PATCH 3/4] xorg-font-common.inc: Remove x11 requirement

Remove the fake news about mkfontscale-native needing x11. Signed-off-by: Jussi Kukkonen --- meta/recipes-graphics/xorg-font/xorg-font-common.inc | 3 --- 1 file changed, 3 deletions(-) diff --git a/meta/recipes-graphics/xorg-font/xorg-font-common.inc

[OE-core] [PATCH 1/4] mkfontdir: Remove x11 requirement

Build does not need libx11, so also does not need the distro feature. Signed-off-by: Jussi Kukkonen --- meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb | 4 1 file changed, 4 insertions(+) diff --git a/meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb