[yocto] [meta-selinux][PATCH] glib-2.0: fix configure error for meson build

2019-06-12 Thread Yi Zhao
In glib 2.60.x, it turns selinux into a meson feature. We should use
'-Dselinux=enabled/disabled' rather than '-Dselinux=true/false' to
enable/disable the feature.

Add meso-enable-selinux.bbclass for this change and inherit it in
glib-2.0 bbappend to fix the configure error.

Signed-off-by: Yi Zhao 
---
 classes/meson-enable-selinux.bbclass  | 4 
 recipes-core/glib-2.0/glib-2.0_%.bbappend | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)
 create mode 100644 classes/meson-enable-selinux.bbclass

diff --git a/classes/meson-enable-selinux.bbclass 
b/classes/meson-enable-selinux.bbclass
new file mode 100644
index 000..91c2a2b
--- /dev/null
+++ b/classes/meson-enable-selinux.bbclass
@@ -0,0 +1,4 @@
+inherit selinux
+
+PACKAGECONFIG_append = " ${@target_selinux(d)}"
+PACKAGECONFIG[selinux] = "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
diff --git a/recipes-core/glib-2.0/glib-2.0_%.bbappend 
b/recipes-core/glib-2.0/glib-2.0_%.bbappend
index e5d2f6f..39a0a3a 100644
--- a/recipes-core/glib-2.0/glib-2.0_%.bbappend
+++ b/recipes-core/glib-2.0/glib-2.0_%.bbappend
@@ -1 +1 @@
-inherit ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'meson-selinux', 
'', d)}
+inherit ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 
'meson-enable-selinux', '', d)}
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc2)

2019-06-12 Thread richard . purdie
On Wed, 2019-06-12 at 00:51 +, Jain, Sangeeta wrote:
> On Tue, 2019-06-11 at 03:32 +, pokybu...@debian9-ty-1.yocto.io
> > wrote:
> > > A build flagged for QA (yocto-2.8_M1.rc2) was completed on the
> > > autobuilder and is available at:
> > > 
> > > 
> > > https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2
> > > 
> > 
> > Some notes for QA:
> Thanks Richard for sharing this.
> > There was a failure in this build in qemux86 oe-selftest. It looks
> > to be a race issue where qemu was shutting down. This needs a bug
> > and looking into but is a minor issue which wouldn't block the
> > milestone release or further QA.
> 
> We are analysing the failures and will file the bugs as suggested.

Just for reference I did file some of the bugs.

