[OE-core] ✗ patchtest: failure for f2fs-tools: Update to Version 1.8.0

[Patchwork]

== Series Details ==

Series: f2fs-tools: Update to Version 1.8.0
Revision: 1
URL   : https://patchwork.openembedded.org/series/6013/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
 (possible values: Pending, Submitted, Accepted, Backport, Denied, 
Inappropriate)

* Issue Series does not apply on top of target branch 
[test_series_merge_on_head] 
  Suggested fixRebase your series on top of targeted branch
  Targeted branch  master (currently at 9c948d3de0)

* Issue Series sent to the wrong mailing list 
[test_target_mailing_list] 
  Suggested fixSend the series again to the correct mailing list (ML)
  Suggested ML openembedded-de...@lists.openembedded.org 
[http://git.openembedded.org/meta-openembedded/]



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] f2fs-tools: Update to Version 1.8.0

[Yong, Jonathan]

Signed-off-by: Yong, Jonathan 
---
 .../0002-Fix-mkfs-out-of-tree-builds.patch | 27 ++
 .../{f2fs-tools_1.4.0.bb => f2fs-tools_1.8.0.bb}   |  5 ++--
 2 files changed, 30 insertions(+), 2 deletions(-)
 create mode 100644 
meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
 rename meta-filesystems/recipes-utils/f2fs-tools/{f2fs-tools_1.4.0.bb => 
f2fs-tools_1.8.0.bb} (81%)

diff --git 
a/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
 
b/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
new file mode 100644
index 000..3aadf3c
--- /dev/null
+++ 
b/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
@@ -0,0 +1,27 @@
+From 1d4f6b6a945eabb364a2035d5ef0b69f68a87f74 Mon Sep 17 00:00:00 2001
+From: "Yong, Jonathan" 
+Date: Mon, 27 Mar 2017 08:34:06 +
+Subject: [PATCH] Fix mkfs out of tree builds
+
+Libraries are built in builddir, not srcdir, fix Makefile.am
+accordingly.
+
+Signed-off-by: Yong, Jonathan 
+---
+ mkfs/Makefile.am | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/mkfs/Makefile.am b/mkfs/Makefile.am
+index 8b4c16c..ae211b2 100644
+--- a/mkfs/Makefile.am
 b/mkfs/Makefile.am
+@@ -10,5 +10,5 @@ lib_LTLIBRARIES = libf2fs_format.la
+ libf2fs_format_la_SOURCES = f2fs_format_main.c f2fs_format.c 
f2fs_format_utils.c
+ libf2fs_format_la_CFLAGS = -DWITH_BLKDISCARD
+ libf2fs_format_la_CPPFLAGS = -I$(top_srcdir)/include
+-libf2fs_format_la_LDFLAGS = -luuid -L$(top_srcdir)/lib -lf2fs \
++libf2fs_format_la_LDFLAGS = -luuid -L$(top_builddir)/lib -lf2fs \
+   -version-info $(FMT_CURRENT):$(FMT_REVISION):$(FMT_AGE)
+-- 
+2.10.2
+
diff --git a/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.4.0.bb 
b/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.8.0.bb
similarity index 81%
rename from meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.4.0.bb
rename to meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.8.0.bb
index 1a558e7..691cb6e 100644
--- a/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.4.0.bb
+++ b/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.8.0.bb
@@ -7,9 +7,10 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=362b4b2594cd362b874a97718faa51d3"
 # to provide libuuid
 DEPENDS = "util-linux"
 
-SRCREV = "baac4b4e6f41ceb02511da49dd3707674f3fea21"
+SRCREV = "1e7aedf99b85d16f94d1d8ad2fcf846403bb2174"
 SRC_URI = 
"git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git \
-file://0001-Remove-AC_CHECK_FILE-for-cross-compilation.patch"
+file://0001-Remove-AC_CHECK_FILE-for-cross-compilation.patch \
+file://0002-Fix-mkfs-out-of-tree-builds.patch"
 S = "${WORKDIR}/git"
 
 inherit pkgconfig autotools
-- 
2.10.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] f2f2-tools 1.4.0 -> 1.8.0

[Yong, Jonathan]

Upgrade f2fs-tools, now supports encryption.

Yong, Jonathan (1):
  f2fs-tools: Update to Version 1.8.0

 .../0002-Fix-mkfs-out-of-tree-builds.patch | 27 ++
 .../{f2fs-tools_1.4.0.bb => f2fs-tools_1.8.0.bb}   |  5 ++--
 2 files changed, 30 insertions(+), 2 deletions(-)
 create mode 100644 
meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
 rename meta-filesystems/recipes-utils/f2fs-tools/{f2fs-tools_1.4.0.bb => 
f2fs-tools_1.8.0.bb} (81%)

-- 
2.10.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] f2fs-tools: Update to Version 1.8.0

[Yong, Jonathan]

Signed-off-by: Yong, Jonathan 
---
 .../0002-Fix-mkfs-out-of-tree-builds.patch | 27 ++
 .../{f2fs-tools_1.4.0.bb => f2fs-tools_1.8.0.bb}   |  5 ++--
 2 files changed, 30 insertions(+), 2 deletions(-)
 create mode 100644 
meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
 rename meta-filesystems/recipes-utils/f2fs-tools/{f2fs-tools_1.4.0.bb => 
f2fs-tools_1.8.0.bb} (81%)

diff --git 
a/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
 
b/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
new file mode 100644
index 000..3aadf3c
--- /dev/null
+++ 
b/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools/0002-Fix-mkfs-out-of-tree-builds.patch
@@ -0,0 +1,27 @@
+From 1d4f6b6a945eabb364a2035d5ef0b69f68a87f74 Mon Sep 17 00:00:00 2001
+From: "Yong, Jonathan" 
+Date: Mon, 27 Mar 2017 08:34:06 +
+Subject: [PATCH] Fix mkfs out of tree builds
+
+Libraries are built in builddir, not srcdir, fix Makefile.am
+accordingly.
+
+Signed-off-by: Yong, Jonathan 
+---
+ mkfs/Makefile.am | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/mkfs/Makefile.am b/mkfs/Makefile.am
+index 8b4c16c..ae211b2 100644
+--- a/mkfs/Makefile.am
 b/mkfs/Makefile.am
+@@ -10,5 +10,5 @@ lib_LTLIBRARIES = libf2fs_format.la
+ libf2fs_format_la_SOURCES = f2fs_format_main.c f2fs_format.c 
f2fs_format_utils.c
+ libf2fs_format_la_CFLAGS = -DWITH_BLKDISCARD
+ libf2fs_format_la_CPPFLAGS = -I$(top_srcdir)/include
+-libf2fs_format_la_LDFLAGS = -luuid -L$(top_srcdir)/lib -lf2fs \
++libf2fs_format_la_LDFLAGS = -luuid -L$(top_builddir)/lib -lf2fs \
+   -version-info $(FMT_CURRENT):$(FMT_REVISION):$(FMT_AGE)
+-- 
+2.10.2
+
diff --git a/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.4.0.bb 
b/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.8.0.bb
similarity index 81%
rename from meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.4.0.bb
rename to meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.8.0.bb
index 1a558e7..691cb6e 100644
--- a/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.4.0.bb
+++ b/meta-filesystems/recipes-utils/f2fs-tools/f2fs-tools_1.8.0.bb
@@ -7,9 +7,10 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=362b4b2594cd362b874a97718faa51d3"
 # to provide libuuid
 DEPENDS = "util-linux"
 
-SRCREV = "baac4b4e6f41ceb02511da49dd3707674f3fea21"
+SRCREV = "1e7aedf99b85d16f94d1d8ad2fcf846403bb2174"
 SRC_URI = 
"git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git \
-file://0001-Remove-AC_CHECK_FILE-for-cross-compilation.patch"
+file://0001-Remove-AC_CHECK_FILE-for-cross-compilation.patch \
+file://0002-Fix-mkfs-out-of-tree-builds.patch"
 S = "${WORKDIR}/git"
 
 inherit pkgconfig autotools
-- 
2.10.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] bitbake.conf: sort HOSTTOOLS and remove duplicates

[Andre McCurdy]

Cleanup only, no functional changes.

Signed-off-by: Andre McCurdy 
---
 meta/conf/bitbake.conf | 20 ++--
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index fa5445b..96a9ed9 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -455,21 +455,21 @@ export PATH
 
 # Tools needed to run builds with OE-Core
 HOSTTOOLS += " \
-bash sh cut sed gcc ld git rm install which find xargs cat true mktemp \
-grep tar gzip touch cp mv basename dirname tr getopt sort awk head tail \
-mkdir patch uniq perl python chmod python3 ar strip expr ls make as \
-ranlib egrep echo chown cpio tee wc wget bzip2 stat date rmdir od diff \
-md5sum dd chrpath file pod2man gunzip python2.7 ln g++ [ false true \
-uname test hostname nm objdump objcopy cmp printf env readlink gawk fgrep \
-expand pwd sleep diffstat chgrp flock ldd strings rpcgen du makeinfo \
-getconf mknod cpp readelf split \
+[ ar as awk basename bash bzip2 cat chgrp chmod chown chrpath cmp cp cpio \
+cpp cut date dd diff diffstat dirname du echo egrep env expand expr false \
+fgrep file find flock g++ gawk gcc getconf getopt git grep gunzip gzip \
+head hostname install ld ldd ln ls make makeinfo md5sum mkdir mknod \
+mktemp mv nm objcopy objdump od patch perl pod2man printf pwd python \
+python2.7 python3 ranlib readelf readlink rm rmdir rpcgen sed sh sleep \
+sort split stat strings strip tail tar tee test touch tr true uname uniq \
+wc wget which xargs \
 "
 
 # Tools needed to run testimage runtime image testing
-HOSTTOOLS += "ps stty ip ssh scp ping"
+HOSTTOOLS += "ip ping ps scp ssh stty"
 
 # Link to these if present
-HOSTTOOLS_NONFATAL += "ccache ld.bfd ld.gold gcc-ar gpg sftp nc socat sudo"
+HOSTTOOLS_NONFATAL += "ccache gcc-ar gpg ld.bfd ld.gold nc sftp socat sudo"
 
 # Temporary add few more detected in bitbake world
 HOSTTOOLS_NONFATAL += "join nl size yes zcat"
-- 
1.9.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/1] apt: fix libdir path for apt.systemd.daily

[Robert Yang]

It should be ${libdir} rather than /usr/lib, otherwise it would fail
when multilib (installed-vs-shipped).

Signed-off-by: Robert Yang 
---
 meta/recipes-devtools/apt/apt-package.inc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/apt/apt-package.inc 
