Re: [yocto] [layerindex-web][PATCH] These changes will add the metadata for product revision and epoch if present in the bitbake recipe.

[Paul Eggleton]

Hi Pranay,

On Tuesday, 1 October 2019 3:52:59 PM NZDT Pranay Mankad wrote:
> Signed-off-by: Pranay Mankad 
> ---
>  .../migrations/0042_recipe_property_addition.py  | 20 
> 
>  layerindex/models.py |  2 ++
>  layerindex/update_layer.py   |  2 ++
>  3 files changed, 24 insertions(+)
>  create mode 100644 layerindex/migrations/0042_recipe_property_addition.py

So the substance of this change is fine, however the commit message needs a bit 
of reworking. 
The shortlog (first line, which is used by git-send-email automatically as the 
subject) should be shorter and then you can have a fuller explanation of the 
change after a blank line. It should look something like this:

-- snip --
Track PE and PR for recipes

This will add the metadata for epoch and revision if present in the
bitbake recipe. These will be automatically available through the REST
API but won't (yet) be visible in the UI.
-- snip --

(Removing snip lines obviously)

Thanks,
Paul

-- 
Paul Eggleton
Intel Open Source Technology Centre


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

[yocto] [meta-security][PATCH 2/2] suricata-update: add package to pull rules

[Armin Kuster]

Signed-off-by: Armin Kuster 
---
 .../suricata/python3-suricata-update_1.0.5.bb | 15 +++
 1 file changed, 15 insertions(+)
 create mode 100644 recipes-ids/suricata/python3-suricata-update_1.0.5.bb

diff --git a/recipes-ids/suricata/python3-suricata-update_1.0.5.bb 
b/recipes-ids/suricata/python3-suricata-update_1.0.5.bb
new file mode 100644
index 000..63f75e0
--- /dev/null
+++ b/recipes-ids/suricata/python3-suricata-update_1.0.5.bb
@@ -0,0 +1,15 @@
+SUMMARY = "The tool for updating your Suricata rules. "
+HOMEPAGE = "http://suricata-ids.org/";
+SECTION = "security Monitor/Admin"
+LICENSE = "GPLv2"
+
+LIC_FILES_CHKSUM = 
"file://LICENSE;beginline=1;endline=2;md5=c70d8d3310941dcdfcd1e02800a1f548"
+
+SRCREV = "dcd0f630e13463750efb1593ad3ccae1ae6c27d4"
+SRC_URI = "git://github.com/OISF/suricata-update;branch='master-1.0.x'"
+
+S = "${WORKDIR}/git"
+
+inherit python3native setuptools3
+
+RDEPENDS_${PN} = "python3-pyyaml"
-- 
2.17.1

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

Re: [yocto] Xilinx/meta-jupyter layer

[Paul Eggleton]

FYI I've just changed the layer index entry to point to the new repo. New 
content should be indexed in a few hours.

Thanks for working this out!

Dmitry: sorry, for clarity did you mean a separate mailing list or one of the 
YP / OE ones ?

Cheers,
Paul

On Saturday, 28 September 2019 9:52:26 AM NZDT Dmitry Kargin wrote:
> Nice job!
> 
> You have my permission, if it is needed to change
> https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/
> links to your repository.
> 
> >Would you recommend maintaining this layer separately or...
> I'd like to keep it separately from meta- and openembedded.
> 
> >Would you suggest having a separate mailing list
> meta-jupyter mailing list is fine.
> 
> On Fri, 27 Sep 2019 at 23:12, Chandana Kalluri  wrote:
> 
> > Hello all,
> >
> > https://github.com/Xilinx/meta-jupyter is a meta-jupyter layer containing
> > recipes for jupyter notebook. The initial recipes are based of Dmitry
> > Kargin's meta-jupyter layer
> > https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/.
> > This layer has not been updated for a while.
> >
> > The Xilinx/meta-jupyter layer also adds recipes for python3 based
> > notebooks apart from existing python2 based notebooks.
> > This layer has been tested using Yocto thud layer and  by running jupyter
> > notebooks on Ultra96 community boards.
> > We would like to maintain Xilinx/meta-jupyter  layer actively and welcome
> > contributions to this layer either through pull requests or via patches
> > sent to meta-xilinx mailing list until a mailing list for meta-jupyter is
> > in place. In the next cycle we will deprecate python2 recipes.
> >
> > A question to community,
> >  - Would you recommend maintaining this layer separately in the current
> > github.com/Xilinx location or be included under meta- openembedded layers.
> > - Would you suggest having a separate mailing list ?
> >
> > Thanks,
> > Chandana
> >
> >
> 


-- 

Paul Eggleton
Intel Open Source Technology Centre


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

[yocto] No rule to make target 'zImage'

[JH]

Hi,

I am building Yocto, it stopped at building kernel "No rule to make
target 'zImage'", what I could be missing?

Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 6 HOSTCC=gcc
-isystem/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/recipe-sysroot-native/usr/include
-O2 -pipe 
-L/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/recipe-sysroot-native/usr/lib
-L/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/recipe-sysroot-native/lib
-Wl,-rpath-link,/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/recipe-sysroot-native/usr/lib
-Wl,-rpath-link,/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/recipe-sysroot-native/lib
-Wl,-rpath,/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/recipe-sysroot-native/usr/lib
-Wl,-rpath,/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/recipe-sysroot-native/lib
-Wl,-O1 HOSTCPP=gcc  -E zImage CC=arm-oe-linux-gnueabi-gcc
-mno-thumb-interwork -marm -fuse-ld=bfd
-fdebug-prefix-map=/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0=/usr/src/debug/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0
-fdebug-prefix-map=/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/recipe-sysroot=
-fdebug-prefix-map=/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/recipe-sysroot-native=
 
-fdebug-prefix-map=/build/Kernel5.3/build/tmp-glibc/work-shared/yocto/kernel-source=/usr/src/kernel
  LD=arm-oe-linux-gnueabi-ld.bfd
| make: *** No rule to make target 'zImage'.  Stop.
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/build/Kernel5.3/build/tmp-glibc/work/yocto-oe-linux-gnueabi/linux-yocto/5.3.0+gitAUTOINC+4d856f72c1-r0/temp/log.do_compile.7842)

Thank you.

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

Re: [yocto] Cannot use "LICENSE_CREATE_PACKAGE = 1" when building the image with mdns

[Khem Raj]

On 9/30/19 8:17 AM, Stefano Cappa wrote:
> I saw your last patch to upgrade mdns, so I'm sending this email also to
> you to try to get help.
> 
> mdns is working correctly, however, when I try to build my image with
> "LICENSE_CREATE_PACKAGE = "1"" in my local.conf as described
> here 
> https://www.yoctoproject.org/docs/2.8/dev-manual/dev-manual.html#providing-license-text
>  I
> get this error message:
> 
> ERROR: mydevice-image-1.0-r0 do_rootfs: Postinstall scriptlets of
> ['mdns'] have failed. If the intention is to defer them to first boot,
> then please place them into pkg_postinst_ontarget_${PN} ().
> Deferring to first boot via 'exit 1' is no longer supported.
> Details of the failure are in
> /home/user/git/poky/build/tmp/work/mydevice1-image-poky-linux-gnueabi/mydevice-image/1.0-r0/temp/log.do_rootfs.
> ERROR: mydevice-image-1.0-r0 do_rootfs: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/user/git/poky/build/tmp/work/mydevice1-poky-linux-gnueabi/mydevice-image/1.0-r0/temp/log.do_rootfs.14586
> ERROR: Task (MY CUSTOM LAYER
> PATH/recipes-core/images/mydevice-image.bb:do_rootfs) failed with exit
> code '1'
> NOTE: Tasks Summary: Attempted 4871 tasks of which 4654 didn't need to
> be rerun and 1 failed.
> 
> Do you have a solution? Why is it happening? 
> 

see mdns recipe especially

pkg_postinst_${PN} (), that function is not able to execute offline
during build. It could be that nsswitch.conf does not exist in your
image rootfs

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

[yocto] (no subject)

[Stephen K Jolley]

All,



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



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



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



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



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



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

-- 

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

*7867 SW Bayberry Dr., Beaverton, OR 97007*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Cannot use "LICENSE_CREATE_PACKAGE = 1" when building the image with mdns

[Stefano Cappa]

I saw your last patch to upgrade mdns, so I'm sending this email also to
you to try to get help.

mdns is working correctly, however, when I try to build my image with
"LICENSE_CREATE_PACKAGE = "1"" in my local.conf as described here
https://www.yoctoproject.org/docs/2.8/dev-manual/dev-manual.html#providing-license-text
I
get this error message:

ERROR: mydevice-image-1.0-r0 do_rootfs: Postinstall scriptlets of ['mdns']
have failed. If the intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget_${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
Details of the failure are in
/home/user/git/poky/build/tmp/work/mydevice1-image-poky-linux-gnueabi/mydevice-image/1.0-r0/temp/log.do_rootfs.
ERROR: mydevice-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/user/git/poky/build/tmp/work/mydevice1-poky-linux-gnueabi/mydevice-image/1.0-r0/temp/log.do_rootfs.14586
ERROR: Task (MY CUSTOM LAYER
PATH/recipes-core/images/mydevice-image.bb:do_rootfs)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 4871 tasks of which 4654 didn't need to be
rerun and 1 failed.

Do you have a solution? Why is it happening?

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

Re: [yocto] Xilinx/meta-jupyter layer

[Mark Hatle]

On 9/27/19 3:12 PM, Chandana Kalluri wrote:
> Hello all,
> 
> https://github.com/Xilinx/meta-jupyter is a meta-jupyter layer containing 
> recipes for jupyter notebook. The initial recipes are based of Dmitry 
> Kargin's meta-jupyter layer 
> https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/. 
> This layer has not been updated for a while. 
> 
> The Xilinx/meta-jupyter layer also adds recipes for python3 based notebooks 
> apart from existing python2 based notebooks.
> This layer has been tested using Yocto thud layer and  by running jupyter 
> notebooks on Ultra96 community boards. 
> We would like to maintain Xilinx/meta-jupyter  layer actively and welcome 
> contributions to this layer either through pull requests or via patches sent 
> to meta-xilinx mailing list until a mailing list for meta-jupyter is in 
> place. In the next cycle we will deprecate python2 recipes. 
> 
> A question to community,
>  - Would you recommend maintaining this layer separately in the current 
> github.com/Xilinx location or be included under meta- openembedded layers.
> - Would you suggest having a separate mailing list ?

I'd suggest that you should consider either keeping it on github, or offering it
to the git.yoctoproject.org.  I can assist with this if you need.

Since this is pretty targeted to a specific use-case, either would make sense 
to me.

--Mark

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

Re: [yocto] qemu-native build fails on sumo due to missing capstone.h

[David Roman]

Have this bug been resolved? I'm facing the same error with 
"warrior:6d2e12e79211b31cdf5ea824fb9a8be54ba9a9eb" and capstone 4.0.1. 
Although in this case I can not see any include path being used in the logs.


On 6/14/18 11:50 PM, Khem Raj wrote:



On Thu, Jun 14, 2018 at 1:08 PM Jon Szymaniak > wrote:


On Thu, Jun 14, 2018 at 14:18 Khem Raj mailto:raj.k...@gmail.com>> wrote:

On Thu, Jun 14, 2018 at 9:56 AM Jon Szymaniak
mailto:jon.szyman...@gmail.com>> wrote:
>
> On Thu, Jun 14, 2018 at 11:43 Khem Raj mailto:raj.k...@gmail.com>> wrote:
> > Do you have capstone development headers/libs installed on
your build host ?
> >
>
> No, and I understand that's an easy thing to address on the
build host.
>
> However, I don't think this should be necessary build host
dependency.
> QEMU includes the capstone codebase as a git submodule, so
everything
> that's needed is there.
>
> Maybe it's just a matter of tweaking the recipe to set
> CMAKE_INSTALL_PREFIX appropriately so that when the build
dives down
> into the capstone directory, this points to the correct prefix?
>
> It looks like the inclusion and use of capstone is new, as
of the QEMU
> version included with sumo. (i.e. This appears not to be the
situation
> with the version used in rocko and pyro).

Least intrusive approach would be to disable it if its not
something you
depend on.


Makes sense, thank you.

Two workarounds that worked for me were either adding qemu-native
to ASSUME_PROVIDED or appending “--disable-capstone” to qemu’s
EXTRA_OECONF.


The fact that not everyone sees this issue makes me think that it 
might be something in your environment that’s triggering this but if 
we disable it then we make the issue irrelevant



I’ll try to follow up with a patch to the recipe in oe-core,
unless you suspect that the source of this is merely something on
my end.




--
Avís -
Aviso - Legal Notice - (LOPD) - http://legal.ifae.es 

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

Re: [yocto] Xilinx/meta-jupyter layer

[Dmitry Kargin]

Nice job!

You have my permission, if it is needed to change
https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/
links to your repository.

>Would you recommend maintaining this layer separately or...
I'd like to keep it separately from meta- and openembedded.

>Would you suggest having a separate mailing list
meta-jupyter mailing list is fine.

On Fri, 27 Sep 2019 at 23:12, Chandana Kalluri  wrote:

> Hello all,
>
> https://github.com/Xilinx/meta-jupyter is a meta-jupyter layer containing
> recipes for jupyter notebook. The initial recipes are based of Dmitry
> Kargin's meta-jupyter layer
> https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/.
> This layer has not been updated for a while.
>
> The Xilinx/meta-jupyter layer also adds recipes for python3 based
> notebooks apart from existing python2 based notebooks.
> This layer has been tested using Yocto thud layer and  by running jupyter
> notebooks on Ultra96 community boards.
> We would like to maintain Xilinx/meta-jupyter  layer actively and welcome
> contributions to this layer either through pull requests or via patches
> sent to meta-xilinx mailing list until a mailing list for meta-jupyter is
> in place. In the next cycle we will deprecate python2 recipes.
>
> A question to community,
>  - Would you recommend maintaining this layer separately in the current
> github.com/Xilinx location or be included under meta- openembedded layers.
> - Would you suggest having a separate mailing list ?
>
> Thanks,
> Chandana
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Xilinx/meta-jupyter layer

[Chandana Kalluri]

Hello all,

https://github.com/Xilinx/meta-jupyter is a meta-jupyter layer containing 
recipes for jupyter notebook. The initial recipes are based of Dmitry Kargin's 
meta-jupyter layer 
https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/. 
This layer has not been updated for a while. 

The Xilinx/meta-jupyter layer also adds recipes for python3 based notebooks 
apart from existing python2 based notebooks.
This layer has been tested using Yocto thud layer and  by running jupyter 
notebooks on Ultra96 community boards. 
We would like to maintain Xilinx/meta-jupyter  layer actively and welcome 
contributions to this layer either through pull requests or via patches sent to 
meta-xilinx mailing list until a mailing list for meta-jupyter is in place. In 
the next cycle we will deprecate python2 recipes. 

A question to community,
 - Would you recommend maintaining this layer separately in the current 
github.com/Xilinx location or be included under meta- openembedded layers.
- Would you suggest having a separate mailing list ?

Thanks,
Chandana

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

[yocto] Where to get kconfig-frontends package?

[Matouš Pokorný]

Hello!

I come from NuttX RTOS project (nuttx.org), and we use Kconfig tool for
configuration. The toolchain build script gets kconfig-frontends source
code from the same server as Yocto (http://ymorin.is-a-geek.org). The
server is down for approx. one week and it caused the fail during the
toolchain building. Have you met this problem as well? We would like to
switch to another more reliable repository, but I read, the server's owner
is one of the Linux core developers. So the server is a kind of primary
source. Do you have a suggestion on how to solve this problem? I would like
to ask you for help because you know the Linux ecosystem and are in the
same situation as we are.

Thank you.

*Matous Pokorny*
Embedded System Developer

*DataVision s.r.o.*
Ukrajinska 2a
101 00 Praha 10
Czech Republic

GSM: (+420) 723 280 471
matous.poko...@datavision.cz
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-cgl][PATCH] heartbeat:Update the patch for new version.

[Lei Maohui]

To fix the patch error as follwing:

WARNING: heartbeat-3.0.6-r0 do_patch: QA Issue: Patch log indicates that
patches do not apply cleanly. [patch-fuzz

Signed-off-by: Lei Maohui 
---
 ...mbership-ccm-Makefile.am-fix-warning.patch | 19 ++-
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git 
a/meta-cgl-common/recipes-cgl/heartbeat/heartbeat/membership-ccm-Makefile.am-fix-warning.patch
 
b/meta-cgl-common/recipes-cgl/heartbeat/heartbeat/membership-ccm-Makefile.am-fix-warning.patch
index 19691db..e27ed79 100644
--- 
a/meta-cgl-common/recipes-cgl/heartbeat/heartbeat/membership-ccm-Makefile.am-fix-warning.patch
+++ 
b/meta-cgl-common/recipes-cgl/heartbeat/heartbeat/membership-ccm-Makefile.am-fix-warning.patch
@@ -1,9 +1,10 @@
-From 30ee44e75da1bc86901b546ea14233d288ce2309 Mon Sep 17 00:00:00 2001
-From: Li xin 
-Date: Tue, 9 Dec 2014 18:15:51 +0900
+From a5e1060c233513cdfc494be410032e6d4ed6f916 Mon Sep 17 00:00:00 2001
+From: Lei Maohui 
+Date: Mon, 30 Sep 2019 12:42:41 +0900
 Subject: [PATCH] membership/ccm/Makefile.am: fix warning
 
-The compile log indicates that host include and/or library paths were used
+The compile log indicates that host include and/or library paths were
+used
 
 Upstream-Status: pending
 
@@ -13,18 +14,18 @@ Signed-off-by: Li Xin 
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/membership/ccm/Makefile.am b/membership/ccm/Makefile.am
-index 105069a..2a89de1 100644
+index eeb8eee..47a6452 100644
 --- a/membership/ccm/Makefile.am
 +++ b/membership/ccm/Makefile.am
 @@ -22,7 +22,7 @@ MAINTAINERCLEANFILES= Makefile.in
- INCLUDES= -I$(top_builddir)/include -I$(top_srcdir)/include \
+ AM_CPPFLAGS   = -I$(top_builddir)/include -I$(top_srcdir)/include \
-I$(top_builddir)/linux-ha -I$(top_srcdir)/linux-ha \
-I$(top_builddir)/libltdl -I$(top_srcdir)/libltdl \
 --I$(includedir)/clplumbing
 +-I$(lt_sysroot)$(includedir)/clplumbing
  
- hadir = $(sysconfdir)/ha.d
- halibdir  = $(libdir)/@HB_PKG@
+ halibexecdir  = $(libexecdir)/@HB_PKG@
+ ccmlibdir = $(halibexecdir)
 -- 
-1.8.4.2
+2.17.1
 
-- 
2.17.2



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