> > There are three timeouts in ptest, acl, bluez5 (#13366) and mdadm
> > (#13368).
> > These are also not going to block the milestone release. The
> > bluez5 issue is gcc9 related, mdadm was exposed by wider testing in
> > master. The
> > acl issue needs a bug opening and investigation as that is a
> > regression.
> 
> Looks like some disconnect here. In test result report, no timeout
> issue reported for acl ptest.

https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2/testresults/testresult-report.txt

acl  | 184 | 9| 0 | 302 T

I hadn't spotted that dbus-test also has a timeout :(.

This timeout is also in the testresults file:

ERROR: Exit status is 9\nDURATION: 302\nTIMEOUT: /usr/lib/acl/ptest\n

in:

https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2/testresults/qemux86-64-ptest/testresults.json

> We are referring to test results at yocto-testresults under tag "
> master/54573-g9910a3631ce953b8dd8f3d57d6e122c7fd8cb462/1"

You are right, there is no mention of this in the log at:

http://git.yoctoproject.org/cgit.cgi/yocto-testresults/tree/runtime/poky/qemux86-64/core-image-sato-sdk-ptest/ptest-acl.log?id=56b1caa6044ce30e92a1895eae48d3935562b627
or
http://git.yoctoproject.org/cgit.cgi/yocto-testresults/commit/runtime/poky/qemux86-64/core-image-sato-sdk-ptest/ptest-acl.log?id=ac623e13e3bc3a348b60fe3b884e6ae567b8230a

I suspect this is due to the information being filtered out as part of
the log processing. We probably shouldn't do that.

Looking at the individual logs in 
https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2/testresults/qemux86-64-ptest/testresults.json,
 the timeout information looks to be truncated off there too.

I do however note that:

"ptestresult.sections": {
"acl": {
"duration": "302",
"exitcode": "9",
"timeout": true
},

is in 
http://git.yoctoproject.org/cgit.cgi/yocto-testresults/tree/runtime/poky/qemux86-64/core-image-sato-sdk-ptest/testresults.json?id=56b1caa6044ce30e92a1895eae48d3935562b627
so the timeout is recorded in the results.

Regards,

Richard


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc2)

2019-06-12 Thread Jain, Sangeeta



>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Wednesday, 12 June, 2019 4:05 PM
>To: Jain, Sangeeta ; pokybuild@debian9-ty-
>1.yocto.io; yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; akuster...@gmail.com; sjolley.yp...@gmail.com
>Subject: Re: QA notification for completed autobuilder build (yocto-2.8_M1.rc2)
>
>On Wed, 2019-06-12 at 00:51 +, Jain, Sangeeta wrote:
>> On Tue, 2019-06-11 at 03:32 +, pokybu...@debian9-ty-1.yocto.io
>> > wrote:
>> > > A build flagged for QA (yocto-2.8_M1.rc2) was completed on the
>> > > autobuilder and is available at:
>> > >
>> > >
>> > > https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2
>> > >
>> >
>> > Some notes for QA:
>> Thanks Richard for sharing this.
>> > There was a failure in this build in qemux86 oe-selftest. It looks
>> > to be a race issue where qemu was shutting down. This needs a bug
>> > and looking into but is a minor issue which wouldn't block the
>> > milestone release or further QA.
>>
>> We are analysing the failures and will file the bugs as suggested.
>
>Just for reference I did file some of the bugs.
>
>> > There are three timeouts in ptest, acl, bluez5 (#13366) and mdadm
>> > (#13368).
>> > These are also not going to block the milestone release. The
>> > bluez5 issue is gcc9 related, mdadm was exposed by wider testing in
>> > master. The acl issue needs a bug opening and investigation as that
>> > is a regression.
>>
>> Looks like some disconnect here. In test result report, no timeout
>> issue reported for acl ptest.
>
>https://autobuilder.yocto.io/pub/releases/yocto-
>2.8_M1.rc2/testresults/testresult-report.txt
>
>acl  | 184 | 9| 0 | 302 T
>
>I hadn't spotted that dbus-test also has a timeout :(.
>
>This timeout is also in the testresults file:
>
>ERROR: Exit status is 9\nDURATION: 302\nTIMEOUT: /usr/lib/acl/ptest\n
>
>in:
>
>https://autobuilder.yocto.io/pub/releases/yocto-
>2.8_M1.rc2/testresults/qemux86-64-ptest/testresults.json
>
>> We are referring to test results at yocto-testresults under tag "
>> master/54573-g9910a3631ce953b8dd8f3d57d6e122c7fd8cb462/1"
>
>You are right, there is no mention of this in the log at:
>
>http://git.yoctoproject.org/cgit.cgi/yocto-
>testresults/tree/runtime/poky/qemux86-64/core-image-sato-sdk-ptest/ptest-
>acl.log?id=56b1caa6044ce30e92a1895eae48d3935562b627
>or
>http://git.yoctoproject.org/cgit.cgi/yocto-
>testresults/commit/runtime/poky/qemux86-64/core-image-sato-sdk-ptest/ptest-
>acl.log?id=ac623e13e3bc3a348b60fe3b884e6ae567b8230a
>
>I suspect this is due to the information being filtered out as part of the log
>processing. We probably shouldn't do that.
>
>Looking at the individual logs in 
>https://autobuilder.yocto.io/pub/releases/yocto-
>2.8_M1.rc2/testresults/qemux86-64-ptest/testresults.json, the timeout
>information looks to be truncated off there too.
>
>I do however note that:
>
>"ptestresult.sections": {
>"acl": {
>"duration": "302",
>"exitcode": "9",
>"timeout": true
>},
>
>is in http://git.yoctoproject.org/cgit.cgi/yocto-
>testresults/tree/runtime/poky/qemux86-64/core-image-sato-sdk-
>ptest/testresults.json?id=56b1caa6044ce30e92a1895eae48d3935562b627
>so the timeout is recorded in the results.

Thanks. Able to trace all time-out issues, including dbus-test !
>
>Regards,
>
>Richard
>

Thanks & Regards,
Sangeeta Jain
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Download git source not the latest

2019-06-12 Thread Richard Purdie
On Tue, 2019-06-11 at 20:38 +1000, JH wrote:
> Hi,
> 
> I set up SRCREV = "${AUTOREV}" in the recipe of my application, but
> too often it downloaded the old revision. How can I force the bitbake
> to download the latest git source?

What did you set PV to?

You need to have SRCPV in PV for autorev to work properly.

Regards,

Richard

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-selinux][PATCH] glib-2.0: fix configure error for meson build

2019-06-12 Thread Alexander Kanavin
On Wed, 12 Jun 2019 at 09:54, Yi Zhao  wrote:

> +PACKAGECONFIG[selinux] =
> "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
>

This line should probably go into the oe-core recipe? It is fine to have
options that depend on things absent in oe-core, as long as those options
are disabled by default.

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [current stable poky kernel] linux-stable-5.0.21-r0

2019-06-12 Thread Zoran Stojsavljevic
Hello to all,

I did (an hour ago) quick git pull on the several git repos for my BBB
target platform.

But I still see that the poky kernel is still one of 5.0 series! Why?
There are already well known stable kernels series 5.1 (5.1.9).

Please, check kernel.org: https://www.kernel.org/

What is the problem (if any)? As I found building kernels of 5.1
series with built-in kernel source tree, there is a mismatch with the
/meta/recipes-kernel/lttng/ lttng package?!

Please, advise?

Thank you,
Zoran
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-selinux][PATCH] glib-2.0: fix configure error for meson build

2019-06-12 Thread Yi Zhao


On 6/12/19 6:03 PM, Alexander Kanavin wrote:
On Wed, 12 Jun 2019 at 09:54, Yi Zhao > wrote:


+PACKAGECONFIG[selinux] =
"-Dselinux=enabled,-Dselinux=disabled,libselinux,"


This line should probably go into the oe-core recipe? It is fine to 
have options that depend on things absent in oe-core, as long as those 
options are disabled by default.



Thanks. I will test it and send a patch to oe-core


//Yi



Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-security][PATCH] python3-fail2ban: Fix build error of xrange.

2019-06-12 Thread Lei, Maohui
Hi,

Please merge this patch to warrior branch.

Best regards
Lei

> -Original Message-
> From: Lei, Maohui
> Sent: Friday, April 19, 2019 11:59 AM
> To: yocto@yoctoproject.org
> Cc: Lei, Maohui
> Subject: [yocto] [meta-security][PATCH] python3-fail2ban: Fix build error of
> xrange.
> 
> NameError: name 'xrange' is not defined
> 
> Signed-off-by: Lei Maohui 
> ---
>  .../files/0001-To-fix-build-error-of-xrang.patch   | 28 
> ++
>  .../fail2ban/python3-fail2ban_0.10.4.0.bb  |  4 
>  2 files changed, 32 insertions(+)
>  create mode 100644 
> recipes-security/fail2ban/files/0001-To-fix-build-error-of-
> xrang.patch
> 
> diff --git a/recipes-security/fail2ban/files/0001-To-fix-build-error-of-
> xrang.patch b/recipes-security/fail2ban/files/0001-To-fix-build-error-of-
> xrang.patch
> new file mode 100644
> index 000..7f0812c
> --- /dev/null
> +++ b/recipes-security/fail2ban/files/0001-To-fix-build-error-of-xrang.patch
> @@ -0,0 +1,28 @@
> +From fe3436d65518099d35c643848cba50253abc249c Mon Sep 17 00:00:00 2001
> +From: Lei Maohui 
> +Date: Thu, 9 May 2019 14:44:51 +0900
> +Subject: [PATCH] To fix build error of xrange.
> +
> +NameError: name 'xrange' is not defined
> +
> +Signed-off-by: Lei Maohui 
> +---
> + fail2ban/__init__.py | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/fail2ban/__init__.py b/fail2ban/__init__.py
> +index fa6dcf7..61789a4 100644
> +--- a/fail2ban/__init__.py
>  b/fail2ban/__init__.py
> +@@ -82,7 +82,7 @@ strptime("2012", "%Y")
> +
> + # short names for pure numeric log-level ("Level 25" could be truncated by
> short formats):
> + def _init():
> +-for i in xrange(50):
> ++for i in range(50):
> + if logging.getLevelName(i).startswith('Level'):
> + logging.addLevelName(i, '#%02d-Lev.' % i)
> + _init()
> +--
> +2.7.4
> +
> diff --git a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb b/recipes-
> security/fail2ban/python3-fail2ban_0.10.4.0.bb
> index 5c887e8..23ef027 100644
> --- a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
> +++ b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
> @@ -2,3 +2,7 @@ inherit setuptools3
>  require python-fail2ban.inc
> 
>  RDEPENDS_${PN}-ptest = "python3-core python3-io python3-modules python3-
> fail2ban"
> +
> +SRC_URI += " \
> +file://0001-To-fix-build-error-of-xrang.patch \
> +"
> --
> 2.7.4



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-security][master][PATCH 1/2] python-fail2ban: solved the conflict with python3-fail2ban

