[yocto] [meta-anaconda][PATCH 2/2] anaconda_support_image: Add package-management to IMAGE_FEATURES

2019-05-09 Thread Ovidiu Panait 
Currently, if a target image does not contain the rpm database,
any rpm queries that anaconda executes will fail.

To fix this, add the rpm database to all images.

Signed-off-by: Ovidiu Panait 
---
 classes/anaconda_support_image.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/classes/anaconda_support_image.bbclass 
b/classes/anaconda_support_image.bbclass
index 71a5d96..ce48616 100644
--- a/classes/anaconda_support_image.bbclass
+++ b/classes/anaconda_support_image.bbclass
@@ -1,5 +1,5 @@
 FEATURE_PACKAGES_anaconda-support = "packagegroup-anaconda-support"
-IMAGE_FEATURES_append = " anaconda-support"
+IMAGE_FEATURES_append = " anaconda-support package-management"
 
 # Generate filesystem images for image copy install
 IMAGE_FSTYPES += "ext4"
-- 
2.20.1

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

[yocto] [meta-anaconda][PATCH 1/2] python3-anaconda: Fix xserver detection

2019-05-09 Thread Ovidiu Panait 
When installing an image that has graphical interface,
/etc/systemd/system/default.target will point to multi-user.target
instead of graphical.target.

To fix this, use the right rpm query to detect the presence of xserver.

Signed-off-by: Ovidiu Panait 
---
 ...aconda-payload-Fix-xserver-detection.patch | 35 +++
 .../anaconda/python3-anaconda_28.22.11.bb |  1 +
 2 files changed, 36 insertions(+)
 create mode 100644 
recipes-installer/anaconda/files/0001-pyanaconda-payload-Fix-xserver-detection.patch

diff --git 
a/recipes-installer/anaconda/files/0001-pyanaconda-payload-Fix-xserver-detection.patch
 
b/recipes-installer/anaconda/files/0001-pyanaconda-payload-Fix-xserver-detection.patch
new file mode 100644
index 000..ae56019
--- /dev/null
+++ 
b/recipes-installer/anaconda/files/0001-pyanaconda-payload-Fix-xserver-detection.patch
@@ -0,0 +1,35 @@
+From f35925543f8b19c7b39cef4679cc0bc74bfa5253 Mon Sep 17 00:00:00 2001
+From: Ovidiu Panait 
+Date: Thu, 9 May 2019 09:04:44 +
+Subject: [PATCH] pyanaconda: payload: Fix xserver detection
+
+When installing an image that has graphical interface,
+/etc/systemd/system/default.target will point to multi-user.target
+instead of graphical.target.
+
+To fix this, use the right rpm query to detect the presence of xserver.
+
+Upstream-Status: Inappropriate [OE specific]
+
+Signed-off-by: Ovidiu Panait 
+---
+ pyanaconda/payload/__init__.py | 3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/pyanaconda/payload/__init__.py b/pyanaconda/payload/__init__.py
+index f67a4cd94..7929407e7 100644
+--- a/pyanaconda/payload/__init__.py
 b/pyanaconda/payload/__init__.py
+@@ -897,8 +897,7 @@ class Payload(object):
+ ts = rpm.TransactionSet(util.getSysroot())
+ 
+ # XXX one day this might need to account for anaconda's display 
mode
+-if ts.dbMatch("provides", 'service(graphical-login)').count() and 
\
+-   ts.dbMatch('provides', 'xorg-x11-server-Xorg').count() and \
++if ts.dbMatch('provides', 'xserver-xorg').count() and \
+not flags.usevnc:
+ # We only manipulate the ksdata.  The symlink is made later
+ # during the config write out.
+-- 
+2.18.1
+
diff --git a/recipes-installer/anaconda/python3-anaconda_28.22.11.bb 
b/recipes-installer/anaconda/python3-anaconda_28.22.11.bb
index 66bbc1c..5deeae4 100755
--- a/recipes-installer/anaconda/python3-anaconda_28.22.11.bb
+++ b/recipes-installer/anaconda/python3-anaconda_28.22.11.bb
@@ -119,6 +119,7 @@ SRC_URI = 
"git://github.com/rhinstaller/anaconda;protocol=https;branch=f28-relea

file://0001-Make-pyanaconda.dbus.typing-work-with-Python-3.7-159.patch \
file://0068-disable-chronyd.patch \
file://0069-disable-location-detection-based-on-IP-address.patch \
+   file://0001-pyanaconda-payload-Fix-xserver-detection.patch \
   "
 
 SRCREV = "0b0d2f86b4323e6ee7a186bc8181ffe7553c9235"
-- 
2.20.1

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

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

2019-05-09 Thread akuster 


On 5/9/19 12:55 AM, Bas Mevissen wrote:
> On 2019-05-07 20:18, Behan Webster wrote:
>
> (...)
>
>> > Yes, both for LF and YP it are off-the-shelf trainings that do not
>> require much preparation.
>
>> Speaking as a course maintainer for LF, keeping the YP course updated
>> is actually a tremendous amount of work (I'm the co-maintainer for
>> the LF YP course).
>> However, the beginner slides tend not to need more than a few hours
>> of updates every 6 months (which again is something I do).
>> Either may appear off-the-shelf, but they aren't from my perspective. ;)
>
> An additional training date would probably not require much extra I
> assume. As the training is given already a few times a year.
> But it is good to hear the training is kept up to date.
Its not the material, need or willingness of the community to help that
is at issue. Its cost.
The more members we have the more we can do. 

Regards,
Armin
>
>> Thanks,
>
>> Behan
>
> -- Bas.


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

Re: [yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

2019-05-09 Thread Bruce Ashfield 
On Thu, May 9, 2019 at 8:10 AM Kevin Hao  wrote:

> Boot test for all these boards.
>
>
I do have more -stable updates coming, and you are seeing some queued 5.0.x
changes that I haven't sent yet (since I'm hung up on resolving a 4.19
conflict for one of the SoC branches), but yes, the changes here are good
and I'll be bumping the qemu boards in the next day or so.

Bruce