b/meta/recipes-devtools/apt/apt-package.inc
index 839d58e2f7..6a01f99c63 100644
--- a/meta/recipes-devtools/apt/apt-package.inc
+++ b/meta/recipes-devtools/apt/apt-package.inc
@@ -83,9 +83,11 @@ do_install () {
install -m 0644 include/apt-pkg/*.h ${D}${includedir}/apt-pkg/
 
install -d ${D}${systemd_unitdir}/system/
-   install -m 0644 ${S}/debian/apt.systemd.daily ${D}/usr/lib/apt/
+   install -m 0644 ${S}/debian/apt.systemd.daily ${D}${libdir}/apt/
install -m 0644 ${S}/debian/apt-daily.service 
${D}${systemd_unitdir}/system/
+   sed -i 's#/usr/lib/apt/#${libdir}/apt/#g' 
${D}${systemd_unitdir}/system/apt-daily.service
install -m 0644 ${S}/debian/apt-daily.timer 
${D}${systemd_unitdir}/system/
install -d ${D}${sysconfdir}/cron.daily/
install -m 0755 ${S}/debian/apt.apt-compat.cron.daily 
${D}${sysconfdir}/cron.daily/
+   sed -i 's#/usr/lib/apt/#${libdir}/apt/#g' 
${D}${sysconfdir}/cron.daily/apt.apt-compat.cron.daily
 }
-- 
2.11.0.rc2.dirty

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/1 V2] apt: fix libdir path for apt.systemd.daily

[Robert Yang]

* V2
  Also fix apt-daily.service and apt.apt-compat.cron.daily as Ross commented.

// Robert

The following changes since commit 9c948d3de08f158387e08a17cdc0cedc7d26bb54:

  oeqa/selftest: don't use cleanall in selftests (2017-03-27 20:22:43 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/apt
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/apt

Robert Yang (1):
  apt: fix libdir path for apt.systemd.daily

 meta/recipes-devtools/apt/apt-package.inc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

-- 
2.11.0.rc2.dirty

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

[Robert Yang]

On 03/27/2017 09:26 PM, Richard Purdie wrote:

On Mon, 2017-03-27 at 03:34 -0700, Robert Yang wrote:

Fixed:
$ bitbake meta-ide-support
$ . ./tmp/environment-setup-i586-poky-linux
$ runqemu tmp/deploy/images/qemux86/core-image-sato-
qemux86.qemuboot.conf

[snip]
/bin/sh: sudo: command not found
runqemu - ERROR - Failed to setup tap device. Run runqemu-gen-tapdevs
to manually create.
[snip]

The qemu can start, but the IP was wrong, this patch fixes the
problem.

[YOCTO #11232]

Signed-off-by: Robert Yang 
---
 meta/conf/bitbake.conf | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index fa5445b65b..0b1d8d82e0 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -468,6 +468,9 @@ HOSTTOOLS += " \
 # Tools needed to run testimage runtime image testing
 HOSTTOOLS += "ps stty ip ssh scp ping"

+# Tools needed by runqemu in meta-ide-support environment
+HOSTTOOLS += "sudo"
+
 # Link to these if present
 HOSTTOOLS_NONFATAL += "ccache ld.bfd ld.gold gcc-ar gpg sftp nc
socat sudo"


sudo is already in HOSTTOOLS_NONFATAL?


Sorry, it isn't there when I added it last week, please drop my patch.

// Robert



Cheers,

Richard


--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2] eudev: restore userspace firmware loading support

[Jonathan Liu]

Hi Otavio,

On 28 March 2017 at 07:09, Otavio Salvador  wrote:

> From: Lauren Post 
>
> This sycncs eudev with systemd. This is required for old kernels to
> work and does same backport as did in:
>
> ,
> | commit 31163abc7bedd477c1aad10e6d1f47dbee194513
> | Author: Jonathan Liu 
> | Date:   Thu Mar 19 15:38:32 2015 +1100
> |
> | systemd: restore userspace firmware loading support
> |
> | This changes the minimum required Linux version from 3.7 back to 3.0.
> |
> | [YOCTO #7409]
> |
> | Signed-off-by: Jonathan Liu 
> | Signed-off-by: Richard Purdie 
> `
>
> Signed-off-by: Lauren Post 
> Signed-off-by: Otavio Salvador 
>

It may be a good idea to submit a pull request at
https://github.com/gentoo/eudev/ to upstream this into eudev as Gentoo
users have also experienced this issue in the past -
https://forums.gentoo.org/viewtopic-t-1011456.html. One of the goals of the
eudev fork is obtaining better compatibility with older kernels.

Regards,
Jonathan
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCHv3 2/2] dnf: move the entire dnf/rpm4 stack to Python 3

[Paul Eggleton]

Hi Alex,

On Tuesday, 28 March 2017 1:53:59 AM NZDT Alexander Kanavin wrote:
> [YOCTO #11180]
> 
> Signed-off-by: Alexander Kanavin 
> ---

If you're doing another rev can you please have a reasonable commit message in 
here? Even if it's trivial.

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [morty][PATCH] parselogs: Whitelist NUC6 firmware load error message on genericx86-64

[California Sullivan]

This was already whitelisted, but the 4.8 kernel changed the error
message, causing it to get caught by parselogs again.

Fixes [YOCTO #10494].

Signed-off-by: California Sullivan 
Signed-off-by: Ross Burton 
(cherry picked from commit e1bad14231115f3b1a2bf844ef5b2022c648b55d)
Signed-off-by: California Sullivan 
---
This is a backport from master. This error occurs on 2.2.1 - see latest
comments on bug 10494. If I need to add additional info to this commit
message, please let me know and I'll send a V2.

 meta/lib/oeqa/runtime/parselogs.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/lib/oeqa/runtime/parselogs.py 
b/meta/lib/oeqa/runtime/parselogs.py
index e79c39a..aa5008b 100644
--- a/meta/lib/oeqa/runtime/parselogs.py
+++ b/meta/lib/oeqa/runtime/parselogs.py
@@ -142,6 +142,7 @@ ignore_errors = {
 'Failed to load firmware i915',
 'Failed to fetch GuC',
 'Failed to initialize GuC',
+'Failed to load DMC firmware',
 'The driver is built-in, so to load the firmware you need to',
 ] + x86_common,
 'edgerouter' : [
-- 
2.5.5

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v2] eudev: restore userspace firmware loading support

[Otavio Salvador]

From: Lauren Post 

This sycncs eudev with systemd. This is required for old kernels to
work and does same backport as did in:

,
| commit 31163abc7bedd477c1aad10e6d1f47dbee194513
| Author: Jonathan Liu 
| Date:   Thu Mar 19 15:38:32 2015 +1100
|
| systemd: restore userspace firmware loading support
|
| This changes the minimum required Linux version from 3.7 back to 3.0.
|
| [YOCTO #7409]
|
| Signed-off-by: Jonathan Liu 
| Signed-off-by: Richard Purdie 
`

Signed-off-by: Lauren Post 
Signed-off-by: Otavio Salvador 
---

Changes in v2:
- Fix inner patches headers

 ...evert-rules-remove-firmware-loading-rules.patch |  28 ++
 ...-remove-userspace-firmware-loading-suppor.patch | 364 +
 meta/recipes-core/udev/eudev_3.2.1.bb  |   2 +
 3 files changed, 394 insertions(+)
 create mode 100644 
meta/recipes-core/udev/eudev/0014-Revert-rules-remove-firmware-loading-rules.patch
 create mode 100644 
meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch

diff --git 
a/meta/recipes-core/udev/eudev/0014-Revert-rules-remove-firmware-loading-rules.patch
 
b/meta/recipes-core/udev/eudev/0014-Revert-rules-remove-firmware-loading-rules.patch
new file mode 100644
index 00..fe2ba5328d
--- /dev/null
+++ 
b/meta/recipes-core/udev/eudev/0014-Revert-rules-remove-firmware-loading-rules.patch
@@ -0,0 +1,28 @@
+From 4f0a722489154da99e7f6b3051afde984eed2f74 Mon Sep 17 00:00:00 2001
+From: Jonathan Liu 
+Date: Thu, 19 Mar 2015 15:01:29 +1100
+Subject: [PATCH] Revert "rules: remove firmware loading rules"
+
+This reverts commit 70e7d754ddb356fb1a2942b262f8cee9650e2a19.
+Userspace firmware loading support is needed for Linux < 3.7.
+
+Upstream-Status: Inappropriate [OE specific]
+
+Signed-off-by: Jonathan Liu 
+---
+ rules/50-firmware.rules | 3 +++
+ 1 file changed, 3 insertions(+)
+ create mode 100644 rules/50-firmware.rules
+
+diff --git a/rules/50-firmware.rules b/rules/50-firmware.rules
+new file mode 100644
+index 000..f0ae684
+--- /dev/null
 b/rules/50-firmware.rules
+@@ -0,0 +1,3 @@
++# do not edit this file, it will be overwritten on update
++
++SUBSYSTEM=="firmware", ACTION=="add", RUN{builtin}="firmware"
+-- 
+2.3.3
+
diff --git 
a/meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch
 
b/meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch
new file mode 100644
index 00..db333e9376
--- /dev/null
+++ 
b/meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch
@@ -0,0 +1,364 @@
+From e415372cc7a2f52e70e1cfa8c6c1f633b411355d Mon Sep 17 00:00:00 2001
+From: Lauren Post 
+Date: Wed, 8 Jun 2016 06:51:56 -0500
+Subject: [PATCH] Revert "udev: remove userspace firmware loading support"
+
+This reverts commit 3b717594600fa717cdf9bcfd0c7c1b703b245482.
+
+Conflicts:
+   configure.ac
+   src/udev/udevd.c
+
+Upstream-Status: Inappropriate [OE specific]
+
+Signed-off-by: Lauren Post 
+---
+ configure.ac |  39 +-
+ rules/Makefile.am|   5 ++
+ src/udev/Makefile.am |  10 +++
+ src/udev/udev-builtin-firmware.c | 154 +++
+ src/udev/udev-builtin.c  |   3 +
+ src/udev/udev.h  |   6 ++
+ src/udev/udevd.c |  13 
+ 7 files changed, 227 insertions(+), 3 deletions(-)
+ create mode 100644 src/udev/udev-builtin-firmware.c
+
+diff --git a/configure.ac b/configure.ac
+index 8691891..65028c2 100644
+--- a/configure.ac
 b/configure.ac
+@@ -238,9 +238,42 @@ AC_CHECK_DECL([unshare],
+ [#include ])
+ 
+ # 
--
+-AC_PATH_TOOL(GPERF, gperf)
+-if test -z "$GPERF" ; then
+-AC_MSG_ERROR([*** gperf not found])
++AC_ARG_WITH(firmware-path,
++   AS_HELP_STRING([--with-firmware-path=DIR[[[:DIR[...],
++  [Firmware search path 
(default=ROOTPREFIX/lib/firmware/updates:ROOTPREFIX/lib/firmware)]),
++   [], 
[with_firmware_path="$rootprefix/lib/firmware/updates:$rootprefix/lib/firmware"])
++OLD_IFS=$IFS
++IFS=:
++for i in $with_firmware_path; do
++   if test "x${FIRMWARE_PATH}" = "x"; then
++  FIRMWARE_PATH="\\\"${i}/\\\""
++   else
++  FIRMWARE_PATH="${FIRMWARE_PATH}, \\\"${i}/\\\""
++   fi
++done
++IFS=$OLD_IFS
++AC_SUBST(FIRMWARE_PATH)
++AS_IF([test "x${FIRMWARE_PATH}" != "x"], [ AC_DEFINE(HAVE_FIRMWARE, 1, 
[Define if FIRMWARE is available]) ])
++AM_CONDITIONAL(ENABLE_FIRMWARE, [test "x${FIRMWARE_PATH}" != "x"])
++
++# 
--
++AC_ARG_ENABLE([gudev],
++   

[OE-core] [PATCHv2 1/1] oeqa/core/loader.py: Do not import underscore modules by default

[mariano . lopez]

From: Mariano Lopez 

Underscore modules are meant to be run only when manually added to the test
suite, so far another mechanisms are in place to make this happen with
runtime, sdk, and esdk (mostly in test* bbclasses).

This will add such functionality in the core framework so other specific
frameworks can take use this without adding something else.

[YOCTO #10980]

Signed-off-by: Mariano Lopez 
---
 meta/lib/oeqa/core/loader.py | 34 ++
 1 file changed, 30 insertions(+), 4 deletions(-)

diff --git a/meta/lib/oeqa/core/loader.py b/meta/lib/oeqa/core/loader.py
index 74f1117..63a1703 100644
--- a/meta/lib/oeqa/core/loader.py
+++ b/meta/lib/oeqa/core/loader.py
@@ -223,8 +223,21 @@ class OETestLoader(unittest.TestLoader):
 msg = 'Tried to import %s test module but is a built-in'
 raise ImportError(msg % module.__name__)
 
-if not self.modules or "all" in self.modules or \
-module.__name__ in self.modules:
+# Normal test modules are loaded if no modules were specified,
+# if module is in the specified module list or if 'all' is in
+# module list.
+# Underscore modules are loaded only if specified in module list.
+load_module = True if not module.__name__.startswith('_') \
+  and (not self.modules \
+   or module.__name__ in self.modules \
+   or 'all' in self.modules) \
+   else False
+
+load_underscore = True if module.__name__.startswith('_') \
+  and module.__name__ in self.modules \
+   else False
+
+if load_module or load_underscore:
 return super(OETestLoader, self).loadTestsFromModule(
 module, *args, pattern=pattern, **kws)
 else:
@@ -238,8 +251,21 @@ class OETestLoader(unittest.TestLoader):
 msg = 'Tried to import %s test module but is a built-in'
 raise ImportError(msg % module.__name__)
 
-if not self.modules or "all" in self.modules or \
-module.__name__ in self.modules:
+# Normal test modules are loaded if no modules were specified,
+# if module is in the specified module list or if 'all' is in
+# module list.
+# Underscore modules are loaded only if specified in module list.
+load_module = True if not module.__name__.startswith('_') \
+  and (not self.modules \
+   or module.__name__ in self.modules \
+   or 'all' in self.modules) \
+   else False
+
+load_underscore = True if module.__name__.startswith('_') \
+  and module.__name__ in self.modules \
+   else False
+
+if load_module or load_underscore:
 return super(OETestLoader, self).loadTestsFromModule(
 module, use_load_tests)
 else:
-- 
2.10.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] ✗ patchtest: failure for eudev: restore userspace firmware loading support

[Patchwork]

== Series Details ==

Series: eudev: restore userspace firmware loading support
Revision: 1
URL   : https://patchwork.openembedded.org/series/6004/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch
 (possible values: Pending, Submitted, Accepted, Backport, Denied, 
Inappropriate)

* Issue A patch file has been added, but does not have a 
Signed-off-by tag [test_signed_off_by_presence] 
  Suggested fixSign off the added patch file 
(meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v4 3/3] oeqa: allow persistent image writes in runqemu()

[Patrick Ohly]

By default, QemuRunner avoids modifying the image files that it boots
into by enabling the qemu snapshot mode. However, some tests may want
to test changes that must persists across reboots, so this mode
should be optional.

This can be combined by copying the image file to a temporary location
first and then booting with that copy. It's also useful when testing
with additional drives attached to a virtual machine.

QemuTinyRunner doesn't use the snapshot parameter and therefore ignores
the new parameter.

Long term, a better way of passing these various configuration
parameters should be used, and perhaps QemuRunner and QemuTinyRunner
can be merged into one again to avoid code duplication. But for now
the patch follows the exiting style.

Signed-off-by: Patrick Ohly 
---
 meta/lib/oeqa/targetcontrol.py| 6 +++---
 meta/lib/oeqa/utils/commands.py   | 4 ++--
 meta/lib/oeqa/utils/qemurunner.py | 4 ++--
 meta/lib/oeqa/utils/qemutinyrunner.py | 2 +-
 4 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/meta/lib/oeqa/targetcontrol.py b/meta/lib/oeqa/targetcontrol.py
index 40a2589..47cfe85 100644
--- a/meta/lib/oeqa/targetcontrol.py
+++ b/meta/lib/oeqa/targetcontrol.py
@@ -182,11 +182,11 @@ class QemuTarget(BaseTarget):
 logger.info("Qemu log file: %s" % self.qemulog)
 super(QemuTarget, self).deploy()
 
-def start(self, params=None, ssh=True, extra_bootparams='', 
runqemuparams='', launch_cmd=''):
+def start(self, params=None, ssh=True, extra_bootparams='', 
runqemuparams='', launch_cmd='', discard_writes=True):
 if launch_cmd:
-start = self.runner.launch(get_ip=ssh, launch_cmd=launch_cmd)
+start = self.runner.launch(get_ip=ssh, launch_cmd=launch_cmd, 
discard_writes=discard_writes)
 else:
-start = self.runner.start(params, get_ip=ssh, 
extra_bootparams=extra_bootparams, runqemuparams=runqemuparams)
+start = self.runner.start(params, get_ip=ssh, 
extra_bootparams=extra_bootparams, runqemuparams=runqemuparams, 
discard_writes=discard_writes)
 
 if start:
 if ssh:
diff --git a/meta/lib/oeqa/utils/commands.py b/meta/lib/oeqa/utils/commands.py
index 88c9bb1..2951dfb 100644
--- a/meta/lib/oeqa/utils/commands.py
+++ b/meta/lib/oeqa/utils/commands.py
@@ -225,7 +225,7 @@ def create_temp_layer(templayerdir, templayername, 
priority=999, recipepathspec=
 
 
 @contextlib.contextmanager
-def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None, overrides={}):
+def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None, overrides={}, discard_writes=True):
 """
 launch_cmd means directly run the command, don't need set rootfs or env 
vars.
 """
@@ -278,7 +278,7 @@ def runqemu(pn, ssh=True, runqemuparams='', 
image_fstype=None, launch_cmd=None, 
 try:
 qemu.deploy()
 try:
-qemu.start(params=qemuparams, ssh=ssh, 
runqemuparams=runqemuparams, launch_cmd=launch_cmd)
+qemu.start(params=qemuparams, ssh=ssh, 
runqemuparams=runqemuparams, launch_cmd=launch_cmd, 
discard_writes=discard_writes)
 except bb.build.FuncFailed:
 raise Exception('Failed to start QEMU - see the logs in %s' % 
logdir)
 
diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index 95f5925..cd79f21 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -97,7 +97,7 @@ class QemuRunner:
 self._dump_host()
 raise SystemExit
 
-def start(self, qemuparams = None, get_ip = True, extra_bootparams = None, 
runqemuparams='', launch_cmd=None):
+def start(self, qemuparams = None, get_ip = True, extra_bootparams = None, 
runqemuparams='', launch_cmd=None, discard_writes=True):
 if self.display:
 os.environ["DISPLAY"] = self.display
 # Set this flag so that Qemu doesn't do any grabs as SDL grabs
@@ -118,7 +118,7 @@ class QemuRunner:
 os.environ["DEPLOY_DIR_IMAGE"] = self.deploy_dir_image
 
 if not launch_cmd:
-launch_cmd = 'runqemu snapshot %s' % runqemuparams
+launch_cmd = 'runqemu %s %s ' % ('snapshot' if discard_writes else 
'', runqemuparams)
 if self.use_kvm:
 logger.info('Using kvm for runqemu')
 launch_cmd += ' kvm'
diff --git a/meta/lib/oeqa/utils/qemutinyrunner.py 
b/meta/lib/oeqa/utils/qemutinyrunner.py
index b1009a0..34cb912 100644
--- a/meta/lib/oeqa/utils/qemutinyrunner.py
+++ b/meta/lib/oeqa/utils/qemutinyrunner.py
@@ -60,7 +60,7 @@ class QemuTinyRunner(QemuRunner):
 with open(self.logfile, "a") as f:
 f.write("%s" % msg)
 
-def start(self, qemuparams = None, ssh=True, extra_bootparams=None, 
runqemuparams=''):
+def start(self, qemuparams = None, ssh=True, extra_bootparams=None, 
runqemuparams='', 

[OE-core] [PATCH v4 2/3] oeqa: allow customizing image used by runqemu()

[Patrick Ohly]

runqemu() takes all parameters for the virtual machine from the
variables of the given recipe. By allowing the caller to provide a
hash with variables that get applied locally, the caller gets more
control.

Here's the intended usage:

   
   overrides = {
'DEPLOY_DIR_IMAGE': self.resultdir,
'IMAGE_LINK_NAME': 'internal-image-%s' % self.image_arch,
   }
   with runqemu('refkit-installer-image', ssh=False,
 overrides=overrides) as qemu:
   

This can be used to replace the image completely with something else
or to copy it before allowing runqemu() to write into it.

Signed-off-by: Patrick Ohly 
---
 meta/lib/oeqa/utils/commands.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/utils/commands.py b/meta/lib/oeqa/utils/commands.py
index 3dfff0f..88c9bb1 100644
--- a/meta/lib/oeqa/utils/commands.py
+++ b/meta/lib/oeqa/utils/commands.py
@@ -225,7 +225,7 @@ def create_temp_layer(templayerdir, templayername, 
priority=999, recipepathspec=
 
 
 @contextlib.contextmanager
-def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None):
+def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None, overrides={}):
 """
 launch_cmd means directly run the command, don't need set rootfs or env 
vars.
 """
@@ -247,6 +247,8 @@ def runqemu(pn, ssh=True, runqemuparams='', 
image_fstype=None, launch_cmd=None, 
 tinfoil.config_data.setVar("FIND_ROOTFS", '1')
 
 recipedata = tinfoil.parse_recipe(pn)
+for key, value in overrides.items():
+recipedata.setVar(key, value)
 
 # The QemuRunner log is saved out, but we need to ensure it is at the 
right
 # log level (and then ensure that since it's a child of the BitBake 
logger,
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v4 1/3] oeqa: allow extending qemuparams="..."

[Patrick Ohly]

Sometimes it is useful to reconfigure the qemu virtual machine
directly. runqemu has the "qemuparams" parameter for that, and the
underlying start() methods also supported modifying that via their
"params" parameter. Only the runqemu() wrapper function lacked
a way to specify additional parameters.

One potential usage is to attach additional disks.

Signed-off-by: Patrick Ohly 
---
 meta/lib/oeqa/utils/commands.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/utils/commands.py b/meta/lib/oeqa/utils/commands.py
index cd7a5e3..3dfff0f 100644
--- a/meta/lib/oeqa/utils/commands.py
+++ b/meta/lib/oeqa/utils/commands.py
@@ -225,7 +225,7 @@ def create_temp_layer(templayerdir, templayername, 
priority=999, recipepathspec=
 
 
 @contextlib.contextmanager
-def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None):
+def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None):
 """
 launch_cmd means directly run the command, don't need set rootfs or env 
vars.
 """
@@ -276,7 +276,7 @@ def runqemu(pn, ssh=True, runqemuparams='', 
image_fstype=None, launch_cmd=None):
 try:
 qemu.deploy()
 try:
-qemu.start(ssh=ssh, runqemuparams=runqemuparams, 
launch_cmd=launch_cmd)
+qemu.start(params=qemuparams, ssh=ssh, 
runqemuparams=runqemuparams, launch_cmd=launch_cmd)
 except bb.build.FuncFailed:
 raise Exception('Failed to start QEMU - see the logs in %s' % 
logdir)
 
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v4 0/3] oeqa: more control over qemu

[Patrick Ohly]

I'm currently working on testing an installer image. During that test
I need to:
- boot with two drives attached to the virtual machine (installer image
  and internal disk)
- install to internal disk
- reboot with just the internal disk

There were several problems doing that:
- attaching second disk via qemuparams was not possible
- run_serial() timed out too early during the long-running install command
- writes to the internal disks were discarded
- booting with only the non-standard internal disk instead of the
  recipe's image was not possible

V2: rebased on top of master-next + Robert's "runqemu: add selftest" series,
no other changes (merge V1 if not taking Robert's patches first)
V3: rebased on top of current master
V4: QemuTinyRunner.start() also needs to accept the new "discard_writes" 
parameter

Patrick Ohly (3):
  oeqa: allow extending qemuparams="..."
  oeqa: allow customizing image used by runqemu()
  oeqa: allow persistent image writes in runqemu()

 meta/lib/oeqa/targetcontrol.py| 6 +++---
 meta/lib/oeqa/utils/commands.py   | 6 --
 meta/lib/oeqa/utils/qemurunner.py | 4 ++--
 meta/lib/oeqa/utils/qemutinyrunner.py | 2 +-
 4 files changed, 10 insertions(+), 8 deletions(-)

base-commit: b2a785f19fe25d244179b8672c846925da6d455a
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] eudev: restore userspace firmware loading support

[Otavio Salvador]

From: Lauren Post 

This sycncs eudev with systemd. This is required for old kernels to
work and does same backport as did in:

,
| commit 31163abc7bedd477c1aad10e6d1f47dbee194513
| Author: Jonathan Liu 
| Date:   Thu Mar 19 15:38:32 2015 +1100
|
| systemd: restore userspace firmware loading support
|
| This changes the minimum required Linux version from 3.7 back to 3.0.
|
| [YOCTO #7409]
|
| Signed-off-by: Jonathan Liu 
| Signed-off-by: Richard Purdie 
`

Signed-off-by: Lauren Post 
Signed-off-by: Otavio Salvador 
---

 ...evert-rules-remove-firmware-loading-rules.patch |  28 ++
 ...-remove-userspace-firmware-loading-suppor.patch | 360 +
 2 files changed, 388 insertions(+)
 create mode 100644 
meta/recipes-core/udev/eudev/0014-Revert-rules-remove-firmware-loading-rules.patch
 create mode 100644 
meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch

diff --git 
a/meta/recipes-core/udev/eudev/0014-Revert-rules-remove-firmware-loading-rules.patch
 
b/meta/recipes-core/udev/eudev/0014-Revert-rules-remove-firmware-loading-rules.patch
new file mode 100644
index 00..fe2ba5328d
--- /dev/null
+++ 
b/meta/recipes-core/udev/eudev/0014-Revert-rules-remove-firmware-loading-rules.patch
@@ -0,0 +1,28 @@
+From 4f0a722489154da99e7f6b3051afde984eed2f74 Mon Sep 17 00:00:00 2001
+From: Jonathan Liu 
+Date: Thu, 19 Mar 2015 15:01:29 +1100
+Subject: [PATCH] Revert "rules: remove firmware loading rules"
+
+This reverts commit 70e7d754ddb356fb1a2942b262f8cee9650e2a19.
+Userspace firmware loading support is needed for Linux < 3.7.
+
+Upstream-Status: Inappropriate [OE specific]
+
+Signed-off-by: Jonathan Liu 
+---
+ rules/50-firmware.rules | 3 +++
+ 1 file changed, 3 insertions(+)
+ create mode 100644 rules/50-firmware.rules
+
+diff --git a/rules/50-firmware.rules b/rules/50-firmware.rules
+new file mode 100644
+index 000..f0ae684
+--- /dev/null
 b/rules/50-firmware.rules
+@@ -0,0 +1,3 @@
++# do not edit this file, it will be overwritten on update
++
++SUBSYSTEM=="firmware", ACTION=="add", RUN{builtin}="firmware"
+-- 
+2.3.3
+
diff --git 
a/meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch
 
b/meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch
new file mode 100644
index 00..82891e1424
--- /dev/null
+++ 
b/meta/recipes-core/udev/eudev/Revert-udev-remove-userspace-firmware-loading-suppor.patch
@@ -0,0 +1,360 @@
+From e415372cc7a2f52e70e1cfa8c6c1f633b411355d Mon Sep 17 00:00:00 2001
+From: Lauren Post 
+Date: Wed, 8 Jun 2016 06:51:56 -0500
+Subject: [PATCH] Revert "udev: remove userspace firmware loading support"
+
+This reverts commit 3b717594600fa717cdf9bcfd0c7c1b703b245482.
+
+Conflicts:
+   configure.ac
+   src/udev/udevd.c
+---
+ configure.ac |  39 +-
+ rules/Makefile.am|   5 ++
+ src/udev/Makefile.am |  10 +++
+ src/udev/udev-builtin-firmware.c | 154 +++
+ src/udev/udev-builtin.c  |   3 +
+ src/udev/udev.h  |   6 ++
+ src/udev/udevd.c |  13 
+ 7 files changed, 227 insertions(+), 3 deletions(-)
+ create mode 100644 src/udev/udev-builtin-firmware.c
+
+diff --git a/configure.ac b/configure.ac
+index 8691891..65028c2 100644
+--- a/configure.ac
 b/configure.ac
+@@ -238,9 +238,42 @@ AC_CHECK_DECL([unshare],
+ [#include ])
+ 
+ # 
--
+-AC_PATH_TOOL(GPERF, gperf)
+-if test -z "$GPERF" ; then
+-AC_MSG_ERROR([*** gperf not found])
++AC_ARG_WITH(firmware-path,
++   AS_HELP_STRING([--with-firmware-path=DIR[[[:DIR[...],
++  [Firmware search path 
(default=ROOTPREFIX/lib/firmware/updates:ROOTPREFIX/lib/firmware)]),
++   [], 
[with_firmware_path="$rootprefix/lib/firmware/updates:$rootprefix/lib/firmware"])
++OLD_IFS=$IFS
++IFS=:
++for i in $with_firmware_path; do
++   if test "x${FIRMWARE_PATH}" = "x"; then
++  FIRMWARE_PATH="\\\"${i}/\\\""
++   else
++  FIRMWARE_PATH="${FIRMWARE_PATH}, \\\"${i}/\\\""
++   fi
++done
++IFS=$OLD_IFS
++AC_SUBST(FIRMWARE_PATH)
++AS_IF([test "x${FIRMWARE_PATH}" != "x"], [ AC_DEFINE(HAVE_FIRMWARE, 1, 
[Define if FIRMWARE is available]) ])
++AM_CONDITIONAL(ENABLE_FIRMWARE, [test "x${FIRMWARE_PATH}" != "x"])
++
++# 
--
++AC_ARG_ENABLE([gudev],
++   AS_HELP_STRING([--disable-gudev], [disable Gobject libudev support 
@<:@default=enabled@:>@]),
++   [], [enable_gudev=yes])
++AS_IF([test "x$enable_gudev" = "xyes"], [ PKG_CHECK_MODULES([GLIB], [glib-2.0 
>= 2.22.0 gobject-2.0 

[OE-core] OpenEmbedded Developer Meeting Oct 22 in Prague

[Philip Balister]

We've had some discussion for scheduling the next OEDEM around the ELCE
in Prague. The Yocto Project Developer day is the Thursday after the
conference (as is the kernel summit). To avoid conflicting with them the
OpenEmbedded board proposes holding the meeting Sunday before ELCE in
Prague.

That is Sunday Oct 22, 2017. We'll work out details closer to the event.
If anyone has terrible issues with this date, let us know.

This meeting is for everyone with an interest in OpenEmbedded (the Yocto
Project build system). We love hearing from people about what we are
doing right, what we are doing wrong, and what we can do better. The
agenda is set by the people attending, we typically setup a wiki page to
collect ideas. So watch for announcements over the next few months.

Philip and the OpenEmbedded board.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] ✗ patchtest: failure for oeqa/core/loader.py: Do not import underscore modules by default

[Patchwork]

== Series Details ==

Series: oeqa/core/loader.py: Do not import underscore modules by default
Revision: 1
URL   : https://patchwork.openembedded.org/series/6002/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patch[1/1] oeqa/core/loader.py: Do not import underscore modules 
by default
 Issue Yocto Project bugzilla tag is not correctly formatted 
[test_bugzilla_entry_format] 
  Suggested fixSpecify bugzilla ID in commit description with format: 
"[YOCTO #]"



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/1] oeqa/core/loader.py: Do not import underscore modules by default

[mariano . lopez]

From: Mariano Lopez 

Underscore modules are meant to be run only when manually added to the test
suite, so far another mechanisms are in place to make this happen with
runtime, sdk, and esdk (mostly in test* bbclasses).

This will add such functionality in the core framework so other specific
frameworks can take use this without adding something else.

[YOCTO 10980]

Signed-off-by: Mariano Lopez 
---
 meta/lib/oeqa/core/loader.py | 34 ++
 1 file changed, 30 insertions(+), 4 deletions(-)

diff --git a/meta/lib/oeqa/core/loader.py b/meta/lib/oeqa/core/loader.py
index 74f1117..63a1703 100644
--- a/meta/lib/oeqa/core/loader.py
+++ b/meta/lib/oeqa/core/loader.py
@@ -223,8 +223,21 @@ class OETestLoader(unittest.TestLoader):
 msg = 'Tried to import %s test module but is a built-in'
 raise ImportError(msg % module.__name__)
 
-if not self.modules or "all" in self.modules or \
-module.__name__ in self.modules:
+# Normal test modules are loaded if no modules were specified,
+# if module is in the specified module list or if 'all' is in
+# module list.
+# Underscore modules are loaded only if specified in module list.
+load_module = True if not module.__name__.startswith('_') \
+  and (not self.modules \
+   or module.__name__ in self.modules \
+   or 'all' in self.modules) \
+   else False
+
+load_underscore = True if module.__name__.startswith('_') \
+  and module.__name__ in self.modules \
+   else False
+
+if load_module or load_underscore:
 return super(OETestLoader, self).loadTestsFromModule(
 module, *args, pattern=pattern, **kws)
 else:
@@ -238,8 +251,21 @@ class OETestLoader(unittest.TestLoader):
 msg = 'Tried to import %s test module but is a built-in'
 raise ImportError(msg % module.__name__)
 
-if not self.modules or "all" in self.modules or \
-module.__name__ in self.modules:
+# Normal test modules are loaded if no modules were specified,
+# if module is in the specified module list or if 'all' is in
+# module list.
+# Underscore modules are loaded only if specified in module list.
+load_module = True if not module.__name__.startswith('_') \
+  and (not self.modules \
+   or module.__name__ in self.modules \
+   or 'all' in self.modules) \
+   else False
+
+load_underscore = True if module.__name__.startswith('_') \
+  and module.__name__ in self.modules \
+   else False
+
+if load_module or load_underscore:
 return super(OETestLoader, self).loadTestsFromModule(
 module, use_load_tests)
 else:
-- 
2.10.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] xserver-nodm-init: option to remove cursor

[Trevor Woerner]

On Mon, Mar 27, 2017 at 11:14 AM, Burton, Ross  wrote:
>
> On 27 March 2017 at 16:10, Trevor Woerner  wrote:
>>
>> What I want is to get rid of the mouse pointer completely. Formfactor has
>> variables that would appear to affect things like rotation and whether or
>> not
>> the calibration routine gets called when X starts up. I don't see anything
>> in
>> there that can disable the showing of the pointer.
>
>
> The touchscreen variable results in the X startup scripts hiding the cursor.

Oh, I see what you're saying... on *SATO*. Agreed. On _sato_ setting
HAVE_TOUCHSCREEN set to 1 hides the cursor:
meta/recipes-sato/machbox-session-sato/session

But what about on plain ol' core-image-x11? Although I wasn't aware of
formfactor before, using it now it still doesn't solve the issue for
me. The existing mechanism tweaks the pointer at the window manager
level, my proposed patch tweaks the pointer at the X server level
which (I'm arguing) is a better place to adjust it. This way it's
independent of everything (except which display server you're using).
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Denys Dmytriyenko]

On Mon, Mar 27, 2017 at 04:52:33PM +0100, Burton, Ross wrote:
> On 27 March 2017 at 16:47, Denys Dmytriyenko  wrote:
> 
> > I haven't personally tested 2017.03 yet, as we are staying on 2017.01 for a
> > bit longer...
> >
> 
> It that just because you've stabilised, or is there something in .03 that
> you're concerned about?

No, I'm not aware of any major issues with .03, although haven't done much 
testing with it due to pending internal release with .01 - the timing is 
rather unfortunate...

-- 
Denys
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] insane.bbclass: error if file-rdeps not met

[Stephano Cetola]

Missing runtime dependencies should result in an error rather than a
warning. Indeed, if RPM is listed in PACKAGE_CLASSES, it will throw
an error rather than install packages with missing dependencies. This
functionality should be consistent across package types. This patch
ensures that an error will be thrown.

[YOCTO #10949]

Signed-off-by: Stephano Cetola 
---
 meta/classes/insane.bbclass | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index 7a869977e1..dc1c2f8d41 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -30,7 +30,7 @@ QA_SANE = "True"
 WARN_QA ?= "ldflags useless-rpaths rpaths staticdev libdir xorg-driver-abi \
 textrel already-stripped incompatible-license files-invalid \
 installed-vs-shipped compile-host-path install-host-path \
-pn-overrides infodir build-deps file-rdeps \
+pn-overrides infodir build-deps \
 unknown-configure-option symlink-to-sysroot multilib \
 invalid-packageconfig host-user-contaminated \
 "
@@ -38,7 +38,7 @@ ERROR_QA ?= "dev-so debug-deps dev-deps debug-files arch 
pkgconfig la \
 perms dep-cmp pkgvarcheck perm-config perm-line perm-link \
 split-strip packages-list pkgv-undefined var-undefined \
 version-going-backwards expanded-d invalid-chars \
-license-checksum dev-elf \
+license-checksum dev-elf file-rdeps \
 "
 FAKEROOT_QA = "host-user-contaminated"
 FAKEROOT_QA[doc] = "QA tests which need to run under fakeroot. If any \
-- 
2.12.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] devtool: open kconfig fragment in binary mode

[Stephano Cetola]

When devtool writes to the kconfig fragment, it writes the output of
the diff command returned from pipe.communicate(). This function
returns binary objects. We should open the kconfig fragment file in
binary mode if we expect to write binary objects to it.

[YOCTO #11171]

Signed-off-by: Stephano Cetola 
---
 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 07c1400388..ffca2c9ec4 100644
--- a/scripts/lib/devtool/standard.py
+++ b/scripts/lib/devtool/standard.py
@@ -1223,7 +1223,7 @@ def _create_kconfig_diff(srctree, rd, outfile):
 stdout, stderr = pipe.communicate()
 if pipe.returncode == 1:
 logger.info("Updating config fragment %s" % outfile)
-with open(outfile, 'w') as fobj:
+with open(outfile, 'wb') as fobj:
 fobj.write(stdout)
 elif pipe.returncode == 0:
 logger.info("Would remove config fragment %s" % outfile)
-- 
2.12.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] scripts/yocto-compat-layer.py: Add dependency validation in add_layer

[Aníbal Limón]

Some layers don't have dependencies so add a validation to avoid
exception when trying to None.split().

Signed-off-by: Aníbal Limón 
---
 scripts/lib/compatlayer/__init__.py | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/scripts/lib/compatlayer/__init__.py 
b/scripts/lib/compatlayer/__init__.py
index 435679e..58f94b7 100644
--- a/scripts/lib/compatlayer/__init__.py
+++ b/scripts/lib/compatlayer/__init__.py
@@ -143,7 +143,11 @@ def add_layer(bblayersconf, layer, layers, logger):
 logger.info('Adding layer %s' % layer['name'])
 
 for collection in layer['collections']:
-for depend in layer['collections'][collection]['depends'].split():
+depends = layer['collections'][collection]['depends']
+if not depends:
+continue
+
+for depend in depends.split():
 # core (oe-core) is suppose to be provided
 if depend == 'core':
 continue
-- 
2.1.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] CPU profiling at thread level

[Richard Purdie]

On Sat, 2017-03-25 at 21:44 +0530, Munagala Naresh wrote:
> Hi Team,
> 
> To analyzes the CPU load consumption of a particular process, we need
> to find the thread level consumption. Default top and ps utils are
> not supporting all the parameters that are available in
> Linux/Android. 
> 
> Could you please suggest some alternatives which works in
> openembedded platform?
> 
> Appreciate any pointers. 

The issue is probably that you're using utils from busybox by default.
If you install the "full" ps from the procps recipe you'll probably
have the experience you want. I think the full top utility may come
from procps too.

Cheers,

Richard
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] CPU profiling at thread level

[Leonardo Sandoval]

On Sat, 2017-03-25 at 21:44 +0530, Munagala Naresh wrote:
> Hi Team,
> 
> 
> 
> To analyzes the CPU load consumption of a particular process, we need
> to find the thread level consumption. Default top and ps utils are not
> supporting all the parameters that are available in Linux/Android. 
> 
I am not a performance expert, but you may try the software package htop
located at meta-oe; other than this, you may try querying /proc/[pid]

> 
> 
> Could you please suggest some alternatives which works in openembedded
> platform?
> 
> 
> Appreciate any pointers. 
> 
> 
> 
> 
> Thanks
> 
> Naresh 
> 
> 
> 
> 
> 
> -- 
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Denys Dmytriyenko]

On Mon, Mar 27, 2017 at 02:19:56PM +0100, Burton, Ross wrote:
> On 26 March 2017 at 22:14, Denys Dmytriyenko  wrote:
> 
> > At least 2 typos in the description...
> >
> 
> Typos aside, this is past the M3 deadline but RC2 is running late, is there
> a good reason to have the upgrade in?
> 
> Also what boards has it been tested on?  As it's from Otavio I presume the
> Freescale boards have been tested.  Denys, have you tested this version on
> your boards?

Ross,

I haven't personally tested 2017.03 yet, as we are staying on 2017.01 for a 
bit longer...

-- 
Denys
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/2] boost: enable more libraries

[Ross Burton]

Enable the fiber, metaparse, and type_erasure libraries.

We can't enable coroutine2 as it needs C++11 and it appears our hacks to
configure the compiler mean boost doesn't think we support that.

Signed-off-by: Ross Burton 
---
 meta/recipes-support/boost/boost.inc | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/recipes-support/boost/boost.inc 
b/meta/recipes-support/boost/boost.inc
index f85e1d1..100fb0d 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -5,17 +5,21 @@ DEPENDS = "bjam-native zlib bzip2"
 ARM_INSTRUCTION_SET_armv4 = "arm"
 ARM_INSTRUCTION_SET_armv5 = "arm"
 
+# When we don't insist that our GCC is 4.3.1 (see below) hopefully coroutine2
+# (which needs C++11) will work.
 BOOST_LIBS = "\
atomic \
chrono \
container \
date_time \
exception \
+   fiber \
filesystem \
graph \
iostreams \
log \
math \
+   metaparse \
program_options \
random \
regex \
@@ -24,6 +28,7 @@ BOOST_LIBS = "\
system \
timer \
test \
+   type_erasure \
thread \
wave \
"
-- 
2.8.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/2] boost: build context and coroutine on ARM

[Ross Burton]

With the right flags to the build, the context library can be built on ARM.

[ YOCTO #11253 ]

Signed-off-by: Ross Burton 
---
 meta/recipes-support/boost/boost.inc | 11 ---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-support/boost/boost.inc 
b/meta/recipes-support/boost/boost.inc
index 4ff70e3..f85e1d1 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -28,12 +28,15 @@ BOOST_LIBS = "\
wave \
"
 
-# only supported by x86 and powerpc
+# Enable context only on platforms we've verified it builds on
+BOOST_LIBS_append_arm = " context coroutine"
+BOOST_LIBS_append_arm-64 = " context coroutine"
+BOOST_LIBS_append_powerpc = " context coroutine"
 BOOST_LIBS_append_x86 = " context coroutine"
 BOOST_LIBS_append_x86-64 = " context coroutine"
-BOOST_LIBS_append_powerpc = " context coroutine"
 # need consistent settings for native builds (x86 override not applied for 
native)
 BOOST_LIBS_remove_class-native = " context coroutine"
+
 # does not compile
 BOOST_LIBS_remove_mips16e = "wave"
 
@@ -168,7 +171,9 @@ BJAM_OPTS= '${BOOST_PARALLEL_MAKE} -d+2 -q \
 # Native compilation of bzip2 isn't working
 BJAM_OPTS_append_class-native = ' -sNO_BZIP2=1'
 
-# Adjust the build for x32
+# Teach bjam how to build as it ignores the compiler flags we pass
+BJAM_OPTS_append_arm += " abi=aapcs binary-format=elf address-model=32 
architecture=arm"
+BJAM_OPTS_append_arm-64 += " abi=aapcs binary-format=elf address-model=64 
architecture=arm"
 BJAM_OPTS_append_linux-gnux32 = " abi=x32 address-model=64"
 
 do_configure() {
-- 
2.8.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 0/3] oeqa/runtime: Import custom targets

[Mariano Lopez]

On 27/03/17 07:38, Richard Purdie wrote:
> On Fri, 2017-03-24 at 15:06 -0700, mariano.lo...@linux.intel.com wrote:
>> From: Mariano Lopez 
>>
>> This series allows to import custom targets to be used with runtime
>> testing.
>> Now is possible to have a target in /lib/oeqa/core/target and
>> testimage and testexport can use such target using TEST_TARGET
>> variable.
>>
>> To register a custom target you just need use decorate a target class
>> with
>> registerTarget, and set "targetName" attribute to the name that will
>> be used
>> by TEST_TARGET variable.
> Unfortunately something about this series break oe-selftest:
>
> https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/229/st
> eps/Running%20oe-selftest/logs/stdio
>
> It doesn't do it in isolation, that test run by itself is fine. When
> run as part of oe-selftest it breaks though. I did bisect it down to
> this series and things have all built fine after I dropped these 3
> patches.
>
> So we'll have to figure out what is happening here...

I'm very sorry that you have to do a bisect to find this out :(

I did run selftest in my workstation to avoid this thing but it seems
it wasn't enough.

The problem is when importing the modules with
oe-test (outside bitbake). I did check it with python 3.4 but I didn't
test it with 3.5 so, I'll start with that.

Regards,
Mariano
>
> Cheers,
>
> Richard

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] xserver-nodm-init: option to remove cursor

[Burton, Ross]

On 27 March 2017 at 16:10, Trevor Woerner  wrote:

> What I want is to get rid of the mouse pointer completely. Formfactor has
> variables that would appear to affect things like rotation and whether or
> not
> the calibration routine gets called when X starts up. I don't see anything
> in
> there that can disable the showing of the pointer.
>

The touchscreen variable results in the X startup scripts hiding the cursor.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] xserver-nodm-init: option to remove cursor

[Trevor Woerner]

On Mon 2017-03-27 @ 12:35:51 PM, Burton, Ross wrote:
> On 25 March 2017 at 05:19, Trevor Woerner  wrote:
> 
> > Add a PACKAGECONFIG option to allow the user to disable the mouse
> > cursor/pointer in the X server. This might be useful where a
> > touchscreen is used.
> >
> 
> This is what the touchscreen variable in the formfactor recipe is for.  Is
> this not sufficient?

To be honest I hadn't noticed formfactor before I created my patch. But
looking at it now, no, I don't think it would be sufficient. I'll take a
couple stabs at it, but I don't think it'll do what I want.

What I want is to get rid of the mouse pointer completely. Formfactor has
variables that would appear to affect things like rotation and whether or not
the calibration routine gets called when X starts up. I don't see anything in
there that can disable the showing of the pointer.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] Yocto Project Status WW13’17

[Jolley, Stephen K]

Current Dev Position: YP 2.3 M4

Next Deadline: YP 2.3 M4 Cutoff is April 10, 2017


*** FEATURE FREEZE for 2.3 is now in effect. ***


SWAT team rotation: Jussi -> Stephano on Mar. 24, 2017.

SWAT team rotation: Stephano -> Maxin on Mar. 31, 2017.

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

·We’ve decided to take M3 to an rc2 build due to the shear amount of 
changes and issues found in rc1. The rc2 build is imminent but there have been 
a number of significant good patches hitting the mailing list and it makes 
sense to pull many of these in.

·We have identified a number of issues which were slowing down 
oe-selftest and the autobuilder, Joshua’s help with these has been much 
appreciated and going forward, build times should be better and builds will be 
more stable. We have been able to use sstate to accelerate selftest now (which 
highlighted some other problems). We do continue to have performance/race 
issues (which as some gpg issue which resulted in a 30 hour selftest) but 
things are looking better.

·Since we’re into the stabilization phase of 2.3, planning for 2.4 has 
begun and we’re entering 2.4 ideas and enhancements in to bugzilla. If you have 
suggestions for 2.4, please ensure they are in bugzilla.


Proposed upcoming dot releases:

YP 2.1.3 Cut off May 15, 2017

YP 2.1.3 Release by May 26, 2017

YP 2.2.2 Cut off May 29, 2017

YP 2.2.2 Release by June 9, 2017


Key YP 2.3 Dates:

YP 2.3 M3 Release is Mar. 10, 2017 (Will be a few weeks late.)

YP 2.3 M4 Cutoff is April 10, 2017

YP 2.3 M4 Release is May 5, 2017


Tracking Metrics:

WDD 2832 (last week 2751)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features

[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
•   Work Telephone:(503) 712-0534
•Cell:   (208) 244-4460
• Email:stephen.k.jol...@intel.com

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] u-boot: Update to 2017.03 release

[Marek Vasut]

Upgrade U-Boot to the latest version.

Signed-off-by: Marek Vasut 
Cc: Denys Dmytriyenko 
Cc: Richard Purdie 
Cc: Ross Burton 
---
 .../u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} | 2 +-
 .../u-boot/{u-boot-fw-utils_2017.01.bb => u-boot-fw-utils_2017.03.bb}   | 0
 .../u-boot/{u-boot-mkimage_2017.01.bb => u-boot-mkimage_2017.03.bb} | 0
 meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb}| 0
 4 files changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-bsp/u-boot/{u-boot-common_2017.01.inc => 
u-boot-common_2017.03.inc} (86%)
 rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.01.bb => 
u-boot-fw-utils_2017.03.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.01.bb => 
u-boot-mkimage_2017.03.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb} (100%)

diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc 
b/meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
similarity index 86%
rename from meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
rename to meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
index df24c853dd..c115f36831 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
@@ -7,7 +7,7 @@ PE = "1"
 
 # We use the revision in order to avoid having to fetch it from the
 # repo during parse
-SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149"
+SRCREV = "8537ddd769f460d7fb7a62a3dcc9669049702e51"
 
 SRC_URI = "git://git.denx.de/u-boot.git"
 
diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb 
b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb
rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb 
b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb
rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.01.bb 
b/meta/recipes-bsp/u-boot/u-boot_2017.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot_2017.01.bb
rename to meta/recipes-bsp/u-boot/u-boot_2017.03.bb
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCHv2] dnf: move the entire dnf/rpm4 stack to Python 3

[Richard Purdie]

On Mon, 2017-03-27 at 15:19 +0300, Alexander Kanavin wrote:
> On 03/25/2017 07:56 PM, Richard Purdie wrote:
> > 
> > > 
> > > [YOCTO #11180]
> > So close but:
> > 
> > https://autobuilder.yocto.io/builders/nightly-multilib/builds/226
> > https://autobuilder.yocto.io/builders/nightly-x32/builds/206
> This is actually a bug in our target Python 3 installation. No idea
> how 
> it went unnoticed - does no one use Python 3 on target with multilib
> or 
> x32 at all?
> 
> 
> Python 3.5.2 (default, Mar 27 2017, 11:43:41)
> [GCC 6.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more
> information.
>  >>> import site
>  >>> site.getsitepackages()
> ['/usr/lib/python3.5/site-packages']
> ^^^ !!!

Highlights we need better testing, thanks for fixing it!

Cheers,

Richard
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 0/3] oeqa/runtime: Import custom targets

[Richard Purdie]

On Fri, 2017-03-24 at 15:06 -0700, mariano.lo...@linux.intel.com wrote:
> From: Mariano Lopez 
> 
> This series allows to import custom targets to be used with runtime
> testing.
> Now is possible to have a target in /lib/oeqa/core/target and
> testimage and testexport can use such target using TEST_TARGET
> variable.
> 
> To register a custom target you just need use decorate a target class
> with
> registerTarget, and set "targetName" attribute to the name that will
> be used
> by TEST_TARGET variable.

Unfortunately something about this series break oe-selftest:

https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/229/st
eps/Running%20oe-selftest/logs/stdio

It doesn't do it in isolation, that test run by itself is fine. When
run as part of oe-selftest it breaks though. I did bisect it down to
this series and things have all built fine after I dropped these 3
patches.

So we'll have to figure out what is happening here...

Cheers,

Richard
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] classes: Replace "if test" file tests with POSIX file tests

[Richard Purdie]

On Sat, 2017-03-25 at 14:03 -0400, Robert P. J. Day wrote:
> In entire meta/classes/ directory, replace shell tests of the form
> "if test -? ..." with POSIX tests of the form "if [ -? ...
> 
> Signed-off-by: Robert P. J. Day 
> 
> ---
> 
>   as i cannot abide those silly "if test" constructs, i zipped
> through
> and changed them to POSIX form. is there any objection to this kind
> of
> cleanup? next up ... all those "x${VAR} = x" tests ...

I've merged most of this. There were pieces of the diff that simply
didn't apply so I skipped them.

The reason I've taken what applied is that this is very expensive for
us to test right now and I made the most of the testing time I had on
the weekend. The issue is changes to the core classes rebuild
everything so we can't reuse sstate and the tests are much slower.

We're running late with M3 rc2 but just about to build it and I thought
it was worth getting some of this in rather none at all. Please do
figure out the remaining pieces and send them and we may or may not
tweak the remaining bits in M4.

Cheers,

Richard
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Otavio Salvador]

On Mon, Mar 27, 2017 at 10:19 AM, Burton, Ross  wrote:
...
> Also what boards has it been tested on?  As it's from Otavio I presume the
> Freescale boards have been tested.  Denys, have you tested this version on
> your boards?

We are using it internally and we will upgrade meta-freescale for this
release as well. I believe it would be great to upgrade this as U-Boot
bieng up to date allows for a more up to date reference code.

If there is any failure in the automated tests I can try to iron them
out but I believe it should be fine.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

[Burton, Ross]

On 27 March 2017 at 14:26, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> sudo is already in HOSTTOOLS_NONFATAL?
>

Good point well made.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

[Richard Purdie]

On Mon, 2017-03-27 at 03:34 -0700, Robert Yang wrote:
> Fixed:
> $ bitbake meta-ide-support
> $ . ./tmp/environment-setup-i586-poky-linux
> $ runqemu tmp/deploy/images/qemux86/core-image-sato-
> qemux86.qemuboot.conf
> 
> [snip]
> /bin/sh: sudo: command not found
> runqemu - ERROR - Failed to setup tap device. Run runqemu-gen-tapdevs 
> to manually create.
> [snip]
> 
> The qemu can start, but the IP was wrong, this patch fixes the
> problem.
> 
> [YOCTO #11232]
> 
> Signed-off-by: Robert Yang 
> ---
>  meta/conf/bitbake.conf | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index fa5445b65b..0b1d8d82e0 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -468,6 +468,9 @@ HOSTTOOLS += " \
>  # Tools needed to run testimage runtime image testing
>  HOSTTOOLS += "ps stty ip ssh scp ping"
>  
> +# Tools needed by runqemu in meta-ide-support environment
> +HOSTTOOLS += "sudo"
> +
>  # Link to these if present
>  HOSTTOOLS_NONFATAL += "ccache ld.bfd ld.gold gcc-ar gpg sftp nc
> socat sudo"

sudo is already in HOSTTOOLS_NONFATAL?

Cheers,

Richard
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCHv4 2/2] dnf: move the entire dnf/rpm4 stack to Python 3

[Alexander Kanavin]

[YOCTO #11180]

Signed-off-by: Alexander Kanavin 
---
 meta/classes/rootfs_rpm.bbclass|   4 +-
 meta/conf/distro/include/security_flags.inc|   3 +-
 .../createrepo-c/createrepo-c_git.bb   |   4 +-
 .../dnf/dnf/0028-Use-backports.lzma-not-lzma.patch |  30 --
 .../dnf/0030-Run-python-scripts-using-env.patch|   6 +-
 meta/recipes-devtools/dnf/dnf_git.bb   |  15 +-
 meta/recipes-devtools/libcomps/libcomps_git.bb |   6 +-
 meta/recipes-devtools/libdnf/libdnf_git.bb |  17 +-
 meta/recipes-devtools/librepo/librepo_git.bb   |   4 +-
 ...-not-add-include-and-library-directories-.patch |  32 --
 .../python-backports-lzma_git.bb   |  21 -
 .../0001-Add-python-3-compatibility.patch  | 552 +
 ...hon-iniparse_0.4.bb => python3-iniparse_0.4.bb} |   8 +-
 ...ython-pygpgme_0.3.bb => python3-pygpgme_0.3.bb} |   6 +-
 ...N_ABI-when-searching-for-python-libraries.patch |  30 ++
 meta/recipes-devtools/rpm/rpm_git.bb   |  16 +-
 16 files changed, 621 insertions(+), 133 deletions(-)
 delete mode 100644 
meta/recipes-devtools/dnf/dnf/0028-Use-backports.lzma-not-lzma.patch
 delete mode 100644 
meta/recipes-devtools/python-backports-lzma/python-backports-lzma/0001-setup.py-do-not-add-include-and-library-directories-.patch
 delete mode 100644 
meta/recipes-devtools/python-backports-lzma/python-backports-lzma_git.bb
 create mode 100644 
meta/recipes-devtools/python/python3-iniparse/0001-Add-python-3-compatibility.patch
 rename meta/recipes-devtools/python/{python-iniparse_0.4.bb => 
python3-iniparse_0.4.bb} (75%)
 rename meta/recipes-devtools/python/{python-pygpgme_0.3.bb => 
python3-pygpgme_0.3.bb} (86%)
 create mode 100644 
meta/recipes-devtools/rpm/files/0001-Add-PYTHON_ABI-when-searching-for-python-libraries.patch

diff --git a/meta/classes/rootfs_rpm.bbclass b/meta/classes/rootfs_rpm.bbclass
index af0f23877ac..7f305f51ca2 100644
--- a/meta/classes/rootfs_rpm.bbclass
+++ b/meta/classes/rootfs_rpm.bbclass
@@ -11,8 +11,8 @@ export STAGING_LIBDIR
 # Add 100Meg of extra space for dnf
 IMAGE_ROOTFS_EXTRA_SPACE_append = "${@bb.utils.contains("PACKAGE_INSTALL", 
"dnf", " + 102400", "" ,d)}"
 
-# Dnf is python based, so be sure python-native is available to us.
-EXTRANATIVEPATH += "python-native"
+# Dnf is python based, so be sure python3-native is available to us.
+EXTRANATIVEPATH += "python3-native"
 
 # opkg is needed for update-alternatives
 RPMROOTFSDEPENDS = "rpm-native:do_populate_sysroot \
diff --git a/meta/conf/distro/include/security_flags.inc 
b/meta/conf/distro/include/security_flags.inc
index 89fd45b859c..6df184213e7 100644
--- a/meta/conf/distro/include/security_flags.inc
+++ b/meta/conf/distro/include/security_flags.inc
@@ -72,12 +72,11 @@ SECURITY_CFLAGS_pn-openssl = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-opensp = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-ppp = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python = "${SECURITY_NO_PIE_CFLAGS}"
-SECURITY_CFLAGS_pn-python-backports-lzma = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python-pycurl = "${SECURITY_NO_PIE_CFLAGS}"
-SECURITY_CFLAGS_pn-python-pygpgme = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python-numpy = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python3-numpy = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python3-pycairo = "${SECURITY_NO_PIE_CFLAGS}"
+SECURITY_CFLAGS_pn-python3-pygpgme = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python3 = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-syslinux = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-slang = "${SECURITY_NO_PIE_CFLAGS}"
diff --git a/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb 
b/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
index 1e69067eebf..31761368b72 100644
--- a/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
+++ b/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
@@ -17,9 +17,9 @@ S = "${WORKDIR}/git"
 DEPENDS = "expat curl glib-2.0 libxml2 openssl bzip2 zlib file sqlite3 xz rpm"
 DEPENDS_append_class-native = " file-replacement-native"
 
-inherit cmake pkgconfig bash-completion distutils-base
+inherit cmake pkgconfig bash-completion distutils3-base
 
-EXTRA_OECMAKE = " -DPYTHON_INSTALL_DIR=${PYTHON_SITEPACKAGES_DIR}"
+EXTRA_OECMAKE = " -DPYTHON_INSTALL_DIR=${PYTHON_SITEPACKAGES_DIR} 
-DPYTHON_DESIRED=3"
 
 BBCLASSEXTEND = "native"
 
diff --git 
a/meta/recipes-devtools/dnf/dnf/0028-Use-backports.lzma-not-lzma.patch 
b/meta/recipes-devtools/dnf/dnf/0028-Use-backports.lzma-not-lzma.patch
deleted file mode 100644
index 57038a8c7d5..000
--- a/meta/recipes-devtools/dnf/dnf/0028-Use-backports.lzma-not-lzma.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From 89af5c84d4b920d22ae882fcc5ab71ba09443cea Mon Sep 17 00:00:00 2001
-From: Alexander Kanavin 
-Date: Fri, 30 Dec 2016 18:28:18 +0200
-Subject: [PATCH 28/30] Use backports.lzma, not lzma
-
-This 

[OE-core] [PATCHv4 1/2] python3: do not hardcode "lib" into site-packages search path

[Alexander Kanavin]

This was not working in multilib or x32 setups and amazingly, was not
noticed until now.

The actual modification is in Lib/site.py, the rest is just devtool moving 
things around in the patch.

Signed-off-by: Alexander Kanavin 
---
 .../python/python3/python-3.3-multilib.patch   | 290 -
 1 file changed, 165 insertions(+), 125 deletions(-)

diff --git a/meta/recipes-devtools/python/python3/python-3.3-multilib.patch 
b/meta/recipes-devtools/python/python3/python-3.3-multilib.patch
index 860190340e2..08c4403cbfa 100644
--- a/meta/recipes-devtools/python/python3/python-3.3-multilib.patch
+++ b/meta/recipes-devtools/python/python3/python-3.3-multilib.patch
@@ -1,16 +1,34 @@
-Upstream-Status: Pending
-
-get the sys.lib from python itself and do not use hardcoded value of 'lib'
+From 51fe6f22d0ba113674fb358bd11d75fe659bd26e Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Tue, 14 May 2013 15:00:26 -0700
+Subject: [PATCH 01/13] get the sys.lib from python itself and do not use
+ hardcoded value of 'lib'
 
 02/2015 Rebased for 3.4.2
 
+Upstream-Status: Pending
 Signed-off-by: Khem Raj 
 Signed-off-by: Alejandro Hernandez 
 
-Index: Python-3.5.2/Include/pythonrun.h
-===
 Python-3.5.2.orig/Include/pythonrun.h
-+++ Python-3.5.2/Include/pythonrun.h
+---
+ Include/pythonrun.h  |  3 +++
+ Lib/distutils/command/install.py |  4 +++-
+ Lib/pydoc.py |  2 +-
+ Lib/site.py  |  4 ++--
+ Lib/sysconfig.py | 18 +-
+ Lib/trace.py |  4 ++--
+ Makefile.pre.in  |  7 +--
+ Modules/getpath.c| 10 +-
+ Python/getplatform.c | 20 
+ Python/sysmodule.c   |  4 
+ configure.ac | 35 +++
+ setup.py |  9 -
+ 12 files changed, 97 insertions(+), 23 deletions(-)
+
+diff --git a/Include/pythonrun.h b/Include/pythonrun.h
+index 9c2e813..2f79cb6 100644
+--- a/Include/pythonrun.h
 b/Include/pythonrun.h
 @@ -23,6 +23,9 @@ typedef struct {
  } PyCompilerFlags;
  #endif
@@ -21,10 +39,10 @@ Index: Python-3.5.2/Include/pythonrun.h
  #ifndef Py_LIMITED_API
  PyAPI_FUNC(int) PyRun_SimpleStringFlags(const char *, PyCompilerFlags *);
  PyAPI_FUNC(int) PyRun_AnyFileFlags(FILE *, const char *, PyCompilerFlags *);
-Index: Python-3.5.2/Lib/distutils/command/install.py
-===
 Python-3.5.2.orig/Lib/distutils/command/install.py
-+++ Python-3.5.2/Lib/distutils/command/install.py
+diff --git a/Lib/distutils/command/install.py 
b/Lib/distutils/command/install.py
+index 67db007..b46b45b 100644
+--- a/Lib/distutils/command/install.py
 b/Lib/distutils/command/install.py
 @@ -19,6 +19,8 @@ from site import USER_BASE
  from site import USER_SITE
  HAS_USER_SITE = True
@@ -43,10 +61,10 @@ Index: Python-3.5.2/Lib/distutils/command/install.py
  'headers': 
'$base/include/python$py_version_short$abiflags/$dist_name',
  'scripts': '$base/bin',
  'data'   : '$base',
-Index: Python-3.5.2/Lib/pydoc.py
-===
 Python-3.5.2.orig/Lib/pydoc.py
-+++ Python-3.5.2/Lib/pydoc.py
+diff --git a/Lib/pydoc.py b/Lib/pydoc.py
+index 3ca08c9..6528730 100755
+--- a/Lib/pydoc.py
 b/Lib/pydoc.py
 @@ -384,7 +384,7 @@ class Doc:
  docmodule = docclass = docroutine = docother = docproperty = docdata = 
fail
  
@@ -56,10 +74,75 @@ Index: Python-3.5.2/Lib/pydoc.py
 "python%d.%d" %  
sys.version_info[:2])):
  """Return the location of module docs or None"""
  
-Index: Python-3.5.2/Lib/trace.py
-===
 Python-3.5.2.orig/Lib/trace.py
-+++ Python-3.5.2/Lib/trace.py
+diff --git a/Lib/site.py b/Lib/site.py
+index 3f78ef5..511931e 100644
+--- a/Lib/site.py
 b/Lib/site.py
+@@ -303,12 +303,12 @@ def getsitepackages(prefixes=None):
+ seen.add(prefix)
+ 
+ if os.sep == '/':
+-sitepackages.append(os.path.join(prefix, "lib",
++sitepackages.append(os.path.join(prefix, sys.lib,
+ "python" + sys.version[:3],
+ "site-packages"))
+ else:
+ sitepackages.append(prefix)
+-sitepackages.append(os.path.join(prefix, "lib", "site-packages"))
++sitepackages.append(os.path.join(prefix, sys.lib, 
"site-packages"))
+ if sys.platform == "darwin":
+ # for framework builds *only* we add the standard Apple
+ # locations.
+diff --git a/Lib/sysconfig.py b/Lib/sysconfig.py
+index 

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Burton, Ross]

On 26 March 2017 at 22:14, Denys Dmytriyenko  wrote:

> At least 2 typos in the description...
>

Typos aside, this is past the M3 deadline but RC2 is running late, is there
a good reason to have the upgrade in?

Also what boards has it been tested on?  As it's from Otavio I presume the
Freescale boards have been tested.  Denys, have you tested this version on
your boards?

Cheers
Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Otavio Salvador]

On Sun, Mar 26, 2017 at 6:14 PM, Denys Dmytriyenko  wrote:
> On Sun, Mar 26, 2017 at 05:08:13PM -0300, Otavio Salvador wrote:
>> Ths 2017.03 release is out since March 13th 2017 and is the latest
>> stable release prior Pyro release.
>
> At least 2 typos in the description...

Sent a v2.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v2] u-boot: Update to 2017.03 release

[Otavio Salvador]

This 2017.03 release is out since March 13th, 2017 and is the latest
stable release prior Pyro release.

Signed-off-by: Otavio Salvador 
---

Changes in v2:
- Fix typo in commit log

 .../u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} | 2 +-
 .../u-boot/{u-boot-fw-utils_2017.01.bb => u-boot-fw-utils_2017.03.bb}   | 0
 .../u-boot/{u-boot-mkimage_2017.01.bb => u-boot-mkimage_2017.03.bb} | 0
 meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb}| 0
 4 files changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-bsp/u-boot/{u-boot-common_2017.01.inc => 
u-boot-common_2017.03.inc} (86%)
 rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.01.bb => 
u-boot-fw-utils_2017.03.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.01.bb => 
u-boot-mkimage_2017.03.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb} (100%)

diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc 
b/meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
similarity index 86%
rename from meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
rename to meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
index df24c853dd..c115f36831 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
@@ -7,7 +7,7 @@ PE = "1"
 
 # We use the revision in order to avoid having to fetch it from the
 # repo during parse
-SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149"
+SRCREV = "8537ddd769f460d7fb7a62a3dcc9669049702e51"
 
 SRC_URI = "git://git.denx.de/u-boot.git"
 
diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb 
b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb
rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb 
b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb
rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.01.bb 
b/meta/recipes-bsp/u-boot/u-boot_2017.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot_2017.01.bb
rename to meta/recipes-bsp/u-boot/u-boot_2017.03.bb
-- 
2.12.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCHv3 1/2] python3: do not hardcode "lib" into site-packages search path

[Alexander Kanavin]

On 03/27/2017 03:58 PM, Burton, Ross wrote:


+
file://0001-Do-not-hardcode-lib-into-site-packages-path.patch \


This should probably be added
to meta/recipes-devtools/python/python3/python-3.3-multilib.patch
instead of being in a separate patch.


Sure, but the patch that does that isn't particularly easy to read, 
because devtool moves things around when modifying patches. You'll see 
in a second.


Alex

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/2] oeqa: tolerate interrupted select() while waiting for qemu

[Patrick Ohly]

Sometimes, the OEQA utility code aborts with:

   ...
   File ".../meta/lib/oeqa/utils/qemurunner.py", line 131, in start
 return self.launch(launch_cmd, qemuparams=qemuparams, get_ip=get_ip, 
extra_bootparams=extra_bootparams)
   File ".../meta/lib/oeqa/utils/qemurunner.py", line 259, in launch
 sread, swrite, serror = select.select(socklist, [], [], 5)
  InterruptedError: [Errno 4] Interrupted system call

strace shows that this is because of a SIGWINCH:

   Connection from 127.0.0.1:52668
   select(21, [20], [], [], {5, 0})= ? ERESTARTNOHAND (To be restarted 
if no handler)
   --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---

This is related to some special conditions:
 * whether qemu opens a graphical console window (enabled in Poky by default)
 * where that window gets opened
 * whether the window manager changes the size of the shell window (mine
   is a tiling window manager and reorders and resizes windows automatically)

Ignoring the interrupted system calls avoids the problem. Code elsewhere (for 
example,
run() in ssh.py) already does the same thing.

Signed-off-by: Patrick Ohly 
---
 meta/lib/oeqa/utils/qemurunner.py | 10 --
 meta/lib/oeqa/utils/qemutinyrunner.py |  5 -
 2 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index cd79f21..ba44b96 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -256,7 +256,10 @@ class QemuRunner:
 bootlog = ''
 data = b''
 while time.time() < endtime and not stopread:
-sread, swrite, serror = select.select(socklist, [], [], 5)
+try:
+sread, swrite, serror = select.select(socklist, [], [], 5)
+except InterruptedError:
+continue
 for sock in sread:
 if sock is self.server_socket:
 qemusock, addr = self.server_socket.accept()
@@ -437,7 +440,10 @@ class QemuRunner:
 if now >= end:
 data += "<<< run_serial(): command timed out after %d seconds 
without output >>>\r\n\r\n" % timeout
 break
-sread, _, _ = select.select([self.server_socket],[],[], end - now)
+try:
+sread, _, _ = select.select([self.server_socket],[],[], end - 
now)
+except InterruptedError:
+continue
 if sread:
 answer = self.server_socket.recv(1024)
 if answer:
diff --git a/meta/lib/oeqa/utils/qemutinyrunner.py 
b/meta/lib/oeqa/utils/qemutinyrunner.py
index b1009a0..df5f9dd 100644
--- a/meta/lib/oeqa/utils/qemutinyrunner.py
+++ b/meta/lib/oeqa/utils/qemutinyrunner.py
@@ -114,7 +114,10 @@ class QemuTinyRunner(QemuRunner):
 stopread = False
 endtime = time.time()+timeout
 while time.time()http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/2] oeqa: QEMU_USE_KVM can list machines

[Patrick Ohly]

Previously, QEMU_USE_KVM=True enabled the use of kvm only when "x86"
was in the MACHINE name. That is too limiting, because for example
intel-corei7-64 can also use kvm but it wasn't possible to enable that
without changing OE-core.

That traditional usage is still supported. In addition, QEMU_USE_KVM
can be set to a list of space-separated MACHINE names for which kvm is
to be enabled.

Signed-off-by: Patrick Ohly 
---
 meta/classes/testimage.bbclass | 4 +++-
 meta/lib/oeqa/targetcontrol.py | 7 ---
 2 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/meta/classes/testimage.bbclass b/meta/classes/testimage.bbclass
index bfe5714..a259423 100644
--- a/meta/classes/testimage.bbclass
+++ b/meta/classes/testimage.bbclass
@@ -210,7 +210,9 @@ def testimage_main(d):
 
 # Get use_kvm
 qemu_use_kvm = d.getVar("QEMU_USE_KVM")
-if qemu_use_kvm and qemu_use_kvm == 'True' and 'x86' in machine:
+if qemu_use_kvm and \
+   (qemu_use_kvm == 'True' and 'x86' in machine or \
+d.getVar('MACHINE') in qemu_use_kvm.split()):
 kvm = True
 else:
 kvm = False
diff --git a/meta/lib/oeqa/targetcontrol.py b/meta/lib/oeqa/targetcontrol.py
index 47cfe85..b256f1b 100644
--- a/meta/lib/oeqa/targetcontrol.py
+++ b/meta/lib/oeqa/targetcontrol.py
@@ -131,9 +131,10 @@ class QemuTarget(BaseTarget):
 dump_target_cmds = d.getVar("testimage_dump_target")
 dump_host_cmds = d.getVar("testimage_dump_host")
 dump_dir = d.getVar("TESTIMAGE_DUMP_DIR")
-if d.getVar("QEMU_USE_KVM", False) is not None \
-   and d.getVar("QEMU_USE_KVM", False) == "True" \
-   and "x86" in d.getVar("MACHINE"):
+qemu_use_kvm = d.getVar("QEMU_USE_KVM")
+if qemu_use_kvm and \
+   (qemu_use_kvm == "True" and "x86" in d.getVar("MACHINE") or \
+d.getVar("MACHINE") in qemu_use_kvm.split()):
 use_kvm = True
 else:
 use_kvm = False
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/2] oeqa: runqemu enhancements

[Patrick Ohly]

Just something that I happened to notice when using oe-selftest a bit
more... Both patches are non-essential enhancements and thus can wait
until after 2.4.

Patrick Ohly (2):
  oeqa: tolerate interrupted select() while waiting for qemu
  oeqa: QEMU_USE_KVM can list machines

 meta/classes/testimage.bbclass|  4 +++-
 meta/lib/oeqa/targetcontrol.py|  7 ---
 meta/lib/oeqa/utils/qemurunner.py | 10 --
 meta/lib/oeqa/utils/qemutinyrunner.py |  5 -
 4 files changed, 19 insertions(+), 7 deletions(-)

base-commit: ff4a94fdf7b42cfd7c5114f29734078874d753b8
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCHv3 1/2] python3: do not hardcode "lib" into site-packages search path

[Burton, Ross]

On 27 March 2017 at 13:53, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:

> +file://0001-Do-not-hardcode-lib-into-site-packages-path.patch
> \
>

This should probably be added
to meta/recipes-devtools/python/python3/python-3.3-multilib.patch instead
of being in a separate patch.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCHv3 2/2] dnf: move the entire dnf/rpm4 stack to Python 3

[Alexander Kanavin]

[YOCTO #11180]

Signed-off-by: Alexander Kanavin 
---
 meta/classes/rootfs_rpm.bbclass|   4 +-
 meta/conf/distro/include/security_flags.inc|   3 +-
 .../createrepo-c/createrepo-c_git.bb   |   4 +-
 .../dnf/dnf/0028-Use-backports.lzma-not-lzma.patch |  30 --
 .../dnf/0030-Run-python-scripts-using-env.patch|   6 +-
 meta/recipes-devtools/dnf/dnf_git.bb   |  15 +-
 meta/recipes-devtools/libcomps/libcomps_git.bb |   6 +-
 meta/recipes-devtools/libdnf/libdnf_git.bb |  17 +-
 meta/recipes-devtools/librepo/librepo_git.bb   |   4 +-
 ...-not-add-include-and-library-directories-.patch |  32 --
 .../python-backports-lzma_git.bb   |  21 -
 .../0001-Add-python-3-compatibility.patch  | 552 +
 ...hon-iniparse_0.4.bb => python3-iniparse_0.4.bb} |   8 +-
 ...ython-pygpgme_0.3.bb => python3-pygpgme_0.3.bb} |   6 +-
 ...N_ABI-when-searching-for-python-libraries.patch |  30 ++
 meta/recipes-devtools/rpm/rpm_git.bb   |  16 +-
 16 files changed, 621 insertions(+), 133 deletions(-)
 delete mode 100644 
meta/recipes-devtools/dnf/dnf/0028-Use-backports.lzma-not-lzma.patch
 delete mode 100644 
meta/recipes-devtools/python-backports-lzma/python-backports-lzma/0001-setup.py-do-not-add-include-and-library-directories-.patch
 delete mode 100644 
meta/recipes-devtools/python-backports-lzma/python-backports-lzma_git.bb
 create mode 100644 
meta/recipes-devtools/python/python3-iniparse/0001-Add-python-3-compatibility.patch
 rename meta/recipes-devtools/python/{python-iniparse_0.4.bb => 
python3-iniparse_0.4.bb} (75%)
 rename meta/recipes-devtools/python/{python-pygpgme_0.3.bb => 
python3-pygpgme_0.3.bb} (86%)
 create mode 100644 
meta/recipes-devtools/rpm/files/0001-Add-PYTHON_ABI-when-searching-for-python-libraries.patch

diff --git a/meta/classes/rootfs_rpm.bbclass b/meta/classes/rootfs_rpm.bbclass
index af0f23877ac..7f305f51ca2 100644
--- a/meta/classes/rootfs_rpm.bbclass
+++ b/meta/classes/rootfs_rpm.bbclass
@@ -11,8 +11,8 @@ export STAGING_LIBDIR
 # Add 100Meg of extra space for dnf
 IMAGE_ROOTFS_EXTRA_SPACE_append = "${@bb.utils.contains("PACKAGE_INSTALL", 
"dnf", " + 102400", "" ,d)}"
 
-# Dnf is python based, so be sure python-native is available to us.
-EXTRANATIVEPATH += "python-native"
+# Dnf is python based, so be sure python3-native is available to us.
+EXTRANATIVEPATH += "python3-native"
 
 # opkg is needed for update-alternatives
 RPMROOTFSDEPENDS = "rpm-native:do_populate_sysroot \
diff --git a/meta/conf/distro/include/security_flags.inc 
b/meta/conf/distro/include/security_flags.inc
index 89fd45b859c..6df184213e7 100644
--- a/meta/conf/distro/include/security_flags.inc
+++ b/meta/conf/distro/include/security_flags.inc
@@ -72,12 +72,11 @@ SECURITY_CFLAGS_pn-openssl = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-opensp = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-ppp = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python = "${SECURITY_NO_PIE_CFLAGS}"
-SECURITY_CFLAGS_pn-python-backports-lzma = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python-pycurl = "${SECURITY_NO_PIE_CFLAGS}"
-SECURITY_CFLAGS_pn-python-pygpgme = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python-numpy = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python3-numpy = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python3-pycairo = "${SECURITY_NO_PIE_CFLAGS}"
+SECURITY_CFLAGS_pn-python3-pygpgme = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-python3 = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-syslinux = "${SECURITY_NO_PIE_CFLAGS}"
 SECURITY_CFLAGS_pn-slang = "${SECURITY_NO_PIE_CFLAGS}"
diff --git a/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb 
b/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
index 1e69067eebf..31761368b72 100644
--- a/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
+++ b/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb
@@ -17,9 +17,9 @@ S = "${WORKDIR}/git"
 DEPENDS = "expat curl glib-2.0 libxml2 openssl bzip2 zlib file sqlite3 xz rpm"
 DEPENDS_append_class-native = " file-replacement-native"
 
-inherit cmake pkgconfig bash-completion distutils-base
+inherit cmake pkgconfig bash-completion distutils3-base
 
-EXTRA_OECMAKE = " -DPYTHON_INSTALL_DIR=${PYTHON_SITEPACKAGES_DIR}"
+EXTRA_OECMAKE = " -DPYTHON_INSTALL_DIR=${PYTHON_SITEPACKAGES_DIR} 
-DPYTHON_DESIRED=3"
 
 BBCLASSEXTEND = "native"
 
diff --git 
a/meta/recipes-devtools/dnf/dnf/0028-Use-backports.lzma-not-lzma.patch 
b/meta/recipes-devtools/dnf/dnf/0028-Use-backports.lzma-not-lzma.patch
deleted file mode 100644
index 57038a8c7d5..000
--- a/meta/recipes-devtools/dnf/dnf/0028-Use-backports.lzma-not-lzma.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From 89af5c84d4b920d22ae882fcc5ab71ba09443cea Mon Sep 17 00:00:00 2001
-From: Alexander Kanavin 
-Date: Fri, 30 Dec 2016 18:28:18 +0200
-Subject: [PATCH 28/30] Use backports.lzma, not lzma
-
-This 

[OE-core] [PATCHv3 1/2] python3: do not hardcode "lib" into site-packages search path

[Alexander Kanavin]

This was not working in multilib or x32 setups and amazingly, was not
noticed until now.

Signed-off-by: Alexander Kanavin 
---
 ...-not-hardcode-lib-into-site-packages-path.patch | 33 ++
 meta/recipes-devtools/python/python3_3.5.2.bb  |  1 +
 2 files changed, 34 insertions(+)
 create mode 100644 
meta/recipes-devtools/python/python3/0001-Do-not-hardcode-lib-into-site-packages-path.patch

diff --git 
a/meta/recipes-devtools/python/python3/0001-Do-not-hardcode-lib-into-site-packages-path.patch
 
b/meta/recipes-devtools/python/python3/0001-Do-not-hardcode-lib-into-site-packages-path.patch
new file mode 100644
index 000..286ba352b0a
--- /dev/null
+++ 
b/meta/recipes-devtools/python/python3/0001-Do-not-hardcode-lib-into-site-packages-path.patch
@@ -0,0 +1,33 @@
+From f2bb0a0e3c4eef4fa3853920ecc1cc59618f1409 Mon Sep 17 00:00:00 2001
+From: Alexander Kanavin 
+Date: Mon, 27 Mar 2017 15:33:43 +0300
+Subject: [PATCH] Do not hardcode "lib" into site-packages path.
+
+Upstream-Status: Inappropriate [oe-core specific]
+Signed-off-by: Alexander Kanavin 
+---
+ Lib/site.py | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/Lib/site.py b/Lib/site.py
+index 3f78ef5..511931e 100644
+--- a/Lib/site.py
 b/Lib/site.py
+@@ -303,12 +303,12 @@ def getsitepackages(prefixes=None):
+ seen.add(prefix)
+ 
+ if os.sep == '/':
+-sitepackages.append(os.path.join(prefix, "lib",
++sitepackages.append(os.path.join(prefix, sys.lib,
+ "python" + sys.version[:3],
+ "site-packages"))
+ else:
+ sitepackages.append(prefix)
+-sitepackages.append(os.path.join(prefix, "lib", "site-packages"))
++sitepackages.append(os.path.join(prefix, sys.lib, 
"site-packages"))
+ if sys.platform == "darwin":
+ # for framework builds *only* we add the standard Apple
+ # locations.
+-- 
+2.11.0
+
diff --git a/meta/recipes-devtools/python/python3_3.5.2.bb 
b/meta/recipes-devtools/python/python3_3.5.2.bb
index 2ff7c9e2780..43cc125b506 100644
--- a/meta/recipes-devtools/python/python3_3.5.2.bb
+++ b/meta/recipes-devtools/python/python3_3.5.2.bb
@@ -37,6 +37,7 @@ SRC_URI += "\
 file://configure.ac-fix-LIBPL.patch \
 file://python3-fix-CVE-2016-1000110.patch \
 file://upstream-random-fixes.patch \
+file://0001-Do-not-hardcode-lib-into-site-packages-path.patch \
"
 SRC_URI[md5sum] = "8906efbacfcdc7c3c9198aeefafd159e"
 SRC_URI[sha256sum] = 
"0010f56100b9b74259ebcd5d4b295a32324b58b517403a10d1a2aa7cb22bca40"
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCHv2] dnf: move the entire dnf/rpm4 stack to Python 3

[Alexander Kanavin]

On 03/25/2017 07:56 PM, Richard Purdie wrote:

[YOCTO #11180]


So close but:

https://autobuilder.yocto.io/builders/nightly-multilib/builds/226
https://autobuilder.yocto.io/builders/nightly-x32/builds/206


This is actually a bug in our target Python 3 installation. No idea how 
it went unnoticed - does no one use Python 3 on target with multilib or 
x32 at all?



Python 3.5.2 (default, Mar 27 2017, 11:43:41)
[GCC 6.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import site
>>> site.getsitepackages()
['/usr/lib/python3.5/site-packages']
   ^^^ !!!



Alex

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] xserver-nodm-init: option to remove cursor

[Burton, Ross]

On 25 March 2017 at 05:19, Trevor Woerner  wrote:

> Add a PACKAGECONFIG option to allow the user to disable the mouse
> cursor/pointer in the X server. This might be useful where a
> touchscreen is used.
>

This is what the touchscreen variable in the formfactor recipe is for.  Is
this not sufficient?

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

[Burton, Ross]

On 27 March 2017 at 11:34, Robert Yang  wrote:

> [snip]
> /bin/sh: sudo: command not found
> runqemu - ERROR - Failed to setup tap device. Run runqemu-gen-tapdevs to
> manually create.
> [snip]
>

This only happens if the tapdevs haven't already been generated, in which
case sudo isn't required.  Should it be a NONFATAL tool?

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] image_types: perform fsck on created ext image

[Enrico Joerns]

Hi Daniel,

On 03/27/2017 09:37 AM, Daniel Schultz wrote:

I have sent fixes for the same problem on Monday.
These include a fix of the wrong return code after optimizations (now it
returns 0) and an fsck execution after the creation of EXT partitions.

The patch which is identical to yours wasn't applied so far, the other
ones were.


ouh, we should have checked that before, but we did not assume that
someone would have posted a fix for this relatively old behavior during
the last days. Reality disabused us... Anyway, good to see that we are
not the only one that stumbled across this issue ;)

But, there is another difference between our patches. We use `-pvfD`,
while you use `-fy` as an fsck.extN option.

I would expect `-p` to be sufficient for letting fsck perform minor
optimizations. If you use `-y` instead, fsck will fix also real issues.
This is not what it should do here, even if it will return 1 afterwards.
If the file system was created with errors I guess we should let the
image creation fail without further touching the ext4.

-D will let fsck perform further directory optimizations
-v might be helpful for debugging purpose


Yes, that's better. I will them also apply to the WIC tools.

Do you think the test expression is still needed?
My opinion is, that it will obfuscate the return code of fsck to either
true or false. This could confuse other people. What do you think?


well, as far as I see it, the test expression will only be needed if 
fsck still returns an error code for those uncritical optimizations it 
performs. With the backported patch applied you had in your series i 
guess there should be no need for the test expression, but I did not 
test it yet in this setup.


Best regards, Enrico

--
Pengutronix e.K.   | Enrico Jörns|
Industrial Linux Solutions | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/2] oe-find-native-sysroot: work with RSS

[Robert Yang]

The generic STAGING_DIR_NATIVE is gone since RSS, so when find
OECORE_NATIVE_SYSROOT, the user has to specify which recipe's
STAGING_DIR_NATIVE will be used as OECORE_NATIVE_SYSROOT.

* The usage is changed from ". oe-find-native-sysroot" to
  ". oe-find-native-sysroot ".
* The oe-run-native's usage has changed from
  "oe-run-native tool" to "oe-run-native native-recipe tool".

Signed-off-by: Robert Yang 
---
 scripts/oe-find-native-sysroot | 56 --
 scripts/oe-run-native  | 15 +++
 scripts/runqemu-export-rootfs  |  2 +-
 scripts/runqemu-extract-sdk|  2 +-
 4 files changed, 49 insertions(+), 26 deletions(-)

diff --git a/scripts/oe-find-native-sysroot b/scripts/oe-find-native-sysroot
index 13a5c46039..ad7b2d1fe8 100755
--- a/scripts/oe-find-native-sysroot
+++ b/scripts/oe-find-native-sysroot
@@ -9,7 +9,7 @@
 # it, e.g:
 #
 # SYSROOT_SETUP_SCRIPT=`which oe-find-native-sysroot`
-# . $SYSROOT_SETUP_SCRIPT
+# . $SYSROOT_SETUP_SCRIPT 
 #
 # This script will terminate execution of your calling program unless
 # you set a variable $SKIP_STRICT_SYSROOT_CHECK to a non-empty string
@@ -30,8 +30,8 @@
 # with this program; if not, write to the Free Software Foundation, Inc.,
 # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 
-if [ "$1" = '--help' -o "$1" = '-h' ] ; then
-echo 'Usage: oe-find-native-sysroot [-h|--help]'
+if [ "$1" = '--help' -o "$1" = '-h' -o $# -ne 1 ] ; then
+echo 'Usage: oe-find-native-sysroot  [-h|--help]'
 echo ''
 echo 'OpenEmbedded find-native-sysroot - helper script to set'
 echo 'environment variables OECORE_NATIVE_SYSROOT and PSEUDO'
@@ -39,11 +39,31 @@ if [ "$1" = '--help' -o "$1" = '-h' ] ; then
 echo 'executable binary'
 echo ''
 echo 'options:'
+echo '  recipe  its STAGING_DIR_NATIVE is used as native 
sysroot'
 echo '  -h, --help  show this help message and exit'
 echo ''
 exit 2
 fi
 
+# Global vars
+BITBAKE_E=""
+OECORE_NATIVE_SYSROOT=""
+
+set_oe_native_sysroot(){
+echo "Running bitbake -e $1"
+BITBAKE_E="`bitbake -e $1`"
+OECORE_NATIVE_SYSROOT=`echo "$BITBAKE_E" | grep ^STAGING_DIR_NATIVE | cut 
-d '"' -f2`
+
+if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
+# This indicates that there was an error running bitbake -e that
+# the user needs to be informed of
+echo "There was an error running bitbake to determine 
STAGING_DIR_NATIVE"
+echo "Here is the output from bitbake -e $1"
+echo $BITBAKE_E
+exit 1
+fi
+}
+
 if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
 BITBAKE=`which bitbake 2> /dev/null`
 if [ "x$BITBAKE" != "x" ]; then
@@ -54,10 +74,10 @@ if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
 exit 1
 fi
 touch conf/sanity.conf
-OECORE_NATIVE_SYSROOT=`bitbake -e | grep ^STAGING_DIR_NATIVE | cut 
-d '"' -f2`
+set_oe_native_sysroot $1
 rm -f conf/sanity.conf
 else
-OECORE_NATIVE_SYSROOT=`bitbake -e | grep ^STAGING_DIR_NATIVE | cut 
-d '"' -f2`
+set_oe_native_sysroot $1
 fi
 else
 echo "Error: Unable to locate bitbake command."
@@ -69,21 +89,11 @@ if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
 fi
 fi
 
-if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
-# This indicates that there was an error running bitbake -e that
-# the user needs to be informed of
-echo "There was an error running bitbake to determine STAGING_DIR_NATIVE"
-echo "Here is the output from bitbake -e"
-bitbake -e
-exit 1
-fi
-
-# Set up pseudo command
-if [ ! -e "$OECORE_NATIVE_SYSROOT/usr/bin/pseudo" ]; then
-echo "Error: Unable to find pseudo binary in 
$OECORE_NATIVE_SYSROOT/usr/bin/"
+if [ ! -e "$OECORE_NATIVE_SYSROOT/" ]; then
+echo "Error: $OECORE_NATIVE_SYSROOT doesn't exist."
 
 if [ "x$OECORE_DISTRO_VERSION" = "x" ]; then
-echo "Have you run 'bitbake meta-ide-support'?"
+echo "Have you run 'bitbake $1 -caddto_recipe_sysroot'?"
 else
 echo "This shouldn't happen - something is wrong with your toolchain 
installation"
 fi
@@ -92,4 +102,12 @@ if [ ! -e "$OECORE_NATIVE_SYSROOT/usr/bin/pseudo" ]; then
 exit 1
 fi
 fi
-PSEUDO="$OECORE_NATIVE_SYSROOT/usr/bin/pseudo"
+
+# Set up pseudo command
+pseudo="$OECORE_NATIVE_SYSROOT/usr/bin/pseudo"
+if [ -e "$pseudo" ]; then
+echo "PSEUDO=$pseudo"
+PSEUDO="$pseudo"
+else
+echo "PSEUDO $pseudo is not found."
+fi
diff --git a/scripts/oe-run-native b/scripts/oe-run-native
index f2453e705a..de3c02ed34 100755
--- a/scripts/oe-run-native
+++ b/scripts/oe-run-native
@@ -22,34 +22,39 @@
 #
 
 if [ $# -lt 1 -o "$1" = '--help' -o "$1" = '-h' ] ; then
-echo 'oe-run-native: error: the following arguments are required: '
-echo 'Usage: oe-run-native tool [parameters]'
+echo 'oe-run-native: error: the following arguments are 

[OE-core] [PATCH 0/2] oe-find-native-sysroot: make it work with RSS

[Robert Yang]

The following changes since commit 78928016f4cf38cf6751cb089200bf950d07ae93:

  classes: Replace "if test" file tests with POSIX file tests (2017-03-27 
11:08:28 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/rssfix
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/rssfix

Robert Yang (2):
  oe-run-native: OLDPATH -> OLD_PATH
  oe-find-native-sysroot: work with RSS

 scripts/oe-find-native-sysroot | 56 --
 scripts/oe-run-native  | 17 -
 scripts/runqemu-export-rootfs  |  2 +-
 scripts/runqemu-extract-sdk|  2 +-
 4 files changed, 50 insertions(+), 27 deletions(-)

-- 
2.11.0.rc2.dirty

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/2] oe-run-native: OLDPATH -> OLD_PATH

[Robert Yang]

It's a typo.

Signed-off-by: Robert Yang 
---
 scripts/oe-run-native | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/oe-run-native b/scripts/oe-run-native
index 7e26ea3fcc..f2453e705a 100755
--- a/scripts/oe-run-native
+++ b/scripts/oe-run-native
@@ -40,7 +40,7 @@ if [ -z "$SYSROOT_SETUP_SCRIPT" ]; then
 fi
 . $SYSROOT_SETUP_SCRIPT
 
-OLDPATH=$PATH
+OLD_PATH=$PATH
 
 # look for a tool only in native sysroot
 
PATH=$OECORE_NATIVE_SYSROOT/usr/bin:$OECORE_NATIVE_SYSROOT/bin:$OECORE_NATIVE_SYSROOT/usr/sbin:$OECORE_NATIVE_SYSROOT/sbin
-- 
2.11.0.rc2.dirty

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/1] bitbake.conf: add sudo to HOSTTOOLS

[Robert Yang]

Fixed:
$ bitbake meta-ide-support
$ . ./tmp/environment-setup-i586-poky-linux
$ runqemu tmp/deploy/images/qemux86/core-image-sato-qemux86.qemuboot.conf

[snip]
/bin/sh: sudo: command not found
runqemu - ERROR - Failed to setup tap device. Run runqemu-gen-tapdevs to 
manually create.
[snip]

The qemu can start, but the IP was wrong, this patch fixes the problem.

[YOCTO #11232]

Signed-off-by: Robert Yang 
---
 meta/conf/bitbake.conf | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index fa5445b65b..0b1d8d82e0 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -468,6 +468,9 @@ HOSTTOOLS += " \
 # Tools needed to run testimage runtime image testing
 HOSTTOOLS += "ps stty ip ssh scp ping"
 
+# Tools needed by runqemu in meta-ide-support environment
+HOSTTOOLS += "sudo"
+
 # Link to these if present
 HOSTTOOLS_NONFATAL += "ccache ld.bfd ld.gold gcc-ar gpg sftp nc socat sudo"
 
-- 
2.11.0.rc2.dirty

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/1] bitbake.conf: add sudo to HOSTTOOLS

[Robert Yang]

The following changes since commit 78928016f4cf38cf6751cb089200bf950d07ae93:

  classes: Replace "if test" file tests with POSIX file tests (2017-03-27 
11:08:28 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/tools
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/tools

Robert Yang (1):
  bitbake.conf: add sudo to HOSTTOOLS

 meta/conf/bitbake.conf | 3 +++
 1 file changed, 3 insertions(+)

-- 
2.11.0.rc2.dirty

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] another cleanup: "grep ... >/dev/null" -> "grep -q"?

[Burton, Ross]

On 25 March 2017 at 19:22, Robert P. J. Day  wrote:

>   1) can most of those be simplified with "grep -q"?
>

Yes.


>   2) is there any need for "egrep" in that last match?
>

egrep is grep -E, but that regex is a valid basic RE, so that can just be
grep.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] oeqa/selftest: don't use cleanall in selftests

[Joshua Lock]

* devtool: oeqa.selftest.devtool.DevtoolTests is taking 4 or more hours on the
  autobuilder because the cleanall call deletes the tarball of the kernel
  source, forcing a large clone which is especially long on an NFS mount.

  The cleanall invocation isn't really required here and switching to clean
  instead should avoid hours of re-cloning the same repository each time we
  run oe-selftest on the autobuilder.
* buildoptions: We only need to ensure the first image isn't an incremental
  image, clean will suffice here.
* runtime-test: no need to clean up the artefacts generated during the test,
  let's leave that to a higher level process rather than using the cleanall
  hammer.

Signed-off-by: Joshua Lock 
---
 meta/lib/oeqa/selftest/buildoptions.py | 2 +-
 meta/lib/oeqa/selftest/devtool.py  | 2 +-
 meta/lib/oeqa/selftest/runtime-test.py | 6 --
 3 files changed, 2 insertions(+), 8 deletions(-)

diff --git a/meta/lib/oeqa/selftest/buildoptions.py 
b/meta/lib/oeqa/selftest/buildoptions.py
index 7ace747..d155f64 100644
--- a/meta/lib/oeqa/selftest/buildoptions.py
+++ b/meta/lib/oeqa/selftest/buildoptions.py
@@ -16,7 +16,7 @@ class ImageOptionsTests(oeSelfTest):
 image_pkgtype = get_bb_var("IMAGE_PKGTYPE")
 if image_pkgtype != 'rpm':
 self.skipTest('Not using RPM as main package format')
-bitbake("-c cleanall core-image-minimal")
+bitbake("-c clean core-image-minimal")
 self.write_config('INC_RPM_IMAGE_GEN = "1"')
 self.append_config('IMAGE_FEATURES += "ssh-server-openssh"')
 bitbake("core-image-minimal")
diff --git a/meta/lib/oeqa/selftest/devtool.py 
b/meta/lib/oeqa/selftest/devtool.py
index a160c83..7f9efe6 100644
--- a/meta/lib/oeqa/selftest/devtool.py
+++ b/meta/lib/oeqa/selftest/devtool.py
@@ -1654,7 +1654,7 @@ class DevtoolTests(DevtoolBase):
 
 tmpconfig = os.path.join(buildir, '.config')
 #Step 3
-bitbake('linux-yocto -c cleanall')
+bitbake('linux-yocto -c clean')
 #Step 4.1
 runCmd('devtool modify virtual/kernel -x %s' % tempdir)
 self.assertTrue(os.path.exists(os.path.join(tempdir, 'Makefile')),
diff --git a/meta/lib/oeqa/selftest/runtime-test.py 
b/meta/lib/oeqa/selftest/runtime-test.py
index ea31c18..e498d04 100644
--- a/meta/lib/oeqa/selftest/runtime-test.py
+++ b/meta/lib/oeqa/selftest/runtime-test.py
@@ -193,8 +193,6 @@ postinst-delayed-t \
present on rootfs dir.
 4. Boot the image created on qemu and verify that the 
file
created by postinst_boot recipe is present on image.
-5. Clean the packages and image created to test with
-   different package managers
 Expected:   The files are successfully created during rootfs and 
boot
 time for 3 different package managers: rpm,ipk,deb and
 for initialization managers: sysvinit and systemd.
@@ -237,7 +235,3 @@ postinst-delayed-t \
 sshargs = '-o UserKnownHostsFile=/dev/null -o 
StrictHostKeyChecking=no'
 result = runCmd('ssh %s root@%s %s' % (sshargs, qemu.ip, 
testcommand))
 self.assertEqual(result.status, 0, 'File %s was not 
created at firts boot'% fileboot_name)
-
-#Step 5
-bitbake(' %s %s -c cleanall' % (rootfs_pkg, boot_pkg))
-bitbake('core-image-minimal -c cleanall')
-- 
2.9.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v3 2/3] oeqa: allow customizing image used by runqemu()

[Patrick Ohly]

runqemu() takes all parameters for the virtual machine from the
variables of the given recipe. By allowing the caller to provide a
hash with variables that get applied locally, the caller gets more
control.

Here's the intended usage:

   
   overrides = {
'DEPLOY_DIR_IMAGE': self.resultdir,
'IMAGE_LINK_NAME': 'internal-image-%s' % self.image_arch,
   }
   with runqemu('refkit-installer-image', ssh=False,
 overrides=overrides) as qemu:
   

This can be used to replace the image completely with something else
or to copy it before allowing runqemu() to write into it.

Signed-off-by: Patrick Ohly 
---
 meta/lib/oeqa/utils/commands.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/utils/commands.py b/meta/lib/oeqa/utils/commands.py
index 3dfff0f..88c9bb1 100644
--- a/meta/lib/oeqa/utils/commands.py
+++ b/meta/lib/oeqa/utils/commands.py
@@ -225,7 +225,7 @@ def create_temp_layer(templayerdir, templayername, 
priority=999, recipepathspec=
 
 
 @contextlib.contextmanager
-def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None):
+def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None, overrides={}):
 """
 launch_cmd means directly run the command, don't need set rootfs or env 
vars.
 """
@@ -247,6 +247,8 @@ def runqemu(pn, ssh=True, runqemuparams='', 
image_fstype=None, launch_cmd=None, 
 tinfoil.config_data.setVar("FIND_ROOTFS", '1')
 
 recipedata = tinfoil.parse_recipe(pn)
+for key, value in overrides.items():
+recipedata.setVar(key, value)
 
 # The QemuRunner log is saved out, but we need to ensure it is at the 
right
 # log level (and then ensure that since it's a child of the BitBake 
logger,
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v3 1/3] oeqa: allow extending qemuparams="..."

[Patrick Ohly]

Sometimes it is useful to reconfigure the qemu virtual machine
directly. runqemu has the "qemuparams" parameter for that, and the
underlying start() methods also supported modifying that via their
"params" parameter. Only the runqemu() wrapper function lacked
a way to specify additional parameters.

One potential usage is to attach additional disks.

Signed-off-by: Patrick Ohly 
---
 meta/lib/oeqa/utils/commands.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/utils/commands.py b/meta/lib/oeqa/utils/commands.py
index cd7a5e3..3dfff0f 100644
--- a/meta/lib/oeqa/utils/commands.py
+++ b/meta/lib/oeqa/utils/commands.py
@@ -225,7 +225,7 @@ def create_temp_layer(templayerdir, templayername, 
priority=999, recipepathspec=
 
 
 @contextlib.contextmanager
-def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None):
+def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None):
 """
 launch_cmd means directly run the command, don't need set rootfs or env 
vars.
 """
@@ -276,7 +276,7 @@ def runqemu(pn, ssh=True, runqemuparams='', 
image_fstype=None, launch_cmd=None):
 try:
 qemu.deploy()
 try:
-qemu.start(ssh=ssh, runqemuparams=runqemuparams, 
launch_cmd=launch_cmd)
+qemu.start(params=qemuparams, ssh=ssh, 
runqemuparams=runqemuparams, launch_cmd=launch_cmd)
 except bb.build.FuncFailed:
 raise Exception('Failed to start QEMU - see the logs in %s' % 
logdir)
 
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v3 0/3] oeqa: more control over qemu

[Patrick Ohly]

I'm currently working on testing an installer image. During that test
I need to:
- boot with two drives attached to the virtual machine (installer image
  and internal disk)
- install to internal disk
- reboot with just the internal disk

There were several problems doing that:
- attaching second disk via qemuparams was not possible
- run_serial() timed out too early during the long-running install command
- writes to the internal disks were discarded
- booting with only the non-standard internal disk instead of the
  recipe's image was not possible

V2: rebased on top of master-next + Robert's "runqemu: add selftest" series,
no other changes (merge V1 if not taking Robert's patches first)
V3: rebased on top of current master

Patrick Ohly (3):
  oeqa: allow extending qemuparams="..."
  oeqa: allow customizing image used by runqemu()
  oeqa: allow persistent image writes in runqemu()

 meta/lib/oeqa/targetcontrol.py| 6 +++---
 meta/lib/oeqa/utils/commands.py   | 6 --
 meta/lib/oeqa/utils/qemurunner.py | 4 ++--
 3 files changed, 9 insertions(+), 7 deletions(-)

base-commit: b2a785f19fe25d244179b8672c846925da6d455a
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v3 3/3] oeqa: allow persistent image writes in runqemu()

[Patrick Ohly]

By default, runqemu() avoids modifying the image files that it boots
into by enabling the qemu snapshot mode. However, some tests may want
to test changes that must persists across reboots, so this mode
should be optional.

This can be combined by copying the image file to a temporary location
first and then booting with that copy. It's also useful when testing
with additional drives attached to a virtual machine.

Signed-off-by: Patrick Ohly 
---
 meta/lib/oeqa/targetcontrol.py| 6 +++---
 meta/lib/oeqa/utils/commands.py   | 4 ++--
 meta/lib/oeqa/utils/qemurunner.py | 4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/meta/lib/oeqa/targetcontrol.py b/meta/lib/oeqa/targetcontrol.py
index 40a2589..47cfe85 100644
--- a/meta/lib/oeqa/targetcontrol.py
+++ b/meta/lib/oeqa/targetcontrol.py
@@ -182,11 +182,11 @@ class QemuTarget(BaseTarget):
 logger.info("Qemu log file: %s" % self.qemulog)
 super(QemuTarget, self).deploy()
 
-def start(self, params=None, ssh=True, extra_bootparams='', 
runqemuparams='', launch_cmd=''):
+def start(self, params=None, ssh=True, extra_bootparams='', 
runqemuparams='', launch_cmd='', discard_writes=True):
 if launch_cmd:
-start = self.runner.launch(get_ip=ssh, launch_cmd=launch_cmd)
+start = self.runner.launch(get_ip=ssh, launch_cmd=launch_cmd, 
discard_writes=discard_writes)
 else:
-start = self.runner.start(params, get_ip=ssh, 
extra_bootparams=extra_bootparams, runqemuparams=runqemuparams)
+start = self.runner.start(params, get_ip=ssh, 
extra_bootparams=extra_bootparams, runqemuparams=runqemuparams, 
discard_writes=discard_writes)
 
 if start:
 if ssh:
diff --git a/meta/lib/oeqa/utils/commands.py b/meta/lib/oeqa/utils/commands.py
index 88c9bb1..2951dfb 100644
--- a/meta/lib/oeqa/utils/commands.py
+++ b/meta/lib/oeqa/utils/commands.py
@@ -225,7 +225,7 @@ def create_temp_layer(templayerdir, templayername, 
priority=999, recipepathspec=
 
 
 @contextlib.contextmanager
-def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None, overrides={}):
+def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, 
launch_cmd=None, qemuparams=None, overrides={}, discard_writes=True):
 """
 launch_cmd means directly run the command, don't need set rootfs or env 
vars.
 """
@@ -278,7 +278,7 @@ def runqemu(pn, ssh=True, runqemuparams='', 
image_fstype=None, launch_cmd=None, 
 try:
 qemu.deploy()
 try:
-qemu.start(params=qemuparams, ssh=ssh, 
runqemuparams=runqemuparams, launch_cmd=launch_cmd)
+qemu.start(params=qemuparams, ssh=ssh, 
runqemuparams=runqemuparams, launch_cmd=launch_cmd, 
discard_writes=discard_writes)
 except bb.build.FuncFailed:
 raise Exception('Failed to start QEMU - see the logs in %s' % 
logdir)
 
diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index 95f5925..cd79f21 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -97,7 +97,7 @@ class QemuRunner:
 self._dump_host()
 raise SystemExit
 
-def start(self, qemuparams = None, get_ip = True, extra_bootparams = None, 
runqemuparams='', launch_cmd=None):
+def start(self, qemuparams = None, get_ip = True, extra_bootparams = None, 
runqemuparams='', launch_cmd=None, discard_writes=True):
 if self.display:
 os.environ["DISPLAY"] = self.display
 # Set this flag so that Qemu doesn't do any grabs as SDL grabs
@@ -118,7 +118,7 @@ class QemuRunner:
 os.environ["DEPLOY_DIR_IMAGE"] = self.deploy_dir_image
 
 if not launch_cmd:
-launch_cmd = 'runqemu snapshot %s' % runqemuparams
+launch_cmd = 'runqemu %s %s ' % ('snapshot' if discard_writes else 
'', runqemuparams)
 if self.use_kvm:
 logger.info('Using kvm for runqemu')
 launch_cmd += ' kvm'
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/1] rpm: change PROVIDES rpm-build to RPROVIDES

[Robert Yang]

The following changes since commit b2a785f19fe25d244179b8672c846925da6d455a:

  mdadm: update criteria to build with corosync (2017-03-26 13:17:04 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/rpm
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/rpm

Robert Yang (1):
  rpm: change PROVIDES rpm-build to RPROVIDES

 meta/recipes-devtools/rpm/rpm_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.11.0.rc2.dirty

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/1] rpm: change PROVIDES rpm-build to RPROVIDES

[Robert Yang]

The rpm 5 has a rpm-build package, so here should use RPROVIDES rather
than PROVIDES to keep compatibility.

Signed-off-by: Robert Yang 
---
 meta/recipes-devtools/rpm/rpm_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/rpm/rpm_git.bb 
b/meta/recipes-devtools/rpm/rpm_git.bb
index 8d2527cbc7..9bccd91168 100644
--- a/meta/recipes-devtools/rpm/rpm_git.bb
+++ b/meta/recipes-devtools/rpm/rpm_git.bb
@@ -107,4 +107,4 @@ PROVIDES += "python-rpm"
 FILES_python-rpm = "${PYTHON_SITEPACKAGES_DIR}/rpm/*"
 
 # rpm 5.x was packaging the rpm build tools separately
-PROVIDES += "rpm-build"
+RPROVIDES_${PN} += "rpm-build"
-- 
2.11.0.rc2.dirty

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] ifupdown: Fix initscript

[David Vincent]

ifupdown does not provide an initscript so this recipe should not
inherit update-rc.d class. Instead, we rely on init-ifupdown recipe to
startup networking.

Signed-off-by: David Vincent 
---
 meta/recipes-core/ifupdown/ifupdown_0.8.16.bb | 5 +
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/meta/recipes-core/ifupdown/ifupdown_0.8.16.bb 
b/meta/recipes-core/ifupdown/ifupdown_0.8.16.bb
index eb8426cb97..5654528ae8 100644
--- a/meta/recipes-core/ifupdown/ifupdown_0.8.16.bb
+++ b/meta/recipes-core/ifupdown/ifupdown_0.8.16.bb
@@ -16,7 +16,7 @@ SRCREV = "11b9f99f7ecc7052497e6786156cfed531f11823"
 S = "${WORKDIR}/git"
 
 
-inherit update-rc.d update-alternatives
+inherit update-alternatives
 
 do_compile () {
chmod a+rx *.pl *.sh
@@ -44,6 +44,3 @@ ALTERNATIVE_${PN} = "ifup ifdown"
 
 ALTERNATIVE_LINK_NAME[ifup] = "${base_sbindir}/ifup"
 ALTERNATIVE_LINK_NAME[ifdown] = "${base_sbindir}/ifdown"
-
-INITSCRIPT_NAME = "ifup"
-INITSCRIPT_PARAMS = "start 39 S . stop 39 0 6 1 ."
-- 
2.12.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] image_types: perform fsck on created ext image

[Daniel Schultz]

Hi Enrico,

Am 24.03.2017 um 15:01 schrieb Enrico Joerns:

Hi Daniel,

On 03/24/2017 02:34 PM, Daniel Schultz wrote:

Hi Enrico,

I have sent fixes for the same problem on Monday.
These include a fix of the wrong return code after optimizations (now it
returns 0) and an fsck execution after the creation of EXT partitions.

The patch which is identical to yours wasn't applied so far, the other
ones were.


ouh, we should have checked that before, but we did not assume that
someone would have posted a fix for this relatively old behavior during
the last days. Reality disabused us... Anyway, good to see that we are
not the only one that stumbled across this issue ;)

But, there is another difference between our patches. We use `-pvfD`,
while you use `-fy` as an fsck.extN option.

I would expect `-p` to be sufficient for letting fsck perform minor
optimizations. If you use `-y` instead, fsck will fix also real issues.
This is not what it should do here, even if it will return 1 afterwards.
If the file system was created with errors I guess we should let the
image creation fail without further touching the ext4.

-D will let fsck perform further directory optimizations
-v might be helpful for debugging purpose


Yes, that's better. I will them also apply to the WIC tools.

Do you think the test expression is still needed?
My opinion is, that it will obfuscate the return code of fsck to either 
true or false. This could confuse other people. What do you think?


--
Mit freundlichen Grüßen,
With best regards,
  Daniel Schultz
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core