2019-06-12 Thread Zang Ruochen
-Use update-alternatives class to resolve conflicts with python3-fail2ban.

Signed-off-by: Zang Ruochen 
---
 recipes-security/fail2ban/python-fail2ban_0.10.4.0.bb | 11 ++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/recipes-security/fail2ban/python-fail2ban_0.10.4.0.bb 
b/recipes-security/fail2ban/python-fail2ban_0.10.4.0.bb
index 17a7dd8..3eea365 100644
--- a/recipes-security/fail2ban/python-fail2ban_0.10.4.0.bb
+++ b/recipes-security/fail2ban/python-fail2ban_0.10.4.0.bb
@@ -1,4 +1,13 @@
-inherit setuptools
+inherit setuptools update-alternatives
 require python-fail2ban.inc
 
 RDEPENDS_${PN}-ptest = "python python-modules python-fail2ban"
+
+ALTERNATIVE_${PN} = "fail2ban-client fail2ban-regex fail2ban-server 
fail2ban-testcases"
+
+ALTERNATIVE_TARGET[fail2ban-client] = "${bindir}/fail2ban-client"
+ALTERNATIVE_TARGET[fail2ban-regex] = "${bindir}/fail2ban-regex"
+ALTERNATIVE_TARGET[fail2ban-server] = "${bindir}/fail2ban-server"
+ALTERNATIVE_TARGET[fail2ban-testcases] = "${bindir}/fail2ban-testcases"
+
+ALTERNATIVE_PRIORITY = "30"
-- 
2.20.1



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-security][master][PATCH 2/2] python3-fail2ban: solved the conflict with python-fail2ban

