Re: [OE-core] [PATCH][fido] bind: CVE-2015-1349 CVE-2015-4620 CVE-2015-5722

Hi Armin, I guess you will backport these to dizzy as well. I created Bug 8281 just to have track of recent bind vulnerabilities: CVEs, CVE-2015-1349, CVE-2015-4620, CVE-2015-5477, CVE-2015-5722, CVE-2015-5986. I think all have been addressed in master and fido, remaining are only these three

[OE-core] [PATCH] mdadm: fix CFLAGS invalid issue

From: Wenzong Fan * Pass global CFLAGS to build: The CFLAGS does not pass to build at all since it was redefined by mdadm Makefile: CFLAGS = $(CWFLAGS) $(CXFLAGS) ... This could be done by setting 'CXFLAGS="${CFLAGS}"'. * Also fix ptest build error caused by global CFLAGS: raid6check.c:

Re: [OE-core] [PATCH][v2] gcc: reformat 0063-nativesdk-gcc-support.patch

ping -Roy On 2015年08月07日 16:11, rongqing...@windriver.com wrote: From: Roy Li 0063-nativesdk-gcc-support.patch can not be applied to source code due to the buggy patch command on sled11, so reformat it, nothing is changed. Signed-off-by: Roy Li --- .../gcc/gcc-4.9/0063-nativesdk-gcc-sup

[OE-core] [PATCH V2 3/3] systemd: Implement OE-Specific systemd-sysv-install

Support for chkconfig (--enable-chkconfig) was removed in favour of calling an abstraction /lib/systemd/systemd-sysv-install. This needs to be implemented for OE. Signed-off-by: Khem Raj --- ...0012-implment-systemd-sysv-install-for-OE.patch | 40 ++ meta/recipes-core/systemd

[OE-core] [PATCH V2 2/3] systemd: Upgrade 219 -> 225

Drop patches that were straight backports from upstream MIT licence was unused and dropped from systemd sources for more details see https://github.com/systemd/systemd/commit/8f1e0c5f38cdf7e401ab4d2bb93ad816d08e7715 Drop gtkdoc dependency since libudev API documentation has been converted from g

[OE-core] [PATCH V2 1/3] rootfs: Conditionally uninstall update-rc.d

update-rc.d is now needed by systemd to interact with sysv scripts, so if we have a mixed system, then we can not uninstall update-rc.d as it is going to break systemd functionality, we check for sysvinit and sytemd in distro and also ensure that its not building an image with readonly rootfs Sign

[OE-core] [PATCH V2 0/3] Systemd Upgrade

Changes Since V1: Install update-rc.d conditionally when both systemd and sysvinit are in distro features and we are not building r/o image The following changes since commit 56c5fa106eeccda2ca92dbeb73ff01ba40992e7d: ptest: use fakeroot for do_install_ptest_base (2015-09-09 14:25:09 +0100) ar

[OE-core] opkg --install and "attempt-only" packages

So, I'm not 100% sure yet, but it appears to me that if you have a large list of "attempt-only" packages, and *any* of them can't be found at all, opkg bails out without doing anything about the rest of them. This seems a little surprising, because my assumption would be that the expected behavior

Re: [OE-core] [PATCH 2/4] rootfs: Do not uninstall update-rc.d

> On Sep 10, 2015, at 4:35 PM, Khem Raj wrote: > >> >> On Sep 10, 2015, at 8:48 AM, Richard Purdie >> wrote: >> >> On Tue, 2015-09-08 at 12:38 -0700, Khem Raj wrote: >>> On Tue, Sep 8, 2015 at 12:03 AM, Khem Raj wrote: > On Sep 7, 2015, at 2:48 PM, Phil Blundell wrote: > >>>

Re: [OE-core] [PATCH 2/4] rootfs: Do not uninstall update-rc.d

> On Sep 10, 2015, at 8:48 AM, Richard Purdie > wrote: > > On Tue, 2015-09-08 at 12:38 -0700, Khem Raj wrote: >> On Tue, Sep 8, 2015 at 12:03 AM, Khem Raj wrote: >>> On Sep 7, 2015, at 2:48 PM, Phil Blundell wrote: On Mon, 2015-09-07 at 14:15 -0700, Khem Raj wrote: >> On

