date:20200622

Re: [yocto] MACHINE and inc files

2020-06-22 Thread Quentin Schulz

Hi Tomek,

On Sun, Jun 21, 2020 at 03:09:40PM +0200, Tomek The Messenger wrote:
> The problem which I have is that this one below doesn't work (*):
> KERNEL_MODULE_AUTOLOAD_velismate += "A"
> KERNEL_MODULE_AUTOLOAD += "B"
> 
> The two kernel modules are autoloaded during linux startup only if I have
> in bb recipe this one:
> KERNEL_MODULE_AUTOLOAD += "A"
> KERNEL_MODULE_AUTOLOAD += "B"
> or
> KERNEL_MODULE_AUTOLOAD_velismate += "A"
> KERNEL_MODULE_AUTOLOAD_velismate += "B"

Because there is a misunderstanding on how _ works :)

KERNEL_MODULE_AUTOLOAD_velismate += "A"
KERNEL_MODULE_AUTOLOAD += "B"

does not mean that you add A in case of velismate machine is used.

You can have *many* variables that are override-able by machines (or
other OVERRIDES values).

In your example above you will actually have two variables for Yocto
internals:
KERNEL_MODULE_AUTOLOAD_velismate = "A"
KERNEL_MODULE_AUTOLOAD = "B"

You can check that by using `-e` after bitbake.

What you want is to **add** to KERNEL_MODULE_AUTOLOAD **only** for
velismate machine. That can be done with:
KERNEL_MODULE_AUTOLOAD_append_velismate = " A"

Note the leading space, and that it's _append_velismate and not
_velismate_append.

This will just work.

> If I have like here (*), so kind of some mix, then kernel-moduleB isn't
> autoloaded.
> On the other hand the below one works OK:
> RPROVIDES_${PN}_velismate += "kernel-module-A"
> RPROVIDES_${PN} += "kernel-module-B"
> RPPROVIDES install in filesystem your kernel module and based on variable
> AUTOLOAD some magic during building kernel image is done that after linux
> startupu your module is loading.
> So I try to pass the above by adding:
> #include ${MACHINE}.inc and in *.inc file I will use KERNEL_MODULE_AUTOLOAD
> without part "_something" as it is problematic when mixing.
> so my temp.bb recipe will looks like:
>   KERNEL_MODULE_AUTOLOAD += "B"
>   include ${MACHINE}.inc  #here for machine velismate kernel module B will
> be added
> 

As per KERNEL_MODULE_AUTOLOAD documentation[1] you can actually put it
in the machine configuration file, which makes **a lot** more sense :)
Forget about all your "I'm pulling my hair"-tries and go with that,
trust me.

[1] 
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-KERNEL_MODULE_AUTOLOAD

> But the problem is that my MACHINE is:
> 'velismate-x11'
> 'velismate-x21'
> not just 'velismate'
> and how to ignore x11,x12 words and not do anything in temp.bb if in future
> machine velismate-x31 will appear.
> It must be something like
> include ${takeOnlyFirstWordOfMachine(${MACHINE})}.inc
> so I probably need to implement function takeOnlyFirstWordOfMachine but
> how, I don't know.
> In makefile it is easy, You have:
> ifeq ($(findstring velismate, $(MACHINE)), velismate)
> endif
> but in bitbake I don't have idea how to done it in the most simplest way.
> 

You want to use MACHINEOVERRIDES for that. Add your 'velismate'
"family" to it (AT THE CORRECT PLACE, use bitbake -e to check, rightmost
in MACHINEOVERRIDES has top priority). You just have to make sure
velismate is in your new machine configuration file.

IIRC, you would need to do:
MACHINEOVERRIDES =. ":velismate"
before all require/include in your machine configuration file.

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-MACHINEOVERRIDES

Quentin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49711): https://lists.yoctoproject.org/g/yocto/message/49711
Mute This Topic: https://lists.yoctoproject.org/mt/74979199/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2020-06-22 Thread Sangeeta Jain

Hello all,

This is the full report for yocto-3.2_M1.rc1:  
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

=== Summary 
No high milestone defects.  
No new defects are found in this cycle.

valgrind ptest failed (BUG id:13951)

=== Bugs 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13951

Thanks,
Sangeeta

> -Original Message-
> From: Pokybuild User 
> Sent: Thursday, 18 June, 2020 7:50 AM
> To: yocto@lists.yoctoproject.org
> Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
> ; Yeoh, Ee Peng ; Chan,
> Aaron Chun Yew ;
> richard.pur...@linuxfoundation.org; akuster...@gmail.com;
> sjolley.yp...@gmail.com; Jain, Sangeeta 
> Subject: QA notification for completed autobuilder build (yocto-3.2_M1.rc1)
> 
> 
> A build flagged for QA (yocto-3.2_M1.rc1) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-3.2_M1.rc1
> 
> 
> Build hash information:
> 
> bitbake: 7689fa781646039524a655295a884e525ad8732c
> meta-gplv2: a8da8eb127a56561bf633ab53bec57fb5dbba537
> meta-intel: 635e8a6892163cc3334a9b947abaca70697d458f
> meta-mingw: 88f9689f7dd0f634f1ac9a370bdf00585d884206
> oecore: 878a8561e10017bb91ea42bbbe6d4acfc0985482
> poky: 29bfa17d6cab31dbf8f1d12e473ef83dd9e92519
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49712): https://lists.yoctoproject.org/g/yocto/message/49712
Mute This Topic: https://lists.yoctoproject.org/mt/74949262/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] License reporting for golang (and rust)

2020-06-22 Thread Irving ST

Hello,

I am building a device that uses some Go (and Rust) dependencies. This
is on Yocto 2.7 / Warrior.

I noticed that after building an image, the generated license.manifest
and package.manifest (in tmp/deploy/licenses/) does not contain any
mention of go packages or rust crates. The go packages seem to
generate directories in tmp/deploy/licenses/ but they do not seem to
be reported in the final image.

For example, an image that contains docker (from meta-virtualization
layer) has build dependencies on, say, go-cli (also from
meta-virtualization layer). This is specified in the docker recipe
having DEPENDS on go-cli recipe. I saw tmp/deploy/licenses/go-cli
directory exists with licensing information, but
tmp/deploy/licenses//license.manifest does not contain any reference
to go-cli.

My best *guess* at the moment is because go packages are build
dependencies (DEPENDS instead of RDEPENDS), they are not considered
shipped packages by bitbake (because they are not shipped, the final
docker package is) and are not listed in the manifest files. This
makes licensing compliance more difficult since I still need to show
the copyright notices even for permissive licenses like MIT - but I
can't show it if I don't know that it has been shipped with the image
(since it's not in the manifest).

Is there a way to get a manifest of go packages shipped into the image?
This issue seems to happen with rust crates as well, so a solution /
explanation for rust would be greatly appreciated too.

Sorry if this has been resolved somewhere, I'm not exactly super
familiar with the golang build system or its integration with Yocto.

Best regards,
Irving Tjiptowarsono
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49713): https://lists.yoctoproject.org/g/yocto/message/49713
Mute This Topic: https://lists.yoctoproject.org/mt/75034537/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto][meta-virtualization][zeus][PATCH] kubernetes: CVE-2019-11254

2020-06-22 Thread Bruce Ashfield

This patch doesn't apply to zeus.

Can you rebase and resubmit ?

Cheers,

Bruce

In message: [yocto][meta-virtualization][zeus][PATCH] kubernetes: CVE-2019-11254
on 18/06/2020 Zhixiong Chi wrote:

> Backport the CVE patch from the upstream:
> https://github.com/kubernetes/kubernetes.git
> 
> Signed-off-by: Zhixiong Chi 
> ---
>  .../kubernetes/CVE-2019-11254.patch   | 797 ++
>  .../kubernetes/kubernetes_git.bb  |   1 +
>  2 files changed, 798 insertions(+)
>  create mode 100644 
> recipes-containers/kubernetes/kubernetes/CVE-2019-11254.patch
> 
> diff --git a/recipes-containers/kubernetes/kubernetes/CVE-2019-11254.patch 
> b/recipes-containers/kubernetes/kubernetes/CVE-2019-11254.patch
> new file mode 100644
> index 000..2d991a9
> --- /dev/null
> +++ b/recipes-containers/kubernetes/kubernetes/CVE-2019-11254.patch
> @@ -0,0 +1,797 @@
> +From e9ba264d57d379d86dfbf3ae94e82eb0ead9c468 Mon Sep 17 00:00:00 2001
> +From: CJ Cullen 
> +Date: Wed, 22 Jan 2020 11:32:39 -0800
> +Subject: [PATCH] update gopkg.in/yaml.v2 to v2.2.8
> +
> +CVE: CVE-2019-11254
> +Upstream-Status: Backport [https://github.com/kubernetes/kubernetes.git 
> branch: release-1.16]
> +Signed-off-by: Zhixiong Chi 
> +---
> + src/import/go.mod   |   4 +-
> + src/import/go.sum   |   4 +-
> + src/import/staging/src/k8s.io/api/go.sum |   4 +-
> + .../src/k8s.io/apiextensions-apiserver/go.mod   |   2 +-
> + .../src/k8s.io/apiextensions-apiserver/go.sum   |   4 +-
> + src/import/staging/src/k8s.io/apimachinery/go.mod|   2 +-
> + src/import/staging/src/k8s.io/apimachinery/go.sum|   4 +-
> + src/import/staging/src/k8s.io/apiserver/go.mod   |   2 +-
> + src/import/staging/src/k8s.io/apiserver/go.sum   |   4 +-
> + src/import/staging/src/k8s.io/cli-runtime/go.sum |   4 +-
> + src/import/staging/src/k8s.io/client-go/go.sum   |   4 +-
> + src/import/staging/src/k8s.io/cloud-provider/go.sum  |   4 +-
> + src/import/staging/src/k8s.io/cluster-bootstrap/go.sum   |   4 +-
> + src/import/staging/src/k8s.io/code-generator/go.mod  |   2 +-
> + src/import/staging/src/k8s.io/code-generator/go.sum  |   4 +-
> + src/import/staging/src/k8s.io/component-base/go.sum  |   4 +-
> + src/import/staging/src/k8s.io/csi-translation-lib/go.sum |   4 +-
> + src/import/staging/src/k8s.io/kube-aggregator/go.sum |   4 +-
> + .../src/k8s.io/kube-controller-manager/go.sum   |   4 +-
> + src/import/staging/src/k8s.io/kube-proxy/go.sum  |   4 +-
> + src/import/staging/src/k8s.io/kube-scheduler/go.sum  |   4 +-
> + src/import/staging/src/k8s.io/kubectl/go.mod |   2 +-
> + src/import/staging/src/k8s.io/kubectl/go.sum |   4 +-
> + src/import/staging/src/k8s.io/kubelet/go.sum |   4 +-
> + .../src/k8s.io/legacy-cloud-providers/go.sum|   4 +-
> + src/import/staging/src/k8s.io/metrics/go.sum |   4 +-
> + src/import/staging/src/k8s.io/node-api/go.sum|   4 +-
> + src/import/staging/src/k8s.io/sample-apiserver/go.sum|   4 +-
> + src/import/staging/src/k8s.io/sample-cli-plugin/go.sum   |   4 +-
> + src/import/staging/src/k8s.io/sample-controller/go.sum   |   4 +-
> + src/import/vendor/gopkg.in/yaml.v2/.travis.yml   |  18 +--
> + src/import/vendor/gopkg.in/yaml.v2/decode.go |  14 ++-
> + src/import/vendor/gopkg.in/yaml.v2/scannerc.go   | 107 
> +-
> + src/import/vendor/gopkg.in/yaml.v2/yaml.go   |   2 +-
> + src/import/vendor/gopkg.in/yaml.v2/yamlh.go  |   1 +
> + src/import/vendor/modules.txt|   2 +-
> + 36 files changed, 130 insertions(+), 124 deletions(-)
> +
> +diff --git a/src/import/go.mod b/go.mod
> +index cf8c9147e62..884870f8843 100644
> +--- a/src/import/go.mod
>  b/src/import/go.mod
> +@@ -139,7 +139,7 @@ require (
> + google.golang.org/grpc v1.23.0
> + gopkg.in/gcfg.v1 v1.2.0
> + gopkg.in/square/go-jose.v2 v2.2.2
> +-gopkg.in/yaml.v2 v2.2.4
> ++gopkg.in/yaml.v2 v2.2.8
> + gotest.tools v2.2.0+incompatible
> + gotest.tools/gotestsum v0.3.5
> + honnef.co/go/tools v0.0.1-2019.2.2
> +@@ -444,7 +444,7 @@ replace (
> + gopkg.in/square/go-jose.v2 => gopkg.in/square/go-jose.v2 v2.2.2
> + gopkg.in/tomb.v1 => gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7
> + gopkg.in/warnings.v0 => gopkg.in/warnings.v0 v0.1.1
> +-gopkg.in/yaml.v2 => gopkg.in/yaml.v2 v2.2.4
> ++gopkg.in/yaml.v2 => gopkg.in/yaml.v2 v2.2.8
> + gotest.tools => gotest.tools v2.2.0+incompatible
> + gotest.tools/gotestsum => gotest.tools/gotestsum v0.3.5
> + honnef.co/go/tools => honnef.co/go/tools v0.0.1-2019.2.2
> +diff --git a/src/import/go.sum b/src/import/go.sum
> +index b5e3f74686f..617081d2d9e 100644
> +--- a/src/import/go.sum
>  b/src/import/go.sum
> +@@ -4

[yocto] [yocto-autobuilder2][PATCH 0/2] Clarification and formatting of README-Guide.md

2020-06-22 Thread Trevor Gamblin

Long-overdue patches based on experiences trying to set up an
autobuilder instance. I've split it into two patches because the second
patch (the one that line wraps the majority of the document) may not be
desired, if the doc is meant to be read in the pre-existing format.
Patch 0001 cleans up the doc so that the sections can be more easily
referenced.

Trevor Gamblin (2):
  README-Guide: cleanup, clarify setup instructions
  README-Guide: wrap lines at 80 characters

 README-Guide.md | 489 
 1 file changed, 372 insertions(+), 117 deletions(-)

-- 
2.26.2

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49717): https://lists.yoctoproject.org/g/yocto/message/49717
Mute This Topic: https://lists.yoctoproject.org/mt/75039158/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [yocto-autobuilder2][PATCH 1/2] README-Guide: cleanup, clarify setup instructions

2020-06-22 Thread Trevor Gamblin

Broke the document up into more sections, and added some info
to make it clear that the same instructions for setting up
the systemd autobuilder can be used to start it manually.

Signed-off-by: Trevor Gamblin 
---
 README-Guide.md | 33 ++---
 1 file changed, 30 insertions(+), 3 deletions(-)

diff --git a/README-Guide.md b/README-Guide.md
index 21dd7c1..83e30d0 100644
--- a/README-Guide.md
+++ b/README-Guide.md
@@ -4,6 +4,8 @@ This guide will walk through how to install a stand-alone 
autobuilder controller
 
 ## 1) Stand-alone Installation
 
+### 1.1) Basic Requirements
+
 The final outputs of this section are a controller and worker installed in the 
same server, ready for trimming back to an individual organization's needs.
 
  > NOTE: The guide assumes that your host OS has the packages installed to 
support BitBake for the release(s) you are targeting.?? Please refer to the 
Yocto manual for those packages.
@@ -17,6 +19,8 @@ sudo pip3 install buildbot buildbot-www 
buildbot-waterfall-view buildbot-console
 
 It is recommended to also install??`testtools` and??`libccpunit-subunit-dev` 
(via apt, in this case) on the worker in order??for certain image tests to work 
correctly (e.g., `core-image-sato-sdk:do_testimage`).
 
+### 1.2) Creating the Autobuilder User's Directory
+
 For a new installation you will need a system user that can run Autobuilder2 
as well as a couple of repositories: Autobuilder2 itself and a helper plugin.  
As root:
 
 ```
@@ -27,11 +31,14 @@ buildbot-worker create-worker -r --umask=0o22 yocto-worker 
localhost example-wor
 cd yocto-controller
 git clone??https://git.yoctoproject.org/git/yocto-autobuilder2??yoctoabb
 ln -rs yoctoabb/master.cfg master.cfg
-cd ~
+cd -
 git clone??https://git.yoctoproject.org/git/yocto-autobuilder-helper
 chown -R pokybuild3:nogroup /home/pokybuild3
 ```
 
+Note: depending on the configuration of your system, you may need to
+replace "nogroup" with "pokybuild3" for the last command to work.
+
  > **IMPORTANT:** In the above command you created a controller and a worker, 
which will attempt to join the controller using??`pass` as the password.?? Feel 
free to change this, knowing that if you do, you must change the controller's 
master configuration file to match.
 
 At the end of this, your build user's home directory (e.g., 
`/home/pokybuild3`) should look like this:
@@ -43,6 +50,8 @@ yocto-controller/yoctoabb
 yocto-worker
 ```
 
+### 1.3) Customizing the Autobuilder Configuration
+
 Next, we need to update the??`yocto-controller/yoctoabb/master.cfg` towards 
the bottom where the??`title`,??`titleURL`, and??`buildbotURL` are all set.  
This is also where you would specify a different password for binding workers 
to the master.
 
 Then, we need to update the??`yocto-controller/yoctoabb/config.py` to include 
our worker.?? In that file, find the line where??`workers` is set and 
add:??["example-worker"]._NOTE:_ if your worker's name is different, use 
that here.?? Section 3.1 discusses how to further refine this list of workers.
@@ -61,9 +70,27 @@ Set??`BASE_HOMEDIR` should be your build user's home 
directory.?? (There are she
 
  > NOTE: The way the build step is written, the worker will pull a fresh copy 
of the helper from the server.  Therefore??these configuration files must be 
committed to the??`yocto-autobuilder-helper`??repo location you have specified 
in??`yoctoabb/config.py`??because the worker is given a build step that pulls 
from that repo (see??`yoctoabb/builders.py`).
 
-Finally, as root,??add the??`yocto-*.service` files to??`/lib/systemd/system` 
(See Appendix A).?? Run: `systemctl daemon-reload`.?? You should now be able to 
successfully start these services (e.g., `sudo systemctl start yocto-*`).?? The 
controller may take up to 15 seconds to start.
+### 1.4) Starting the Autobuilder
+
+At this point, you can start your Autobuilder controller, worker, and
+janitor in one of two ways: using buildbot manually, or by creating
+systemd service files.
+
+ 1.4.1) Manually Starting the Autobuilder
+
+Run the following from the pokybuild3 directory:
+
+ 1. yocto-autobuilder-helper/janitor/ab-janitor&
+ 2. buildbot start yocto-controller
+ 3. buildbot-worker start yocto-worker
+
+ 1.4.2) Creating Service Files
+
+ 1. As root,??add the??`yocto-*.service` files to??`/lib/systemd/system` (See 
Appendix A).?? 
+ 2. Run: `systemctl daemon-reload`.?? 
+ 3. You should now be able to successfully start these services (e.g., `sudo 
systemctl start yocto-*`).??The controller may take up to 15 seconds to start.
 
-### 1.1) Configuring the Worker's Hash Equivalency Server
+### 1.5) Configuring the Worker's Hash Equivalency Server
 
 A key part of the autobuilder setup is the use of a hash equivalency
 server, which is started manually on the Yocto hosts. By default, the 
-- 
2.26.2

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49716): https://lists.yoctoproj

[yocto] [yocto-autobuilder2][PATCH 2/2] README-Guide: wrap lines at 80 characters

2020-06-22 Thread Trevor Gamblin

Signed-off-by: Trevor Gamblin 
---
 README-Guide.md | 454 
 1 file changed, 341 insertions(+), 113 deletions(-)

diff --git a/README-Guide.md b/README-Guide.md
index 83e30d0..aaefd02 100644
--- a/README-Guide.md
+++ b/README-Guide.md
@@ -1,14 +1,20 @@
 # Installing and Maintaining the Yocto Autobuilder 2
 
-This guide will walk through how to install a stand-alone autobuilder 
controller and worker, and then reconfigure it with new builds, etc.?? The 
guide was written with the help of Richard Purdie under the context of a 
headless Ubuntu 18.04.02 Server installation.
+This guide will walk through how to install a stand-alone autobuilder 
controller
+and worker, and then reconfigure it with new builds, etc.?? The guide was 
written
+with the help of Richard Purdie under the context of a headless Ubuntu 18.04.02
+Server installation.
 
 ## 1) Stand-alone Installation
 
 ### 1.1) Basic Requirements
 
-The final outputs of this section are a controller and worker installed in the 
same server, ready for trimming back to an individual organization's needs.
+The final outputs of this section are a controller and worker installed in the
+same server, ready for trimming back to an individual organization's needs.
 
- > NOTE: The guide assumes that your host OS has the packages installed to 
support BitBake for the release(s) you are targeting.?? Please refer to the 
Yocto manual for those packages.
+ > NOTE: The guide assumes that your host OS has the packages installed to
+ > support BitBake for the release(s) you are targeting.?? Please refer to the
+ > Yocto manual for those packages.
 
 The latest version of BuildBot is written in Python 3, so installation 
via??pip3:
 
@@ -17,11 +23,15 @@ apt install git build-essential python3-pip virtualenv 
enchant npm
 sudo pip3 install buildbot buildbot-www buildbot-waterfall-view 
buildbot-console-view buildbot-grid-view buildbot-worker
 ```
 
-It is recommended to also install??`testtools` and??`libccpunit-subunit-dev` 
(via apt, in this case) on the worker in order??for certain image tests to work 
correctly (e.g., `core-image-sato-sdk:do_testimage`).
+It is recommended to also install??`testtools` and??`libccpunit-subunit-dev` 
(via
+apt, in this case) on the worker in order??for certain image tests to work
+correctly (e.g., `core-image-sato-sdk:do_testimage`).
 
 ### 1.2) Creating the Autobuilder User's Directory
 
-For a new installation you will need a system user that can run Autobuilder2 
as well as a couple of repositories: Autobuilder2 itself and a helper plugin.  
As root:
+For a new installation you will need a system user that can run Autobuilder2 as
+well as a couple of repositories: Autobuilder2 itself and a helper plugin.  As
+root:
 
 ```
 useradd -m --system pokybuild3
@@ -39,9 +49,13 @@ chown -R pokybuild3:nogroup /home/pokybuild3
 Note: depending on the configuration of your system, you may need to
 replace "nogroup" with "pokybuild3" for the last command to work.
 
- > **IMPORTANT:** In the above command you created a controller and a worker, 
which will attempt to join the controller using??`pass` as the password.?? Feel 
free to change this, knowing that if you do, you must change the controller's 
master configuration file to match.
+ > **IMPORTANT:** In the above command you created a controller and a worker,
+ > which will attempt to join the controller using??`pass` as the password.?? 
Feel
+ > free to change this, knowing that if you do, you must change the 
controller's
+ > master configuration file to match.
 
-At the end of this, your build user's home directory (e.g., 
`/home/pokybuild3`) should look like this:
+At the end of this, your build user's home directory (e.g., `/home/pokybuild3`)
+should look like this:
 
 ```
 yocto-autobuilder-helper
@@ -52,23 +66,50 @@ yocto-worker
 
 ### 1.3) Customizing the Autobuilder Configuration
 
-Next, we need to update the??`yocto-controller/yoctoabb/master.cfg` towards 
the bottom where the??`title`,??`titleURL`, and??`buildbotURL` are all set.  
This is also where you would specify a different password for binding workers 
to the master.
+Next, we need to update the??`yocto-controller/yoctoabb/master.cfg` towards the
+bottom where the??`title`,??`titleURL`, and??`buildbotURL` are all set.  This 
is
+also where you would specify a different password for binding workers to the
+master.
 
-Then, we need to update the??`yocto-controller/yoctoabb/config.py` to include 
our worker.?? In that file, find the line where??`workers` is set and 
add:??["example-worker"]._NOTE:_ if your worker's name is different, use 
that here.?? Section 3.1 discusses how to further refine this list of workers.
+Then, we need to update the??`yocto-controller/yoctoabb/config.py` to include 
our
+worker.?? In that file, find the line where??`workers` is set and
+add:??["example-worker"]._NOTE:_ if your worker's name is different, use 
that
+here.?? Section 3.1 discusses

Re: [yocto] populate_sdk couldn't create the SDK installer for my image #sdk

2020-06-22 Thread Khem Raj




On 6/22/20 3:47 AM, Robert Varga wrote:

Hello Yocto Community,

I am new to the Yocto Project and need some help regarding creating the 
SDK installer for my image on a Ubuntu 18.04 host machine...
So far I was able to build an image for my target (based on latest 
Warrior branch). The image is based on the core-image-full-cmdline as it 
gets referenced by the corresponding recipe my-image.bb (see attachment):
Additional, I created an distro configuration file mydistro.conf which 
includes the poky.conf distro configuration file (see attachment).
When I execute bitbake my-image -c populate_sdk, I get following errors 
within last task (while the do_populate_skd task):


| NOTE: Executing create_sdk_files ...
| DEBUG: Executing shell function create_sdk_files
| DEBUG: Shell function create_sdk_files finished
| NOTE: Executing check_sdk_sysroots ...
| DEBUG: Executing python function check_sdk_sysroots
| DEBUG: Python function check_sdk_sysroots finished
| NOTE: Executing tar_sdk ...
| DEBUG: Executing shell function tar_sdk
| DEBUG: Shell function tar_sdk finished
| NOTE: Executing create_shar ...
| DEBUG: Executing shell function create_shar
| sed: -e expression #6, char 21: unterminated `s' command


are there any aliases etc. to common programs like install in your 
environment ?
maybe do bitbake -e  my-image and inspect the output especially 
do_populate_sdk function and see if you find some sed cmd being called 
with invalid options.



| WARNING: exit code 1 from a shell command.
| DEBUG: Python function do_populate_sdk finished
| ERROR: Function failed: create_shar (log file is located at 
/home/varga-r/projects/yocto/build/tmp/work/mymachine-poky-linux-gnueabi/my-image/1.0-r0/temp/log.do_populate_sdk.126574)
ERROR: Task 
(/home/varga-r/projects/yocto/poky/meta-robert/recipes-core/images/my-image.bb:do_populate_sdk) 
failed with exit code '1'
NOTE: Tasks Summary: Attempted 3588 tasks of which 2265 didn't need to 
be rerun and 1 failed.

Summary: 1 task failed:
   
/home/varga-r/projects/yocto/poky/meta-robert/recipes-core/images/my-image.bb:do_populate_sdk

Summary: There were 13 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


The complete log log.do_populate_sdk.126574 is also attached.

Could some help me to find the root cause of this issue? Any help would 
be appreciated.


--
Rob



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49719): https://lists.yoctoproject.org/g/yocto/message/49719
Mute This Topic: https://lists.yoctoproject.org/mt/75035545/21656
Mute #sdk: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/sdk
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2020-06-22 Thread Stephen 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 374
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, "3.1", "3.2, "3.99" and "Future", the more pressing/urgent issues
being in "3.1" and then "3.2".

 

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_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49720): https://lists.yoctoproject.org/g/yocto/message/49720
Mute This Topic: https://lists.yoctoproject.org/mt/75048588/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.2

2020-06-22 Thread Stephen Jolley

All,

Below is the list as of top 46 bug owners as of the end of WW25 of who have
open medium or higher bugs and enhancements against YP 3.2.   There are 91
possible work days left until the final release candidates for YP 3.2 needs
to be released.


Who

Count


richard.pur...@linuxfoundation.org

29


david.re...@windriver.com

19


bluelightn...@bluelightning.org

17


bruce.ashfi...@gmail.com

14


r...@burtonini.com

11


mark.mor...@windriver.com

9


akuster...@gmail.com

7


mich...@yoctoproject.org

5


qi.c...@windriver.com

5


randy.macl...@windriver.com

4


pbar...@konsulko.com

4


yi.z...@windriver.com

3


jon.ma...@arm.com

3


jpewhac...@gmail.com

3


rpj...@crashcourse.ca

3


raj.k...@gmail.com

3


alejan...@enedino.org

2


kai.k...@windriver.com

2


dl...@gmx.de

2


chee.yang@intel.com

2


timothy.t.orl...@intel.com

2


trevor.gamb...@windriver.com

2


jpuhl...@mvista.com

2


mark.ha...@kernel.crashing.org

2


se...@seebs.net

2


ycnakaj...@gmail.com

2


mostthings...@gmail.com

2


kerg...@gmail.com

2


jae...@xilinx.com

2


martin.ja...@gmail.com

1


limon.ani...@gmail.com

1


matthew.z...@windriver.com

1


sakib.sa...@windriver.com

1


maxime.roussinbelan...@gmail.com

1


ricardo.riba...@gmail.com

1


nicolas.deche...@linaro.org

1


b...@stusta.de

1


hongxu@windriver.com

1


kai.ruh...@live.com

1


liu.min...@gmail.com

1


jason.wes...@windriver.com

1


naveen.kumar.sa...@intel.com

1


ms...@mvista.com

1


de...@denix.org

1


akus...@mvista.com

1


changqing...@windriver.com

1


Grand Total

182

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49721): https://lists.yoctoproject.org/g/yocto/message/49721
Mute This Topic: https://lists.yoctoproject.org/mt/75048626/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW25!

2020-06-22 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


mark.mor...@windriver.com

2


r...@burtonini.com

1


anuj.mit...@intel.com

1


timothy.t.orl...@intel.com

1


richard.pur...@linuxfoundation.org

1


jpewhac...@gmail.com

1


Grand Total

7

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49722): https://lists.yoctoproject.org/g/yocto/message/49722
Mute This Topic: https://lists.yoctoproject.org/mt/75048716/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW25

2020-06-22 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW25 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  13123

package.PackageTests.test_gdb_hardlink_debug failed

randy.macl...@windriver.com

randy.macl...@windriver.com

3.2 M1

3.2 M2


 

  13425

Add bblock and bbunlock helper tools

randy.macl...@windriver.com

newco...@yoctoproject.org

3.2 M1

3.2 M2


 

  13676

selftest  test_gdb_hardlink_debug failure

randy.macl...@windriver.com

randy.macl...@windriver.com

3.2 M1

3.2 M2


 

  13690

runqemu with slirp, forwarded host ports are not available on host

timothy.t.orl...@intel.com

timothy.t.orl...@intel.com

3.2 M1

3.2 M2


 

  13722

Debugging With the GNU Project Debugger enhancements

randy.macl...@windriver.com

rpj...@crashcourse.ca

3.2 M1

3.2 M2


 

  13766

Using TCLIB=musl results in SDKs producing incompatible binaries

randy.macl...@windriver.com

randy.macl...@windriver.com

3.2 M1

3.2 M2


 

  13793

layerindex-web: Django 1.11 LTS EOL April 2020; need to upgrade to Django
2.2 LTS

timothy.t.orl...@intel.com

amber.n.ell...@intel.com

3.2 M1

3.2 M2


 

  13888

Toaster is not starting for Django-3

randy.macl...@windriver.com

david.re...@windriver.com

3.1.1

3.1.2


 

  13899

buildtools missing OpenMP (rpm-native: parseSpec.c:10:10: fatal error:
omp.h: No such file or directory)

randy.macl...@windriver.com

st...@sakoman.com

3.1.1

3.1.2


 

  13904

do_prepare_recipe_sysroot: postinst-useradd-* does not run in order of
dependency and sometimes fails

jackie.hu...@windriver.com

jackie.hu...@windriver.com

3.2 M1

3.2 M4


 

  13938

devtool modify virtual/kernel fails when EXTRAVERSION field is empty in
Makefile

timothy.t.orl...@intel.com

timothy.t.orl...@intel.com

3.2 M1

3.2 M2

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49723): https://lists.yoctoproject.org/g/yocto/message/49723
Mute This Topic: https://lists.yoctoproject.org/mt/75048744/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH] sssd: disable build secrets

2020-06-22 Thread kai


On 6/17/20 11:41 AM, kai wrote:

From: Kai Kang 

It requires http_parser.h to build secrets:

| configure: error:
| You must have the header file http_parser.h installed to build sssd
| with secrets responder. If you want to build sssd without secret responder
| then specify --without-secrets when running configure.

The header file is from package http-parser[1] rather than apache2. But
there is no recipe http-parser in openembedded. So disable build secrets
for sssd and remove related systemd service and socket files.

Reference:
1. https://github.com/nodejs/http-parser


Ping.




Signed-off-by: Kai Kang 
---
  recipes-security/sssd/sssd_1.16.4.bb | 7 +++
  1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/recipes-security/sssd/sssd_1.16.4.bb 
b/recipes-security/sssd/sssd_1.16.4.bb
index 7ea1586..2c3c803 100644
--- a/recipes-security/sssd/sssd_1.16.4.bb
+++ b/recipes-security/sssd/sssd_1.16.4.bb
@@ -39,8 +39,7 @@ PACKAGECONFIG += "${@bb.utils.contains('DISTRO_FEATURES', 
'systemd', 'systemd',
  
  PACKAGECONFIG[autofs] = "--with-autofs, --with-autofs=no"

  PACKAGECONFIG[crypto] = "--with-crypto=libcrypto, , libcrypto"
-PACKAGECONFIG[curl] = "--with-secrets --with-kcm, --without-secrets --without-kcm, 
curl jansson"
-PACKAGECONFIG[http] = "--with-secrets, --without-secrets, apache2"
+PACKAGECONFIG[curl] = "--with-kcm, --without-kcm, curl jansson"
  PACKAGECONFIG[infopipe] = "--with-infopipe, --with-infopipe=no, "
  PACKAGECONFIG[manpages] = "--with-manpages, --with-manpages=no"
  PACKAGECONFIG[nl] = "--with-libnl, --with-libnl=no, libnl"
@@ -60,6 +59,7 @@ EXTRA_OECONF += " \
  --without-python2-bindings \
  --enable-pammoddir=${base_libdir}/security \
  --without-python2-bindings \
+--without-secrets \
  "
  
  do_configure_prepend() {

@@ -85,6 +85,7 @@ do_install () {
  # Remove /var/run as it is created on startup
  rm -rf ${D}${localstatedir}/run
  
+rm -f ${D}${systemd_system_unitdir}/sssd-secrets.*

  }
  
  pkg_postinst_ontarget_${PN} () {

@@ -109,8 +110,6 @@ SYSTEMD_SERVICE_${PN} = " \
  sssd-pam-priv.socket \
  sssd-pam.service \
  sssd-pam.socket \
-sssd-secrets.service \
-sssd-secrets.socket \
  sssd.service \
  "
  SYSTEMD_AUTO_ENABLE = "disable"





--
Kai Kang
Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49724): https://lists.yoctoproject.org/g/yocto/message/49724
Mute This Topic: https://lists.yoctoproject.org/mt/74931372/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] MACHINE and inc files

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

[yocto] License reporting for golang (and rust)

Re: [yocto][meta-virtualization][zeus][PATCH] kubernetes: CVE-2019-11254

[yocto] [yocto-autobuilder2][PATCH 0/2] Clarification and formatting of README-Guide.md

[yocto] [yocto-autobuilder2][PATCH 1/2] README-Guide: cleanup, clarify setup instructions

[yocto] [yocto-autobuilder2][PATCH 2/2] README-Guide: wrap lines at 80 characters

Re: [yocto] populate_sdk couldn't create the SDK installer for my image #sdk

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[yocto] Current high bug count owners for Yocto Project 3.2

[yocto] Enhancements/Bugs closed WW25!

[yocto] M+ & H bugs with Milestone Movements WW25

Re: [yocto] [meta-security][PATCH] sssd: disable build secrets

13 matches

Site Navigation

Mail list logo

Footer information