Re: [OE-core] [PATCH 2/2] cmake: use Ninja by default

2018-01-19 Thread Alejandro Enedino Hernandez Samaniego 

On 01/18/2018 04:38 AM, Ross Burton wrote:
> This changes the cmake class to use Ninja instead of Make by default.
>
> If a recipe is broken with Ninja then the recipe can set 
> OECMAKE_GENERATOR="Unix
> Makefiles" to change back to Make.
>
> Signed-off-by: Ross Burton 
> ---
>   meta/classes/cmake.bbclass | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
> index 74a952142ff..d60dad8d66b 100644
> --- a/meta/classes/cmake.bbclass
> +++ b/meta/classes/cmake.bbclass
> @@ -9,7 +9,7 @@ CCACHE = ""
>   
>   # What CMake generator to use.
>   # The supported options are "Unix Makefiles" or "Ninja".
> -OECMAKE_GENERATOR ?= "Unix Makefiles"
> +OECMAKE_GENERATOR ?= "Ninja"
>   
>   python() {
>   generator = d.getVar("OECMAKE_GENERATOR")

Awesome, testing it now!

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

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.01 release

2018-01-19 Thread Marek Vasut 
On 01/19/2018 10:58 PM, Tom Rini wrote:
> On Fri, Jan 19, 2018 at 10:46:56PM +0100, Marek Vasut wrote:
>> On 01/19/2018 07:18 PM, Otavio Salvador wrote:
>>> On Fri, Jan 19, 2018 at 3:45 PM, Marek Vasut  wrote:
 This upgrades the U-Boot from 2017.11 to 2018.01 release
 and drops patches accepted upstream.

 Signed-off-by: Marek Vasut 
>>>
>>> Acked-by: Otavio Salvador 
>>>
>>> ...
  file://MPC8315ERDB-enable-DHCP.patch \
>>>
>>> Please send this patch for next release so we can drop it as well.
>>
>> Look up the previous thread on why this patch is still here ...
> 
> Yes, and FWIW, I still think it's of the type that's safely merged
> upstream.  A group of users needs additional generic functionality
> enabled on a board.  CC the listed maintainer, and York, and I expect it
> would come in.  Thanks!

It didn't go too well last time and the time before, but sure, I can try
again ...

-- 
Best regards,
Marek Vasut
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.01 release

2018-01-19 Thread Tom Rini 
On Fri, Jan 19, 2018 at 10:46:56PM +0100, Marek Vasut wrote:
> On 01/19/2018 07:18 PM, Otavio Salvador wrote:
> > On Fri, Jan 19, 2018 at 3:45 PM, Marek Vasut  wrote:
> >> This upgrades the U-Boot from 2017.11 to 2018.01 release
> >> and drops patches accepted upstream.
> >>
> >> Signed-off-by: Marek Vasut 
> > 
> > Acked-by: Otavio Salvador 
> > 
> > ...
> >>  file://MPC8315ERDB-enable-DHCP.patch \
> > 
> > Please send this patch for next release so we can drop it as well.
> 
> Look up the previous thread on why this patch is still here ...

Yes, and FWIW, I still think it's of the type that's safely merged
upstream.  A group of users needs additional generic functionality
enabled on a board.  CC the listed maintainer, and York, and I expect it
would come in.  Thanks!

-- 
Tom


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

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.01 release

2018-01-19 Thread Marek Vasut 
On 01/19/2018 07:18 PM, Otavio Salvador wrote:
> On Fri, Jan 19, 2018 at 3:45 PM, Marek Vasut  wrote:
>> This upgrades the U-Boot from 2017.11 to 2018.01 release
>> and drops patches accepted upstream.
>>
>> Signed-off-by: Marek Vasut 
> 
> Acked-by: Otavio Salvador 
> 
> ...
>>  file://MPC8315ERDB-enable-DHCP.patch \
> 
> Please send this patch for next release so we can drop it as well.

Look up the previous thread on why this patch is still here ...

-- 
Best regards,
Marek Vasut
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v3] recipes-core: move hwclock.sh to util-linux

2018-01-19 Thread Alex Stewart 
* Move the hwclock.sh initscript from the busybox recipe to util-linux.
  This script is generally useful for distros that get their hwclock
  implementation from sources other than busybox and we follow debian's
  example by providing it in util-linux.

:busybox/*
* Remove the busybox-hwclock package, as it no longer has a purpose.
* If busybox is configured to include hwclock, the busybox package will
  RDEPEND on util-linux-hwclock-init.

:util-linux/*
* Add util-linux-hwclock-init as its own recipe so that distros which
  exclusively use busybox do not have to build the entire util-linux
  recipe to get the hwclock.sh initscript.
* Provide the hwclock.sh script in util-linux-hwclock-init, which can be
  pulled by any packages that depend on its functionality.
* util-linux-hwclock RDEPENDS on util-linux-hwclock-init for its
  initscript.

Signed-off-by: Alex Stewart 
---
 meta/recipes-core/busybox/busybox.inc  | 16 +++--
 meta/recipes-core/busybox/busybox_1.27.2.bb|  1 -
 meta/recipes-core/busybox/files/hwclock.sh | 83 --
 .../util-linux/util-linux-hwclock-init_1.0.bb  | 33 +
 meta/recipes-core/util-linux/util-linux.inc|  1 +
 meta/recipes-core/util-linux/util-linux/hwclock.sh | 83 ++
 6 files changed, 126 insertions(+), 91 deletions(-)
 delete mode 100644 meta/recipes-core/busybox/files/hwclock.sh
 create mode 100644 meta/recipes-core/util-linux/util-linux-hwclock-init_1.0.bb
 create mode 100644 meta/recipes-core/util-linux/util-linux/hwclock.sh

diff --git a/meta/recipes-core/busybox/busybox.inc 
b/meta/recipes-core/busybox/busybox.inc
index 4012f921c6..d9c3c2793b 100644
--- a/meta/recipes-core/busybox/busybox.inc
+++ b/meta/recipes-core/busybox/busybox.inc
@@ -20,19 +20,17 @@ export EXTRA_LDFLAGS = "${LDFLAGS}"
 
 EXTRA_OEMAKE = "CC='${CC}' LD='${CCLD}' V=1 ARCH=${TARGET_ARCH} 
CROSS_COMPILE=${TARGET_PREFIX} SKIP_STRIP=y HOSTCC='${BUILD_CC}' 
HOSTCPP='${BUILD_CPP}'"
 
-PACKAGES =+ "${PN}-httpd ${PN}-udhcpd ${PN}-udhcpc ${PN}-syslog ${PN}-mdev 
${PN}-hwclock"
+PACKAGES =+ "${PN}-httpd ${PN}-udhcpd ${PN}-udhcpc ${PN}-syslog ${PN}-mdev"
 
 FILES_${PN}-httpd = "${sysconfdir}/init.d/busybox-httpd /srv/www"
 FILES_${PN}-syslog = "${sysconfdir}/init.d/syslog* 
${sysconfdir}/syslog-startup.conf* ${sysconfdir}/syslog.conf* 
${systemd_unitdir}/system/syslog.service ${sysconfdir}/default/busybox-syslog"
 FILES_${PN}-mdev = "${sysconfdir}/init.d/mdev ${sysconfdir}/mdev.conf 
${sysconfdir}/mdev/*"
 FILES_${PN}-udhcpd = "${sysconfdir}/init.d/busybox-udhcpd"
 FILES_${PN}-udhcpc = "${sysconfdir}/udhcpc.d ${datadir}/udhcpc"
-FILES_${PN}-hwclock = "${sysconfdir}/init.d/hwclock.sh"
 
-INITSCRIPT_PACKAGES = "${PN}-httpd ${PN}-syslog ${PN}-udhcpd ${PN}-mdev 
${PN}-hwclock"
+INITSCRIPT_PACKAGES = "${PN}-httpd ${PN}-syslog ${PN}-udhcpd ${PN}-mdev"
 
 INITSCRIPT_NAME_${PN}-httpd = "busybox-httpd"
-INITSCRIPT_NAME_${PN}-hwclock = "hwclock.sh"
 INITSCRIPT_NAME_${PN}-mdev = "mdev"
 INITSCRIPT_PARAMS_${PN}-mdev = "start 04 S ."
 INITSCRIPT_NAME_${PN}-syslog = "syslog"
@@ -276,9 +274,6 @@ do_install () {
if grep "CONFIG_UDHCPD=y" ${B}/.config; then
install -m 0755 ${WORKDIR}/busybox-udhcpd 
${D}${sysconfdir}/init.d/
fi
-   if grep "CONFIG_HWCLOCK=y" ${B}/.config; then
-   install -m 0755 ${WORKDIR}/hwclock.sh ${D}${sysconfdir}/init.d/
-   fi
if grep "CONFIG_UDHCPC=y" ${B}/.config; then
install -d ${D}${sysconfdir}/udhcpc.d
install -d ${D}${datadir}/udhcpc
@@ -377,6 +372,13 @@ python do_package_prepend () {
 else:
 set_alternative_vars("${sysconfdir}/busybox.links.nosuid", 
"${base_bindir}/busybox.nosuid")
 set_alternative_vars("${sysconfdir}/busybox.links.suid", 
"${base_bindir}/busybox.suid")
+
+# If busybox is configured to provide a hwclock implementation, add a
+# package dependency on util-linux-hwclock-init for the
+# /etc/init.d/hwclock.sh initscript.
+with open(d.getVar('B', expand=True) + '/.config', 'r') as fp_conf:
+if 'CONFIG_HWCLOCK=y' in fp_conf.read():
+d.appendVar('RDEPENDS_busybox', ' util-linux-hwclock-init ')
 }
 
 pkg_postinst_${PN} () {
diff --git a/meta/recipes-core/busybox/busybox_1.27.2.bb 
b/meta/recipes-core/busybox/busybox_1.27.2.bb
index 6c1f4888cf..af2abadc5e 100644
--- a/meta/recipes-core/busybox/busybox_1.27.2.bb
+++ b/meta/recipes-core/busybox/busybox_1.27.2.bb
@@ -8,7 +8,6 @@ SRC_URI = 
"http://www.busybox.net/downloads/busybox-${PV}.tar.bz2;name=tarball \
file://busybox-udhcpd \
file://default.script \
file://simple.script \
-   file://hwclock.sh \
file://mount.busybox \
file://syslog \
file://syslog-startup.conf \
diff --git a/meta/recipes-core/busybox/files/hwclock.sh 
b/meta/recipes-core/busybox/files/hwclock.sh
deleted file mode 100644
index

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.01 release

2018-01-19 Thread Otavio Salvador 
On Fri, Jan 19, 2018 at 3:45 PM, Marek Vasut  wrote:
> This upgrades the U-Boot from 2017.11 to 2018.01 release
> and drops patches accepted upstream.
>
> Signed-off-by: Marek Vasut 

Acked-by: Otavio Salvador 

...
>  file://MPC8315ERDB-enable-DHCP.patch \

Please send this patch for next release so we can drop it as well.

-- 
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] [oe-commits] [openembedded-core] 08/08: json-glib: update to 1.4.2

2018-01-19 Thread Martin Jansa 
I have gobject-introspection-data in DISTRO_FEATURES_BACKFILL_CONSIDERED.

I am able to reproduce this with nodistro after adding:
DISTRO_FEATURES_remove = "gobject-introspection-data"
or the same to DISTRO_FEATURES_BACKFILL_CONSIDERED.

This one is with require conf/distro/include/security_flags.inc
http://errors.yoctoproject.org/Errors/Details/164873/

this one is without security_flags.inc:
http://errors.yoctoproject.org/Errors/Details/164874/

The older version was building fine with gobject-introspection disabled.


On Fri, Jan 19, 2018 at 4:07 PM, Alexander Kanavin  wrote:

> On 01/19/2018 04:06 PM, Martin Jansa wrote:
>
>> qemuarm, qemux86, raspberrypi3 and few more arm MACHINEs.
>>
>
> I just tried with qemux86 - builds fine, and the g-i files are present in
> the packages.
>
> Alex
> --
> ___
> 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

[OE-core] [PATCH] u-boot: Upgrade to 2018.01 release

2018-01-19 Thread Marek Vasut 
This upgrades the U-Boot from 2017.11 to 2018.01 release
and drops patches accepted upstream.

Signed-off-by: Marek Vasut 
Cc: Otavio Salvador 
Cc: Ross Burton 
Cc: Richard Purdie 
---
 .../u-boot/files/10m50-update-device-tree.patch| 28 ---
 .../u-boot/files/v2017.11-fw-utils-build-fix.patch | 41 --
 ...ommon_2017.11.inc => u-boot-common_2018.01.inc} |  4 +--
 ...utils_2017.11.bb => u-boot-fw-utils_2018.01.bb} |  0
 ...kimage_2017.11.bb => u-boot-mkimage_2018.01.bb} |  0
 .../{u-boot_2017.11.bb => u-boot_2018.01.bb}   |  0
 6 files changed, 1 insertion(+), 72 deletions(-)
 delete mode 100644 meta/recipes-bsp/u-boot/files/10m50-update-device-tree.patch
 delete mode 100644 
meta/recipes-bsp/u-boot/files/v2017.11-fw-utils-build-fix.patch
 rename meta/recipes-bsp/u-boot/{u-boot-common_2017.11.inc => 
u-boot-common_2018.01.inc} (72%)
 rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.11.bb => 
u-boot-fw-utils_2018.01.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.11.bb => 
u-boot-mkimage_2018.01.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot_2017.11.bb => u-boot_2018.01.bb} (100%)

diff --git a/meta/recipes-bsp/u-boot/files/10m50-update-device-tree.patch 
b/meta/recipes-bsp/u-boot/files/10m50-update-device-tree.patch
deleted file mode 100644
index 841953cd10..00
--- a/meta/recipes-bsp/u-boot/files/10m50-update-device-tree.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-Nios II for MAX10 10m50 board requires update to 
-its device tree to enable CPU driver during
-u-boot pre-relocation. This patch tag the CPU 
-with dm-pre-reloc flag.
-
-Upstream-Status: Submitted
-
-Signed-off-by: Gan, Yau Wai 
-

- arch/nios2/dts/10m50_devboard.dts | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/arch/nios2/dts/10m50_devboard.dts 
b/arch/nios2/dts/10m50_devboard.dts
-index 05eac30..461ae68 100644
 a/arch/nios2/dts/10m50_devboard.dts
-+++ b/arch/nios2/dts/10m50_devboard.dts
-@@ -19,6 +19,7 @@
-   #size-cells = <0>;
- 
-   cpu: cpu@0 {
-+  u-boot,dm-pre-reloc;
-   device_type = "cpu";
-   compatible = "altr,nios2-1.1";
-   reg = <0x>;
--- 
-2.7.4
-
diff --git a/meta/recipes-bsp/u-boot/files/v2017.11-fw-utils-build-fix.patch 
b/meta/recipes-bsp/u-boot/files/v2017.11-fw-utils-build-fix.patch
deleted file mode 100644
index bd6e4a572f..00
--- a/meta/recipes-bsp/u-boot/files/v2017.11-fw-utils-build-fix.patch
+++ /dev/null
@@ -1,41 +0,0 @@
-From ded84f90a1066eef5f34daa4539273de64f7b811 Mon Sep 17 00:00:00 2001
-From: Stefan Agner 
-Date: Tue, 14 Nov 2017 15:47:18 +0100
-Subject: [PATCH 1/1] envtools: make sure version/timestamp header file are
- available
-
-With commit 84d46e7e8948 ("tools: env: allow to print U-Boot version")
-the fw_env utilities need the version.h header file. Building only
-the envtools in a pristine build directory will fail due to missing
-header files.
-
-Make sure the header files are a dependency of the envtools target.
-
-Fixes: 84d46e7e8948 ("tools: env: allow to print U-Boot version")
-Signed-off-by: Stefan Agner 
-Tested-by: Peter Robinson 
-Reviewed-by: Simon Glass 
-
-Upstream-Status: Backport 
[http://git.denx.de/?p=u-boot.git;a=commit;h=ded84f90a1066eef5f34daa4539273de64f7b811]
-
-Signed-off-by: Kristian Amlie 

- Makefile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/Makefile b/Makefile
-index 61fd973..f8c66a2 100644
 a/Makefile
-+++ b/Makefile
-@@ -1447,7 +1447,7 @@ checkarmreloc: u-boot
-   false; \
-   fi
- 
--envtools: scripts_basic
-+envtools: scripts_basic $(version_h) $(timestamp_h)
-   $(Q)$(MAKE) $(build)=tools/env
- 
- tools-only: scripts_basic $(version_h) $(timestamp_h)
--- 
-2.7.4
-
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc 
b/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
similarity index 72%
rename from meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
rename to meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
index 65f1228043..d2073ea0c7 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
@@ -7,12 +7,10 @@ PE = "1"
 
 # We use the revision in order to avoid having to fetch it from the
 # repo during parse
-SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
+SRCREV = "f3dd87e0b98999a78e500e8c6d2b063ebadf535a"
 
 SRC_URI = "git://git.denx.de/u-boot.git \
 file://MPC8315ERDB-enable-DHCP.patch \
-file://10m50-update-device-tree.patch \
-file://v2017.11-fw-utils-build-fix.patch \
 "
 
 S = "${WORKDIR}/git"
diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.11.bb

Re: [OE-core] [PATCH] glibc:CVE-2017-17426

2018-01-19 Thread Burton, Ross 
This needs rebasing to master, and I suspect your email servers are
corrupting your mails as I often have to go and fix up your patches which
have had long lines wrapped:

Applying: glibc:CVE-2017-17426
error: corrupt patch at line 64

Ross

On 17 January 2018 at 02:46, Huang, Qiyu 
wrote:

> ping
>
>
> > -Original Message-
> > From: Huang, Qiyu
> > Sent: Wednesday, December 20, 2017 4:11 PM
> > To: openembedded-core@lists.openembedded.org
> > Cc: Huang, Qiyu 
> > Subject: [OE-core][PATCH] glibc:CVE-2017-17426
> >
> > Fix the CVE-2017-17426.
> >
> > Signed-off-by: Huang Qiyu 
> > ---
> >  ...-overflow-in-malloc-when-tcache-is-enable.patch | 52
> > ++
> >  meta/recipes-core/glibc/glibc_2.26.bb  |  1 +
> >  2 files changed, 53 insertions(+)
> >  create mode 100644
> > meta/recipes-core/glibc/glibc/0029-Fix-integer-overflow-in-
> malloc-when-tcache
> > -is-enable.patch
> >
> > diff --git
> > a/meta/recipes-core/glibc/glibc/0029-Fix-integer-
> overflow-in-malloc-when-tcac
> > he-is-enable.patch
> > b/meta/recipes-core/glibc/glibc/0029-Fix-integer-
> overflow-in-malloc-when-tcac
> > he-is-enable.patch
> > new file mode 100644
> > index 000..623bed7
> > --- /dev/null
> > +++ b/meta/recipes-core/glibc/glibc/0029-Fix-integer-overflow-in-malloc-
> > +++ when-tcache-is-enable.patch
> > @@ -0,0 +1,52 @@
> > +From 34697694e8a93b325b18f25f7dcded55d6baeaf6 Mon Sep 17 00:00:00
> > 2001
> > +From: Arjun Shankar 
> > +Date: Thu, 30 Nov 2017 13:31:45 +0100
> > +Subject: [PATCH] Fix integer overflow in malloc when tcache is enabled
> > +[BZ  #22375]
> > +
> > +When the per-thread cache is enabled, __libc_malloc uses request2size
> > +(which does not perform an overflow check) to calculate the chunk size
> > +from the requested allocation size. This leads to an integer overflow
> > +causing malloc to incorrectly return the last successfully allocated
> > +block when called with a very large size argument (close to SIZE_MAX).
> > +
> > +This commit uses checked_request2size instead, removing the overflow.
> > +
> > +Upstream-status: Backport
> > +---
> > + ChangeLog   | 6 ++
> > + malloc/malloc.c | 3 ++-
> > + 2 files changed, 8 insertions(+), 1 deletion(-)
> > +
> > +diff --git a/ChangeLog b/ChangeLog
> > +index b55ed22..888f9fb 100644
> > +--- a/ChangeLog
> >  b/ChangeLog
> > +@@ -1,3 +1,9 @@
> > ++2017-11-30  Arjun Shankar  
> > ++
> > ++[BZ #22375]
> > ++* malloc/malloc.c (__libc_malloc): Use checked_request2size
> > ++instead of request2size.
> > ++
> > + 2017-08-02  Siddhesh Poyarekar  
> > +
> > + * sysdeps/sparc/sparc32/sparcv9/fpu/multiarch/s_llrint.S
> > +diff --git a/malloc/malloc.c b/malloc/malloc.c index 79f0e9e..0c9e074
> > +100644
> > +--- a/malloc/malloc.c
> >  b/malloc/malloc.c
> > +@@ -3050,7 +3050,8 @@ __libc_malloc (size_t bytes)
> > + return (*hook)(bytes, RETURN_ADDRESS (0));  #if USE_TCACHE
> > +   /* int_free also calls request2size, be careful to not pad twice.
> > +*/
> > +-  size_t tbytes = request2size (bytes);
> > ++  size_t tbytes;
> > ++  checked_request2size (bytes, tbytes);
> > +   size_t tc_idx = csize2tidx (tbytes);
> > +
> > +   MAYBE_INIT_TCACHE ();
> > +--
> > +2.7.4
> > +
> > diff --git a/meta/recipes-core/glibc/glibc_2.26.bb
> > b/meta/recipes-core/glibc/glibc_2.26.bb
> > index 135ec4f..36b2004 100644
> > --- a/meta/recipes-core/glibc/glibc_2.26.bb
> > +++ b/meta/recipes-core/glibc/glibc_2.26.bb
> > @@ -43,6 +43,7 @@ SRC_URI =
> > "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \
> >
> > file://0026-assert-Suppress-pedantic-warning-caused-by-statement.patch \
> > file://0027-glibc-reset-dl-load-write-lock-after-forking.patch
> \
> > file://0028-Bug-4578-add-ld.so-lock-while-fork.patch \
> > +
> > + file://0029-Fix-integer-overflow-in-malloc-when-tcache-is-enable.patch
> > + \
> >  "
> >
> >  NATIVESDKFIXES ?= ""
> > --
> > 2.7.4
>
>
>
> --
> ___
> 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] grep: support Perl regular expression

2018-01-19 Thread Burton, Ross 
On 18 January 2018 at 03:41, Haiqing Bai  wrote:

> +PACKAGECONFIG[pcre] = ",--disable-perl-regexp,libpcre"
>

For clarity and ensure consistent behaviour if the defaults change, this
should also be passing --enable-perl-regexp.

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

[OE-core] ✗ patchtest: failure for mtd-utils: remove double hashtable iterator definition (rev4)

2018-01-19 Thread Patchwork 
== Series Details ==

Series: mtd-utils: remove double hashtable iterator definition (rev4)
Revision: 4
URL   : https://patchwork.openembedded.org/series/10612/
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 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 77144bc808)

* Issue Upstream-Status is Submitted, but it is not mentioned where 
[test_upstream_status_presence_format] 
  Suggested fixInclude where mtd-utils-fix-hashtable_iterator.patch was 
submitted
  Current  Upstream-Status: Submitted to dizzy
  Standard format  Upstream-Status: Submitted [where]



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] [OE-CORE] [PATCH v4] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Oleg Kokorin 
hashtable_iterator_key and hashtable_iterator_value redefinition inside
mkfs.ubifs/hashtable/hashtable_itr.h cause linker redefinition error

Signed-off-by: Oleg Kokorin 
---
 .../mtd-utils-fix-hashtable_iterator.patch | 58 ++
 meta/recipes-devtools/mtd/mtd-utils_git.bb |  1 +
 2 files changed, 59 insertions(+)
 create mode 100644 
meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch

diff --git 
a/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch 
b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
new file mode 100644
index 000..b6cf3a3
--- /dev/null
+++ b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
@@ -0,0 +1,58 @@
+Upstream-Status: Submitted to dizzy
+
+Author: Oleg Kokorin 
+Date:   Fri Jan 19 11:52:12 2018 +0100
+
+mtd-utils: remove double hashtable iterator definition
+
+hashtable_iterator_key and hashtable_iterator_value redefinition inside
+mkfs.ubifs/hashtable/hashtable_itr.h cause linker redefinition error:
+
+|   CC  mkfs.ubifs/hashtable/hashtable_itr.o
+| mkfs.ubifs/hashtable/hashtable_itr.c:42:1: error: redefinition of 
'hashtable_iterator_key'
+|  hashtable_iterator_key(struct hashtable_itr *i)
+|  ^
+| In file included from mkfs.ubifs/hashtable/hashtable_itr.c:5:0:
+| mkfs.ubifs/hashtable/hashtable_itr.h:32:1: note: previous definition of 
'hashtable_iterator_key' was here
+|  hashtable_iterator_key(struct hashtable_itr *i)
+|  ^
+| mkfs.ubifs/hashtable/hashtable_itr.c:46:1: error: redefinition of 
'hashtable_iterator_value'
+|  hashtable_iterator_value(struct hashtable_itr *i)
+|  ^
+| In file included from mkfs.ubifs/hashtable/hashtable_itr.c:5:0:
+| mkfs.ubifs/hashtable/hashtable_itr.h:41:1: note: previous definition of 
'hashtable_iterator_value' was here
+|  hashtable_iterator_value(struct hashtable_itr *i)
+
+Signed-off-by: Oleg Kokorin 
+
+Index: 
setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/x86_64-linux/mtd-utils-native/1.5.1+gitAUTOINC+9f107132a6-r0/git/mkfs.ubifs/hashtable/hashtable_itr.h
+===
+--- a/mkfs.ubifs/hashtable/hashtable_itr.h
 b/mkfs.ubifs/hashtable/hashtable_itr.h
+@@ -27,22 +27,22 @@ hashtable_iterator(struct hashtable *h);
+ 
/*/
+ /* hashtable_iterator_key
+  * - return the value of the (key,value) pair at the current position */
+-
++/*
+ extern inline void *
+ hashtable_iterator_key(struct hashtable_itr *i)
+ {
+ return i->e->k;
+ }
+-
++*/
+ 
/*/
+ /* value - return the value of the (key,value) pair at the current position */
+-
++/*
+ extern inline void *
+ hashtable_iterator_value(struct hashtable_itr *i)
+ {
+ return i->e->v;
+ }
+-
++*/
+ 
/*/
+ /* advance - advance the iterator to the next element
+  *   returns zero if advanced to end of table */
diff --git a/meta/recipes-devtools/mtd/mtd-utils_git.bb 
b/meta/recipes-devtools/mtd/mtd-utils_git.bb
index 52297c6..f903a65 100644
--- a/meta/recipes-devtools/mtd/mtd-utils_git.bb
+++ b/meta/recipes-devtools/mtd/mtd-utils_git.bb
@@ -11,6 +11,7 @@ SRCREV = "9f107132a6a073cce37434ca9cda6917dd8d866b"
 SRC_URI = "git://git.infradead.org/mtd-utils.git \
file://add-exclusion-to-mkfs-jffs2-git-2.patch \
file://fix-armv7-neon-alignment.patch \
+   file://mtd-utils-fix-hashtable_iterator.patch \
 "
 
 PV = "1.5.1+git${SRCPV}"
-- 
2.7.4

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

[OE-core] Question about multi rootfs UIDs when using wic

2018-01-19 Thread Volker Vogelhuber 

I'm currently trying to create a multi RootFS WIC image as mentioned in
directdisk-multi-rootfs.wks. For that I have two image recipes. One that 
is creating only an ext4 image (image-recovery), and the second that is 
also creating a WIC image (image-main). I used the IMAGE_FSTYPES 
variable for that. The WKS file for the second image is integrating the 
recovery image by specifying --rootfs-dir=image-recovery in it's part 
description.


# primary / recovery image
part / --source rootfs --rootfs-dir=image-main --exclude-path mnt/data/ 
mnt/data2/ --fstype=ext4 --label primary_rootfs --align 1024 --size 700 
--overhead-factor=1.0
part /recovery --source rootfs --rootfs-dir=image-recovery --fstype=ext4 
--label recovery_rootfs --align 1024 --size 640 --overhead-factor=1.0


The UIDs of the second rootfs (image-main) are correctly set to 0 within 
the file system when calling mkfs.ext4 during prepare_rootfs_ext. For 
the recovery rootfs the UID is always set to my own (host) one which is 
of course not valid for the image where that UID does not exist.
I tried calling the mkfs.ext4 command myself from a terminal and for 
whatever reason an image created out of the rootfs folder of the second 
image (image-main) recipe is deployed with the correct UID 0, while the 
rootfs folder of the first image (image-recovery) recipe always uses the 
UID of the source folder/files.


I search the code of e2fsprogs for the line that sets the UID and added 
a printf in set_inode_extra. There I can see clearly that the source UID 
for the file is 0 for the rootfs of the image-main rootfs folder while 
it is 1 (my own UID) for the image-recovery. I wonder how the UID of 
the image-main rootfs folder can be zero when I don't call any command 
with root permissions. I searched for a preparation step where the UIDs 
are managed in the scripts folder of Yocto, but didn't found any hint 
for the whole behavior. So while it is good that the rootfs partition of 
the main rootfs has the UID set correctly to zero, I can't understand 
why it happens. On the other side I can understand why the UID of the 
recovery rootfs is set to my own one, but it stops me from booting that 
rootfs because the UIDs of the files and folders are set to a user that 
does not exist on the target system.


Can someone please explain to me, how that UID handling is meant to be done?
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] mesa: Upgrade 17.3.2 -> 17.3.3 release

2018-01-19 Thread Otavio Salvador 
The 17.3.3 release, published in January 18th, 2018. It fixes a number
of issues since 17.3.2 release.

The release notes can be seen at:

  https://www.mesa3d.org/relnotes/17.3.3.html

Signed-off-by: Otavio Salvador 
---

 meta/recipes-graphics/mesa/{mesa-gl_17.3.2.bb => mesa-gl_17.3.3.bb} | 0
 meta/recipes-graphics/mesa/{mesa_17.3.2.bb => mesa_17.3.3.bb}   | 4 ++--
 2 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-graphics/mesa/{mesa-gl_17.3.2.bb => mesa-gl_17.3.3.bb} 
(100%)
 rename meta/recipes-graphics/mesa/{mesa_17.3.2.bb => mesa_17.3.3.bb} (88%)

diff --git a/meta/recipes-graphics/mesa/mesa-gl_17.3.2.bb 
b/meta/recipes-graphics/mesa/mesa-gl_17.3.3.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa-gl_17.3.2.bb
rename to meta/recipes-graphics/mesa/mesa-gl_17.3.3.bb
diff --git a/meta/recipes-graphics/mesa/mesa_17.3.2.bb 
b/meta/recipes-graphics/mesa/mesa_17.3.3.bb
similarity index 88%
rename from meta/recipes-graphics/mesa/mesa_17.3.2.bb
rename to meta/recipes-graphics/mesa/mesa_17.3.3.bb
index c2143ad32d..6e3f29a2c4 100644
--- a/meta/recipes-graphics/mesa/mesa_17.3.2.bb
+++ b/meta/recipes-graphics/mesa/mesa_17.3.3.bb
@@ -12,8 +12,8 @@ SRC_URI = 
"https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
file://0001-anv_icd.py-improve-reproducible-builds.patch \
"
 
-SRC_URI[md5sum] = "5c59b779925f504ffd0f13c7dcd29ac6"
-SRC_URI[sha256sum] = 
"e2844a13f2d6f8f24bee65804a51c42d8dc6ae9c36cff7ee61d0940e796d64c6"
+SRC_URI[md5sum] = "139b5f608b371c0d4395596162f88791"
+SRC_URI[sha256sum] = 
"41bac5de0ef6adc1f41a1ec0f80c19e361298ce02fa81b5f9ba4fdca33a9379b"
 
 #because we cannot rely on the fact that all apps will use pkgconfig,
 #make eglplatform.h independent of MESA_EGL_NO_X11_HEADER
-- 
2.16.0

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

[OE-core] ✗ patchtest: failure for mtd-utils: remove double hashtable iterator definition (rev3)

2018-01-19 Thread Patchwork 
== Series Details ==

Series: mtd-utils: remove double hashtable iterator definition (rev3)
Revision: 3
URL   : https://patchwork.openembedded.org/series/10612/
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 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 77144bc808)

* Issue Upstream-Status is Submitted, but it is not mentioned where 
[test_upstream_status_presence_format] 
  Suggested fixInclude where mtd-utils-fix-hashtable_iterator.patch was 
submitted
  Current  Upstream-Status: Submitted to dizzy
  Standard format  Upstream-Status: Submitted [where]



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

Re: [OE-core] [oe-commits] [openembedded-core] 08/08: json-glib: update to 1.4.2

2018-01-19 Thread Alexander Kanavin 

On 01/19/2018 04:06 PM, Martin Jansa wrote:

qemuarm, qemux86, raspberrypi3 and few more arm MACHINEs.


I just tried with qemux86 - builds fine, and the g-i files are present 
in the packages.


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

Re: [OE-core] [PATCH] [OE-CORE] [PATCH v3] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Alexander Kanavin 

On 01/19/2018 05:07 PM, Oleg Kokorin wrote:


+Upstream-Status: Submitted to dizzy


Upstream here means the maintainers of mtd-utils. Have you shown the 
patch to them? What did they say?


Also, if you're seeing this with dizzy, this is a very old and no longer 
supported or maintained Yocto release. Does the problem occur with any 
of the recent ones? Or shall the patch only be applied to the dizzy branch?



+mtd-utils: remove double hashtable iterator definition
+
+hashtable_iterator_key and hashtable_iterator_value redefinition inside
+mkfs.ubifs/hashtable/hashtable_itr.h cause linker redefinition error


You need to include the error message here.


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

[OE-core] [PATCH] [OE-CORE] [PATCH v3] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Oleg Kokorin 
hashtable_iterator_key and hashtable_iterator_value redefinition inside
mkfs.ubifs/hashtable/hashtable_itr.h cause linker redefinition error

Signed-off-by: Oleg Kokorin 
---
 .../mtd-utils-fix-hashtable_iterator.patch | 43 ++
 meta/recipes-devtools/mtd/mtd-utils_git.bb |  1 +
 2 files changed, 44 insertions(+)
 create mode 100644 
meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch

diff --git 
a/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch 
b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
new file mode 100644
index 000..4253286
--- /dev/null
+++ b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
@@ -0,0 +1,43 @@
+Upstream-Status: Submitted to dizzy
+
+Author: Oleg Kokorin 
+Date:   Fri Jan 19 11:52:12 2018 +0100
+
+mtd-utils: remove double hashtable iterator definition
+
+hashtable_iterator_key and hashtable_iterator_value redefinition inside
+mkfs.ubifs/hashtable/hashtable_itr.h cause linker redefinition error
+
+Signed-off-by: Oleg Kokorin 
+
+Index: 
setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/x86_64-linux/mtd-utils-native/1.5.1+gitAUTOINC+9f107132a6-r0/git/mkfs.ubifs/hashtable/hashtable_itr.h
+===
+--- a/mkfs.ubifs/hashtable/hashtable_itr.h
 b/mkfs.ubifs/hashtable/hashtable_itr.h
+@@ -27,22 +27,22 @@ hashtable_iterator(struct hashtable *h);
+ 
/*/
+ /* hashtable_iterator_key
+  * - return the value of the (key,value) pair at the current position */
+-
++/*
+ extern inline void *
+ hashtable_iterator_key(struct hashtable_itr *i)
+ {
+ return i->e->k;
+ }
+-
++*/
+ 
/*/
+ /* value - return the value of the (key,value) pair at the current position */
+-
++/*
+ extern inline void *
+ hashtable_iterator_value(struct hashtable_itr *i)
+ {
+ return i->e->v;
+ }
+-
++*/
+ 
/*/
+ /* advance - advance the iterator to the next element
+  *   returns zero if advanced to end of table */
diff --git a/meta/recipes-devtools/mtd/mtd-utils_git.bb 
b/meta/recipes-devtools/mtd/mtd-utils_git.bb
index 52297c6..f903a65 100644
--- a/meta/recipes-devtools/mtd/mtd-utils_git.bb
+++ b/meta/recipes-devtools/mtd/mtd-utils_git.bb
@@ -11,6 +11,7 @@ SRCREV = "9f107132a6a073cce37434ca9cda6917dd8d866b"
 SRC_URI = "git://git.infradead.org/mtd-utils.git \
file://add-exclusion-to-mkfs-jffs2-git-2.patch \
file://fix-armv7-neon-alignment.patch \
+   file://mtd-utils-fix-hashtable_iterator.patch \
 "
 
 PV = "1.5.1+git${SRCPV}"
-- 
2.7.4

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

[OE-core] [PATCH 3/3] connman: Implement subnet route in session

2018-01-19 Thread André Draszik 
From: Jian Liang 

Implement subnet route creation/deletion in session, e.g.

default via 192.168.100.1 dev eth0
192.168.100.0/24 dev eth0

Signed-off-by: Jian Liang 
Signed-off-by: André Draszik 
---
 ...Add-prefixlen-to-iproute_default_function.patch | 63 ++
 ...ent-subnet-route-creation-deletion-in-ipr.patch | 69 +++
 ...ent-APIs-for-creating-and-deleting-subnet.patch | 68 +++
 ...e-subnet-route-creation-and-deletion-APIs.patch | 77 ++
 meta/recipes-connectivity/connman/connman_1.35.bb  |  4 ++
 5 files changed, 281 insertions(+)
 create mode 100644 
meta/recipes-connectivity/connman/connman/0001-inet-Add-prefixlen-to-iproute_default_function.patch
 create mode 100644 
meta/recipes-connectivity/connman/connman/0002-inet-Implement-subnet-route-creation-deletion-in-ipr.patch
 create mode 100644 
meta/recipes-connectivity/connman/connman/0003-inet-Implement-APIs-for-creating-and-deleting-subnet.patch
 create mode 100644 
meta/recipes-connectivity/connman/connman/0004-session-Use-subnet-route-creation-and-deletion-APIs.patch

diff --git 
a/meta/recipes-connectivity/connman/connman/0001-inet-Add-prefixlen-to-iproute_default_function.patch
 
b/meta/recipes-connectivity/connman/connman/0001-inet-Add-prefixlen-to-iproute_default_function.patch
new file mode 100644
index 00..dd7b356741
--- /dev/null
+++ 
b/meta/recipes-connectivity/connman/connman/0001-inet-Add-prefixlen-to-iproute_default_function.patch
@@ -0,0 +1,63 @@
+From 508dc60a1f0758ebc586b6b086478a176d493086 Mon Sep 17 00:00:00 2001
+From: Jian Liang 
+Date: Thu, 5 Oct 2017 09:34:41 +0100
+Subject: [PATCH 1/4] inet: Add prefixlen to iproute_default_function
+To: conn...@lists.01.org
+Cc: w...@monom.org
+
+Add prefixlen parameter to this function in preparation for using
+it also in creating subnet route later, e.g.
+
+default via 192.168.100.1 dev eth0
+192.168.100.0/24 dev eth0
+
+Signed-off-by: Jian Liang 
+
+---
+Upstream-Status: Backport 
[https://git.kernel.org/pub/scm/network/connman/connman.git/commit/?id=edda5b695de2ee79f02314abc9b46fdd46b388e1]
+Signed-off-by: André Draszik 
+ src/inet.c | 7 ---
+ 1 file changed, 4 insertions(+), 3 deletions(-)
+
+diff --git a/src/inet.c b/src/inet.c
+index b887aa0..ab8aec8 100644
+--- a/src/inet.c
 b/src/inet.c
+@@ -2796,7 +2796,7 @@ int __connman_inet_del_fwmark_rule(uint32_t table_id, 
int family, uint32_t fwmar
+ }
+ 
+ static int iproute_default_modify(int cmd, uint32_t table_id, int ifindex,
+-  const char *gateway)
++  const char *gateway, unsigned char prefixlen)
+ {
+   struct __connman_inet_rtnl_handle rth;
+   unsigned char buf[sizeof(struct in6_addr)];
+@@ -2829,6 +2829,7 @@ static int iproute_default_modify(int cmd, uint32_t 
table_id, int ifindex,
+   rth.req.u.r.rt.rtm_protocol = RTPROT_BOOT;
+   rth.req.u.r.rt.rtm_scope = RT_SCOPE_UNIVERSE;
+   rth.req.u.r.rt.rtm_type = RTN_UNICAST;
++  rth.req.u.r.rt.rtm_dst_len = prefixlen;
+ 
+   __connman_inet_rtnl_addattr_l(, sizeof(rth.req), RTA_GATEWAY,
+   buf, len);
+@@ -2860,7 +2861,7 @@ int __connman_inet_add_default_to_table(uint32_t 
table_id, int ifindex,
+ {
+   /* ip route add default via 1.2.3.4 dev wlan0 table 1234 */
+ 
+-  return iproute_default_modify(RTM_NEWROUTE, table_id, ifindex, gateway);
++  return iproute_default_modify(RTM_NEWROUTE, table_id, ifindex, gateway, 
0);
+ }
+ 
+ int __connman_inet_del_default_from_table(uint32_t table_id, int ifindex,
+@@ -2868,7 +2869,7 @@ int __connman_inet_del_default_from_table(uint32_t 
table_id, int ifindex,
+ {
+   /* ip route del default via 1.2.3.4 dev wlan0 table 1234 */
+ 
+-  return iproute_default_modify(RTM_DELROUTE, table_id, ifindex, gateway);
++  return iproute_default_modify(RTM_DELROUTE, table_id, ifindex, gateway, 
0);
+ }
+ 
+ int __connman_inet_get_interface_ll_address(int index, int family,
+-- 
+2.7.4
+
diff --git 
a/meta/recipes-connectivity/connman/connman/0002-inet-Implement-subnet-route-creation-deletion-in-ipr.patch
 
b/meta/recipes-connectivity/connman/connman/0002-inet-Implement-subnet-route-creation-deletion-in-ipr.patch
new file mode 100644
index 00..9c953e5d51
--- /dev/null
+++ 
b/meta/recipes-connectivity/connman/connman/0002-inet-Implement-subnet-route-creation-deletion-in-ipr.patch
@@ -0,0 +1,69 @@
+From 08cda4004491d3971a8b9df937426c43800d15b1 Mon Sep 17 00:00:00 2001
+From: Jian Liang 
+Date: Thu, 5 Oct 2017 09:37:06 +0100
+Subject: [PATCH 2/4] inet: Implement subnet route creation/deletion in
+ iproute_default_modify
+To: conn...@lists.01.org
+Cc: w...@monom.org
+
+- Calculate subnet address base on gateway address and prefixlen
+- Differentiate creation of routes to

[OE-core] [PATCH 2/3] connman: Fix a crash using wispr over TLS

2018-01-19 Thread André Draszik 
From: Jian Liang 

This is happened when doing wispr against a HTTPS URL
rather than the default one, i.e.
http://ipv4.connman.net/online/status.html

When gnutls_channel is instantiated, the gnutls_channel->established
has to be initiated as FALSE. Otherwise, check_handshake function
won't work. A random initial value 1 of gnutls_channel->established
will make check_handshake return G_IO_STATUS_NORMAL, when the channel
is actually not ready to be used. The observed behaviours are,

- wispr is getting random errors in wispr_portal_web_result
- ConnMan crashes on exit after those random errors
- when wispr is luckly working, ConnMan doesn't crash on exit

Signed-off-by: Jian Liang 
Signed-off-by: André Draszik 
---
 ...iognutls-Fix-a-crash-using-wispr-over-TLS.patch | 41 ++
 meta/recipes-connectivity/connman/connman_1.35.bb  |  1 +
 2 files changed, 42 insertions(+)
 create mode 100644 
meta/recipes-connectivity/connman/connman/0001-giognutls-Fix-a-crash-using-wispr-over-TLS.patch

diff --git 
a/meta/recipes-connectivity/connman/connman/0001-giognutls-Fix-a-crash-using-wispr-over-TLS.patch
 
b/meta/recipes-connectivity/connman/connman/0001-giognutls-Fix-a-crash-using-wispr-over-TLS.patch
new file mode 100644
index 00..f9080d4ba9
--- /dev/null
+++ 
b/meta/recipes-connectivity/connman/connman/0001-giognutls-Fix-a-crash-using-wispr-over-TLS.patch
@@ -0,0 +1,41 @@
+From 929fc9b7068100444e0ffcccd25841f78791e619 Mon Sep 17 00:00:00 2001
+From: Jian Liang 
+Date: Fri, 15 Sep 2017 06:40:08 -0400
+Subject: [PATCH] gweb: Fix a crash using wispr over TLS
+To: conn...@lists.01.org
+Cc: w...@monom.org
+
+When gnutls_channel is instantiated, the gnutls_channel->established
+has to be initiated as FALSE. Otherwise, check_handshake function
+won't work. A random initial value 1 of gnutls_channel->established
+will make check_handshake return G_IO_STATUS_NORMAL, when the channel
+is actually not ready to be used. The observed behaviours are,
+
+- wispr is getting random errors in wispr_portal_web_result
+- ConnMan crashes on exit after those random errors
+- when wispr is luckly working, ConnMan doesn't crash on exit
+
+Signed-off-by: Jian Liang 
+
+---
+Upstream-Status: Backport 
[https://git.kernel.org/pub/scm/network/connman/connman.git/commit/?id=73e53f3bd9e7debae86341f1eee7b97862a56a5e]
+Signed-off-by: André Draszik 
+ gweb/giognutls.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/gweb/giognutls.c b/gweb/giognutls.c
+index 09dc9e7..c029a8b 100644
+--- a/gweb/giognutls.c
 b/gweb/giognutls.c
+@@ -421,7 +421,7 @@ GIOChannel *g_io_channel_gnutls_new(int fd)
+ 
+   DBG("");
+ 
+-  gnutls_channel = g_new(GIOGnuTLSChannel, 1);
++  gnutls_channel = g_new0(GIOGnuTLSChannel, 1);
+ 
+   channel = (GIOChannel *) gnutls_channel;
+ 
+-- 
+2.7.4
+
diff --git a/meta/recipes-connectivity/connman/connman_1.35.bb 
b/meta/recipes-connectivity/connman/connman_1.35.bb
index e7e5d38d61..4663a7e3e8 100644
--- a/meta/recipes-connectivity/connman/connman_1.35.bb
+++ b/meta/recipes-connectivity/connman/connman_1.35.bb
@@ -7,6 +7,7 @@ SRC_URI  = 
"${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
 file://no-version-scripts.patch \
 file://includes.patch \
 file://0001-session-Keep-track-of-addr-in-fw_snat-session.patch \
+file://0001-giognutls-Fix-a-crash-using-wispr-over-TLS.patch \
 "
 SRC_URI_append_libc-musl = " 
file://0002-resolve-musl-does-not-implement-res_ninit.patch \
  "
-- 
2.15.1

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

[OE-core] [PATCH 1/3] connman: fix nat-postrouting not update issue

2018-01-19 Thread André Draszik 
From: Jian Liang 

When more than one session are created with the same
"AllowedInterface", connman failed to update nat-
postrouting rules when new IP address was got

Signed-off-by: Jian Liang 
Signed-off-by: André Draszik 
---
 ...ion-Keep-track-of-addr-in-fw_snat-session.patch | 112 +
 meta/recipes-connectivity/connman/connman_1.35.bb  |   1 +
 2 files changed, 113 insertions(+)
 create mode 100644 
meta/recipes-connectivity/connman/connman/0001-session-Keep-track-of-addr-in-fw_snat-session.patch

diff --git 
a/meta/recipes-connectivity/connman/connman/0001-session-Keep-track-of-addr-in-fw_snat-session.patch
 
b/meta/recipes-connectivity/connman/connman/0001-session-Keep-track-of-addr-in-fw_snat-session.patch
new file mode 100644
index 00..f1b4d0aaa7
--- /dev/null
+++ 
b/meta/recipes-connectivity/connman/connman/0001-session-Keep-track-of-addr-in-fw_snat-session.patch
@@ -0,0 +1,112 @@
+From b5fd5945886fa1845db5c969424b63d894fe0376 Mon Sep 17 00:00:00 2001
+From: Jian Liang 
+Date: Fri, 25 Aug 2017 10:02:16 -0400
+Subject: [PATCH 1/2] session: Keep track of addr in fw_snat & session
+To: conn...@lists.01.org
+Cc: w...@monom.org
+
+When there is more than one session in fw_snat's list of sessions,
+fw_snat failed to be re-created when update-session-state is triggered
+with new IP address. This is because index alone is not sufficient to
+decide if fw_snat needs to be re-created. The solution here is to keep
+a track of IP addr and use it to avoid false lookup of fw_snat.
+
+Signed-off-by: Jian Liang 
+
+---
+Upstream-Status: Backport 
[https://git.kernel.org/pub/scm/network/connman/connman.git/commit/?id=f9e27d4abfcab5c80a38e0850b5ddb26277f97c1]
+Signed-off-by: André Draszik 
+ src/session.c | 19 +++
+ 1 file changed, 15 insertions(+), 4 deletions(-)
+
+diff --git a/src/session.c b/src/session.c
+index 9e3c559..965ac06 100644
+--- a/src/session.c
 b/src/session.c
+@@ -65,6 +65,7 @@ struct connman_session {
+   struct firewall_context *fw;
+   uint32_t mark;
+   int index;
++  char *addr;
+   char *gateway;
+   bool policy_routing;
+   bool snat_enabled;
+@@ -79,6 +80,7 @@ struct fw_snat {
+   GSList *sessions;
+   int id;
+   int index;
++  char *addr;
+   struct firewall_context *fw;
+ };
+ 
+@@ -200,7 +202,7 @@ static char *service2bearer(enum connman_service_type type)
+   return "";
+ }
+ 
+-static struct fw_snat *fw_snat_lookup(int index)
++static struct fw_snat *fw_snat_lookup(int index, const char *addr)
+ {
+   struct fw_snat *fw_snat;
+   GSList *list;
+@@ -208,8 +210,11 @@ static struct fw_snat *fw_snat_lookup(int index)
+   for (list = fw_snat_list; list; list = list->next) {
+   fw_snat = list->data;
+ 
+-  if (fw_snat->index == index)
++  if (fw_snat->index == index) {
++  if (g_strcmp0(addr, fw_snat->addr) != 0)
++  continue;
+   return fw_snat;
++  }
+   }
+   return NULL;
+ }
+@@ -224,6 +229,7 @@ static int fw_snat_create(struct connman_session *session,
+ 
+   fw_snat->fw = __connman_firewall_create();
+   fw_snat->index = index;
++  fw_snat->addr = g_strdup(addr);
+ 
+   fw_snat->id = __connman_firewall_enable_snat(fw_snat->fw,
+   index, ifname, addr);
+@@ -238,6 +244,7 @@ static int fw_snat_create(struct connman_session *session,
+   return 0;
+ err:
+   __connman_firewall_destroy(fw_snat->fw);
++  g_free(fw_snat->addr);
+   g_free(fw_snat);
+   return err;
+ }
+@@ -393,7 +400,7 @@ static void del_nat_rules(struct connman_session *session)
+   return;
+ 
+   session->snat_enabled = false;
+-  fw_snat = fw_snat_lookup(session->index);
++  fw_snat = fw_snat_lookup(session->index, session->addr);
+ 
+   if (!fw_snat)
+   return;
+@@ -420,8 +427,11 @@ static void add_nat_rules(struct connman_session *session)
+   if (!addr)
+   return;
+ 
++  g_free(session->addr);
++  session->addr = g_strdup(addr);
++
+   session->snat_enabled = true;
+-  fw_snat = fw_snat_lookup(index);
++  fw_snat = fw_snat_lookup(index, session->addr);
+   if (fw_snat) {
+   fw_snat_ref(session, fw_snat);
+   return;
+@@ -502,6 +512,7 @@ static void free_session(struct connman_session *session)
+   g_free(session->info);
+   g_free(session->info_last);
+   g_free(session->gateway);
++  g_free(session->addr);
+ 
+   g_free(session);
+ }
+-- 
+2.7.4
+
diff --git a/meta/recipes-connectivity/connman/connman_1.35.bb 
b/meta/recipes-connectivity/connman/connman_1.35.bb
index 950946fe76..e7e5d38d61 100644
---

[OE-core] [PATCH 0/3] connman: add a few backported patches

2018-01-19 Thread André Draszik 
The following patches backport a few connman fixes, as connman
hasn't seen a new release since August 2017.

Cheers,
Andre'

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

Re: [OE-core] [PATCH] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Burton, Ross 
On 19 January 2018 at 14:23, Oleg Kokorin  wrote:

> hello Ross
>
> the whole patch supply procedure these days is completely messed-up IMHO.
>
> if I'm not sending to upstream, then why the damn patch being e-mailed? or
> perhaps
> just because I can't understand the difference in between "pending"
> (where?), "submitted" (definitely is),
> "accepted" (by who?), "backport" (to where?), "denied" (do you really
> assume someone will push the patch with the flag "denied" in it?
>
> you've added too much complexity requirements to apply inside the patch
> file.
> how could I know what means for you "sending or not" to upstream?
>
> from the wiki point, it's completely unclear what kind of status should I
> apply for the patch by default.
> https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
> so what do you want for "Upstream-Status:" instead of pending?
>

"Upstream" in distribution-builder-land means "the maintainer of the
package that I'm trying to build".  So in this case, the mtd-utils
maintainers.  If you've got a patch and cannot  be bothered to submit it
upstream, Pending is correct. Submitted means you've submitted it to the
maintainers.  Accepted means they've accepted it.  Backport means you've
backported the patch from the upstream source.  Denied means upstream have
refused the patch but we need it for some reason.


> and by the way, a robot refused my patch again, because it's not in sync
> with whatever the new stuff is in.
> if "git pull --rebase" is not enough, it would be WAY better to mention
> this command specifically in the WIKI about.
> I see a lot of completely useless text in the wiki but it helped not at
> all to push the patch an easy and more important the fast way.
>

That should be sufficient, I can confirm that your patch doesn't apply to
master, and the last time this file was modified was in December, so maybe
you're not working from the right branch?

and, GIT know's well who is signign and what is the commit message, so if
> you need patches with the git log attached ahead of each, why not to
> mention in wiki special command about injecting log message inside patch
> file. this definitely will simplify patches submission.
>

It's entirely appropriate for the patch to have a much longer explanatory
message than the commit.  Also I can send a patch to oe-core which contains
a patch that someone else has authored, in which case copying it
automatically wouldn't be correct.

All we're asking is that any patches added say what they do, if they're
upstream, and who wrote it.

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

Re: [OE-core] ✗ patchtest: failure - defective robot

2018-01-19 Thread Oleg Kokorin 

hello All

anybody know the proper way to crack around this useless robot keeping complaining about missing Sign-Off field inside the patch file while the field is in?

thanks

Oleg

 

Sent: Friday, January 19, 2018 at 3:02 PM
From: Patchwork 
To: "Oleg Kokorin" 
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for mtd-utils: remove double hashtable iterator definition (rev2)

== Series Details ==

Series: mtd-utils: remove double hashtable iterator definition (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/10612/
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 Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at 77144bc808)

* Issue A patch file has been added, but does not have a Signed-off-by tag [test_signed_off_by_presence]
Suggested fix Sign off the added patch file (meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.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] -> ...).

---
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

Re: [OE-core] [oe-commits] [openembedded-core] 08/08: json-glib: update to 1.4.2

2018-01-19 Thread Burton, Ross 
On 19 January 2018 at 14:06, Martin Jansa  wrote:

> qemuarm, qemux86, raspberrypi3 and few more arm MACHINEs.
>

Can you replicate with nodistro?

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

Re: [OE-core] [oe-commits] [openembedded-core] 08/08: json-glib: update to 1.4.2

2018-01-19 Thread Martin Jansa 
qemuarm, qemux86, raspberrypi3 and few more arm MACHINEs.

On Fri, Jan 19, 2018 at 3:02 PM, Burton, Ross  wrote:

> On 19 January 2018 at 13:58, Martin Jansa  wrote:
>
>> It fails here since this upgrade, maybe the 0001-Do-not-disable-gobjec
>> t-introspection-when-cross-comp.patch is still useful and wasn't
>> completely merged upstream?
>>
>
> The patch was to let G-I work when cross-compiling, so it's unrelated.
>
>
>> FAILED: json-glib/Json-1.0.typelib
>> json-glib/1.4.2-r0/recipe-sysroot/usr/bin/g-ir-compiler-wrapper
>> json-glib/Json-1.0.gir --output json-glib/Json-1.0.typelib
>> Could not find GIR file 'GObject-2.0.gir'; check XDG_DATA_DIRS or use
>> --includedir
>> error parsing file json-glib/Json-1.0.gir: Failed to parse included gir
>> GObject-2.0
>> If the above error message is about missing .so libraries, then setting
>> up GIR_EXTRA_LIBS_PATH in the recipe should help.
>> (typically like this: GIR_EXTRA_LIBS_PATH="${B}/something/.libs" )
>> ninja: build stopped: subcommand failed.
>> WARNING: exit code 1 from a shell command.
>>
>
> What MACHINE?
>
> Ross
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [oe-commits] [openembedded-core] 08/08: json-glib: update to 1.4.2

2018-01-19 Thread Burton, Ross 
On 19 January 2018 at 13:58, Martin Jansa  wrote:

> It fails here since this upgrade, maybe the 0001-Do-not-disable-gobjec
> t-introspection-when-cross-comp.patch is still useful and wasn't
> completely merged upstream?
>

The patch was to let G-I work when cross-compiling, so it's unrelated.


> FAILED: json-glib/Json-1.0.typelib
> json-glib/1.4.2-r0/recipe-sysroot/usr/bin/g-ir-compiler-wrapper
> json-glib/Json-1.0.gir --output json-glib/Json-1.0.typelib
> Could not find GIR file 'GObject-2.0.gir'; check XDG_DATA_DIRS or use
> --includedir
> error parsing file json-glib/Json-1.0.gir: Failed to parse included gir
> GObject-2.0
> If the above error message is about missing .so libraries, then setting up
> GIR_EXTRA_LIBS_PATH in the recipe should help.
> (typically like this: GIR_EXTRA_LIBS_PATH="${B}/something/.libs" )
> ninja: build stopped: subcommand failed.
> WARNING: exit code 1 from a shell command.
>

What MACHINE?

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

[OE-core] ✗ patchtest: failure for mtd-utils: remove double hashtable iterator definition (rev2)

2018-01-19 Thread Patchwork 
== Series Details ==

Series: mtd-utils: remove double hashtable iterator definition (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/10612/
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 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 77144bc808)

* 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-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.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] -> ...).

---
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

Re: [OE-core] [PATCH] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Burton, Ross 
On 19 January 2018 at 13:54, Oleg Kokorin  wrote:

> +Upstream-Status: Pending
>

Is there a reason you're not sending this upstream?

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

Re: [OE-core] [PATCH] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Burton, Ross 
On 19 January 2018 at 13:57, Oleg Kokorin  wrote:

> I've got the points and re-sent the patch, but I'd like to add mine:
>
> by adding complexity instead of taking care of git and specifically
> send-email command providing necessary portions you'd like to have in patch
> in automated manner - you are decrising number of participants
> significantly.
>

Re-adding oe-core again.

How can git know that you're the original author of the patch and didn't
just copy/paste?  How can git know that you've hacked a workaround, or
backported a fix from upstream?

I'm fine with a small barrier to contributions when it means that in five
years time I'm not scratching my head at a patch with lost history, no
comments, no ownership, no indication whether it's a workaround or should
be sent upstream, wondering what it was meant to do.

There are still plenty of patches like that in oe-core, where the history
disappears into BitKeeper repositories that nobody has anymore.

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

Re: [OE-core] [oe-commits] [openembedded-core] 08/08: json-glib: update to 1.4.2

2018-01-19 Thread Martin Jansa 
It fails here since this upgrade, maybe the 0001-Do-not-disable-
gobject-introspection-when-cross-comp.patch is still useful and wasn't
completely merged upstream?

FAILED: json-glib/Json-1.0.typelib
json-glib/1.4.2-r0/recipe-sysroot/usr/bin/g-ir-compiler-wrapper
json-glib/Json-1.0.gir --output json-glib/Json-1.0.typelib
Could not find GIR file 'GObject-2.0.gir'; check XDG_DATA_DIRS or use
--includedir
error parsing file json-glib/Json-1.0.gir: Failed to parse included gir
GObject-2.0
If the above error message is about missing .so libraries, then setting up
GIR_EXTRA_LIBS_PATH in the recipe should help.
(typically like this: GIR_EXTRA_LIBS_PATH="${B}/something/.libs" )
ninja: build stopped: subcommand failed.
WARNING: exit code 1 from a shell command.

On Thu, Jan 18, 2018 at 1:51 PM,  wrote:

> This is an automated email from the git hooks/post-receive script.
>
> rpurdie pushed a commit to branch master
> in repository openembedded-core.
>
> commit 6b87ad5b08004554f08d2f68027908956f3795e1
> Author: Yi Zhao 
> AuthorDate: Tue Jan 16 08:32:33 2018 +0800
>
> json-glib: update to 1.4.2
>
> Drop 0001-Do-not-disable-gobject-introspection-when-cross-comp.patch
> since it has been fixed upstream.
>
> Signed-off-by: Yi Zhao 
> Signed-off-by: Richard Purdie 
> ---
>  ...ble-gobject-introspection-when-cross-comp.patch | 32
> --
>  .../{json-glib_1.2.8.bb => json-glib_1.4.2.bb} |  7 ++---
>  2 files changed, 2 insertions(+), 37 deletions(-)
>
> diff --git a/meta/recipes-gnome/json-glib/json-glib/0001-Do-not-
> disable-gobject-introspection-when-cross-comp.patch
> b/meta/recipes-gnome/json-glib/json-glib/0001-Do-not-
> disable-gobject-introspection-when-cross-comp.patch
> deleted file mode 100644
> index 849bb9d..000
> --- a/meta/recipes-gnome/json-glib/json-glib/0001-Do-not-
> disable-gobject-introspection-when-cross-comp.patch
> +++ /dev/null
> @@ -1,32 +0,0 @@
> -From 293452c963188666dae99521294f09a0cf9582e2 Mon Sep 17 00:00:00 2001
> -From: Alexander Kanavin 
> -Date: Fri, 4 Aug 2017 16:01:11 +0300
> -Subject: [PATCH] Do not disable gobject introspection when
> cross-compiling.
> -
> -Introspection does work fine for instance in Open Embedded,
> -one of the most prominent cross-compilation frameworks
> -(through qemu emulating target hardware), so let the user
> -decide if he wants the feature or not.
> -
> -Upstream-Status: Pending
> -Signed-off-by: Alexander Kanavin 
> 
> - meson.build | 2 +-
> - 1 file changed, 1 insertion(+), 1 deletion(-)
> -
> -diff --git a/meson.build b/meson.build
> -index 43cbfd9..8a32f26 100644
>  a/meson.build
> -+++ b/meson.build
> -@@ -147,7 +147,7 @@ root_dir = include_directories('.')
> -
> - gnome = import('gnome')
> - gir = find_program('g-ir-scanner', required: false)
> --build_gir = gir.found() and not meson.is_cross_build() and not
> get_option('disable_introspection')
> -+build_gir = gir.found() and not get_option('disable_introspection')
> -
> - subdir('json-glib')
> -
> ---
> -2.13.2
> -
> diff --git a/meta/recipes-gnome/json-glib/json-glib_1.2.8.bb
> b/meta/recipes-gnome/json-glib/json-glib_1.4.2.bb
> similarity index 84%
> rename from meta/recipes-gnome/json-glib/json-glib_1.2.8.bb
> rename to meta/recipes-gnome/json-glib/json-glib_1.4.2.bb
> index 31912d1..fad0a2d 100644
> --- a/meta/recipes-gnome/json-glib/json-glib_1.2.8.bb
> +++ b/meta/recipes-gnome/json-glib/json-glib_1.4.2.bb
> @@ -10,11 +10,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=
> 7fbc338309ac38fefcd64b04bb903e34"
>
>  DEPENDS = "glib-2.0"
>
> -SRC_URI_append = " \
> -   
> file://0001-Do-not-disable-gobject-introspection-when-cross-comp.patch
> \
> -   "
> -SRC_URI[archive.md5sum] = "ff31e7d0594df44318e12facda3d086e"
> -SRC_URI[archive.sha256sum] = "fd55a9037d39e7a10f0db64309f5f0
> 265fa32ec962bf85066087b83a2807f40a"
> +SRC_URI[archive.md5sum] = "35107e23a7bbbc70f31c34f7b9adf1c3"
> +SRC_URI[archive.sha256sum] = "2d7709a44749c7318599a6829322e0
> 81915bdc73f5be5045882ed120bb686dc8"
>
>  GNOMEBASEBUILDCLASS = "meson"
>  inherit gnomebase lib_package gobject-introspection gtk-doc manpages
> gettext
>
> --
> To stop receiving notification emails like this one, please contact
> the administrator of this repository.
> --
> ___
> Openembedded-commits mailing list
> openembedded-comm...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-commits
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Oleg Kokorin 
hashtable_iterator_key and hashtable_iterator_value redefinition inside
mkfs.ubifs/hashtable/hashtable_itr.h cause linker redefinition error

Signed-off-by: Oleg Kokorin 
---
 .../mtd-utils-fix-hashtable_iterator.patch | 43 ++
 meta/recipes-devtools/mtd/mtd-utils_git.bb |  1 +
 2 files changed, 44 insertions(+)
 create mode 100644 
meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch

diff --git 
a/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch 
b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
new file mode 100644
index 000..c7a46bd
--- /dev/null
+++ b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
@@ -0,0 +1,43 @@
+Upstream-Status: Pending
+
+Author: Oleg Kokorin 
+Date:   Fri Jan 19 11:52:12 2018 +0100
+
+mtd-utils: remove double hashtable iterator definition
+
+hashtable_iterator_key and hashtable_iterator_value redefinition inside
+mkfs.ubifs/hashtable/hashtable_itr.h cause linker redefinition error
+
+Signed-off-by: Oleg Kokorin 
+
+Index: 
setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/x86_64-linux/mtd-utils-native/1.5.1+gitAUTOINC+9f107132a6-r0/git/mkfs.ubifs/hashtable/hashtable_itr.h
+===
+--- a/mkfs.ubifs/hashtable/hashtable_itr.h
 b/mkfs.ubifs/hashtable/hashtable_itr.h
+@@ -27,22 +27,22 @@ hashtable_iterator(struct hashtable *h);
+ 
/*/
+ /* hashtable_iterator_key
+  * - return the value of the (key,value) pair at the current position */
+-
++/*
+ extern inline void *
+ hashtable_iterator_key(struct hashtable_itr *i)
+ {
+ return i->e->k;
+ }
+-
++*/
+ 
/*/
+ /* value - return the value of the (key,value) pair at the current position */
+-
++/*
+ extern inline void *
+ hashtable_iterator_value(struct hashtable_itr *i)
+ {
+ return i->e->v;
+ }
+-
++*/
+ 
/*/
+ /* advance - advance the iterator to the next element
+  *   returns zero if advanced to end of table */
diff --git a/meta/recipes-devtools/mtd/mtd-utils_git.bb 
b/meta/recipes-devtools/mtd/mtd-utils_git.bb
index 52297c6..f903a65 100644
--- a/meta/recipes-devtools/mtd/mtd-utils_git.bb
+++ b/meta/recipes-devtools/mtd/mtd-utils_git.bb
@@ -11,6 +11,7 @@ SRCREV = "9f107132a6a073cce37434ca9cda6917dd8d866b"
 SRC_URI = "git://git.infradead.org/mtd-utils.git \
file://add-exclusion-to-mkfs-jffs2-git-2.patch \
file://fix-armv7-neon-alignment.patch \
+   file://mtd-utils-fix-hashtable_iterator.patch \
 "
 
 PV = "1.5.1+git${SRCPV}"
-- 
2.7.4

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

Re: [OE-core] [PATCH] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Burton, Ross 
On 19 January 2018 at 13:17, Oleg Kokorin  wrote:

> hello Ross
> why do I see this e-mail from you?
> "Signed-off-by: Oleg Kokorin " is in the patch.
>

The file mtd-utils-fix-hashtable_iterator.patch needs this information
too.  See the wiki link I added (and the mail from patchtest that was also
sent).

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

Re: [OE-core] [PATCH v2] package: Record PE and PR values for shlib dependencies

2018-01-19 Thread Böszörményi Zoltán 

Ping.

Do you have any objection against the idea of this patch
after the described observations?

Thanks in advance,
Zoltán Böszörményi

2018-01-16 11:10 keltezéssel, Böszörményi Zoltán írta:

2018-01-14 12:27 keltezéssel, Richard Purdie írta:

On Fri, 2018-01-12 at 14:46 +0100, Böszörményi Zoltán wrote:

When downgrading a package or using a substitute with lower version,
the way to do it is adding or increasing PE and there may be other
reasons to set PE.

But it doesn't directly help dependant packages because the shlib
records only contain PV.

Let's add the PE value into the shlib records for packages where
it's set.

The in-memory variables storing the versions now use the PE:PV
notation but the on-disk files must use something else because
the : character is already used as field delimiter in the
package.list
files storing the shlib records. Use # instead in the files,
so the file format doesn't change. Conversion occurs on reading
and writing the package.list files.


Can you explain a bit more about why/how this causes a problem?

PE is needed to maintain consistency of package feeds but the shlibs
code is primarily used for build time dependency analysis to figure out
which packages need to depend upon what and ensure runtime dependencies
are met. I'm not sure that should care about PE.


See my mail about describing the use case at
http://lists.openembedded.org/pipermail/openembedded-devel/2018-January/116291.html

Practically it can prevent proper dist-ugprade because
library package dependencies can be installed later
than binaries requiring them. If this happens, running
any binary may crash in the pkg_postinst scriptlet.

My use case was the eglibc_linaro-2.19 -> glibc_2.24 transition
but any upgrade where the package already has a PE value set
may be in the same situation. E.g. glib-2.0 1:2.48.2 in Morty vs
1:2.52.3 in Rocko.

A bbappend file can also modify PV. In case PE is missing from
the shlib deps, you can even end up with the same situation
in the same distro with extra layers.


For PR, again its primarily for package feeds so that updates are
detected and I'm not sure why the shlibs code should need to care about
it.


Besides PE, it is also better to always ship libraries and
binaries from the same build, i.e. with the same PV-PR value.

Such an example is e.g. util-linux with util-linux-mount and
libmount1.

The above described situation may occur if a patch is backported
that adds a new library function which is also used at the same
time from binaries in the same patch. All without increasing
the actual package version. This may be a rare case but I am sure
it is not without an example in Yocto. I am not sure if a recipe
review enforces changing PR in this case, though, but it should.


Perhaps if you explain more about the issues you're having which this
fixes I'll better understand the problem/need.


I think I just did.

Automatically relying on the full [PE:]PV[-PR] (note the optional
parts which are also done automatically in the patch) adds even
better consistency in the repo and upgrades can be done in the
correct order.

Upgrades should even work if I just cherry-pick some upgrades
but not all, i.e. "opkg upgrade "
should pull the libglib-2.0_0 version it was built with which is
not happening now because the library dependency is only (>= 2.52.3)
in Rocko but 1:2.48.2 from Morty satisfies it.

OPKG 0.3.x has a dist-upgrade mode and Rocko also introduced dnf,
so I assume at some point a proper distro upgrade will get supported.

Best regards,
Zoltán Böszörményi


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

[OE-core] [PATCH] common-licenses: Add BSD-1-Clause

2018-01-19 Thread André Draszik 
From: André Draszik 

Some projects are starting to use it.
  https://spdx.org/licenses//BSD-1-Clause.html

Signed-off-by: André Draszik 
---
 meta/files/common-licenses/BSD-1-Clause | 9 +
 1 file changed, 9 insertions(+)
 create mode 100644 meta/files/common-licenses/BSD-1-Clause

diff --git a/meta/files/common-licenses/BSD-1-Clause 
b/meta/files/common-licenses/BSD-1-Clause
new file mode 100644
index 00..ded889768f
--- /dev/null
+++ b/meta/files/common-licenses/BSD-1-Clause
@@ -0,0 +1,9 @@
+
+Copyright (c) , 
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this 
list of conditions and the following disclaimer.
+THIS SOFTWARE IS PROVIDED BY Berkeley Software Design, Inc. "AS IS" AND ANY 
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 
DISCLAIMED. IN NO EVENT SHALL Berkeley Software Design, Inc. BE LIABLE FOR ANY 
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON 
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS 
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
-- 
2.15.1

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

[OE-core] [PATCH][pyro] python3-native: Add python3-misc-native to RPROVIDES

2018-01-19 Thread André Draszik 
From: Fabio Berton 

OE-core commit 800753069f667cd1664d70b3779150c467e3b3fe remove
RPROVIDES list to get runtime dependences from manifest file.
python3-misc is added in python3 recipe, we need to add
native runtime to use python3-misc with native recipes.

Signed-off-by: Fabio Berton 
Signed-off-by: Richard Purdie 
(cherry picked from commit 31fd20811f6d11e7ed6ac84caf776ac46cd6fb6f)
Signed-off-by: André Draszik 
---
 meta/recipes-devtools/python/python3-native_3.5.2.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/python/python3-native_3.5.2.bb 
b/meta/recipes-devtools/python/python3-native_3.5.2.bb
index 3f4b567278..782e2cda9f 100644
--- a/meta/recipes-devtools/python/python3-native_3.5.2.bb
+++ b/meta/recipes-devtools/python/python3-native_3.5.2.bb
@@ -79,3 +79,5 @@ do_install() {
# Tests are large and we don't need them in the native sysroot
rm ${D}${libdir}/python${PYTHON_MAJMIN}/test -rf
 }
+
+RPROVIDES += "python3-misc-native"
-- 
2.15.1

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

Re: [OE-core] [PATCH] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Burton, Ross 
On 19 January 2018 at 11:06, Oleg Kokorin  wrote:

> diff --git 
> a/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
> b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-
> hashtable_iterator.patch
> new file mode 100644
> index 000..082f3b1
> --- /dev/null
> +++ b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-
> hashtable_iterator.patch
> @@ -0,0 +1,31 @@
> +Index: setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/
> x86_64-linux/mtd-utils-native/1.5.1+gitAUTOINC+9f107132a6-
> r0/git/mkfs.ubifs/hashtable/hashtable_itr.h
>

This patch (the patch you add) needs a explanatory comment,
upstream-status, and signed-off-by:

https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

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

[OE-core] ✗ patchtest: failure for mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Patchwork 
== Series Details ==

Series: mtd-utils: remove double hashtable iterator definition
Revision: 1
URL   : https://patchwork.openembedded.org/series/10612/
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 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 6b87ad5b08)

* 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-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch)

* Issue Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence_format] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
  Standard format  Upstream-Status: 
  Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], 
Submitted [where]



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] mtd-utils: remove double hashtable iterator definition

2018-01-19 Thread Oleg Kokorin 
hashtable_iterator_key and hashtable_iterator_value redefinition inside
mkfs.ubifs/hashtable/hashtable_itr.h cause linker redefinition error

Signed-off-by: Oleg Kokorin 
---
 .../mtd-utils-fix-hashtable_iterator.patch | 31 ++
 meta/recipes-devtools/mtd/mtd-utils_git.bb |  1 +
 2 files changed, 32 insertions(+)
 create mode 100644 
meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch

diff --git 
a/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch 
b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
new file mode 100644
index 000..082f3b1
--- /dev/null
+++ b/meta/recipes-devtools/mtd/mtd-utils/mtd-utils-fix-hashtable_iterator.patch
@@ -0,0 +1,31 @@
+Index: 
setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/x86_64-linux/mtd-utils-native/1.5.1+gitAUTOINC+9f107132a6-r0/git/mkfs.ubifs/hashtable/hashtable_itr.h
+===
+--- a/mkfs.ubifs/hashtable/hashtable_itr.h
 b/mkfs.ubifs/hashtable/hashtable_itr.h
+@@ -27,22 +27,22 @@ hashtable_iterator(struct hashtable *h);
+ 
/*/
+ /* hashtable_iterator_key
+  * - return the value of the (key,value) pair at the current position */
+-
++/*
+ extern inline void *
+ hashtable_iterator_key(struct hashtable_itr *i)
+ {
+ return i->e->k;
+ }
+-
++*/
+ 
/*/
+ /* value - return the value of the (key,value) pair at the current position */
+-
++/*
+ extern inline void *
+ hashtable_iterator_value(struct hashtable_itr *i)
+ {
+ return i->e->v;
+ }
+-
++*/
+ 
/*/
+ /* advance - advance the iterator to the next element
+  *   returns zero if advanced to end of table */
diff --git a/meta/recipes-devtools/mtd/mtd-utils_git.bb 
b/meta/recipes-devtools/mtd/mtd-utils_git.bb
index 52297c6..f903a65 100644
--- a/meta/recipes-devtools/mtd/mtd-utils_git.bb
+++ b/meta/recipes-devtools/mtd/mtd-utils_git.bb
@@ -11,6 +11,7 @@ SRCREV = "9f107132a6a073cce37434ca9cda6917dd8d866b"
 SRC_URI = "git://git.infradead.org/mtd-utils.git \
file://add-exclusion-to-mkfs-jffs2-git-2.patch \
file://fix-armv7-neon-alignment.patch \
+   file://mtd-utils-fix-hashtable_iterator.patch \
 "
 
 PV = "1.5.1+git${SRCPV}"
-- 
2.7.4

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

Re: [OE-core] [PATCH] image_types: add support for modern f2fs flash filesystem

2018-01-19 Thread Richard Purdie 
On Thu, 2018-01-18 at 09:16 -0800, Saul Wold wrote:
> The f2fs filesystem is a newer flash filesystem that is available in
> meta-filesystems. This needs a minimum sized blank space to operate
> in correctly.
> 
> The f2fs has overprovision functionality and when building smaller
> filesystems, you actually need more space, therefore under 500M (or
> so)
> double the amount of space needed in order to handle the
> overprovision
> functions in f2fs.
> 
> Signed-off-by: Saul Wold 
> ---
>  meta/classes/image_types.bbclass | 20 
>  1 file changed, 20 insertions(+)

We'll need to exclude this fs type from the test:

https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/762/steps/Running%20oe-selftest/logs/stdio

Cheers,

Richard


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

Re: [OE-core] [PATCH] bash: 4.4 -> 4.4.12

2018-01-19 Thread Alexander Kanavin 

On 01/19/2018 09:54 AM, Martin Hundebøll wrote:

1.Upgrade bash from 4.4 to 4.4.12.
2.Delete bash44-001, bash44-002, bash44-003, bash44-004, bash44-005, 
bash44-006, bash44-007,bash44-008, bash44-009, bash44-0010, 
bash44-0011, bash44-0012, since it is integrated upstream.


Signed-off-by: Huang Qiyu 
---
  meta/recipes-extended/bash/bash_4.4.12.bb | 24 +
  meta/recipes-extended/bash/bash_4.4.bb    | 60 
---

  2 files changed, 24 insertions(+), 60 deletions(-)


You need to delete the patch files too.


The patches are fetched from GNU_MIRROR, no?


Ah, yes, that's right.

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