[OE-core] Failed to boot core-image-minimal-qemux86-64.cpio.gz

Does anyone know the reason, please ? $ runqemu nographic tmp/deploy/images/qemux86-64 core-image-minimal cpio.gz [6.375829] ALSA device list: [6.375990] No soundcards found. [6.429357] Freeing unused kernel memory: 1376K (81f1f000 - 82077000) [6.429708] Write

Re: [OE-core] [PATCH 20/24] libiconv: remove recipe

On 02/24/2017 01:04 AM, Burton, Ross wrote: > ERROR: Nothing PROVIDES 'virtual/nativesdk-libiconv' (but > virtual:nativesdk:/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-qa-extras/build/meta/recipes-core/gettext/gettext_0.19.8.1.bb > DEPENDS

[OE-core] [PATCH] webkitgtk: update to 2.14.5

Remove a reference to WebKit/LICENSE, as the directory is not there anymore (and the LICENSE file in it hasn't been moved somewhere else) - it was a relic of webkit 1.x era. Signed-off-by: Alexander Kanavin --- .../recipes-sato/webkit/{webkitgtk_2.14.2.bb => webkitgtk_2.14.5.bb} | 5 ++--- 1 fil

[OE-core] [PATCH] tar: CVE-2016-6321

Skip members whose names contain "..". Reference: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6321 Upstream patch: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=7340f67b9860ea0531c1450e5aa261c50f671 Signed-off-by: Sona Sarmadi --- meta/recipes-extended/tar/tar/CVE-2016-6321.p

Re: [OE-core] [PATCH] deprecated.bbclass: Add a PNDEPRECATED variable for recipes

> If nobody speaks up within some amount of time the maintainer considers reasonable (I'm thinking a Yocto release cycle) then it's fair game to remove the recipe in question. Maybe this is different case with at least some PNBLACKLIST entries we currently have, but I don't remove PNBLACKLISTed re

[OE-core] [RFC PATCH 1/1] core-image-minimal-initramfs: set QB_DEFAULT_FSTYPE

Fixed: MACHINE = "qemux86" $ bitbake core-image-minimal-initramfs $ runqemu qemux86 nographic [snip] Exception: Failed to find rootfs: tmp/deploy/images/qemux86/core-image-minimal-initramfs-qemux86-20170224082533*.ext4 or tmp/deploy/images/qemux86/core-image-minimal-initramfs-qemux86*.ext4 [snip]

[OE-core] [RFC PATCH 0/1] core-image-minimal-initramfs: set QB_DEFAULT_FSTYPE

Hi, This is a RFC patch, my concern is that QB_DEFAULT_FSTYPE is only used for qemu boot, it is harmless for non qemu machines, so I assume that it is OK to set it in the image recipe. There are also other image recipes have the similar issues: WARNING: meta/recipes-core/images/core-image-minimal

Re: [OE-core] [PATCH 0/5] Packages upgrade

Mike Crowe has done the upgrade for ccache, so I removed it from the PULL: The following changes since commit 65cfc8aca3ff7e39453977a0215a350d13cb85ef: libva: Find the correct wayland-scanner (2017-02-23 12:29:21 -0800) are available in the git repository at: git://git.openembedded.org/op

[OE-core] [PATCH] buildstats.bbclass: Avoid index exception in /proc/PID/io parsing

From: Pavel Modilaynen There is some probability (depends on system load) to get empty or line containing "0" as the last line while reading /proc/PID/io. Avoid build failure by checking if line contains separator ":" before split. Signed-off-by: Pavel Modilaynen Signed-off-by: Daniel Lublin -

[OE-core] Yocto Bug#10456 discuss

Hi Jussi and bruce Yocto Bug#10456: X can not launch on qemumips64 I find the kernel 4.4 is ok, and on the latest 4.9 is ok, but on kernel 4.8 is failed. This is because this commit in linux-yocto-4.8: ~~ commit d03516df837587368fc6e75591f6329c072

[OE-core] [PATCH] guile: fix a bashism

From: Ming Liu A following flaw was detected by verify-bashisms script: .. meta/recipes-devtools/guile/guile_2.0.13.bb possible bashism in guile_cross_config line 94 ($'...' should be "$(printf '...')"): echo '#!'`which ${BUILD_SYS}-guile`$' \\\n--no-auto-compile -e main -s\n!#\n(define

[OE-core] [PATCHv2] tar: CVE-2016-6321

Skip members whose names contain "..". Reference: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6321 Upstream patch: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=7340f67b9860ea0531c1450e5aa261c50f671 Signed-off-by: Sona Sarmadi --- meta/recipes-extended/tar/tar/CVE-2016-6321.p

Re: [OE-core] Patchwork not picking changes from the ML

On Wed, 2017-02-22 at 15:56 -0600, Jose Lamego wrote: > > On 02/22/2017 02:55 PM, Michael Halstead wrote: > > I've seen several issues with hooks. I was working on them yesterday and > > will continue today. > > > > These are currently managed by hand but we are moving them into > > configuration

Re: [OE-core] [PATCH 24/24] systemtap: update to 3.1

On 22 February 2017 at 14:51, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > > Add support for python 3 probes ERROR: QA Issue: lib64-systemtap: Files/directories were installed but not shipped in any package: /usr/lib/python3.5/site-packages/HelperSDT-0.1.0-py3.5.egg-info /usr

Re: [OE-core] Yocto Bug#10456 discuss

On 2017-02-24 5:33 AM, Dengke Du wrote: Hi Jussi and bruce Yocto Bug#10456: X can not launch on qemumips64 I find the kernel 4.4 is ok, and on the latest 4.9 is ok, but on kernel 4.8 is failed. This is because this commit in linux-yocto-4.8: ~~ com

Re: [OE-core] Patchwork not picking changes from the ML

On 2017-02-24 15:21, Patrick Ohly wrote: On Wed, 2017-02-22 at 15:56 -0600, Jose Lamego wrote: On 02/22/2017 02:55 PM, Michael Halstead wrote: I've seen several issues with hooks. I was working on them yesterday and will continue today. These are currently managed by hand but we are moving th

[OE-core] [PATCH v2] oeqa/sdk/cases:Adds validation for SDK compatibility tests

Added validation for SDK compatibility tests with eSDK. buildcvs, buildiptables, gcc, perl, python and buildgalculator based on target manifest file. Running with: $ bitbake -c testsdkext [YOCTO #9090] Signed-off-by: Francisco Pedraza --- meta/lib/oeqa/sdk/cases/buildcvs.py| 8

[OE-core] [PATCH v2] deprecated.bbclass: Add a PNDEPRECATED variable for recipes

Based on the blacklist behaviour, recipes can be tagged as deprecated. Such recipes will produce a warning message when included in a build but unlike blacklisted recipes, the build will continue. Signed-off-by: Joe MacDonald --- documentation/ref-manual/ref-classes.xml | 28 ++

[OE-core] [PATCH] python3-pip: RDEPEND on python3-html.

Without this pip3 fails with "ImportError: No module named 'html'" Signed-off-by: Ismo Puustinen --- meta/recipes-devtools/python/python3-pip_9.0.1.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/python/python3-pip_9.0.1.bb b/meta/recipes-devtools/python/python3-pip

[OE-core] [PATCH] ell: Initial recipe for Embedded Linux Library

Based on the ofono recipe, add ell.inc for generic recipe components and use it from ell_git.bb. Signed-off-by: Ankit Navik --- meta/recipes-core/ell/ell.inc| 10 ++ meta/recipes-core/ell/ell_git.bb | 9 + 2 files changed, 19 insertions(+) create mode 100644 meta/recipes-co

Re: [OE-core] [PATCH 24/24] systemtap: update to 3.1

On 02/24/2017 04:22 PM, Burton, Ross wrote: Add support for python 3 probes ERROR: QA Issue: lib64-systemtap: Files/directories were installed but not shipped in any package: /usr/lib/python3.5/site-packages/HelperSDT-0.1.0-py3.5.egg-info /usr/lib/python3.5/site-packages/HelperSDT-0.1.0-py3.

[OE-core] [PATCH] systemtap: update to 3.1

Removed patches are in upstream. Rebase monitor-option.patch and no-msgfmt-check.patch Add support for python 3 probes (this necessitates the 0001-Do-not-let-configure-write-a-python-location-into-th.patch and the Add 0001-Install-python-modules-to-correct-library-dir.patch to install python mod

[OE-core] [PATCH 1/2] iproute2: upgrade to 4.10.0

4.9.0 -> 4.10.0 added the following patch to fix build with musl libc 1) 0001-libc-compat.h-add-musl-workaround.patch Signed-off-by: Maxin B. John --- .../0001-libc-compat.h-add-musl-workaround.patch | 41 +++ .../iproute2/iproute2/iproute2-4.9.0-musl.patch| 131

[OE-core] [PATCH 2/2] gstreamer: update to 1.10.4

bug-fix release: *) Various fixes for crashes, assertions, deadlocks and memory leaks on fuzzed input files and in other situations (CVE-2017-5847, CVE-2017-5848) *) gst-libav was updated to ffmpeg 3.2.4, fixing a couple of CVEs Signed-off-by: Maxin B. John --- .../{gstreamer1.0-libav_1.10.3.b

[OE-core] [PATCH v3] oeqa/sdk/cases:Adds validation for SDK compatibility tests

Added validation for SDK compatibility tests with eSDK. buildcvs, buildiptables, gcc, perl, python and buildgalculator based on target manifest file.Running with: $ bitbake -c testsdkext [YOCTO #9090] Signed-off-by: Francisco Pedraza --- meta/lib/oeqa/sdk/cases/buildcvs.py| 5 - me

Re: [OE-core] Patchwork not picking changes from the ML

On Fri, 2017-02-24 at 15:33 +0100, Gary Thomas wrote: > On 2017-02-24 15:21, Patrick Ohly wrote: > > On Wed, 2017-02-22 at 15:56 -0600, Jose Lamego wrote: > >> > >> On 02/22/2017 02:55 PM, Michael Halstead wrote: > >>> I've seen several issues with hooks. I was working on them yesterday and > >>> w

Re: [OE-core] Patchwork not picking changes from the ML

On 24 February 2017 at 16:27, Patrick Ohly wrote: > Let me clarify that my original proposal was to reply only to the > original author. That was meant to keep noise down on the list. However, > perhaps it should also go to the list? > > Then others can help check that Patchwork works, as the ori

Re: [OE-core] Patchwork not picking changes from the ML

On 02/24/2017 10:27 AM, Patrick Ohly wrote: > On Fri, 2017-02-24 at 15:33 +0100, Gary Thomas wrote: >> On 2017-02-24 15:21, Patrick Ohly wrote: >>> On Wed, 2017-02-22 at 15:56 -0600, Jose Lamego wrote: On 02/22/2017 02:55 PM, Michael Halstead wrote: > I've seen several issues with ho

Re: [OE-core] [PATCH] ell: Initial recipe for Embedded Linux Library

On 24 February 2017 at 16:00, Ankit Navik wrote: > meta/recipes-core/ell/ell.inc| 10 ++ > meta/recipes-core/ell/ell_git.bb | 9 + > Unless you have other recipes using the .inc file, then just merge these into a single .bb. > +DEPENDS = "dbus" > +RDEPENDS_${PN} += "dbus"

Re: [OE-core] [PATCH v2 1/1] kernel.bbclass: Make sanity check opt-out and provide easy opt-out

On 02/23/2017 04:13 PM, Cal Sullivan wrote: On 02/23/2017 03:27 PM, Cal Sullivan wrote: On 02/23/2017 03:07 PM, Burton, Ross wrote: On 23 February 2017 at 22:32, California Sullivan > wrote: The only change from V1 to V2 is the updated commit

[OE-core] [PATCH] ell: Initial recipe for Embedded Linux Library

Add generic recipe for ELL. Signed-off-by: Ankit Navik --- meta/recipes-core/ell/ell_git.bb | 17 + 1 file changed, 17 insertions(+) create mode 100644 meta/recipes-core/ell/ell_git.bb diff --git a/meta/recipes-core/ell/ell_git.bb b/meta/recipes-core/ell/ell_git.bb new file mod

Re: [OE-core] [PATCH] deprecated.bbclass: Add a PNDEPRECATED variable for recipes

On 02/24/2017 01:16 AM, Martin Jansa wrote: >> If nobody speaks up within some > amount of time the maintainer considers reasonable (I'm thinking a Yocto > release > cycle) then it's fair game to remove the recipe in question. > > Maybe this is different case with at least some PNBLACKLIST entries

Re: [OE-core] [PATCH] ell: Initial recipe for Embedded Linux Library

On 24 February 2017 at 18:42, Ankit Navik wrote: > Add generic recipe for ELL. > This doesn't answer the question of "why?". Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/lis

Re: [OE-core] [PATCH] deprecated.bbclass: Add a PNDEPRECATED variable for recipes

OK, should I update all currently PNBLACKLISTed recipes to add " - the recipe will be removed on 2017-09-01 unless the issue is fixed" in the PNBLACKLIST value, so that we can delete all blacklisted recipes before 2.4 release? On Fri, Feb 24, 2017 at 9:39 PM, Philip Balister wrote: > On 02/24/20

[OE-core] [PATCH] Revert "flex: upgrade to 2.6.2"

This reverts commit 3632abd01abb8dfff230e18f828af705da488f97. The commit upgraded flex and changed the way it was constructed. There is a problem with either the upgrade or changes in construction mechanism resulting in problems similar to: ../cil/src/cil_lexer.lo: In function `cil_lexer_setup':

Re: [OE-core] [PATCH] Revert "flex: upgrade to 2.6.2"

This was already sent to ML 2 weeks ago: http://lists.openembedded.org/pipermail/openembedded-core/2017-February/132584.html discussed few times since it was upgraded and I was pinging Ross about it few days ago as well, hopefully it will be included before pyro is branched. On Fri, Feb 24, 2017

Re: [OE-core] [PATCH] Revert "flex: upgrade to 2.6.2"

On 24 February 2017 at 20:54, Martin Jansa wrote: > and I was pinging Ross about it few days ago as well, hopefully it will be > included before pyro is branched. > It's in the current MUT, don't worry! :) Ross -- ___ Openembedded-core mailing list O

[OE-core] [PATCH 1/1] oelib/buildhistory.py: Add unittest for buildhistory_analysis

The buildhistory_analysis module (in which buildhistory-diff is based) was lacking unittest for its functions. Created selftest module for this and a few testcases to cover basic cases. [YOCTO #10727] Signed-off-by: Humberto Ibarra --- meta/lib/oeqa/selftest/oelib/buildhistory.py | 88 +

Re: [OE-core] [PATCH] wic: Prevent duplicate entries on fstab

On 23 February 2017 at 18:13, Fabio Berton wrote: > > Add function to read fstab and return all mount points. This function > is useful to _update_fstab doesn't duplicate entries in /etc/fstab. The AB just failed all over with this error message: | Traceback (most recent call last): | File "/

Re: [OE-core] Yocto Bug#10456 discuss

OK, thanks, I will send patch to revert it in Morty. Dengke 在 02/24/2017 10:24 PM, Bruce Ashfield 写道: On 2017-02-24 5:33 AM, Dengke Du wrote: Hi Jussi and bruce Yocto Bug#10456: X can not launch on qemumips64 I find the kernel 4.4 is ok, and on the latest 4.9 is ok, but on kernel 4.8 is faile

Re: [OE-core] Patchwork not picking changes from the ML

On 2017-02-24 17:46, Burton, Ross wrote: On 24 February 2017 at 16:27, Patrick Ohly mailto:patrick.o...@intel.com>> wrote: Let me clarify that my original proposal was to reply only to the original author. That was meant to keep noise down on the list. However, perhaps it should als