Re: [OE-core] [PATCH] lttng: Fix timer calculation error

On 07/10/2015 01:33 AM, jianchuan.w...@windriver.com wrote: > --- /dev/null > +++ > b/meta/recipes-kernel/lttng/lttng-tools/lttng-tools-Fix-live-timer-calculation-error.patch > @@ -0,0 +1,42 @@ > +From 161496fbe1465817a77a50a1172734dae81a13ef Mon Sep 17 00:00:00 2001 > +From: Mikael Beckius > +Da

Re: [OE-core] [PATCH v2] selftest/manifest.py: Test support for manifests

Thanks for the notice, I'll check it up. Benjamin On Thu, 2015-09-10 at 10:52 +0100, Burton, Ross wrote: > > On 2 September 2015 at 21:18, Benjamin Esquivel < > benjamin.esqui...@linux.intel.com> wrote: > > adding support for tests to verify manifest collections > > (i.e. all the manifests found i

Re: [OE-core] [PATCH] meta: Fix Upstream-Status statements

On 10 September 2015 at 20:45, Martin Jansa wrote: > > Should have mentioned that. There are two cases from memory, where I was > > fixing a Upstream-Status by hand and looked at the git history to > identify > > who added the file. > > Don't you need their permission or confirmation before addi

Re: [OE-core] [PATCH] meta: Fix Upstream-Status statements

On Thu, Sep 10, 2015 at 08:33:38PM +0100, Burton, Ross wrote: > On 10 September 2015 at 20:33, Martin Jansa wrote: > > > There are at least 2 cases where SOB line is added, why? > > > > Should have mentioned that. There are two cases from memory, where I was > fixing a Upstream-Status by hand a

Re: [OE-core] [PATCH] webkitgtk: add a new recipe for latest upstream version

On 10 September 2015 at 19:18, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > +Upstream-status: Backport [should appear in 2.10, > http://trac.webkit.org/changeset/184856] > Capital S in Status, and missing a signed-off-by (your name in the patch header doesn't count). I've made

Re: [OE-core] [PATCH] meta: Fix Upstream-Status statements

On 10 September 2015 at 20:33, Martin Jansa wrote: > There are at least 2 cases where SOB line is added, why? > Should have mentioned that. There are two cases from memory, where I was fixing a Upstream-Status by hand and looked at the git history to identify who added the file. Ross -- _

Re: [OE-core] [PATCH] meta: Fix Upstream-Status statements

On Thu, Sep 10, 2015 at 08:10:03PM +0100, Ross Burton wrote: > Fix a variety of problems such as typos, bad punctuations, or incorrect > Upstream-Status values. There are at least 2 cases where SOB line is added, why? > Signed-off-by: Ross Burton > --- > .../files/0001-Unset-need_charset_alias-

[OE-core] [PATCH] meta: Fix Upstream-Status statements

Fix a variety of problems such as typos, bad punctuations, or incorrect Upstream-Status values. Signed-off-by: Ross Burton --- .../files/0001-Unset-need_charset_alias-when-building-for-musl.patch | 2 +- meta/recipes-bsp/hostap/hostap-utils-0.4.7/ldflags.patch | 2 +- meta/recipe

[OE-core] [PATCH] webkitgtk: add a new recipe for latest upstream version

Also, add a backported patch that prevents too long command lines from happening. Recipe for the obsolete webkit-gtk 1.8.3 is removed in a separate commit. (From OE-Core rev: 1ffa1c36f5d3d3f076840c9239c17f13f36064c3) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie --- ...fixes

Re: [OE-core] Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close)

>> And the autobuilder could automatically reject or flag a patch that adds >> custom 'Pending' patches, if the patch author is determined to be on the >> 'naughty' list :-) > > That might just alter peoples behavior and change them to use > "Submitted" and still not do anything. It does not addres

Re: [OE-core] Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close)

>> Pending means "I wrote a patch but cannot be bothered to send it >> upstream”. > > Or more politely, I am working on upstreaming it on my own schedule. Allowing "own schedule" doesn't work out in reality. Here's how many 'Pending' patches the yocto releases have: master: 712 fido: 681 dizzy:

Re: [OE-core] [PATCH v2] u-boot.inc: Add host compiler flags and openssl-native dependency

On Thu, Sep 10, 2015 at 7:24 AM, Nathan Rossi wrote: > U-Boot will compile its own tools during the build, with specific > configurations (aka when CONFIG_FIT_SIGNATURE is enabled) the host tools > require openssl. This patch adds 'openssl' as a PACKAGECONFIG that > enables the use of openssl-nati

Re: [OE-core] [PATCH] kernel-arch.bbclass: Allow 'baremetal' CPUs

No argument here. I agree that baremetal builds should be/could be streamlined. In particular, the code should support self-contained baremetal CPU specific meta layers so there would be no need to add new (baremetal) CPUs into various tables in meta/siteinfo.bbclass and meta/insane.bbclass.

Re: [OE-core] [PATCH] waf.bbclass: filter out non -j from PARALLEL_MAKE

On Thu, Sep 10, 2015 at 1:54 PM, Enrico Scholz wrote: > 'waf' supports only simple '-j' and fails when parallel make flags > contain extended options like '--load-average'. > > Patch uses the method from 'boost.inc' to filter '-j'. > > Signed-off-by: Enrico Scholz Acked-by: Otavio Salvador --

[OE-core] [PATCH][fido] wic: fix path parsing, use last occurrence

If the path contains 'scripts' more than once the first occurrence will be incorrectly used. Use rfind instead of find to find the last occurrence. Signed-off-by: George McCollister --- scripts/lib/wic/plugin.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/lib/wic/

[OE-core] [PATCH] wic: fix path parsing, use last occurrence

If the path contains 'scripts' more than once the first occurrence will be incorrectly used. Use rfind instead of find to find the last occurrence. Signed-off-by: George McCollister --- scripts/lib/wic/plugin.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/lib/wic/

[OE-core] [PATCH] waf.bbclass: filter out non -j from PARALLEL_MAKE

'waf' supports only simple '-j' and fails when parallel make flags contain extended options like '--load-average'. Patch uses the method from 'boost.inc' to filter '-j'. Signed-off-by: Enrico Scholz --- meta/classes/waf.bbclass | 24 +++- 1 file changed, 23 insertions(+), 1

[OE-core] [PATCH] license.bbclass: try copyfile() as fallback when link() fails

link() will fail with EXDEV when source and destination are on different mountpoints. Unfortunately, stat().st_dev does not identify the mountpoint so that copy_license_files() fails in bind-mount environments. E.g.: | # mkdir /tmp/a /tmp/b /tmp/X /tmp/X/a /tmp/X/b | # touch /tmp/a/foo | # moun

Re: [OE-core] Patch merge process

On Thu, Sep 10, 2015 at 12:39 PM, Martin Jansa wrote: > On Thu, Sep 10, 2015 at 06:23:07PM +0300, Alexander Kanevskiy wrote: ... >> might be. I haven't checked latest versions 2.10+, but versions below were >> not up to the shape compared to e.g. pull-request workflow in GitHub. > > GitHub's pull-

Re: [OE-core] [RFC][dizzy][fido][master][PATCH 1/3] rootfs.py: Allow to override postinst-intercepts location

All 3 in master so backporting to Dizzy. - armin On 09/04/2015 05:27 AM, Martin Jansa wrote: > On Fri, Sep 04, 2015 at 02:22:26PM +0200, Martin Jansa wrote: >> * useful when we need to overlay/extend intercept scripts from oe-core > > 2/3 and 3/3 could be a bit dangerous or controversial (main r

Re: [OE-core] Robert Yang : perf: fix for rebuilding

On Wed, Sep 02, 2015 at 06:00:35PM +0200, Martin Jansa wrote: > I'm still seeing issues when perf is rebuilt > > The original issue was: > OSError: [Errno 2] No such file or directory: > 'BUILD/work/qemux86-webos-linux/perf/1.0-r9/perf-1.0' > > as described here: > http://patches.openembedded.or

[OE-core] [PATCH v2] distutils.bbclass: Handle python-backport modules

When installing backport modules they stumble upon each other, complaining with the following error: ERROR: The recipe python-backports-ssl is trying to install files into a shared area when those files already exist. This is the correct behavior since thats just the way they were designed, all

Re: [OE-core] [PATCH 2/4] rootfs: Do not uninstall update-rc.d

On Tue, 2015-09-08 at 12:38 -0700, Khem Raj wrote: > On Tue, Sep 8, 2015 at 12:03 AM, Khem Raj wrote: > > > >> On Sep 7, 2015, at 2:48 PM, Phil Blundell wrote: > >> > >> On Mon, 2015-09-07 at 14:15 -0700, Khem Raj wrote: > On Sep 7, 2015, at 12:36 PM, Phil Blundell wrote: > > On S

Re: [OE-core] Patch merge process

On Thu, Sep 10, 2015 at 06:23:07PM +0300, Alexander Kanevskiy wrote: > On Thu, Sep 10, 2015 at 5:18 PM, Martin Jansa > wrote: > > > On Thu, Sep 10, 2015 at 05:03:25PM +0300, Alexander Kanevskiy wrote: > > > On Wed, Sep 9, 2015 at 12:06 AM, Martin Jansa > > > wrote: > > > Gerrit, despite its good

Re: [OE-core] Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close)

On 09/10/2015 05:08 AM, Alexander Kanavin wrote: > On 09/10/2015 02:50 PM, Trevor Woerner wrote: > >>> Then we can formulate a policy on top of that: for example, if a patch >>> has been 'Pending' for 3 months, the person who added it gets a >>> reminder to update the status; if the patch has be

Re: [OE-core] Patch merge process

On Thu, Sep 10, 2015 at 5:18 PM, Martin Jansa wrote: > On Thu, Sep 10, 2015 at 05:03:25PM +0300, Alexander Kanevskiy wrote: > > On Wed, Sep 9, 2015 at 12:06 AM, Martin Jansa > > wrote: > > Gerrit, despite its good ability to integrate into existing > infrastructures > > might be not the best sol

Re: [OE-core] Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close)

> On Sep 10, 2015, at 5:12 AM, Burton, Ross wrote: > > > On 10 September 2015 at 13:12, Gary Thomas > wrote: > What would you do to the poor sod that sends a patch upstream > (i.e. Pending) that is not being moved on by the upstream holders? > Punish him by making his

[OE-core] [PATCHv2] fontcache: allow to pass extra parameters and environment to fc-cache

* this can be useful for passing extra parameters, pass -v by default to see what's going on in do_rootfs * we need to use this for extra parameter we implemented in fontconfig: --ignore-mtime always use cache file regardless of font directory mtime because the checksum of fontcache generat

[OE-core] [wic][PATCH 1/3] wic: add dependencies to wic-image-minimal recipe

Added "DEPENDS =" line to the recipe to ensure that all tools required for image creation are built. Signed-off-by: Ed Bartosh --- meta-selftest/recipes-test/images/wic-image-minimal.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-selftest/recipes-test/images/wic-image-minimal.bb

[OE-core] [wic][PATCH 3/3] wic: fix partition size calculation

It was wrongly assumed that part.size is meagured in Mb. In fact it's in Kb, so there is no need to convert bitbake variable ROOTFS_SIZE as it's also in Kb. Signed-off-by: Ed Bartosh --- scripts/lib/wic/imager/direct.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/script

[OE-core] [wic][PATCH 2/3] wic: use ext4 in wic-image-minimal.wks

ext4 is used in canned wks files, so let's use it here too for the sake of consistency. Signed-off-by: Ed Bartosh --- meta-selftest/recipes-test/images/wic-image-minimal.wks | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/meta-selftest/recipes-test/images/wic-image-mini

[OE-core] [wic][PATCH 0/3] wic bugfix and improvements

Hi, This patchset contains a changes suggested by QA team. Daniel, thank you for suggestions! The following changes since commit d4585fa23d56a58c583ee33db067a23177a936b1: bsps: update 3.14 SRCREVs (2015-09-09 14:27:57 +0100) are available in the git repository at: git://git.yoctoproject.or

Re: [OE-core] Patch merge process

On Thu, Sep 10, 2015 at 05:03:25PM +0300, Alexander Kanevskiy wrote: > On Wed, Sep 9, 2015 at 12:06 AM, Martin Jansa > wrote: > > > On Tue, Sep 08, 2015 at 11:39:17AM -0700, Khem Raj wrote: > > > On Tue, Sep 8, 2015 at 11:18 AM, Trevor Woerner > > wrote: > > > > If Richard doesn't want to use ge

Re: [OE-core] Patch merge process

On Wed, Sep 9, 2015 at 12:06 AM, Martin Jansa wrote: > On Tue, Sep 08, 2015 at 11:39:17AM -0700, Khem Raj wrote: > > On Tue, Sep 8, 2015 at 11:18 AM, Trevor Woerner > wrote: > > > If Richard doesn't want to use gerrit for OE-core, that doesn't exclude > > > others from using it for the layers th

Re: [OE-core] Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close)

On 2015-09-10 06:12, Burton, Ross wrote: On 10 September 2015 at 13:12, Gary Thomas mailto:g...@mlbassoc.com>> wrote: What would you do to the poor sod that sends a patch upstream (i.e. Pending) that is not being moved on by the upstream holders? Punish him by making his patch (and

Re: [OE-core] Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close)

On 10 September 2015 at 13:12, Gary Thomas wrote: > What would you do to the poor sod that sends a patch upstream > (i.e. Pending) that is not being moved on by the upstream holders? > Punish him by making his patch (and potentially all others he > has created) invalid? Seems a bit harsh... > S

Re: [OE-core] Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close)

On 2015-09-10 06:08, Alexander Kanavin wrote: On 09/10/2015 02:50 PM, Trevor Woerner wrote: Then we can formulate a policy on top of that: for example, if a patch has been 'Pending' for 3 months, the person who added it gets a reminder to update the status; if the patch has been 'Pending' for 6

[OE-core] Policy for 'Pending' patches (was Re: [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close)

On 09/10/2015 02:50 PM, Trevor Woerner wrote: Then we can formulate a policy on top of that: for example, if a patch has been 'Pending' for 3 months, the person who added it gets a reminder to update the status; if the patch has been 'Pending' for 6 months and the patch person has been unrespons

Re: [OE-core] [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close

On 10 September 2015 at 12:50, Trevor Woerner wrote: > With so many maintainers on so many different layers/etc we would need > some sort of billboard somewhere listing the names of people currently > on the "naughty" list ;-) > I prefer the concept of a naughty list to blanket rejecting... and

[OE-core] [fido][PATCH 1/3] rootfs.py: Allow to override postinst-intercepts location

* useful when we need to overlay/extend intercept scripts from oe-core Signed-off-by: Martin Jansa --- meta/lib/oe/rootfs.py | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py index e86480c..d2de2c6 100644 --- a/meta/lib/oe/roo

[OE-core] [fido][PATCH 2/3] rootfs.py: show intercept script output in log.do_rootfs

* without this the output wasn't shown anywhere even when the bb.warn says: "See log for details!" Signed-off-by: Martin Jansa --- meta/lib/oe/rootfs.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py index d2de2c6..15ad642 10

[OE-core] [fido][PATCH 3/3] postinst_intercept: allow to pass variables with spaces

* trying to pass foo="a b" through postinst_intercept ends with the actual script header to containing: b foo=a which fails because "b" command doesn't exist. Signed-off-by: Martin Jansa --- scripts/postinst-intercepts/postinst_intercept | 2 +- 1 file changed, 1 insertion(+), 1 deletion

[OE-core] [dizzy][PATCH 2/3] rootfs.py: show intercept script output in log.do_rootfs

From: Martin Jansa * without this the output wasn't shown anywhere even when the bb.warn says: "See log for details!" Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie --- meta/lib/oe/rootfs.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oe/rootfs.

[OE-core] [dizzy][PATCH 1/3] rootfs.py: Allow to override postinst-intercepts location

From: Martin Jansa * useful when we need to overlay/extend intercept scripts from oe-core Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie --- meta/lib/oe/rootfs.py | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py

[OE-core] [dizzy][PATCH 3/3] postinst_intercept: allow to pass variables with spaces

From: Martin Jansa * trying to pass foo="a b" through postinst_intercept ends with the actual script header to containing: b foo=a which fails because "b" command doesn't exist. Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie --- scripts/postinst-intercepts/postinst_intercep

Re: [OE-core] [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close

On 09/10/15 07:21, Alexander Kanavin wrote: > On 09/09/2015 07:02 PM, Khem Raj wrote: > >> So I encourage you to formulate a policy and make a proposal to >> community and get everyone on board in changing >> the policy OE wide. > > > Actually, first we need some kind of tool that keeps track of cu

Re: [OE-core] [PATCH 02/16] slang: Fix namespace conflict vis-a-vis posix_close

On 09/09/2015 07:02 PM, Khem Raj wrote: So I encourage you to formulate a policy and make a proposal to community and get everyone on board in changing the policy OE wide. Actually, first we need some kind of tool that keeps track of custom patches and their upstream-statuses and minimizes

[OE-core] [PATCH v2] u-boot.inc: Add host compiler flags and openssl-native dependency

U-Boot will compile its own tools during the build, with specific configurations (aka when CONFIG_FIT_SIGNATURE is enabled) the host tools require openssl. This patch adds 'openssl' as a PACKAGECONFIG that enables the use of openssl-native as a dependency and also adds the HOSTCC flags that U-Boot

Re: [OE-core] [PATCH 0/1] sstate.bbclass: fixes for SSTATE_SIG_KEY when use SSTATE_MIRRORS

On 09/10/2015 06:14 PM, Burton, Ross wrote: I sent an almost identical patch to this yesterday :) Thanks, please drop this one, something is wrong with my thunderbird's searching, I had searched before I worked on it, but didn't find the patch, I searched it again just now, and did find it. (

Re: [OE-core] [PATCH 0/1] sstate.bbclass: fixes for SSTATE_SIG_KEY when use SSTATE_MIRRORS

I sent an almost identical patch to this yesterday :) (your patch breaks is SSTATE_VERIFY_KEY="0") Ross On 10 September 2015 at 11:04, Robert Yang wrote: > The following changes since commit > 56c5fa106eeccda2ca92dbeb73ff01ba40992e7d: > > ptest: use fakeroot for do_install_ptest_base (2015-0

[OE-core] [PATCH 0/1] sstate.bbclass: fixes for SSTATE_SIG_KEY when use SSTATE_MIRRORS

The following changes since commit 56c5fa106eeccda2ca92dbeb73ff01ba40992e7d: ptest: use fakeroot for do_install_ptest_base (2015-09-09 14:25:09 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/ss http://cgit.openembedded.org/cgit.cgi/o

[OE-core] [PATCH 1/1] sstate.bbclass: fixes for SSTATE_SIG_KEY when use SSTATE_MIRRORS

Fixed: WARNING: Failed to fetch URL file://Ubuntu-12.04/39/sstate:m4-native:x86_64-linux:1.4.17:r0:x86_64:3:39ecb836d5fc7802ce6f45f33f1cae36_populate_sysroot.tgz.sig, attempting MIRRORS if available ERROR: Fetcher failure: Unable to find file file://Ubuntu-12.04/39/sstate:m4-native:x86_64-linux:

Re: [OE-core] [PATCH v2] selftest/manifest.py: Test support for manifests

On 2 September 2015 at 21:18, Benjamin Esquivel < benjamin.esqui...@linux.intel.com> wrote: > adding support for tests to verify manifest collections > (i.e. all the manifests found in a given dir) checking them > to provide entries that exist in an specified pkgdata dir > > tests added: > -addin

Re: [OE-core] [PATCH] u-boot.inc: Add host compiler flags and openssl-native dependency

On Thu, 2015-09-10 at 16:57 +1000, Nathan Rossi wrote: > I think the best solution that would cover your request but also not > add any potential confusion for users, would be to have the > PACKAGECONFIG for u-boot but default to having the config enabled. And > for users who want to completely rem