> Signed-off-by: Kevin Hao 
> ---
>  .../recipes-kernel/linux/linux-yocto_4.19.bbappend   | 20
> ++--
>  .../recipes-kernel/linux/linux-yocto_5.0.bbappend| 20
> ++--
>  2 files changed, 20 insertions(+), 20 deletions(-)
>
> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
> index 6025230c7306..ec269d905c4b 100644
> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
>  KMACHINE_genericx86-64 ?= "common-pc-64"
>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>
> -SRCREV_machine_genericx86?= "11e0e616ed095bb8012e1b4a231254c9656a0193"
> -SRCREV_machine_genericx86-64 ?= "11e0e616ed095bb8012e1b4a231254c9656a0193"
> -SRCREV_machine_edgerouter ?= "eebb51300a07804a020ec468b5f8c5bf720198d9"
> -SRCREV_machine_beaglebone-yocto ?=
> "eebb51300a07804a020ec468b5f8c5bf720198d9"
> -SRCREV_machine_mpc8315e-rdb ?= "8b60f968823256f5d2889c4520d70299ca21411b"
> +SRCREV_machine_genericx86?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
> +SRCREV_machine_genericx86-64 ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
> +SRCREV_machine_edgerouter ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
> +SRCREV_machine_beaglebone-yocto ?=
> "5664dc14399edcaad210bbeb6343d84561fb3ea8"
> +SRCREV_machine_mpc8315e-rdb ?= "d419f4ca6ba4b097b8ad710a93b89510f5b2998c"
>
>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
> @@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
>  COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>
> -LINUX_VERSION_genericx86 = "4.19.19"
> -LINUX_VERSION_genericx86-64 = "4.19.19"
> -LINUX_VERSION_edgerouter = "4.19.14"
> -LINUX_VERSION_beaglebone-yocto = "4.19.14"
> -LINUX_VERSION_mpc8315e-rdb = "4.19.14"
> +LINUX_VERSION_genericx86 = "4.19.34"
> +LINUX_VERSION_genericx86-64 = "4.19.34"
> +LINUX_VERSION_edgerouter = "4.19.34"
> +LINUX_VERSION_beaglebone-yocto = "4.19.34"
> +LINUX_VERSION_mpc8315e-rdb = "4.19.34"
> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
> index 5cf6e1f0649e..d7cf1216f45d 100644
> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
>  KMACHINE_genericx86-64 ?= "common-pc-64"
>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>
> -SRCREV_machine_genericx86?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
> -SRCREV_machine_genericx86-64 ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
> -SRCREV_machine_edgerouter ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
> -SRCREV_machine_beaglebone-yocto ?=
> "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
> -SRCREV_machine_mpc8315e-rdb ?= "8b62af7f252af10588276802c4c6d7c502e875be"
> +SRCREV_machine_genericx86?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
> +SRCREV_machine_genericx86-64 ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
> +SRCREV_machine_edgerouter ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
> +SRCREV_machine_beaglebone-yocto ?=
> "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
> +SRCREV_machine_mpc8315e-rdb ?= "670ce7e9db627d0c2067cfdb571ddc1f117818d8"
>
>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
> @@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
>  COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>
> -LINUX_VERSION_genericx86 = "5.0.3"
> -LINUX_VERSION_genericx86-64 = "5.0.3"
> -LINUX_VERSION_edgerouter = "5.0.3"
> -LINUX_VERSION_beaglebone-yocto = "5.0.3"
> -LINUX_VERSION_mpc8315e-rdb = "5.0.3"
> +LINUX_VERSION_genericx86 = "5.0.13"
> +LINUX_VERSION_genericx86-64 = "5.0.13"
> +LINUX_VERSION_edgerouter = "5.0.13"
> +LINUX_VERSION_beaglebone-yocto = "5.0.13"
> +LINUX_VERSION_mpc8315e-rdb = "5.0.13"
> --
> 2.14.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

2019-05-09 Thread Bruce Ashfield 
On Thu, May 9, 2019 at 12:30 PM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:

> From yesterday... Latest stable release of:
> https://github.com/jumpnow/meta-bbb
>
> My GitHub for BBB (BeagleBone Black):
> https://github.com/ZoranStojsavljevic/bbb-yocto
>
> Both worked out for my bash script (adopted for my needs -> sticks and
> ropes) and KAS tool!
>
> https://github.com/ZoranStojsavljevic/bbb-yocto/tree/master/bbb-releases/bbb-warrior
>
> Kernel 5.0.13 (please, look into/upon the traces):
>
> https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/target-bbb-platform-traces.txt
>
>
While interesting .. it really isn't relevant in this context. But thanks
for sharing anyway!

Cheers,

Bruce



> Thank you,
> Zoran
> ___
>
> On Thu, May 9, 2019 at 2:53 PM Bruce Ashfield 
> wrote:
> >
> >
> >
> > On Thu, May 9, 2019 at 8:10 AM Kevin Hao 
> wrote:
> >>
> >> Boot test for all these boards.
> >>
> >
> > I do have more -stable updates coming, and you are seeing some queued
> 5.0.x changes that I haven't sent yet (since I'm hung up on resolving a
> 4.19 conflict for one of the SoC branches), but yes, the changes here are
> good and I'll be bumping the qemu boards in the next day or so.
> >
> > Bruce
> >
> >
> >>
> >> Signed-off-by: Kevin Hao 
> >> ---
> >>  .../recipes-kernel/linux/linux-yocto_4.19.bbappend   | 20
> ++--
> >>  .../recipes-kernel/linux/linux-yocto_5.0.bbappend| 20
> ++--
> >>  2 files changed, 20 insertions(+), 20 deletions(-)
> >>
> >> diff --git
> a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
> >> index 6025230c7306..ec269d905c4b 100644
> >> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
> >> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
> >> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
> >>  KMACHINE_genericx86-64 ?= "common-pc-64"
> >>  KMACHINE_beaglebone-yocto ?= "beaglebone"
> >>
> >> -SRCREV_machine_genericx86?=
> "11e0e616ed095bb8012e1b4a231254c9656a0193"
> >> -SRCREV_machine_genericx86-64 ?=
> "11e0e616ed095bb8012e1b4a231254c9656a0193"
> >> -SRCREV_machine_edgerouter ?= "eebb51300a07804a020ec468b5f8c5bf720198d9"
> >> -SRCREV_machine_beaglebone-yocto ?=
> "eebb51300a07804a020ec468b5f8c5bf720198d9"
> >> -SRCREV_machine_mpc8315e-rdb ?=
> "8b60f968823256f5d2889c4520d70299ca21411b"
> >> +SRCREV_machine_genericx86?=
> "5664dc14399edcaad210bbeb6343d84561fb3ea8"
> >> +SRCREV_machine_genericx86-64 ?=
> "5664dc14399edcaad210bbeb6343d84561fb3ea8"
> >> +SRCREV_machine_edgerouter ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
> >> +SRCREV_machine_beaglebone-yocto ?=
> "5664dc14399edcaad210bbeb6343d84561fb3ea8"
> >> +SRCREV_machine_mpc8315e-rdb ?=
> "d419f4ca6ba4b097b8ad710a93b89510f5b2998c"
> >>
> >>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
> >>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
> >> @@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
> >>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
> >>  COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
> >>
> >> -LINUX_VERSION_genericx86 = "4.19.19"
> >> -LINUX_VERSION_genericx86-64 = "4.19.19"
> >> -LINUX_VERSION_edgerouter = "4.19.14"
> >> -LINUX_VERSION_beaglebone-yocto = "4.19.14"
> >> -LINUX_VERSION_mpc8315e-rdb = "4.19.14"
> >> +LINUX_VERSION_genericx86 = "4.19.34"
> >> +LINUX_VERSION_genericx86-64 = "4.19.34"
> >> +LINUX_VERSION_edgerouter = "4.19.34"
> >> +LINUX_VERSION_beaglebone-yocto = "4.19.34"
> >> +LINUX_VERSION_mpc8315e-rdb = "4.19.34"
> >> diff --git
> a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
> >> index 5cf6e1f0649e..d7cf1216f45d 100644
> >> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
> >> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
> >> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
> >>  KMACHINE_genericx86-64 ?= "common-pc-64"
> >>  KMACHINE_beaglebone-yocto ?= "beaglebone"
> >>
> >> -SRCREV_machine_genericx86?=
> "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
> >> -SRCREV_machine_genericx86-64 ?=
> "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
> >> -SRCREV_machine_edgerouter ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
> >> -SRCREV_machine_beaglebone-yocto ?=
> "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
> >> -SRCREV_machine_mpc8315e-rdb ?=
> "8b62af7f252af10588276802c4c6d7c502e875be"
> >> +SRCREV_machine_genericx86?=
> "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
> >> +SRCREV_machine_genericx86-64 ?=
> "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
> >> +SRCREV_machine_edgerouter ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
> >> +SRCREV_machine_beaglebone-yocto ?=
> "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
> >> +SRCREV_machine_mpc8315e-rdb ?=
> "670ce7e9db627d0c2067cfdb571ddc1f117818d8"
> >>
> >>  COMPATIBLE_MACHINE_genericx86 =

Re: [yocto] python-numpy RDEPENDS not honored?

2019-05-09 Thread Aaron Cohen 
I think the problem is in the python-numpy_1.14.5.bb recipe.

It does: RDEPENDS_${PN}_class-target_append = ...

where it seems to need to be: RDEPENDS_${PN}_append_class-target = ...

Note the position of the word append.

If someone wanted to point me in the right direction, I could try to make a
qa task that would discover this sort of error if it seems feasible?

--Aaron


On Thu, May 9, 2019 at 4:15 PM Aaron Cohen  wrote:

> python-numpy is being installed on my image as a dependency of one of my
> packages.
>
> However, none of python-numpy's RDEPENDS are currently being included on
> the image.
>
> When I run bitbake -e python-numpy > numpy.txt, I see that for some
> reason, the RDEPENDS is being overridden to a nearly empty value:
>
> # $RDEPENDS_python-numpy [5 operations]
>> #   append
>> /home/joel-cohen/code/juevos/poky/meta/classes/distutils-base.bbclass:2
>> # "${@['', '${PYTHON_PN}-core']['${CLASSOVERRIDE}' ==
>> 'class-target']}"
>> #   set
>> /home/joel-cohen/code/juevos/poky/meta/recipes-devtools/python-numpy/python-numpy.inc:112
>> # "${PYTHON_PN}-unittest   ${PYTHON_PN}-difflib
>>  ${PYTHON_PN}-pprint   ${PYTHON_PN}-pickle
>>  ${PYTHON_PN}-shell   ${PYTHON_PN}-nose
>>${PYTHON_PN}-doctest   ${PYTHON_PN}-datetime
>>${PYTHON_PN}-distutils   ${PYTHON_PN}-misc
>>  ${PYTHON_PN}-mmap
>>  ${PYTHON_PN}-netclient   ${PYTHON_PN}-numbers
>>  ${PYTHON_PN}-pydoc   ${PYTHON_PN}-pkgutil
>>  ${PYTHON_PN}-email   ${PYTHON_PN}-compression
>>  ${PYTHON_PN}-ctypes   ${PYTHON_PN}-threading "
>> #   rename from RDEPENDS_${PN} data.py:117 [expandKeys]
>> # "${PYTHON_PN}-unittest   ${PYTHON_PN}-difflib
>>  ${PYTHON_PN}-pprint   ${PYTHON_PN}-pickle
>>  ${PYTHON_PN}-shell   ${PYTHON_PN}-nose
>>${PYTHON_PN}-doctest   ${PYTHON_PN}-datetime
>>${PYTHON_PN}-distutils   ${PYTHON_PN}-misc
>>  ${PYTHON_PN}-mmap
>>  ${PYTHON_PN}-netclient   ${PYTHON_PN}-numbers
>>  ${PYTHON_PN}-pydoc   ${PYTHON_PN}-pkgutil
>>  ${PYTHON_PN}-email   ${PYTHON_PN}-compression
>>  ${PYTHON_PN}-ctypes   ${PYTHON_PN}-threading "
>> #   override[class-native]:set
>> /home/joel-cohen/code/juevos/poky/meta/recipes-devtools/python-numpy/python-numpy.inc:114
>> # ""
>> #   override[class-native]:rename from RDEPENDS_${PN}_class-native
>> data_smart.py:644 [renameVar]
>> # ""
>> # pre-expansion value:
>> #   " ${PYTHON_PN}-subprocess "
>> RDEPENDS_python-numpy=" python-subprocess "
>
>
>
> Anyone have any ideas for why this recipe doesn't seem to be behaving
> correctly?
>
> I'm using poky 2.6 at the moment.
>
> Thanks for any help,
> Aaron
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How do IMAGE_FEATURES+="tools-sdk" and TOOLCHAIN_TARGET_TASK interact?

2019-05-09 Thread Aaron Cohen 
Looking through the recipes and classes, it seems that adding "tools-sdk"
to the IMAGE_FEATURES of an image just adds a relatively arbitrary list of
"sdk-ish" packages to the image from packagegroup-core-sdk

I had assumed that tools-sdk would duplicate the logic of "populate_sdk"
somehow, so that what you end up on the target is equivalent to what is in
a generated SDK.

In particular, if I add something to TOOLCHAIN_TARGET_TASK, it doesn't seem
to also be added to anything that tools-sdk cares about.

Am I missing something?

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

Re: [yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

2019-05-09 Thread Zoran Stojsavljevic 
There is always around, lurking, the replacement crew... Please, do
not forget about that!

And the replacement crew is always ahead... ;-)

Zoran
___

On Thu, May 9, 2019 at 9:32 PM Bruce Ashfield  wrote:
>
>
>
> On Thu, May 9, 2019 at 12:30 PM Zoran Stojsavljevic 
>  wrote:
>>
>> From yesterday... Latest stable release of:
>> https://github.com/jumpnow/meta-bbb
>>
>> My GitHub for BBB (BeagleBone Black):
>> https://github.com/ZoranStojsavljevic/bbb-yocto
>>
>> Both worked out for my bash script (adopted for my needs -> sticks and
>> ropes) and KAS tool!
>> https://github.com/ZoranStojsavljevic/bbb-yocto/tree/master/bbb-releases/bbb-warrior
>>
>> Kernel 5.0.13 (please, look into/upon the traces):
>> https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/target-bbb-platform-traces.txt
>>
>
> While interesting .. it really isn't relevant in this context. But thanks for 
> sharing anyway!
>
> Cheers,
>
> Bruce
>
>
>>
>> Thank you,
>> Zoran
>> ___
>>
>> On Thu, May 9, 2019 at 2:53 PM Bruce Ashfield  
>> wrote:
>> >
>> >
>> >
>> > On Thu, May 9, 2019 at 8:10 AM Kevin Hao  wrote:
>> >>
>> >> Boot test for all these boards.
>> >>
>> >
>> > I do have more -stable updates coming, and you are seeing some queued 
>> > 5.0.x changes that I haven't sent yet (since I'm hung up on resolving a 
>> > 4.19 conflict for one of the SoC branches), but yes, the changes here are 
>> > good and I'll be bumping the qemu boards in the next day or so.
>> >
>> > Bruce
>> >
>> >
>> >>
>> >> Signed-off-by: Kevin Hao 
>> >> ---
>> >>  .../recipes-kernel/linux/linux-yocto_4.19.bbappend   | 20 
>> >> ++--
>> >>  .../recipes-kernel/linux/linux-yocto_5.0.bbappend| 20 
>> >> ++--
>> >>  2 files changed, 20 insertions(+), 20 deletions(-)
>> >>
>> >> diff --git 
>> >> a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend 
>> >> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
>> >> index 6025230c7306..ec269d905c4b 100644
>> >> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
>> >> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
>> >> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
>> >>  KMACHINE_genericx86-64 ?= "common-pc-64"
>> >>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>> >>
>> >> -SRCREV_machine_genericx86?= 
>> >> "11e0e616ed095bb8012e1b4a231254c9656a0193"
>> >> -SRCREV_machine_genericx86-64 ?= 
>> >> "11e0e616ed095bb8012e1b4a231254c9656a0193"
>> >> -SRCREV_machine_edgerouter ?= "eebb51300a07804a020ec468b5f8c5bf720198d9"
>> >> -SRCREV_machine_beaglebone-yocto ?= 
>> >> "eebb51300a07804a020ec468b5f8c5bf720198d9"
>> >> -SRCREV_machine_mpc8315e-rdb ?= "8b60f968823256f5d2889c4520d70299ca21411b"
>> >> +SRCREV_machine_genericx86?= 
>> >> "5664dc14399edcaad210bbeb6343d84561fb3ea8"
>> >> +SRCREV_machine_genericx86-64 ?= 
>> >> "5664dc14399edcaad210bbeb6343d84561fb3ea8"
>> >> +SRCREV_machine_edgerouter ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
>> >> +SRCREV_machine_beaglebone-yocto ?= 
>> >> "5664dc14399edcaad210bbeb6343d84561fb3ea8"
>> >> +SRCREV_machine_mpc8315e-rdb ?= "d419f4ca6ba4b097b8ad710a93b89510f5b2998c"
>> >>
>> >>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>> >>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
>> >> @@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
>> >>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
>> >>  COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>> >>
>> >> -LINUX_VERSION_genericx86 = "4.19.19"
>> >> -LINUX_VERSION_genericx86-64 = "4.19.19"
>> >> -LINUX_VERSION_edgerouter = "4.19.14"
>> >> -LINUX_VERSION_beaglebone-yocto = "4.19.14"
>> >> -LINUX_VERSION_mpc8315e-rdb = "4.19.14"
>> >> +LINUX_VERSION_genericx86 = "4.19.34"
>> >> +LINUX_VERSION_genericx86-64 = "4.19.34"
>> >> +LINUX_VERSION_edgerouter = "4.19.34"
>> >> +LINUX_VERSION_beaglebone-yocto = "4.19.34"
>> >> +LINUX_VERSION_mpc8315e-rdb = "4.19.34"
>> >> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend 
>> >> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
>> >> index 5cf6e1f0649e..d7cf1216f45d 100644
>> >> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
>> >> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
>> >> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
>> >>  KMACHINE_genericx86-64 ?= "common-pc-64"
>> >>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>> >>
>> >> -SRCREV_machine_genericx86?= 
>> >> "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
>> >> -SRCREV_machine_genericx86-64 ?= 
>> >> "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
>> >> -SRCREV_machine_edgerouter ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
>> >> -SRCREV_machine_beaglebone-yocto ?= 
>> >> "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
>> >> -SRCREV_machine_mpc8315e-rdb ?= "8b62af7f252af10588276802c4c6d7c502e875be"
>> >> +SRCREV_machine_genericx86?= 
>> >> "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
>> >>

[yocto] python-numpy RDEPENDS not honored?

2019-05-09 Thread Aaron Cohen 
python-numpy is being installed on my image as a dependency of one of my
packages.

However, none of python-numpy's RDEPENDS are currently being included on
the image.

When I run bitbake -e python-numpy > numpy.txt, I see that for some reason,
the RDEPENDS is being overridden to a nearly empty value:

# $RDEPENDS_python-numpy [5 operations]
> #   append
> /home/joel-cohen/code/juevos/poky/meta/classes/distutils-base.bbclass:2
> # "${@['', '${PYTHON_PN}-core']['${CLASSOVERRIDE}' == 'class-target']}"
> #   set
> /home/joel-cohen/code/juevos/poky/meta/recipes-devtools/python-numpy/python-numpy.inc:112
> # "${PYTHON_PN}-unittest   ${PYTHON_PN}-difflib
>${PYTHON_PN}-pprint   ${PYTHON_PN}-pickle
>${PYTHON_PN}-shell   ${PYTHON_PN}-nose
>  ${PYTHON_PN}-doctest   ${PYTHON_PN}-datetime
>  ${PYTHON_PN}-distutils   ${PYTHON_PN}-misc
>${PYTHON_PN}-mmap   ${PYTHON_PN}-netclient
>  ${PYTHON_PN}-numbers   ${PYTHON_PN}-pydoc
>  ${PYTHON_PN}-pkgutil   ${PYTHON_PN}-email
>  ${PYTHON_PN}-compression
>  ${PYTHON_PN}-ctypes   ${PYTHON_PN}-threading "
> #   rename from RDEPENDS_${PN} data.py:117 [expandKeys]
> # "${PYTHON_PN}-unittest   ${PYTHON_PN}-difflib
>${PYTHON_PN}-pprint   ${PYTHON_PN}-pickle
>${PYTHON_PN}-shell   ${PYTHON_PN}-nose
>  ${PYTHON_PN}-doctest   ${PYTHON_PN}-datetime
>  ${PYTHON_PN}-distutils   ${PYTHON_PN}-misc
>${PYTHON_PN}-mmap   ${PYTHON_PN}-netclient
>  ${PYTHON_PN}-numbers   ${PYTHON_PN}-pydoc
>  ${PYTHON_PN}-pkgutil   ${PYTHON_PN}-email
>  ${PYTHON_PN}-compression
>  ${PYTHON_PN}-ctypes   ${PYTHON_PN}-threading "
> #   override[class-native]:set
> /home/joel-cohen/code/juevos/poky/meta/recipes-devtools/python-numpy/python-numpy.inc:114
> # ""
> #   override[class-native]:rename from RDEPENDS_${PN}_class-native
> data_smart.py:644 [renameVar]
> # ""
> # pre-expansion value:
> #   " ${PYTHON_PN}-subprocess "
> RDEPENDS_python-numpy=" python-subprocess "



Anyone have any ideas for why this recipe doesn't seem to be behaving
correctly?

I'm using poky 2.6 at the moment.

Thanks for any help,
Aaron
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

2019-05-09 Thread Rudolf J Streif 

Chiming in here

On 5/7/19 11:18 AM, Behan Webster wrote:
On May 7, 2019, at 2:47 AM, Bas Mevissen > wrote:


On 2019-05-07 07:20, Behan Webster wrote:

> On May 6, 2019, at 8:36 AM, Bas Mevissen > wrote:

> On 5/6/19 12:45 PM, Josef Holzmayr wrote:
> I'd actually word it a little bit differently:
> If there is only *ONE* attendee who did not properly do the 
homework, it

> will have a massive impact an the rest of the group. And that somebody
> will show up unpreparedly is absolutely certain in my opinion.
> With sufficient trainers, one can continue for most and provide 
some assistance to the one falling behind.


Usually more than one. And this is generally very disruptive to the 
class as a whole.


There are always people who are prepared to the T and others who just 
casually stroll into the class. We all know that as we all went through 
various stages of schooling. :) No matter what you do, there always will 
be a glitch. I tried it all from course preparation instructions, shell 
scripts setting up systems, USB sticks and network drives with downloads 
and shared state cache, virtual machine images, build systems set up in 
the cloud, you name it. If it is not somebody who is unprepared it is a 
technical issue: lack of disk space, network connectivity, corporate 
computers that do not allow USB sticks,... Instructors just have to deal 
with it.
>> As someone who actually got started through the YPDD beginner 
track (and
>> also often recommends it to new beginners), my opinion is clearly 
that

>> we either should have it, be it only for a handful of attendees, or
>> offer a *real* replacement, with face to face training. My 
experience is

>> that this personal thing in the very beginning is an absolutely
>> essential part of many YP/OE careers.
>
> I agree. That is how I started, next to a compressed Linux 
Foundation Yocto training that was offered just before the event then.



Yes. By me and my colleagues who train for the Linux Foundation.


> So it might be wise to ask LF or get something organised. It would 
mostly require a room and a sponsor for some small devkit.


We've run the beginner track for the last few years. The discussion 
is precisely that the YP event is proposing to not run the beginner 
track this year at all.


But why? There appears to be a constant demand.


An excellent question. I agree with you. I don’t have an answer 
however. Not my decision.


I certainly would advocate to have the beginner track. It's a good way 
of getting people interested, and eventually excited, for the Yocto 
Project. Conferences and dev days are an opportunity to do advertising 
and to grow the community. We cannot do that just by catering to people 
who are already using YP. We need new folks as we are already running 
into issues where things have to be dropped because there is nobody who 
is maintaining it.




We're happy to do it again if given the space.


Yes, both for LF and YP it are off-the-shelf trainings that do not 
require much preperation.


Speaking as a course maintainer for LF, keeping the YP course updated 
is actually a tremendous amount of work (I’m the co-maintainer for the 
LF YP course).


However, the beginner slides tend not to need more than a few hours of 
updates every 6 months (which again is something I do).


Either may appear off-the-shelf, but they aren’t from my perspective. ;)


I can wholeheartedly second that. I developed the original YP class of 
the LF and taught it many times and have since developed my own class 
material teaching classes. While the basic concept of course remains the 
same it is the little details that change. With every new version of the 
YP a course maintainer has to go through every single exercise and 
example in the course material and try it out again to see if it still 
works. And quite frankly, sometimes it is rather silly things that have 
changed and break something.


In particular for a beginner class lasting one day only, every single 
disruption sets the class back and there is no opportunity to recover 
from it. The day is already packed just to cover the core concepts.


Cheers,
Rudi




Thanks,

Behan


--
-
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3396 x700

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

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

2019-05-09 Thread Behan Webster 
> On May 9, 2019, at 8:38 AM, Rudolf J Streif  wrote:
> 
> Chiming in here
> 
> On 5/7/19 11:18 AM, Behan Webster wrote:
>>> On May 7, 2019, at 2:47 AM, Bas Mevissen >> > wrote:
>>> 
>>> On 2019-05-07 07:20, Behan Webster wrote:
>>> 
 > On May 6, 2019, at 8:36 AM, Bas Mevissen >>> > > wrote:
 > On 5/6/19 12:45 PM, Josef Holzmayr wrote:
 > I'd actually word it a little bit differently:
 > If there is only *ONE* attendee who did not properly do the homework, it
 > will have a massive impact an the rest of the group. And that somebody
 > will show up unpreparedly is absolutely certain in my opinion.
 > With sufficient trainers, one can continue for most and provide some 
 > assistance to the one falling behind.
>>> 
 Usually more than one. And this is generally very disruptive to the class 
 as a whole.
>>> 
> There are always people who are prepared to the T and others who just 
> casually stroll into the class. We all know that as we all went through 
> various stages of schooling. :) No matter what you do, there always will be a 
> glitch. I tried it all from course preparation instructions, shell scripts 
> setting up systems, USB sticks and network drives with downloads and shared 
> state cache, virtual machine images, build systems set up in the cloud, you 
> name it. If it is not somebody who is unprepared it is a technical issue: 
> lack of disk space, network connectivity, corporate computers that do not 
> allow USB sticks,... Instructors just have to deal with it.

And if you have a multiple day class, you can absorb such disruption.

But for single day events you basically have to make sure there is little to no 
wiggle room for failure. And for individual talks, there is almost no room for 
disruption at all during labs.

Assuming pre-class work essentially means there will be massive disruption on 
the day because many/most/all the attendees won’t have done it.

This is why we’ve largely done lecture only beginner talks at YPDD to make sure 
we cover as much material as we can and limit the possibility of in class 
issues.

 >> As someone who actually got started through the YPDD beginner track (and
 >> also often recommends it to new beginners), my opinion is clearly that
 >> we either should have it, be it only for a handful of attendees, or
 >> offer a *real* replacement, with face to face training. My experience is
 >> that this personal thing in the very beginning is an absolutely
 >> essential part of many YP/OE careers.
 >
 > I agree. That is how I started, next to a compressed Linux Foundation 
 > Yocto training that was offered just before the event then.
>>> 
 Yes. By me and my colleagues who train for the Linux Foundation.
>>> 
 > So it might be wise to ask LF or get something organised. It would 
 > mostly require a room and a sponsor for some small devkit.
>>> 
 We've run the beginner track for the last few years. The discussion is 
 precisely that the YP event is proposing to not run the beginner track 
 this year at all.
>>> 
>>> But why? There appears to be a constant demand.
>> 
>> An excellent question. I agree with you. I don’t have an answer however. Not 
>> my decision.
>> 
> I certainly would advocate to have the beginner track. It's a good way of 
> getting people interested, and eventually excited, for the Yocto Project. 
> Conferences and dev days are an opportunity to do advertising and to grow the 
> community. We cannot do that just by catering to people who are already using 
> YP. We need new folks as we are already running into issues where things have 
> to be dropped because there is nobody who is maintaining it.
> 
All agreed.

 We're happy to do it again if given the space.
>>> 
>>> Yes, both for LF and YP it are off-the-shelf trainings that do not require 
>>> much preperation.
>> 
>> Speaking as a course maintainer for LF, keeping the YP course updated is 
>> actually a tremendous amount of work (I’m the co-maintainer for the LF YP 
>> course).
>> 
>> However, the beginner slides tend not to need more than a few hours of 
>> updates every 6 months (which again is something I do).
>> 
>> Either may appear off-the-shelf, but they aren’t from my perspective. ;)
> I can wholeheartedly second that. I developed the original YP class of the LF 
> and taught it many times and have since developed my own class material 
> teaching classes.
> 
And you did a great job!
> While the basic concept of course remains the same it is the little details 
> that change. With every new version of the YP a course maintainer has to go 
> through every single exercise and example in the course material and try it 
> out again to see if it still works. And quite frankly, sometimes it is rather 
> silly things that have changed and break something.
> 
So very true.
> In particular for a beginner class lasting one day only, every

Re: [yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

2019-05-09 Thread Zoran Stojsavljevic 
>From yesterday... Latest stable release of:
https://github.com/jumpnow/meta-bbb

My GitHub for BBB (BeagleBone Black):
https://github.com/ZoranStojsavljevic/bbb-yocto

Both worked out for my bash script (adopted for my needs -> sticks and
ropes) and KAS tool!
https://github.com/ZoranStojsavljevic/bbb-yocto/tree/master/bbb-releases/bbb-warrior

Kernel 5.0.13 (please, look into/upon the traces):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/target-bbb-platform-traces.txt

Thank you,
Zoran
___

On Thu, May 9, 2019 at 2:53 PM Bruce Ashfield  wrote:
>
>
>
> On Thu, May 9, 2019 at 8:10 AM Kevin Hao  wrote:
>>
>> Boot test for all these boards.
>>
>
> I do have more -stable updates coming, and you are seeing some queued 5.0.x 
> changes that I haven't sent yet (since I'm hung up on resolving a 4.19 
> conflict for one of the SoC branches), but yes, the changes here are good and 
> I'll be bumping the qemu boards in the next day or so.
>
> Bruce
>
>
>>
>> Signed-off-by: Kevin Hao 
>> ---
>>  .../recipes-kernel/linux/linux-yocto_4.19.bbappend   | 20 
>> ++--
>>  .../recipes-kernel/linux/linux-yocto_5.0.bbappend| 20 
>> ++--
>>  2 files changed, 20 insertions(+), 20 deletions(-)
>>
>> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend 
>> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
>> index 6025230c7306..ec269d905c4b 100644
>> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
>> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
>> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
>>  KMACHINE_genericx86-64 ?= "common-pc-64"
>>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>>
>> -SRCREV_machine_genericx86?= "11e0e616ed095bb8012e1b4a231254c9656a0193"
>> -SRCREV_machine_genericx86-64 ?= "11e0e616ed095bb8012e1b4a231254c9656a0193"
>> -SRCREV_machine_edgerouter ?= "eebb51300a07804a020ec468b5f8c5bf720198d9"
>> -SRCREV_machine_beaglebone-yocto ?= 
>> "eebb51300a07804a020ec468b5f8c5bf720198d9"
>> -SRCREV_machine_mpc8315e-rdb ?= "8b60f968823256f5d2889c4520d70299ca21411b"
>> +SRCREV_machine_genericx86?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
>> +SRCREV_machine_genericx86-64 ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
>> +SRCREV_machine_edgerouter ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
>> +SRCREV_machine_beaglebone-yocto ?= 
>> "5664dc14399edcaad210bbeb6343d84561fb3ea8"
>> +SRCREV_machine_mpc8315e-rdb ?= "d419f4ca6ba4b097b8ad710a93b89510f5b2998c"
>>
>>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
>> @@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
>>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
>>  COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>>
>> -LINUX_VERSION_genericx86 = "4.19.19"
>> -LINUX_VERSION_genericx86-64 = "4.19.19"
>> -LINUX_VERSION_edgerouter = "4.19.14"
>> -LINUX_VERSION_beaglebone-yocto = "4.19.14"
>> -LINUX_VERSION_mpc8315e-rdb = "4.19.14"
>> +LINUX_VERSION_genericx86 = "4.19.34"
>> +LINUX_VERSION_genericx86-64 = "4.19.34"
>> +LINUX_VERSION_edgerouter = "4.19.34"
>> +LINUX_VERSION_beaglebone-yocto = "4.19.34"
>> +LINUX_VERSION_mpc8315e-rdb = "4.19.34"
>> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend 
>> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
>> index 5cf6e1f0649e..d7cf1216f45d 100644
>> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
>> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
>> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
>>  KMACHINE_genericx86-64 ?= "common-pc-64"
>>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>>
>> -SRCREV_machine_genericx86?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
>> -SRCREV_machine_genericx86-64 ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
>> -SRCREV_machine_edgerouter ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
>> -SRCREV_machine_beaglebone-yocto ?= 
>> "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
>> -SRCREV_machine_mpc8315e-rdb ?= "8b62af7f252af10588276802c4c6d7c502e875be"
>> +SRCREV_machine_genericx86?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
>> +SRCREV_machine_genericx86-64 ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
>> +SRCREV_machine_edgerouter ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
>> +SRCREV_machine_beaglebone-yocto ?= 
>> "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
>> +SRCREV_machine_mpc8315e-rdb ?= "670ce7e9db627d0c2067cfdb571ddc1f117818d8"
>>
>>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
>> @@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
>>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
>>  COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>>
>> -LINUX_VERSION_genericx86 = "5.0.3"
>> -LINUX_VERSION_genericx86-64 = "5.0.3"
>> -LINUX_VERSION_edgerouter = "5.0.3"
>> -LINUX_VERSION_beaglebone-yocto = "5.0.3"

Re: [yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

2019-05-09 Thread Alexander Kanavin 
SSTATE_DIR and DL_DIR can (and should) be shared between all builds.

Each MACHINE/DISTRO combination works best with it's own build_dir.

Alex

On Thu, 9 May 2019 at 11:47, Fabian Knapp  wrote:

>
> Hello,
>
> we have multiple MACHINEs and DISTROs and Im wondering for which
> combinations I have to setup a dedicated build dir, SSTATE_DIR and DL_DIR.
>
> Information in the form of:
>
> Each (change of) MACHINE needs its dedicated SSTATE_DIR and build dir but
> can share DL_DIR.
>
> would be very helpful for me.
>
> Thank you in advance.
>
> Fabian
>
> [image: Visit us at EES Europe] 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

2019-05-09 Thread Fabian Knapp 

Hello,

we have multiple MACHINEs and DISTROs and Im wondering for which combinations I 
have to setup a dedicated build dir, SSTATE_DIR and DL_DIR.

Information in the form of:

Each (change of) MACHINE needs its dedicated SSTATE_DIR and build dir but can 
share DL_DIR.

would be very helpful for me.

Thank you in advance.

Fabian

[Visit us at EES Europe]
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

2019-05-09 Thread Burton, Ross 
On Thu, 9 May 2019 at 10:47, Fabian Knapp  wrote:

> we have multiple MACHINEs and DISTROs and Im wondering for which
> combinations I have to setup a dedicated build dir, SSTATE_DIR and DL_DIR.
>
> Information in the form of:
>
> Each (change of) MACHINE needs its dedicated SSTATE_DIR and build dir but
> can share DL_DIR.
>

You can always share DL_DIR and SSTATE_DIR.

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

[yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

2019-05-09 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao 
---
 .../recipes-kernel/linux/linux-yocto_4.19.bbappend   | 20 ++--
 .../recipes-kernel/linux/linux-yocto_5.0.bbappend| 20 ++--
 2 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
index 6025230c7306..ec269d905c4b 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
@@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86?= "11e0e616ed095bb8012e1b4a231254c9656a0193"
-SRCREV_machine_genericx86-64 ?= "11e0e616ed095bb8012e1b4a231254c9656a0193"
-SRCREV_machine_edgerouter ?= "eebb51300a07804a020ec468b5f8c5bf720198d9"
-SRCREV_machine_beaglebone-yocto ?= "eebb51300a07804a020ec468b5f8c5bf720198d9"
-SRCREV_machine_mpc8315e-rdb ?= "8b60f968823256f5d2889c4520d70299ca21411b"
+SRCREV_machine_genericx86?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
+SRCREV_machine_genericx86-64 ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
+SRCREV_machine_edgerouter ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
+SRCREV_machine_beaglebone-yocto ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
+SRCREV_machine_mpc8315e-rdb ?= "d419f4ca6ba4b097b8ad710a93b89510f5b2998c"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
-LINUX_VERSION_genericx86 = "4.19.19"
-LINUX_VERSION_genericx86-64 = "4.19.19"
-LINUX_VERSION_edgerouter = "4.19.14"
-LINUX_VERSION_beaglebone-yocto = "4.19.14"
-LINUX_VERSION_mpc8315e-rdb = "4.19.14"
+LINUX_VERSION_genericx86 = "4.19.34"
+LINUX_VERSION_genericx86-64 = "4.19.34"
+LINUX_VERSION_edgerouter = "4.19.34"
+LINUX_VERSION_beaglebone-yocto = "4.19.34"
+LINUX_VERSION_mpc8315e-rdb = "4.19.34"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
index 5cf6e1f0649e..d7cf1216f45d 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
@@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
-SRCREV_machine_genericx86-64 ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
-SRCREV_machine_edgerouter ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
-SRCREV_machine_beaglebone-yocto ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
-SRCREV_machine_mpc8315e-rdb ?= "8b62af7f252af10588276802c4c6d7c502e875be"
+SRCREV_machine_genericx86?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
+SRCREV_machine_genericx86-64 ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
+SRCREV_machine_edgerouter ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
+SRCREV_machine_beaglebone-yocto ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
+SRCREV_machine_mpc8315e-rdb ?= "670ce7e9db627d0c2067cfdb571ddc1f117818d8"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
-LINUX_VERSION_genericx86 = "5.0.3"
-LINUX_VERSION_genericx86-64 = "5.0.3"
-LINUX_VERSION_edgerouter = "5.0.3"
-LINUX_VERSION_beaglebone-yocto = "5.0.3"
-LINUX_VERSION_mpc8315e-rdb = "5.0.3"
+LINUX_VERSION_genericx86 = "5.0.13"
+LINUX_VERSION_genericx86-64 = "5.0.13"
+LINUX_VERSION_edgerouter = "5.0.13"
+LINUX_VERSION_beaglebone-yocto = "5.0.13"
+LINUX_VERSION_mpc8315e-rdb = "5.0.13"
-- 
2.14.4

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

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

2019-05-09 Thread Bas Mevissen 

On 2019-05-07 20:18, Behan Webster wrote:

(...)


> Yes, both for LF and YP it are off-the-shelf trainings that do not require 
much preparation.


Speaking as a course maintainer for LF, keeping the YP course updated 
is actually a tremendous amount of work (I'm the co-maintainer for the 
LF YP course).
However, the beginner slides tend not to need more than a few hours of 
updates every 6 months (which again is something I do).
Either may appear off-the-shelf, but they aren't from my perspective. 
;)


An additional training date would probably not require much extra I 
assume. As the training is given already a few times a year.

But it is good to hear the training is kept up to date.


Thanks,



Behan


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

[yocto] [meta-security][PATCH 2/2] smack: kernel fragment update

2019-05-09 Thread Armin Kuster 
Signed-off-by: Armin Kuster 
---
 recipes-kernel/linux/linux-yocto-5.0/smack.cfg | 11 +--
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/recipes-kernel/linux/linux-yocto-5.0/smack.cfg 
b/recipes-kernel/linux/linux-yocto-5.0/smack.cfg
index 62f465a..0d5fc64 100644
--- a/recipes-kernel/linux/linux-yocto-5.0/smack.cfg
+++ b/recipes-kernel/linux/linux-yocto-5.0/smack.cfg
@@ -1,8 +1,7 @@
-CONFIG_IP_NF_SECURITY=m
-CONFIG_IP6_NF_SECURITY=m
-CONFIG_EXT2_FS_SECURITY=y
-CONFIG_EXT3_FS_SECURITY=y
-CONFIG_EXT4_FS_SECURITY=y
-CONFIG_SECURITY=y
+CONFIG_NETLABEL=y
+CONFIG_SECURITY_NETWORK=y
+# CONFIG_SECURITY_NETWORK_XFRM is not set
 CONFIG_SECURITY_SMACK=y
+CONFIG_SECURITY_SMACK_BRINGUP=y
+CONFIG_SECURITY_SMACK_APPEND_SIGNALS=y
 CONFIG_TMPFS_XATTR=y
-- 
2.17.1

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

[yocto] Join Us – May 13th, 2019 – Live Coding with Yocto Project

2019-05-09 Thread Volosincu, Andreea S 
Hello Everybody,

The next live coding session is approaching quickly.

When: May 13th, 2019, 5:00 PM CET
Where: Yocto Project Twitch channel - https://www.twitch.tv/yocto_project
What: Yocto Project developer, Josef Holzmayr, will show you how to create a 
simple layer, derive a customized image and go through a devtool example

Live Coding with Yocto Project is a live streaming series for Linux developers 
who want to learn how to build Linux distros quickly and easily using the Yocto 
Project tools. The show is hosted by Yocto Project developers. We talk, explore 
devtools and write code along the way.

Add it to your calendar – 
https://calendar.google.com/calendar/ical/d7umm3pdhorsnnjbe1cvbgfhlk%40group.calendar.google.com/public/basic.ics

See you soon!
Yocto Project Advocacy Team
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH 1/2] oe-selftest: add running cve checker

2019-05-09 Thread Armin Kuster 
Signed-off-by: Armin Kuster 
---
 lib/oeqa/selftest/cases/cvechecker.py | 27 +++
 1 file changed, 27 insertions(+)
 create mode 100644 lib/oeqa/selftest/cases/cvechecker.py

diff --git a/lib/oeqa/selftest/cases/cvechecker.py 
b/lib/oeqa/selftest/cases/cvechecker.py
new file mode 100644
index 000..23ca7d2
--- /dev/null
+++ b/lib/oeqa/selftest/cases/cvechecker.py
@@ -0,0 +1,27 @@
+import os
+import re
+
+from oeqa.selftest.case import OESelftestTestCase
+from oeqa.utils.commands import bitbake, get_bb_var
+
+class CveCheckerTests(OESelftestTestCase):
+def test_cve_checker(self):
+image = "core-image-sato"
+
+deploy_dir = get_bb_var("DEPLOY_DIR_IMAGE")
+image_link_name = get_bb_var('IMAGE_LINK_NAME', image)
+
+manifest_link = os.path.join(deploy_dir, "%s.cve" % image_link_name)
+
+self.logger.info('CVE_CHECK_MANIFEST = "%s"' % manifest_link)
+if (not 'cve-check' in get_bb_var('INHERIT')):
+add_cve_check_config = 'INHERIT += "cve-check"'
+self.append_config(add_cve_check_config)
+self.append_config('CVE_CHECK_MANIFEST = "%s"' % manifest_link)
+result = bitbake("-k -c cve_check %s" % image, ignore_status=True)
+if (not 'cve-check' in get_bb_var('INHERIT')):
+self.remove_config(add_cve_check_config)
+
+isfile = os.path.isfile(manifest_link)
+self.assertEqual(True, isfile, 'Failed to create cve data file : %s' % 
manifest_link)
+
-- 
2.17.1

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

Re: [yocto] Eclipse (plugin, settings)

2019-05-09 Thread Arno Steffens 
I always afraid of that, so don't wanna shot you.
But instead of a plugin, is there anywhere like a howto/manual what to do best?
Nowadays IDEs are so full off settings/adjustments that is hard to get an 
overview.
I found an "C/C++ GCC Cross Compiler Support" that might be useful.
Arno

> Gesendet: Mittwoch, 08. Mai 2019 um 15:36 Uhr
> Von: "Zoran Stojsavljevic" 
> An: "Arno Steffens" 
> Cc: "Yocto Project" 
> Betreff: Re: [yocto] Eclipse (plugin, settings)
>
> https://marc.info/?l=openembedded-core=155482339222316=2
>
> (do not shoot the messenger, thank you)
>
> Zoran
> ___
>
> On Wed, May 8, 2019 at 1:11 PM Arno Steffens  wrote:
> >
> > I want to use Eclipse as IDE for coding/debugging.
> > What do I have to set to get the proper compiler prefixes and pathes, libs 
> > and includes ?
> > Or any way to combine the environment setup with start of eclipse?
> >
> > I have seen there was a Eclipse plugin, but not for newer versions as 
> > 2019.03.
> >
> > Here (https://www.yoctoproject.org/software-item/eclipse-ide-plug-in/) is 
> > referenced to the eSDK manual, but no word about eclipse in it. Til now I 
> > just use SDK.
> >
> > Thanks
> > Arno
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2019-05-09 Thread Lei Maohui 
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