2019-06-12 Thread Zang Ruochen
-Use update-alternatives class to resolve conflicts with python-fail2ban

Signed-off-by: Zang Ruochen 
---
 recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb | 10 +-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb 
b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
index 23ef027..e01482c 100644
--- a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
+++ b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
@@ -1,4 +1,4 @@
-inherit setuptools3
+inherit setuptools3 update-alternatives
 require python-fail2ban.inc
 
 RDEPENDS_${PN}-ptest = "python3-core python3-io python3-modules 
python3-fail2ban"
@@ -6,3 +6,11 @@ RDEPENDS_${PN}-ptest = "python3-core python3-io 
python3-modules python3-fail2ban
 SRC_URI += " \
 file://0001-To-fix-build-error-of-xrang.patch \
 "
+
+ALTERNATIVE_${PN} = "fail2ban-client fail2ban-regex fail2ban-server 
fail2ban-testcases"
+ALTERNATIVE_TARGET[fail2ban-client] = "${bindir}/fail2ban-client"
+ALTERNATIVE_TARGET[fail2ban-regex] = "${bindir}/fail2ban-regex"
+ALTERNATIVE_TARGET[fail2ban-server] = "${bindir}/fail2ban-server"
+ALTERNATIVE_TARGET[fail2ban-testcases] = "${bindir}/fail2ban-testcases"
+
+ALTERNATIVE_PRIORITY = "60"
-- 
2.20.1



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-security][master][PATCH 0/2] python-fail2ban: solved the conflict with python3-fail2ban

2019-06-12 Thread Zang Ruochen
-Use the update-alternatives class to resolve conflicts.

Zang Ruochen (2):
  [yocto][meta-security][master][PATCH 1/2] python-fail2ban: solved
the conflict with python3-fail2ban
  [yocto][meta-security][master][PATCH 2/2] python3-fail2ban:
solved the conflict with python-fail2ban

 recipes-security/fail2ban/python-fail2ban_0.10.4.0.bb | 11 ++-
 .../fail2ban/python3-fail2ban_0.10.4.0.bb | 10 +-
 2 files changed, 19 insertions(+), 2 deletions(-)

-- 
2.20.1



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc2)

2019-06-12 Thread Jain, Sangeeta
Hello All,

Intel and WR YP QA is now working on QA execution for YP build 2.8 M1 RC2.
We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:

1. OE-Core
2. BSP-hw
3. BSP-Qemu

Runtime auto test for following platforms:

1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. MPC8315e-rdb
7. Beaglebone

ETA for completion is Friday, 15 June.


Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Tuesday, 11 June, 2019 4:51 PM
>To: pokybu...@debian9-ty-1.yocto.io; yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; akuster...@gmail.com; sjolley.yp...@gmail.com;
>Jain, Sangeeta 
>Subject: Re: QA notification for completed autobuilder build (yocto-2.8_M1.rc2)
>
>On Tue, 2019-06-11 at 03:32 +, pokybu...@debian9-ty-1.yocto.io
>wrote:
>> A build flagged for QA (yocto-2.8_M1.rc2) was completed on the
>> autobuilder and is available at:
>>
>>
>> https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2
>>
>
>Some notes for QA:
>
>There was a failure in this build in qemux86 oe-selftest. It looks to be a 
>race issue
>where qemu was shutting down. This needs a bug and looking into but is a minor
>issue which wouldn't block the milestone release or further QA.
>
>There are three timeouts in ptest, acl, bluez5 (#13366) and mdadm (#13368).
>These are also not going to block the milestone release. The
>bluez5 issue is gcc9 related, mdadm was exposed by wider testing in master. The
>acl issue needs a bug opening and investigation as that is a regression.
>
>There is a lot more testing happening under automation than in previous builds,
>particularly on arm hosts/targets.
>
>Cheers,
>
>Richard

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto