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

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

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

-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

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

-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

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

-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

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

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

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

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

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

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

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

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

Re: [yocto] Download git source not the latest

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

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

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

Re: [yocto] 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: > > > > > > > > >

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

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