[OE-core] [PATCH] ltp: Add "udevadm trigger" before swap verification in mkswap01.sh

2019-11-12 Thread Yongxin Liu
Swap verification sometimes fails due to race condition with udev.
This is a known issue: https://github.com/linux-test-project/ltp/issues/458.
"udevadm trigger" forces udev to sync up device events with kernel.

Signed-off-by: Yongxin Liu 
---
 ...-Add-udevadm-trigger-before-swap-verifica.patch | 35 ++
 meta/recipes-extended/ltp/ltp_20190517.bb  |  1 +
 2 files changed, 36 insertions(+)
 create mode 100644 
meta/recipes-extended/ltp/ltp/0001-mkswap01.sh-Add-udevadm-trigger-before-swap-verifica.patch

diff --git 
a/meta/recipes-extended/ltp/ltp/0001-mkswap01.sh-Add-udevadm-trigger-before-swap-verifica.patch
 
b/meta/recipes-extended/ltp/ltp/0001-mkswap01.sh-Add-udevadm-trigger-before-swap-verifica.patch
new file mode 100644
index 00..1b433d3ad3
--- /dev/null
+++ 
b/meta/recipes-extended/ltp/ltp/0001-mkswap01.sh-Add-udevadm-trigger-before-swap-verifica.patch
@@ -0,0 +1,35 @@
+From fae8852a63d9fa6e56fb8b24eaf10560bd13757f Mon Sep 17 00:00:00 2001
+From: Yongxin Liu 
+Date: Tue, 12 Nov 2019 11:33:50 +0800
+Subject: [PATCH] mkswap01.sh: Add "udevadm trigger" before swap verification
+
+Fix: https://github.com/linux-test-project/ltp/issues/458
+
+Sometimes the swap device cannot show up in /dev/disk/by-uuid/
+or /dev/disk/by-lable/ due to the issue #458. When this issue
+happens, "blkid -c /dev/null" and "ls /dev/disk/by-uuid/" show
+different UUID of the device.
+
+Upstream-Status: Submitted [https://patchwork.ozlabs.org/patch/1193414]
+
+Signed-off-by: Yongxin Liu 
+---
+ testcases/commands/mkswap/mkswap01.sh | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/testcases/commands/mkswap/mkswap01.sh 
b/testcases/commands/mkswap/mkswap01.sh
+index 3a348c6e6..9437c4a4e 100755
+--- a/testcases/commands/mkswap/mkswap01.sh
 b/testcases/commands/mkswap/mkswap01.sh
+@@ -129,6 +129,8 @@ mkswap_test()
+   return
+   fi
+ 
++  udevadm trigger --name-match=$TST_DEVICE
++
+   if [ -n "$device" ]; then
+   mkswap_verify "$mkswap_op" "$op_arg" "$device" "$size" 
"$dev_file"
+   if [ $? -ne 0 ]; then
+-- 
+2.14.4
+
diff --git a/meta/recipes-extended/ltp/ltp_20190517.bb 
b/meta/recipes-extended/ltp/ltp_20190517.bb
index 5915b1c72a..47aa9675d8 100644
--- a/meta/recipes-extended/ltp/ltp_20190517.bb
+++ b/meta/recipes-extended/ltp/ltp_20190517.bb
@@ -50,6 +50,7 @@ SRC_URI = "git://github.com/linux-test-project/ltp.git \

file://0001-syscall-rt_sigtimedwait01-Fix-wrong-sigset-length-fo.patch \
file://0001-cve-2017-17052-Avoid-unsafe-exits-in-threads.patch \

file://0001-overcommit_memory-update-for-mm-fix-false-positive-O.patch \
+   
file://0001-mkswap01.sh-Add-udevadm-trigger-before-swap-verifica.patch \
"
 
 S = "${WORKDIR}/git"
-- 
2.14.4

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


[OE-core] [PATCH] libedit:upgrade 20190324 -> 20191025

2019-11-12 Thread Zang Ruochen
-libedit/0001-readline.c-fix-cannot-get-history.patch
Removed since this is included in 20191025-3.1.

Signed-off-by: Zang Ruochen 
---
 ...01-readline.c-fix-cannot-get-history.patch | 34 ---
 ...0190324-3.1.bb => libedit_20191025-3.1.bb} |  5 ++-
 2 files changed, 2 insertions(+), 37 deletions(-)
 delete mode 100644 
meta/recipes-devtools/libedit/libedit/0001-readline.c-fix-cannot-get-history.patch
 rename meta/recipes-devtools/libedit/{libedit_20190324-3.1.bb => 
libedit_20191025-3.1.bb} (70%)

diff --git 
a/meta/recipes-devtools/libedit/libedit/0001-readline.c-fix-cannot-get-history.patch
 
b/meta/recipes-devtools/libedit/libedit/0001-readline.c-fix-cannot-get-history.patch
deleted file mode 100644
index 7e54ac97ea..00
--- 
a/meta/recipes-devtools/libedit/libedit/0001-readline.c-fix-cannot-get-history.patch
+++ /dev/null
@@ -1,34 +0,0 @@
-From ef1fa9bef497d9491a51017f3cad0135a23bb0b4 Mon Sep 17 00:00:00 2001
-From: Changqing Li 
-Date: Tue, 20 Aug 2019 17:33:15 +0800
-Subject: [PATCH] readline.c: fix cannot get history
-
-if history_offset not increate when add history,
-it will make current history event not align with offset,
-and cannot get history correctly.
-
-Upstream-Status: Submitted [tech-userle...@netbsd.org] 
-
-Signed-off-by: Changqing Li 

- src/readline.c | 3 +++
- 1 file changed, 3 insertions(+)
-
-diff --git a/src/readline.c b/src/readline.c
-index 43ac5bd..54b0548 100644
 a/src/readline.c
-+++ b/src/readline.c
-@@ -1476,7 +1476,10 @@ add_history(const char *line)
-   if (ev.num == history_length)
-   history_base++;
-   else
-+{
-+history_offset++;
-   history_length = ev.num;
-+}
-   return 0;
- }
- 
--- 
-2.7.4
-
diff --git a/meta/recipes-devtools/libedit/libedit_20190324-3.1.bb 
b/meta/recipes-devtools/libedit/libedit_20191025-3.1.bb
similarity index 70%
rename from meta/recipes-devtools/libedit/libedit_20190324-3.1.bb
rename to meta/recipes-devtools/libedit/libedit_20191025-3.1.bb
index 25667ccce7..f810013a68 100644
--- a/meta/recipes-devtools/libedit/libedit_20190324-3.1.bb
+++ b/meta/recipes-devtools/libedit/libedit_20191025-3.1.bb
@@ -12,9 +12,8 @@ inherit autotools
 
 SRC_URI = "http://www.thrysoee.dk/editline/${BP}.tar.gz \
file://stdc-predef.patch \
-   file://0001-readline.c-fix-cannot-get-history.patch \
   "
-SRC_URI[md5sum] = "bec755c8044ad84b752dfe49a0b371d8"
-SRC_URI[sha256sum] = 
"ac8f0f51c1cf65492e4d1e3ed2be360bda41e54633444666422fbf393bba1bae"
+SRC_URI[md5sum] = "2d6568467080cfd75e715d045102b544"
+SRC_URI[sha256sum] = 
"6dff036660d478bfaa14e407fc5de26d22da1087118c897b1a3ad2e90cb7bf39"
 
 BBCLASSEXTEND = "native nativesdk"
-- 
2.20.1



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


[OE-core] [master][zeus][PATCH 2/2] sysstat: Correct when to use the package provided systemd unit files

2019-11-12 Thread Peter Kjellerstedt
There have been a number of changes back and forth as to when and how
to use the systemd unit files provided by the package. The correct
condition is actually that both cron and systemd need to be enabled
for them to be installed.

Signed-off-by: Peter Kjellerstedt 
---
 meta/recipes-extended/sysstat/sysstat.inc | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-extended/sysstat/sysstat.inc 
b/meta/recipes-extended/sysstat/sysstat.inc
index 9394090136..62de36b44b 100644
--- a/meta/recipes-extended/sysstat/sysstat.inc
+++ b/meta/recipes-extended/sysstat/sysstat.inc
@@ -17,7 +17,7 @@ DEPENDS += "base-passwd"
 # autotools-brokensep as this package doesn't use automake
 inherit autotools-brokensep gettext systemd upstream-version-is-even
 
-PACKAGECONFIG ??= ""
+PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}"
 PACKAGECONFIG[lm-sensors] = 
"--enable-sensors,--disable-sensors,lmsensors,lmsensors-libsensors"
 PACKAGECONFIG[cron] = "--enable-install-cron 
--enable-copy-only,--disable-install-cron --disable-copy-only"
 PACKAGECONFIG[systemd] = 
"--with-systemdsystemunitdir=${systemd_system_unitdir}"
@@ -46,7 +46,9 @@ do_install() {
echo "d ${localstatedir}/log/sa - - - -" \
 > ${D}${sysconfdir}/tmpfiles.d/sysstat.conf
 
-   if ${@bb.utils.contains('PACKAGECONFIG', 'cron', 'false', 
'true', d)}; then
+   # Unless both cron and systemd are enabled, install our own
+   # systemd unit file. Otherwise the package will install one.
+   if ${@bb.utils.contains('PACKAGECONFIG', 'cron systemd', 
'false', 'true', d)}; then
install -d ${D}${systemd_unitdir}/system
install -m 0644 ${WORKDIR}/sysstat.service 
${D}${systemd_unitdir}/system
sed -i -e 's#@LIBEXECDIR@#${libexecdir}#g' 
${D}${systemd_unitdir}/system/sysstat.service
-- 
2.21.0

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


[OE-core] [master][zeus][PATCH 1/2] sysstat: Correct our systemd unit file

2019-11-12 Thread Peter Kjellerstedt
In commit 8862f21e (sysstat: 12.1.3 -> 12.1.6), sa_lib_dir was changed
from "${libdir}/sa" to "${libexecdir}/sa" to avoid problems with
multilib. However, the systemd unit file was not changed accordingly,
which lead to the following error when trying to start the service:

  systemd[4698]: sysstat.service: Failed at step EXEC spawning
  /usr/lib/sa/sa1: No such file or directory

Signed-off-by: Peter Kjellerstedt 
---
 meta/recipes-extended/sysstat/sysstat.inc | 4 ++--
 meta/recipes-extended/sysstat/sysstat/sysstat.service | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-extended/sysstat/sysstat.inc 
b/meta/recipes-extended/sysstat/sysstat.inc
index 5a7d2114ca..9394090136 100644
--- a/meta/recipes-extended/sysstat/sysstat.inc
+++ b/meta/recipes-extended/sysstat/sysstat.inc
@@ -49,7 +49,7 @@ do_install() {
if ${@bb.utils.contains('PACKAGECONFIG', 'cron', 'false', 
'true', d)}; then
install -d ${D}${systemd_unitdir}/system
install -m 0644 ${WORKDIR}/sysstat.service 
${D}${systemd_unitdir}/system
-   sed -i -e 's#@LIBDIR@#${libdir}#g' 
${D}${systemd_unitdir}/system/sysstat.service
+   sed -i -e 's#@LIBEXECDIR@#${libexecdir}#g' 
${D}${systemd_unitdir}/system/sysstat.service
fi
fi
 }
@@ -62,6 +62,6 @@ pkg_postinst_${PN} () {
fi
 }
 
-FILES_${PN} += "${libdir}/sa ${systemd_system_unitdir}"
+FILES_${PN} += "${systemd_system_unitdir}"
 
 TARGET_CC_ARCH += "${LDFLAGS}"
diff --git a/meta/recipes-extended/sysstat/sysstat/sysstat.service 
b/meta/recipes-extended/sysstat/sysstat/sysstat.service
index aff07109f5..ca46befb99 100644
--- a/meta/recipes-extended/sysstat/sysstat/sysstat.service
+++ b/meta/recipes-extended/sysstat/sysstat/sysstat.service
@@ -5,7 +5,7 @@ Description=Resets System Activity Logs
 Type=oneshot
 RemainAfterExit=yes
 User=root
-ExecStart=@LIBDIR@/sa/sa1 --boot
+ExecStart=@LIBEXECDIR@/sa/sa1 --boot
 
 [Install]
 WantedBy=multi-user.target
-- 
2.21.0

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


[OE-core] [PATCH] python3-six:upgrade 1.12.0 -> 1.13.0

2019-11-12 Thread Zang Ruochen
-License-Update: Copyright year updated to 2019.

Signed-off-by: Zang Ruochen 
---
 meta/recipes-devtools/python/python-six.inc | 6 +++---
 .../python/{python3-six_1.12.0.bb => python3-six_1.13.0.bb} | 0
 2 files changed, 3 insertions(+), 3 deletions(-)
 rename meta/recipes-devtools/python/{python3-six_1.12.0.bb => 
python3-six_1.13.0.bb} (100%)

diff --git a/meta/recipes-devtools/python/python-six.inc 
b/meta/recipes-devtools/python/python-six.inc
index c706dcaf25..c386090b4b 100644
--- a/meta/recipes-devtools/python/python-six.inc
+++ b/meta/recipes-devtools/python/python-six.inc
@@ -2,10 +2,10 @@ SUMMARY = "Python 2 and 3 compatibility library"
 HOMEPAGE = "https://pypi.python.org/pypi/six/;
 SECTION = "devel/python"
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=83e0f622bd5ac7d575dbd83d094d69b5"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=f82eb3a1a7fade60bda5980935084b62"
 
-SRC_URI[md5sum] = "9ae5d1feed8c0215f4ae4adcd9207fcb"
-SRC_URI[sha256sum] = 
"d16a0141ec1a18405cd4ce8b4613101da75da0e9a7aec5bdd4fa804d0e0eba73"
+SRC_URI[md5sum] = "e92c23c882c7d5564ce5773fe31b2771"
+SRC_URI[sha256sum] = 
"30f610279e8b2578cab6db20741130331735c781b56053c59c4076da27f06b66"
 
 inherit pypi
 
diff --git a/meta/recipes-devtools/python/python3-six_1.12.0.bb 
b/meta/recipes-devtools/python/python3-six_1.13.0.bb
similarity index 100%
rename from meta/recipes-devtools/python/python3-six_1.12.0.bb
rename to meta/recipes-devtools/python/python3-six_1.13.0.bb
-- 
2.20.1



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


[OE-core] [PATCH] libinput:upgrade 1.14.1 -> 1.14.3

2019-11-12 Thread Zang Ruochen
Signed-off-by: Zang Ruochen 
---
 .../wayland/{libinput_1.14.1.bb => libinput_1.14.3.bb}| 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-graphics/wayland/{libinput_1.14.1.bb => 
libinput_1.14.3.bb} (90%)

diff --git a/meta/recipes-graphics/wayland/libinput_1.14.1.bb 
b/meta/recipes-graphics/wayland/libinput_1.14.3.bb
similarity index 90%
rename from meta/recipes-graphics/wayland/libinput_1.14.1.bb
rename to meta/recipes-graphics/wayland/libinput_1.14.3.bb
index c74a9bad1f..f06a8d28f8 100644
--- a/meta/recipes-graphics/wayland/libinput_1.14.1.bb
+++ b/meta/recipes-graphics/wayland/libinput_1.14.3.bb
@@ -13,8 +13,8 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=1f2ea9ebff3a2c6d458faf58492efb63"
 DEPENDS = "libevdev udev mtdev"
 
 SRC_URI = "http://www.freedesktop.org/software/${BPN}/${BP}.tar.xz;
-SRC_URI[md5sum] = "da29a704dc6f7ea2d5aac754db046340"
-SRC_URI[sha256sum] = 
"e333a3242835c019ca37d2cef8b51a87d3138eb47444119c0153dc7a8656ee70"
+SRC_URI[md5sum] = "d052faa64eb6d2e649e582cc0fcf6e32"
+SRC_URI[sha256sum] = 
"0feb3a0589709cc1032893bfaf4c49150d5360bd9782bec888f9e4dd9044c5b7"
 
 UPSTREAM_CHECK_REGEX = "libinput-(?P\d+\.\d+\.(?!9\d+)\d+)"
 
-- 
2.20.1



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


[OE-core] [PATCH] mc: Fix build reproducibility

2019-11-12 Thread Joshua Watt
Fixes some issues with reproducible builds. Adds a patch to allow the
configure arguments to be omitted from the build and also explicitly
setting some autoconf paths that were picking up hosttools.

Signed-off-by: Joshua Watt 
---
 ...Add-option-to-control-configure-args.patch | 99 +++
 meta/recipes-extended/mc/mc_4.8.23.bb |  5 +-
 2 files changed, 103 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-extended/mc/files/0001-Add-option-to-control-configure-args.patch

diff --git 
a/meta/recipes-extended/mc/files/0001-Add-option-to-control-configure-args.patch
 
b/meta/recipes-extended/mc/files/0001-Add-option-to-control-configure-args.patch
new file mode 100644
index 000..e76aac81612
--- /dev/null
+++ 
b/meta/recipes-extended/mc/files/0001-Add-option-to-control-configure-args.patch
@@ -0,0 +1,99 @@
+From a54501d3c9541bc8600225aa2d42531f93c6def7 Mon Sep 17 00:00:00 2001
+From: Joshua Watt 
+Date: Sat, 9 Nov 2019 20:01:48 -0600
+Subject: [PATCH] Add option to control configure args
+
+Embedding the configure time options into the executable can lead to
+non-reproducible builds, since configure options often have embedded
+paths. Add a configure time option to control if the configure args are
+embedded so this can be disabled.
+
+Upstream-Status: Submitted [https://midnight-commander.org/ticket/4031]
+Signed-off-by: Joshua Watt 
+---
+ configure.ac   | 6 ++
+ src/args.c | 6 ++
+ src/textconf.c | 2 ++
+ 3 files changed, 14 insertions(+)
+
+diff --git a/configure.ac b/configure.ac
+index 19d1a76be..a1948f6b9 100644
+--- a/configure.ac
 b/configure.ac
+@@ -544,6 +544,12 @@ dnl Clarify do we really need GModule
+ AM_CONDITIONAL([HAVE_GMODULE], [test -n "$g_module_supported" && \
+ test x"$textmode_x11_support" = x"yes" -o 
x"$enable_aspell" = x"yes"])
+ 
++AC_ARG_ENABLE([configure-args],
++AS_HELP_STRING([--enable-configure-args], [Handle all compiler warnings 
as errors]))
++if test "x$enable_configure_args" != xno; then
++AC_DEFINE([ENABLE_CONFIGURE_ARGS], 1, [Define to enable showing configure 
arguments in help])
++fi
++
+ AC_DEFINE_UNQUOTED([MC_CONFIGURE_ARGS], ["$ac_configure_args"], [MC configure 
arguments])
+ 
+ AC_CONFIG_FILES(
+diff --git a/src/args.c b/src/args.c
+index baef1a1c8..f8dc24020 100644
+--- a/src/args.c
 b/src/args.c
+@@ -95,7 +95,9 @@ static gboolean mc_args__nouse_subshell = FALSE;
+ #endif /* ENABLE_SUBSHELL */
+ static gboolean mc_args__show_datadirs = FALSE;
+ static gboolean mc_args__show_datadirs_extended = FALSE;
++#ifdef ENABLE_CONFIGURE_ARGS
+ static gboolean mc_args__show_configure_opts = FALSE;
++#endif
+ 
+ static GOptionGroup *main_group;
+ 
+@@ -125,6 +127,7 @@ static const GOptionEntry argument_main_table[] = {
+  NULL
+ },
+ 
++#ifdef ENABLE_CONFIGURE_ARGS
+ /* show configure options */
+ {
+  "configure-options", '\0', G_OPTION_FLAG_IN_MAIN, G_OPTION_ARG_NONE,
+@@ -132,6 +135,7 @@ static const GOptionEntry argument_main_table[] = {
+  N_("Print configure options"),
+  NULL
+ },
++#endif
+ 
+ {
+  "printwd", 'P', G_OPTION_FLAG_IN_MAIN, G_OPTION_ARG_STRING,
+@@ -758,11 +762,13 @@ mc_args_show_info (void)
+ return FALSE;
+ }
+ 
++#ifdef ENABLE_CONFIGURE_ARGS
+ if (mc_args__show_configure_opts)
+ {
+ show_configure_options ();
+ return FALSE;
+ }
++#endif
+ 
+ return TRUE;
+ }
+diff --git a/src/textconf.c b/src/textconf.c
+index 1e0613e58..f39b9e028 100644
+--- a/src/textconf.c
 b/src/textconf.c
+@@ -232,10 +232,12 @@ show_datadirs_extended (void)
+ 
+ /* 
-
 */
+ 
++#ifdef ENABLE_CONFIGURE_ARGS
+ void
+ show_configure_options (void)
+ {
+ (void) printf ("%s\n", MC_CONFIGURE_ARGS);
+ }
++#endif
+ 
+ /* 
-
 */
+-- 
+2.23.0
+
diff --git a/meta/recipes-extended/mc/mc_4.8.23.bb 
b/meta/recipes-extended/mc/mc_4.8.23.bb
index 83de8dbb2c6..71f61b48485 100644
--- a/meta/recipes-extended/mc/mc_4.8.23.bb
+++ b/meta/recipes-extended/mc/mc_4.8.23.bb
@@ -8,6 +8,7 @@ RDEPENDS_${PN} = "ncurses-terminfo"
 
 SRC_URI = "http://www.midnight-commander.org/downloads/${BPN}-${PV}.tar.bz2 \
file://0001-mc-replace-perl-w-with-use-warnings.patch \
+   file://0001-Add-option-to-control-configure-args.patch \
"
 SRC_URI[md5sum] = "152927ac29cf0e61d7d019f261bb7d89"
 SRC_URI[sha256sum] = 
"238c4552545dcf3065359bd50753abbb150c1b22ec5a36eaa02c82808293267d"
@@ -21,9 +22,11 @@ PACKAGECONFIG ??= ""
 PACKAGECONFIG[smb] = "--enable-vfs-smb,--disable-vfs-smb,samba,"
 PACKAGECONFIG[sftp] = "--enable-vfs-sftp,--disable-vfs-sftp,libssh2,"
 
-EXTRA_OECONF = "--with-screen=ncurses --without-gpm-mouse --without-x"
+EXTRA_OECONF = "--with-screen=ncurses --without-gpm-mouse --without-x 
--disable-configure-args"

[OE-core] [PATCH] curl:upgrade 7.66.0 -> 7.67.0

2019-11-12 Thread Zang Ruochen
Signed-off-by: Zang Ruochen 
---
 meta/recipes-support/curl/{curl_7.66.0.bb => curl_7.67.0.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/curl/{curl_7.66.0.bb => curl_7.67.0.bb} (95%)

diff --git a/meta/recipes-support/curl/curl_7.66.0.bb 
b/meta/recipes-support/curl/curl_7.67.0.bb
similarity index 95%
rename from meta/recipes-support/curl/curl_7.66.0.bb
rename to meta/recipes-support/curl/curl_7.67.0.bb
index d1975f2460..e08e08ed4a 100644
--- a/meta/recipes-support/curl/curl_7.66.0.bb
+++ b/meta/recipes-support/curl/curl_7.67.0.bb
@@ -9,8 +9,8 @@ SRC_URI = "http://curl.haxx.se/download/curl-${PV}.tar.bz2 \
file://0001-replace-krb5-config-with-pkg-config.patch \
 "
 
-SRC_URI[md5sum] = "c238aa394e3aa47ca4fcb0491774149f"
-SRC_URI[sha256sum] = 
"6618234e0235c420a21f4cb4c2dd0badde76e6139668739085a70c4e2fe7a141"
+SRC_URI[md5sum] = "7be288f6fd5b7b5e402ef3b36a461a24"
+SRC_URI[sha256sum] = 
"dd5f6956821a548bf4b44f067a530ce9445cc8094fd3e7e3fc7854815858586c"
 
 CVE_PRODUCT = "curl libcurl"
 inherit autotools pkgconfig binconfig multilib_header
-- 
2.20.1



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


[OE-core] [PATCH] libcheck:upgrade 0.12.0 -> 0.13.0

2019-11-12 Thread Zang Ruochen
Signed-off-by: Zang Ruochen 
---
 .../libcheck/{libcheck_0.12.0.bb => libcheck_0.13.0.bb}   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/libcheck/{libcheck_0.12.0.bb => 
libcheck_0.13.0.bb} (83%)

diff --git a/meta/recipes-support/libcheck/libcheck_0.12.0.bb 
b/meta/recipes-support/libcheck/libcheck_0.13.0.bb
similarity index 83%
rename from meta/recipes-support/libcheck/libcheck_0.12.0.bb
rename to meta/recipes-support/libcheck/libcheck_0.13.0.bb
index 25ac2c4b26..226417f991 100644
--- a/meta/recipes-support/libcheck/libcheck_0.12.0.bb
+++ b/meta/recipes-support/libcheck/libcheck_0.13.0.bb
@@ -7,8 +7,8 @@ LIC_FILES_CHKSUM = 
"file://COPYING.LESSER;md5=2d5025d4aa3495befef8f17206a5b0a1"
 
 SRC_URI = 
"https://github.com/${BPN}/check/releases/download/${PV}/check-${PV}.tar.gz \
file://not-echo-compiler-info-to-check_stdint.h.patch"
-SRC_URI[md5sum] = "31b17c6075820a434119592941186f70"
-SRC_URI[sha256sum] = 
"464201098bee00e90f5c4bdfa94a5d3ead8d641f9025b560a27755a83b824234"
+SRC_URI[md5sum] = "2c730c40b08482eaeb10132517970593"
+SRC_URI[sha256sum] = 
"c4336b31447acc7e3266854f73ec188cdb15554d0edd44739631da174a569909"
 UPSTREAM_CHECK_URI = "https://github.com/libcheck/check/releases/;
 
 S = "${WORKDIR}/check-${PV}"
-- 
2.20.1



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


Re: [OE-core] [PATCH 14/20] OEQA: move manual bash test to runtime

2019-11-12 Thread akuster808



On 11/12/19 5:33 PM, Mittal, Anuj wrote:
> On Mon, 2019-11-11 at 20:33 -0800, Armin Kuster wrote:
>> +
>> +class Bsp(OESelftestTestCase):
>> +def test_bash_installed(self):
>> +"""
>> +Summary:The purpose of this test case is to verify
>> that bash 
>> +in exists in the image. Test came from
>> manual.
>> +Expected:   Bash is found.
>> +"""
>> +
>> +features = 'IMAGE_INSTALL_append = " bash"\n'
>> +self.write_config(features)
>> +bitbake('core-image-minimal')
>> +
>> +with runqemu('core-image-minimal') as qemu:
>> +result = runCmd("which bash" , shell=True)
>> +self.assertEqual(0, result.status, "Couldn't find bash")
>> -- 
> We have IncompatibleLicensePerImageTests that tests for presence of
> bash when different LICENSE values are set.
Yeah, I found that later as I was poking around but want to send the
patch just to have the conversation.
>
> Perhaps we don't need this and can consider this case covered by that
> test?

I am fine with that.

thanks,
Armin
>
> Thanks,
>
> Anuj

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


Re: [OE-core] [PATCH 14/20] OEQA: move manual bash test to runtime

2019-11-12 Thread Mittal, Anuj
On Mon, 2019-11-11 at 20:33 -0800, Armin Kuster wrote:
> +
> +class Bsp(OESelftestTestCase):
> +def test_bash_installed(self):
> +"""
> +Summary:The purpose of this test case is to verify
> that bash 
> +in exists in the image. Test came from
> manual.
> +Expected:   Bash is found.
> +"""
> +
> +features = 'IMAGE_INSTALL_append = " bash"\n'
> +self.write_config(features)
> +bitbake('core-image-minimal')
> +
> +with runqemu('core-image-minimal') as qemu:
> +result = runCmd("which bash" , shell=True)
> +self.assertEqual(0, result.status, "Couldn't find bash")
> -- 

We have IncompatibleLicensePerImageTests that tests for presence of
bash when different LICENSE values are set.

Perhaps we don't need this and can consider this case covered by that
test?

Thanks,

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


Re: [OE-core] ✗ patchtest: failure for cdrtools-native: Don't set uid/gid during install

2019-11-12 Thread Mittal, Anuj
On Tue, 2019-11-12 at 23:31 +, Paul Barker wrote:
> I'm not sure what's wrong here. I've given the reason in the format
> shown in 
> https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status
> .
> 
> Maybe it's getting tripped up by the capitalisation of Upstream-
> status and giving a poor error message.

Looks like it:

https://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe/tree/tests/test_patch_upstream_status.py

Thanks,

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


Re: [OE-core] ✗ patchtest: failure for cdrtools-native: Don't set uid/gid during install

2019-11-12 Thread Paul Barker
On Tue, 12 Nov 2019, at 23:02, Patchwork wrote:
> == Series Details ==
> 
> Series: cdrtools-native: Don't set uid/gid during install
> Revision: 1
> URL   : https://patchwork.openembedded.org/series/21103/
> 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 Upstream-Status is Inappropriate, but no reason was 
> provided [test_upstream_status_presence_format] 
>   Suggested fixInclude a brief reason why 
> 0001-Don-t-set-uid-gid-during-install.patch is inappropriate
>   Current  Upstream-status: Inappropriate [native]
>   Standard format  Upstream-Status: Inappropriate [reason]

I'm not sure what's wrong here. I've given the reason in the format shown in 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status.

Maybe it's getting tripped up by the capitalisation of Upstream-status and 
giving a poor error message.

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


Re: [OE-core] [PATCH] pseudo: Add statx support to fix fedora30 issues

2019-11-12 Thread akuster808



On 11/12/19 1:46 PM, Peter Kjellerstedt wrote:
>> -Original Message-
>> From: openembedded-core-boun...@lists.openembedded.org > boun...@lists.openembedded.org> On Behalf Of Richard Purdie
>> Sent: den 7 november 2019 21:53
>> To: Seebs 
>> Cc: openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH] pseudo: Add statx support to fix fedora30
>> issues
>>
>> On Thu, 2019-11-07 at 14:34 -0600, Seebs wrote:
>>> On Thu,  7 Nov 2019 20:04:44 +
>>> Richard Purdie  wrote:
>>>
 Modern distros (e.g. fedora30) are starting to use the new statx()
 syscall through the newly exposed glibc wrapper function in
 software
 like coreutils (e.g. the ls command). Add support to intercept this
 to pseudo.
>>> I think this should be okay. If there's no real statx() wrapper, the
>>> real_statx() call probably fails, but also things probably won't have
>>> thought it existed/worked.
>> That was my thinking...
>>
>>> Worth double-checking that things still run with this in place on a
>>> system that doesn't have a statx wrapper, when configuring and
>>> building things like coreutils that will check for it.
>> coreutils looks to be using a standard configure check for the statx
>> function.
>>
>> Even in OE, we'd not want to configure/compile with pseudo loaded and
>> active so I think we should be ok...
>>
>> Cheers,
>>
>> Richard
> As a Fedora 30 user, I expect this needs to be backported to Zeus, 
> Warrior, etc as well or I guess I will start seeing problems when 
> building them?

this is already staged in both test branches.

- armin
>
> //Peter
>

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


[OE-core] ✗ patchtest: failure for cdrtools-native: Don't set uid/gid during install

2019-11-12 Thread Patchwork
== Series Details ==

Series: cdrtools-native: Don't set uid/gid during install
Revision: 1
URL   : https://patchwork.openembedded.org/series/21103/
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 Upstream-Status is Inappropriate, but no reason was 
provided [test_upstream_status_presence_format] 
  Suggested fixInclude a brief reason why 
0001-Don-t-set-uid-gid-during-install.patch is inappropriate
  Current  Upstream-status: Inappropriate [native]
  Standard format  Upstream-Status: Inappropriate [reason]



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] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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 0/1] cdrtools-native: Don't set uid/gid during install

2019-11-12 Thread Paul Barker
This could be seen as a belt-and-braces approach since I've just sent a patch
to add a native intercept script for chgrp but I think it's also worth fixing
the offending recipe itself.

Paul Barker (1):
  cdrtools-native: Don't set uid/gid during install

 ...001-Don-t-set-uid-gid-during-install.patch | 27 +++
 .../cdrtools/cdrtools-native_3.01.bb  |  5 +++-
 2 files changed, 31 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-devtools/cdrtools/cdrtools-native/0001-Don-t-set-uid-gid-during-install.patch

-- 
2.24.0

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


[OE-core] [PATCH 1/1] cdrtools-native: Don't set uid/gid during install

2019-11-12 Thread Paul Barker
This is a native recipe so won't be installed as root.

If the string 'root' is part of the username then the install script
can get tricked into thinking we are root (regardless of the actual
uid or permissions) resulting in attempts to run chown/chgrp
inappropriately.

Signed-off-by: Paul Barker 
---
 ...001-Don-t-set-uid-gid-during-install.patch | 27 +++
 .../cdrtools/cdrtools-native_3.01.bb  |  5 +++-
 2 files changed, 31 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-devtools/cdrtools/cdrtools-native/0001-Don-t-set-uid-gid-during-install.patch

diff --git 
a/meta/recipes-devtools/cdrtools/cdrtools-native/0001-Don-t-set-uid-gid-during-install.patch
 
b/meta/recipes-devtools/cdrtools/cdrtools-native/0001-Don-t-set-uid-gid-during-install.patch
new file mode 100644
index 00..06d73df82b
--- /dev/null
+++ 
b/meta/recipes-devtools/cdrtools/cdrtools-native/0001-Don-t-set-uid-gid-during-install.patch
@@ -0,0 +1,27 @@
+From 529cd5b007aa681c3ca14e5ab1e30469dd51646b Mon Sep 17 00:00:00 2001
+From: Paul Barker 
+Date: Tue, 12 Nov 2019 22:17:19 +
+Subject: [PATCH] Don't set uid/gid during install
+
+Signed-off-by: Paul Barker 
+Upstream-status: Inappropriate [native]
+---
+ RULES/rules.prg | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/RULES/rules.prg b/RULES/rules.prg
+index 023555c..f70f1a7 100644
+--- a/RULES/rules.prg
 b/RULES/rules.prg
+@@ -94,7 +94,7 @@ INSGRP=  $(__DEFINSGRP:$(_UNIQ)%=%)
+ 
+ LD=   @echo " ==> LINKING   \"$@\""; ld
+ LOCALIZE= @echo " ==> LOCALIZING \"$@\""; $(RM_F) $@; cp
+-INSTALL=  @echo " ==> INSTALLING \"$@\""; sh $(SRCROOT)/conf/install-sh 
-c -m $(INSMODEINS) -o $(INSUSR) -g $(INSGRP)
++INSTALL=  @echo " ==> INSTALLING \"$@\""; sh $(SRCROOT)/conf/install-sh 
-c -m $(INSMODEINS)
+ CHMOD=@echo " ==> SETTING PERMISSIONS ON \"$@\""; chmod
+ CHOWN=@echo " ==> SETTING OWNER ON \"$@\""; chown
+ CHGRP=@echo " ==> SETTING GROUP ON \"$@\""; chgrp
+-- 
+2.24.0
+
diff --git a/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb 
b/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb
index 78e1565e47..1c602e7ce7 100644
--- a/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb
+++ b/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb
@@ -7,7 +7,10 @@ SECTION = "console/utils"
 LICENSE = "GPLv2 & CDDL-1.0 & LGPLv2.1+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=32f68170be424c2cd64804337726b312"
 
-SRC_URI = "${SOURCEFORGE_MIRROR}/project/cdrtools/cdrtools-${REALPV}.tar.bz2"
+SRC_URI = " \
+   ${SOURCEFORGE_MIRROR}/project/cdrtools/cdrtools-${REALPV}.tar.bz2 \
+   file://0001-Don-t-set-uid-gid-during-install.patch \
+   "
 UPSTREAM_VERSION_UNKNOWN = "1"
 
 SRC_URI[md5sum] = "7d45c5b7e1f78d85d1583b361aee6e8b"
-- 
2.24.0

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


[OE-core] [PATCH] scripts/native-intercept: Add chgrp intercept

2019-11-12 Thread Paul Barker
Some installation rules have been seen to run chgrp for native recipes
which leads to 'Operation not permitted' errors. To prevent this we
need a chgrp intercept script to go with the existing chown intercept.

Signed-off-by: Paul Barker 
---
 scripts/native-intercept/chgrp | 5 +
 1 file changed, 5 insertions(+)
 create mode 100755 scripts/native-intercept/chgrp

diff --git a/scripts/native-intercept/chgrp b/scripts/native-intercept/chgrp
new file mode 100755
index 00..399c979f9a
--- /dev/null
+++ b/scripts/native-intercept/chgrp
@@ -0,0 +1,5 @@
+#! /bin/sh
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+echo "Intercept $0: $@ -- do nothing"
-- 
2.24.0

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


Re: [OE-core] [PATCH] pseudo: Add statx support to fix fedora30 issues

2019-11-12 Thread Peter Kjellerstedt
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org  boun...@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 7 november 2019 21:53
> To: Seebs 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] pseudo: Add statx support to fix fedora30
> issues
> 
> On Thu, 2019-11-07 at 14:34 -0600, Seebs wrote:
> > On Thu,  7 Nov 2019 20:04:44 +
> > Richard Purdie  wrote:
> >
> > > Modern distros (e.g. fedora30) are starting to use the new statx()
> > > syscall through the newly exposed glibc wrapper function in
> > > software
> > > like coreutils (e.g. the ls command). Add support to intercept this
> > > to pseudo.
> >
> > I think this should be okay. If there's no real statx() wrapper, the
> > real_statx() call probably fails, but also things probably won't have
> > thought it existed/worked.
> 
> That was my thinking...
> 
> > Worth double-checking that things still run with this in place on a
> > system that doesn't have a statx wrapper, when configuring and
> > building things like coreutils that will check for it.
> 
> coreutils looks to be using a standard configure check for the statx
> function.
> 
> Even in OE, we'd not want to configure/compile with pseudo loaded and
> active so I think we should be ok...
> 
> Cheers,
> 
> Richard

As a Fedora 30 user, I expect this needs to be backported to Zeus, 
Warrior, etc as well or I guess I will start seeing problems when 
building them?

//Peter

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


Re: [OE-core] [meta-oe] modemmanager: Upgrade 1.10.6 -> 1.10.8

2019-11-12 Thread Khem Raj
On Tue, 2019-11-12 at 11:56 -0800, Michael Scott wrote:
> Includes: Fix for an issue presenting after 1.10.6 update where modem
> would enter status denied state.
> 
> See:
> https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?h=1.10.8=47fd8a1e55cac0b0b45812e1dda826f38c264d1b
> 

Patch is ok, but please send it to openembedded-devel mailing list, so
it can be caught by patchwork into right project.

> Signed-off-by: Michael Scott 
> ---
>  .../{modemmanager_1.10.6.bb => modemmanager_1.10.8.bb}| 4
> ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>  rename meta-oe/recipes-
> connectivity/modemmanager/{modemmanager_1.10.6.bb =>
> modemmanager_1.10.8.bb} (92%)
> 
> diff --git a/meta-oe/recipes-
> connectivity/modemmanager/modemmanager_1.10.6.bb b/meta-oe/recipes-
> connectivity/modemmanager/modemmanager_1.10.8.bb
> similarity index 92%
> rename from meta-oe/recipes-
> connectivity/modemmanager/modemmanager_1.10.6.bb
> rename to meta-oe/recipes-
> connectivity/modemmanager/modemmanager_1.10.8.bb
> index 92d4fe0f4..3cd21cc0d 100644
> --- a/meta-oe/recipes-
> connectivity/modemmanager/modemmanager_1.10.6.bb
> +++ b/meta-oe/recipes-
> connectivity/modemmanager/modemmanager_1.10.8.bb
> @@ -14,8 +14,8 @@ DEPENDS = "glib-2.0 libgudev intltool-native
> libxslt-native"
>  SRC_URI = "
> http://www.freedesktop.org/software/ModemManager/ModemManager-${PV}.tar.xz
> \
> "
>  
> -SRC_URI[md5sum] = "7452a94f0d1ca361ae51ff1d287c53f5"
> -SRC_URI[sha256sum] =
> "3c2ca73782215664141042422759899ca9846440fc26d6223c7cf7ea4dd3c996"
> +SRC_URI[md5sum] = "c05ac4246c81cc15d617c4a129232988"
> +SRC_URI[sha256sum] =
> "cbe174078dbdf3f746a55f0004353d3c27da2a31da553036d90fc7dc34a0169a"
>  
>  S = "${WORKDIR}/ModemManager-${PV}"
>  

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


[OE-core] [PATCH] strace: Fix build found with 64bit time_t/musl

2019-11-12 Thread Khem Raj
This ensures that its using linux headers for matching the syscall
structures

Signed-off-by: Khem Raj 
---
 .../strace/strace/sys_headers.patch   | 25 +++
 meta/recipes-devtools/strace/strace_5.3.bb|  1 +
 2 files changed, 26 insertions(+)
 create mode 100644 meta/recipes-devtools/strace/strace/sys_headers.patch

diff --git a/meta/recipes-devtools/strace/strace/sys_headers.patch 
b/meta/recipes-devtools/strace/strace/sys_headers.patch
new file mode 100644
index 00..e46f2c350d
--- /dev/null
+++ b/meta/recipes-devtools/strace/strace/sys_headers.patch
@@ -0,0 +1,25 @@
+Remove configure checks for few sys/ headers
+
+sys/ipc.h, sys/sem.h, sys/shm.h, and sys/msg.h are actually wrappers
+for kernel headers in libc if available, here strace is trying to match
+traced process's APIs to syscalls kernel structures
+
+Removing the checks makes it default to right kernel UAPI headers under linux/
+
+Upstream-Status: Submitted 
[https://lists.strace.io/pipermail/strace-devel/2019-November/009222.html]
+Suggested-by: Rich Felker 
+Signed-off-by: Khem Raj 
+--- a/configure.ac
 b/configure.ac
+@@ -439,11 +439,7 @@ AC_CHECK_HEADERS(m4_normalize([
+   sys/conf.h
+   sys/eventfd.h
+   sys/fanotify.h
+-  sys/ipc.h
+-  sys/msg.h
+   sys/quota.h
+-  sys/sem.h
+-  sys/shm.h
+   sys/signalfd.h
+   sys/xattr.h
+   ustat.h
diff --git a/meta/recipes-devtools/strace/strace_5.3.bb 
b/meta/recipes-devtools/strace/strace_5.3.bb
index db6004583b..b000afb30b 100644
--- a/meta/recipes-devtools/strace/strace_5.3.bb
+++ b/meta/recipes-devtools/strace/strace_5.3.bb
@@ -15,6 +15,7 @@ SRC_URI = "https://strace.io/files/${PV}/strace-${PV}.tar.xz \

file://0001-tests-sigaction-Check-for-mips-and-alpha-before-usin.patch \
file://ptest-spacesave.patch \
file://uintptr_t.patch \
+   file://sys_headers.patch \
"
 SRC_URI[md5sum] = "84f5e72de813c9b1bb6057ee8ab428d8"
 SRC_URI[sha256sum] = 
"6c131198749656401fe3efd6b4b16a07ea867e8f530867ceae8930bbc937a047"
-- 
2.24.0

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


[OE-core] [meta-oe] modemmanager: Upgrade 1.10.6 -> 1.10.8

2019-11-12 Thread Michael Scott
Includes: Fix for an issue presenting after 1.10.6 update where modem
would enter status denied state.

See:
https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?h=1.10.8=47fd8a1e55cac0b0b45812e1dda826f38c264d1b

Signed-off-by: Michael Scott 
---
 .../{modemmanager_1.10.6.bb => modemmanager_1.10.8.bb}| 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta-oe/recipes-connectivity/modemmanager/{modemmanager_1.10.6.bb => 
modemmanager_1.10.8.bb} (92%)

diff --git a/meta-oe/recipes-connectivity/modemmanager/modemmanager_1.10.6.bb 
b/meta-oe/recipes-connectivity/modemmanager/modemmanager_1.10.8.bb
similarity index 92%
rename from meta-oe/recipes-connectivity/modemmanager/modemmanager_1.10.6.bb
rename to meta-oe/recipes-connectivity/modemmanager/modemmanager_1.10.8.bb
index 92d4fe0f4..3cd21cc0d 100644
--- a/meta-oe/recipes-connectivity/modemmanager/modemmanager_1.10.6.bb
+++ b/meta-oe/recipes-connectivity/modemmanager/modemmanager_1.10.8.bb
@@ -14,8 +14,8 @@ DEPENDS = "glib-2.0 libgudev intltool-native libxslt-native"
 SRC_URI = 
"http://www.freedesktop.org/software/ModemManager/ModemManager-${PV}.tar.xz \
"
 
-SRC_URI[md5sum] = "7452a94f0d1ca361ae51ff1d287c53f5"
-SRC_URI[sha256sum] = 
"3c2ca73782215664141042422759899ca9846440fc26d6223c7cf7ea4dd3c996"
+SRC_URI[md5sum] = "c05ac4246c81cc15d617c4a129232988"
+SRC_URI[sha256sum] = 
"cbe174078dbdf3f746a55f0004353d3c27da2a31da553036d90fc7dc34a0169a"
 
 S = "${WORKDIR}/ModemManager-${PV}"
 
-- 
2.24.0

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


[OE-core] [PATCH] wayland: Fix wayland-scanner build for MinGW

2019-11-12 Thread Joshua Watt
Applies 2 patches to fix the wayland-scanner build for MinGW (e.g.
nativesdk-wayland)

Signed-off-by: Joshua Watt 
---
 ...nner-Add-configure-check-for-strndup.patch |  50 ++
 ...v_signal-to-wayland-server-private.h.patch | 166 ++
 .../wayland/wayland_1.17.0.bb |   2 +
 3 files changed, 218 insertions(+)
 create mode 100644 
meta/recipes-graphics/wayland/wayland/0001-scanner-Add-configure-check-for-strndup.patch
 create mode 100644 
meta/recipes-graphics/wayland/wayland/0002-Move-wl_priv_signal-to-wayland-server-private.h.patch

diff --git 
a/meta/recipes-graphics/wayland/wayland/0001-scanner-Add-configure-check-for-strndup.patch
 
b/meta/recipes-graphics/wayland/wayland/0001-scanner-Add-configure-check-for-strndup.patch
new file mode 100644
index 000..c4435875ad4
--- /dev/null
+++ 
b/meta/recipes-graphics/wayland/wayland/0001-scanner-Add-configure-check-for-strndup.patch
@@ -0,0 +1,50 @@
+From 3c8b4467a1ca229e72fb5223787ed400a19c65c0 Mon Sep 17 00:00:00 2001
+From: Joshua Watt 
+Date: Fri, 25 Oct 2019 21:03:23 -0500
+Subject: [PATCH] scanner: Add configure check for strndup
+
+Some platforms may not have strndup() (e.g. MinGW), so provide a
+equivalent implementation if it's not found.
+
+Upstream-Status: Accepted [4a1f348c20157db7bd7c759fdeb23fbe8729c571]
+Signed-off-by: Joshua Watt 
+---
+ configure.ac  |  2 +-
+ src/scanner.c | 11 +++
+ 2 files changed, 12 insertions(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index 8d56f2b..1c99e21 100644
+--- a/configure.ac
 b/configure.ac
+@@ -63,7 +63,7 @@ fi
+ AC_SUBST(GCC_CFLAGS)
+ 
+ AC_CHECK_HEADERS([sys/prctl.h])
+-AC_CHECK_FUNCS([accept4 mkostemp posix_fallocate prctl])
++AC_CHECK_FUNCS([accept4 mkostemp posix_fallocate prctl strndup])
+ 
+ AC_ARG_ENABLE([libraries],
+ [AC_HELP_STRING([--disable-libraries],
+diff --git a/src/scanner.c b/src/scanner.c
+index a94be5d..27004bc 100644
+--- a/src/scanner.c
 b/src/scanner.c
+@@ -916,6 +916,17 @@ verify_arguments(struct parse_context *ctx,
+ 
+ }
+ 
++#ifndef HAVE_STRNDUP
++char *
++strndup(const char *s, size_t size)
++{
++  char *r = malloc(size + 1);
++  strncpy(r, s, size);
++  r[size] = '\0';
++  return r;
++}
++#endif
++
+ static void
+ end_element(void *data, const XML_Char *name)
+ {
diff --git 
a/meta/recipes-graphics/wayland/wayland/0002-Move-wl_priv_signal-to-wayland-server-private.h.patch
 
b/meta/recipes-graphics/wayland/wayland/0002-Move-wl_priv_signal-to-wayland-server-private.h.patch
new file mode 100644
index 000..b05b875abb5
--- /dev/null
+++ 
b/meta/recipes-graphics/wayland/wayland/0002-Move-wl_priv_signal-to-wayland-server-private.h.patch
@@ -0,0 +1,166 @@
+From e746f3bf7c8bb2f5dcf9e93edffc23b56eff12d0 Mon Sep 17 00:00:00 2001
+From: Joshua Watt 
+Date: Tue, 5 Nov 2019 09:09:50 -0600
+Subject: [PATCH] Move wl_priv_signal to wayland-server-private.h
+
+Including wayland-server-core.h in wayland-private.h is problematic
+because wayland-private.h is included by wayland-scanner which should be
+able to build against non-POSIX platforms (e.g. MinGW). The only reason
+that wayland-server-core.h was included in wayland-private.h was for the
+wl_private_signal definitions, so move those to a
+wayland-server-private.h file that can be included by both
+wayland-server.c and the tests.
+
+Upstream-Status: Accepted [e7d88f35eb89cf0cc77cbddd834cacc63683a9cc]
+Signed-off-by: Joshua Watt 
+---
+ Makefile.am  |  3 +-
+ src/wayland-private.h| 22 +--
+ src/wayland-server-private.h | 53 
+ src/wayland-server.c |  1 +
+ tests/newsignal-test.c   |  2 +-
+ 5 files changed, 58 insertions(+), 23 deletions(-)
+ create mode 100644 src/wayland-server-private.h
+
+diff --git a/Makefile.am b/Makefile.am
+index f47d055..026d981 100644
+--- a/Makefile.am
 b/Makefile.am
+@@ -56,7 +56,8 @@ libwayland_private_la_SOURCES =  \
+   src/connection.c\
+   src/wayland-os.c\
+   src/wayland-os.h\
+-  src/wayland-private.h
++  src/wayland-private.h   \
++  src/wayland-server-private.h
+ 
+ include_HEADERS = \
+   src/wayland-util.h  \
+diff --git a/src/wayland-private.h b/src/wayland-private.h
+index 29516ec..dc7d12f 100644
+--- a/src/wayland-private.h
 b/src/wayland-private.h
+@@ -31,11 +31,11 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #define WL_HIDE_DEPRECATED 1
+ 
+ #include "wayland-util.h"
+-#include "wayland-server-core.h"
+ 
+ /* Invalid memory address */
+ #define WL_ARRAY_POISON_PTR (void *) 4
+@@ -236,26 +236,6 @@ zalloc(size_t s)
+   return calloc(1, s);
+ }
+ 
+-struct wl_priv_signal {
+-  struct wl_list listener_list;
+-  struct wl_list emit_list;
+-};
+-
+-void
+-wl_priv_signal_init(struct wl_priv_signal 

Re: [OE-core] [PATCH v6] mesa: Upgrade to 19.2.1

2019-11-12 Thread Alexander Kanavin
On Tue, 12 Nov 2019 at 19:16, Khem Raj  wrote:

> > > in this case, texrel will endup causing sigsegv, this is a mesa issue,
> > > primarily we have been working it around so far.
> >
> > I sent a new patch, it probably doesn't fix this issue though.
> >
>
> sure, and I think we should be able to address it with a patch or some
> feature disable/enable a mechanism
> I wonder what changed in new build system that it cant be knobbed out
> as it used to be with autotools
>

It is probably upstream's removal of the 'asm' configuration switch which
was previously set to false and now is always on.
Seems like switching that on enables poorly written assembly code that
causes the qa issue?

Also there should be a runtime test for all of this. There is a test for
kmscube over virgl but only for glibc.

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


Re: [OE-core] [PATCH v6] mesa: Upgrade to 19.2.1

2019-11-12 Thread Khem Raj
On Tue, Nov 12, 2019 at 10:07 AM Alistair Francis  wrote:
>
> On Tue, Nov 12, 2019 at 8:19 AM Khem Raj  wrote:
> >
> > On Sat, Nov 9, 2019 at 7:36 AM Alexander Kanavin  
> > wrote:
> > >
> > > On Sat, 9 Nov 2019 at 00:02, Alistair Francis  
> > > wrote:
> > >>
> > >> > right this means glx-tls is not working anymore, and it will fail on
> > >> > musl at runtime
> > >> > see
> > >> > https://gitlab.freedesktop.org/mesa/mesa/issues/966
> > >>
> > >> So what do we do here?
> > >>
> > >> There are some patches in that issue, but they don't cleanly apply and
> > >> seem hacky anyway. Can we have two versions of mesa? One for musl and
> > >> one for others until this is fixed upstream?
> > >
> > >
> > > Maybe we can silence the warning for musl only, via 
> > > INSANE_SKIP_..._libc-musl = "textrel"?
> > > ffmpeg does the same already.
> >
> > in this case, texrel will endup causing sigsegv, this is a mesa issue,
> > primarily we have been working it around so far.
>
> I sent a new patch, it probably doesn't fix this issue though.
>

sure, and I think we should be able to address it with a patch or some
feature disable/enable a mechanism
I wonder what changed in new build system that it cant be knobbed out
as it used to be with autotools

> We can't just not update mesa because of this.

We can certainly take time to fix it, we are early in release cycle.

What about having two
> versions, or for musl and one for glibc?
>

Probably a bad idea

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


Re: [OE-core] [PATCH v6] mesa: Upgrade to 19.2.1

2019-11-12 Thread Alistair Francis
On Tue, Nov 12, 2019 at 8:19 AM Khem Raj  wrote:
>
> On Sat, Nov 9, 2019 at 7:36 AM Alexander Kanavin  
> wrote:
> >
> > On Sat, 9 Nov 2019 at 00:02, Alistair Francis  wrote:
> >>
> >> > right this means glx-tls is not working anymore, and it will fail on
> >> > musl at runtime
> >> > see
> >> > https://gitlab.freedesktop.org/mesa/mesa/issues/966
> >>
> >> So what do we do here?
> >>
> >> There are some patches in that issue, but they don't cleanly apply and
> >> seem hacky anyway. Can we have two versions of mesa? One for musl and
> >> one for others until this is fixed upstream?
> >
> >
> > Maybe we can silence the warning for musl only, via 
> > INSANE_SKIP_..._libc-musl = "textrel"?
> > ffmpeg does the same already.
>
> in this case, texrel will endup causing sigsegv, this is a mesa issue,
> primarily we have been working it around so far.

I sent a new patch, it probably doesn't fix this issue though.

We can't just not update mesa because of this. What about having two
versions, or for musl and one for glibc?

Alistair

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


Re: [OE-core] [PATCH v6] mesa: Upgrade to 19.2.1

2019-11-12 Thread Khem Raj
On Sat, Nov 9, 2019 at 7:36 AM Alexander Kanavin  wrote:
>
> On Sat, 9 Nov 2019 at 00:02, Alistair Francis  wrote:
>>
>> > right this means glx-tls is not working anymore, and it will fail on
>> > musl at runtime
>> > see
>> > https://gitlab.freedesktop.org/mesa/mesa/issues/966
>>
>> So what do we do here?
>>
>> There are some patches in that issue, but they don't cleanly apply and
>> seem hacky anyway. Can we have two versions of mesa? One for musl and
>> one for others until this is fixed upstream?
>
>
> Maybe we can silence the warning for musl only, via INSANE_SKIP_..._libc-musl 
> = "textrel"?
> ffmpeg does the same already.

in this case, texrel will endup causing sigsegv, this is a mesa issue,
primarily we have been working it around so far.

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


[OE-core] Yocto Project Status WW46'19

2019-11-12 Thread sjolley.yp.pm
Current Dev Position: YP 3.1 M1 

Next Deadline: YP 3.1 M1 build Dec. 2, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Anuj 
*   SWAT team rotation: Anuj -> Chen on Nov. 15, 2019
*   SWAT team rotation: Chen > Paul on Nov. 22, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday Nov. 14th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday Dec. 3rd at 8am PDT (
 https://zoom.us/j/990892712)
*   Weekly Engineering Sync Tuesday Nov. 12th at 8am PDT (
 https://zoom.us/j/990892712)
*   Twitch - Next event is Tuesday Nov. 12th at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   YP 2.7.2 is still undergoing QA
*   There were some key fixes for pseudo related issues which mean it
continues to work with modern distros like Fedora 31.
*   Patches have continued to merge and master is staying roughly
current with the pending patch queue but there continue to be recurring
build failures that are not being addressed.
*   The YP TSC worked on and shared a proposal on how an LTS release
could work which is available at:

https://docs.google.com/document/d/1AwAFDf52f_FoXksbHEVUMlu4hpcI0JMGVG-Kj_sU
kyc/ . There has been much discussion about this, patience would be
appreciated as the TSC and governing board work through this to come up with
plans on how we proceed.
*   We are continuing to collect ideas for YP 3.1 in this document:

https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjn
ABc/edit?usp=sharing
*   If anyone has any status items for the project they'd like to add to
the weekly reports, please email Richard and Stephen.

 

Proposed YP 3.1 Milestone Dates:

*   YP 3.1 M1 Proposed build date 12/2/2019
*   YP 3.1 M1 Proposed release date 12/13/2019
*   YP 3.1 M2 Proposed build date 1/20/2020
*   YP 3.1 M2 Proposed release date 1/31/2020
*   YP 3.1 M3 Proposed build date 2/24/2020
*   YP 3.1 M3 Proposed release date 3/6/2020
*   YP 3.1 M4 Proposed build date  3/30/2020
*   YP 3.1 M4 Proposed release date  4/24/2020

 

Planned upcoming dot releases:

*   YP 3.0.1 has patches being queued in poky-contrib
*   YP 2.7.2 (Warrior) is in QA.

 

Tracking Metrics:

*   WDD 2508 (last week 2518) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1445 (last week 1446)
*   Patches in the Pending State: 579 (40%) [last week 579 (40%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[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 Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

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


Re: [OE-core] [PATCH v6] mesa: Upgrade to 19.2.1

2019-11-12 Thread Adrian Bunk
On Fri, Nov 08, 2019 at 10:13:07AM -0800, Khem Raj wrote:
> On Fri, Nov 8, 2019 at 2:32 AM Ross Burton  wrote:
> > On 04/11/2019 22:48, Alistair Francis wrote:
> > > From: Alistair Francis 
> > >
> > > Upgrade mesa and mesa-gl to 19.2.1.
> > >
> > > The license hash change was a trivial new line removal.
> > >
> > > The glx-tls option was removed as it isn't included in the meson.build
> > > file. It has been replaced with 'use-elf-tls' instead.
> >
> > I think this has regressed something, this is a new warning on musl builds:
> >
> > do_package_qa: QA Issue: ELF binary
> > '[...]libgles2-mesa/usr/lib/libGLESv2.so.2.0.0' has relocations in .text
> > [textrel]
> >
> > (ditto for libGLESv1_CM.so.1.1.0 libGL.so.1.2.0 libglapi.so.0.0.0)
> 
> right this means glx-tls is not working anymore, and it will fail on
> musl at runtime
> see
> https://gitlab.freedesktop.org/mesa/mesa/issues/966

glx-tls is already PACKAGECONFIG_remove_libc-musl.

That this is no longer sufficient is the regression Ross mentioned.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

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


Re: [OE-core] [PATCH 5/5] cve-update-db-native: don't refresh more than once an hour

2019-11-12 Thread Ross Burton

On 11/11/2019 22:19, akuster808 wrote:

err, I thought the NVD db is only updated once every two hours. And why
is this not a variable so folks can tweak accordingly?


This a fast-path so that a refresh isn't even attempted 60 minutes after 
a fetch.  A fetch involves checking the last updates times in the 
metadata anyway so is relatively fast.


Don't see the need for this to be another variable.  Do you have a 
better refresh interval?


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


[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2019-11-12 Thread Stephen K Jolley
All,

 

The triage team is starting to try and collect up and classify bugs which a 
newcomer to the project would be able to work on in a way which means people 
can find them. They're being listed on the triage page under the appropriate 
heading:

 

  
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work on 
who doesn't have deep experience with the project.  If anyone can help, please 
take ownership of the bug and send patches!  If anyone needs help/advice there 
are people on irc who can likely do so, or some of the more experienced 
contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs 
reported into the Bugzilla. The number of people attending that meeting has 
fallen, as have the number of people available to help fix bugs. One of the 
things we hear users report is they don't know how to help. We (the triage 
team) are therefore going to start reporting out the currently 298 unassigned 
or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out 
with these.  Bugs are split into two types, "true bugs" where things don't work 
as they should and "enhancements" which are features we'd want to add to the 
system.  There are also roughly four different "priority" classes right now, 
“3.1”, “3.2, "3.99" and "Future", the more pressing/urgent issues being in 
"3.1" and then “3.2”.

 

Please review this link and if a bug is something you would be able to help 
with either take ownership of the bug, or send me ( 
 sjolley.yp...@gmail.com) an e-mail with the 
bug number you would like and I will assign it to you (please make sure you 
have a Bugzilla account).  The list is at:  
 
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

7867 SW Bayberry Dr., Beaverton, OR 97007

*Cell:(208) 244-4460

* Email: s  
jolley.yp...@gmail.com  

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


[OE-core] [PATCH] staging.bbclass: Fix wrong library path in sysroot_strip

2019-11-12 Thread Junling Zheng
Do not reset libdir and base_libdir in sysroot_strip, and just pass crude
paths as they will be reset later in strip_execs.

Signed-off-by: Junling Zheng 
---
 meta/classes/staging.bbclass | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass
index cca0b7e0d6..58d57a4323 100644
--- a/meta/classes/staging.bbclass
+++ b/meta/classes/staging.bbclass
@@ -75,8 +75,6 @@ python sysroot_strip () {
 
 dstdir = d.getVar('SYSROOT_DESTDIR')
 pn = d.getVar('PN')
-libdir = os.path.abspath(dstdir + os.sep + d.getVar("libdir"))
-base_libdir = os.path.abspath(dstdir + os.sep + d.getVar("base_libdir"))
 qa_already_stripped = 'already-stripped' in (d.getVar('INSANE_SKIP_' + pn) 
or "").split()
 strip_cmd = d.getVar("STRIP")
 
-- 
2.17.1

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


[OE-core] [PATCH] report-error.bbclass: replace angle brackets with and

2019-11-12 Thread changqing.li
From: Changqing Li 

when we have below content in local.conf or auto.conf:
BUILDHISTORY_COMMIT_AUTHOR ?= "Khem Raj "
send-error-report will fail with "HTTP Error 500: OK"

error-report-web do rudimentary check on all fields that are
passed to the graphs page to avoid any XSS happening, if contains
'<', the server will return error(Invalid characters in json).
fixed by use escape of <> to replace it.

NOTE: with this change, error-report-web need to add filter 'safe'
for the string wanted to display to avoid further HTML escaping
prior to output. Below is how the content displayed on webpage:
with the filter 'safe':
BUILDHISTORY_COMMIT_AUTHOR ?= "Khem Raj "
without the filter 'safe':
BUILDHISTORY_COMMIT_AUTHOR ?= "Khem Raj raj.k...@gmail.com"

Another patch for error-report-web will send to yocto mail list.

[YOCTO #13252]

Signed-off-by: Changqing Li 
---
 meta/classes/report-error.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/report-error.bbclass 
b/meta/classes/report-error.bbclass
index 1a12db1..6046867 100644
--- a/meta/classes/report-error.bbclass
+++ b/meta/classes/report-error.bbclass
@@ -36,6 +36,7 @@ def get_conf_data(e, filename):
 continue
 else:
 jsonstring=jsonstring + line
+jsonstring = jsonstring.replace("<", "").replace(">", "")
 return jsonstring
 
 python errorreport_handler () {
-- 
2.7.4

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