Date   

Re: Applying grpc fix to `zeus`

Randy MacLeod
 

On 12/16/19 6:26 PM, dmitri.toubelis@... wrote:
Hi,

Would it be possible to retrofit this patch https://patchwork.openembedded.org/patch/168023/ to `zeus`? This fixes an issue with grpc package build failing when multilib is enabled.

HI Dmitri,

The patch is undergoing tests in master-next as of 20 hours ago:
   http://git.openembedded.org/meta-openembedded/log/?h=master-next

So wait a day or two and if it gets merged to master, cherry-pick it back to zeus and
send it in if no one else does that before you do.

https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Sending_using_git-send-email

Thanks,

../Randy



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

View/Reply Online (#47704): https://lists.yoctoproject.org/g/yocto/message/47704
Mute This Topic: https://lists.yoctoproject.org/mt/68746345/3616765
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [randy.macleod@...]
-=-=-=-=-=-=-=-=-=-=-=-


-- 
# Randy MacLeod
# Wind River Linux


Applying grpc fix to `zeus`

dmitri.toubelis@...
 

Hi,

Would it be possible to retrofit this patch https://patchwork.openembedded.org/patch/168023/ to `zeus`? This fixes an issue with grpc package build failing when multilib is enabled.

Regard,
-Dmitri


Problem with rootfs boot on my raspberrypi. #raspberrypi

wojciech.st@...
 

Hi
I am building simple image for my raspbery pi 3 A+ and connect to the pi via USB-UART converter and see the following in the console
...
[ 2.071459] Run /bin/init as init process
[ 2.076507] Run /bin/sh as init process
sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell
sh-4.4#



I build with the "bitbake core-image-base" and tried to run it on rpi 3A+, 3B, 3B+ and the problem is always the same it cannot switch to the rootfs on the sd card it seem like it stack at initramfs or some middle ground.

I burn the *.rpi-sdimg image to SD card with dd from my Ubuntu16.04 host machine.
I tried with two branches thud and warrior and the problem is exactly the same.
The strange thing is that in this initramfs there are no tools like find grep modprobe etc. but I see my extra tools "
i2c-tools vim"

Here is my local.conf adjustments:
MACHINE ?= "raspberrypi3"
ENABLE_I2C = "1"
ENABLE_UART = "1"
IMAGE_INSTALL += "i2c-tools vim"

and the bblayer.conf
BBLAYERS ?= " \
  /media/dave/Develop/yoctopi/warrior/sources/poky/meta \
  /media/dave/Develop/yoctopi/warrior/sources/poky/meta-poky \
  /media/dave/Develop/yoctopi/warrior/sources/poky/meta-yocto-bsp \
  /media/dave/Develop/yoctopi/warrior/sources/meta-openembedded/meta-oe \
  /media/dave/Develop/yoctopi/warrior/sources/meta-raspberrypi \
  "

I tried also to build with the deprecated image "bitbake rpi-basic-image" but then I did not get my extra tools
"i2c-tools vim".

Anyone have any idea what can be wrong with my approach ?

Regards,

Wojciech


How to upgrade the kernel

Lewis Muhlenkamp <lewis.muhlenkamp@...>
 

Hello,

 

I am still fairly new to Yocto and Openembedded.  I’ve built a custom distribution and have a few images.  I’m now in the process of trying to determine how to upgrade from one version to another.

 

I created an image using Yocto 2.6.  When I install it, it installs the following kernel RPMs:

 

### Start “rpm -qa | grep kernel | grep -v kernel-module” output ###

kernel-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common

kernel-image-4.14.110-intel-pk-standard-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common

kernel-4.14.110-intel-pk-standard-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common

kernel-image-bzimage-4.14.110-intel-pk-standard-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common

### End “rpm -qa | grep kernel | grep -v kernel-module” output ###

 

 

I built a newer image using Yocto 3.0.  In the RPM repo I have the following kernel RPMs:

 

### Start “ls -1 /var/opt/repos/os | grep kernel | grep -v kernel-module” output ###

kernel-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm

kernel-4.19.73-intel-pk-standard-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm

kernel-dev-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm

kernel-image-4.19.73-intel-pk-standard-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm

kernel-image-bzimage-4.19.73-intel-pk-standard-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm

kernel-vmlinux-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm

systemd-kernel-install-243+0+efb536d0cb-r0.corei7_64.rpm

### End “ls -1 /var/opt/repos/os | grep kernel | grep -v kernel-module” output ###

 

 

When I try to do “dnf upgrade” I get the following error messages:

 

### Start excerpt from “dnf upgrade” command ###

Last metadata expiration check: 0:40:06 ago on Mon Dec 16 17:43:31 2019.

Dependencies resolved.

================================================================================

Package

     Arch                   Version                               Repository

                                                                           Size

================================================================================

Upgrading:

kernel

     corei7_64_intel_common 4.19.73+git0+a7cb57afb9_ca05e9cd64-r0 OS_Repo 5.6 k

kernel-4.19.73-intel-pk-standard

     corei7_64_intel_common 4.19.73+git0+a7cb57afb9_ca05e9cd64-r0 OS_Repo  16 k

kernel-image-4.19.73-intel-pk-standard

     corei7_64_intel_common 4.19.73+git0+a7cb57afb9_ca05e9cd64-r0 OS_Repo 5.8 k

kernel-image-bzimage-4.19.73-intel-pk-standard

     corei7_64_intel_common 4.19.73+git0+a7cb57afb9_ca05e9cd64-r0 OS_Repo 7.8 M

Transaction Summary

================================================================================

Install  1297 Packages

Upgrade   666 Packages

Skip        5 Packages

 

Total size: 232 M

Is this ok [y/N]: y

Downloading Packages:

Running transaction check

Transaction check succeeded.

Running transaction test

Error: Transaction check error:

  file /boot/bzImage from install of kernel-image-bzimage-4.19.73-intel-pk-standard-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common conflicts with file from package kernel-image-bzimage-4.14.110-intel-pk-standard-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common

 

Error Summary

-------------

### End excerpt from “dnf upgrade” command ###

 

 

I also tried running “dnf upgrade --best --allowerasing”, but got the same results.

 

Can I upgrade a system using the dnf command?  If so, how?  If not, what do I need to do to allow the system to be upgraded using the dnf command?

 

Thank you

 

Lewis Muhlenkamp

 

Follow this link to read our Privacy Statement


[PATCH yocto-autobuilder-helper v2 3/3] README: add git-config commands to setup the mailer

Ross Burton <ross.burton@...>
 

---
README | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README b/README
index 4f2a7f1..249feb2 100644
--- a/README
+++ b/README
@@ -29,4 +29,8 @@ Authors:
Contributions:
=20
Patches for this code should be sent to the yocto@...=
mailing list
-with [yocto-autobuilder-helper] in the subject.
+with [yocto-autobuilder-helper] in the subject. This can be configured =
automatically
+with the following commands:
+
+ git config --local --add format.subjectprefix 'PATCH yocto-autobuilde=
r-helper'
+ git config --local --add sendemail.to yocto@...
--=20
2.20.1


[PATCH yocto-autobuilder-helper v2 2/3] README: fix list address

Ross Burton <ross.burton@...>
 

---
README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README b/README
index 2747510..4f2a7f1 100644
--- a/README
+++ b/README
@@ -28,5 +28,5 @@ Authors:
=20
Contributions:
=20
-Patches for this code should be sent to the yocto@... maili=
ng list
+Patches for this code should be sent to the yocto@...=
mailing list
with [yocto-autobuilder-helper] in the subject.
--=20
2.20.1


[PATCH yocto-autobuilder-helper v2 1/3] config: don't run meta-intel in qemu yet

Ross Burton <ross.burton@...>
 

meta-intel BSPs are not compatible with the qemu BSPs currently, so don't
attempt to execute testimage.

Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index 5730f85..79695c2 100644
--- a/config.json
+++ b/config.json
@@ -387,7 +387,7 @@
"NEEDREPOS" : ["poky", "meta-intel"],
"ADDLAYER" : ["${BUILDDIR}/../meta-intel"],
"MACHINE" : "intel-corei7-64",
- "TEMPLATE" : "arch-hw-qemu"
+ "TEMPLATE" : "arch-hw"
},
"genericx86-64-alt" : {
"MACHINE" : "genericx86-64",
--=20
2.20.1


[PATCH yocto-autobuilder-helper] README: add git-config commands to setup the mailer

Ross Burton <ross.burton@...>
 

---
README | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README b/README
index 2747510..f49fc48 100644
--- a/README
+++ b/README
@@ -29,4 +29,8 @@ Authors:
Contributions:
=20
Patches for this code should be sent to the yocto@... maili=
ng list
-with [yocto-autobuilder-helper] in the subject.
+with [yocto-autobuilder-helper] in the subject. This can be configured =
automatically
+with the following commands:
+
+ git config --local --add format.subjectprefix 'PATCH yocto-autobuilde=
r-helper'
+ git config --local --add sendemail.to yocto@...
--=20
2.20.1


[PATCH yocto-autobuilder-helper] config: don't run meta-intel in qemu yet

Ross Burton <ross.burton@...>
 

meta-intel BSPs are not compatible with the qemu BSPs currently, so don't
attempt to execute testimage.

Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index 5730f85..79695c2 100644
--- a/config.json
+++ b/config.json
@@ -387,7 +387,7 @@
"NEEDREPOS" : ["poky", "meta-intel"],
"ADDLAYER" : ["${BUILDDIR}/../meta-intel"],
"MACHINE" : "intel-corei7-64",
- "TEMPLATE" : "arch-hw-qemu"
+ "TEMPLATE" : "arch-hw"
},
"genericx86-64-alt" : {
"MACHINE" : "genericx86-64",
--=20
2.20.1


Re: Docker Error on Yocto Build on ARM

Aj Cit
 

Hi Bruce,

Thank you for the clarification. Shall work in the direction cited.

We will get back to you if we face any more issues as and when we proceed. 

Best,
Aj

On Mon, Dec 16, 2019 at 6:41 PM Bruce Ashfield <bruce.ashfield@...> wrote:
On Mon, Dec 16, 2019 at 7:23 AM Aj Cit <aj.ci.01.239@...> wrote:
>
> Hi,
>
> We are getting the following error while building yocto -warrior QEMUarm64; however we are getting the following error while running the docker service.:
>

The meta-virtualization list is the right place to ask questions about docker.

> systemctl status docker, returned error.
> Dec 16 09:00:19 qemuarm64 dockerd[340]: Error starting daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program NAT chain: Failed to inject DOCKER in PRERO
> UTING chain: iptables failed: iptables --wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER: iptables: No chain/target/match by that name.
>

This is almost always a side effect the kernel not being configured
correctly, and even more often, the kernel modules are not installed
in your image.

If you are using linux-yocto, and you have virtualization in your
DISTRO_FEATURES, the kernel config is taken care of. But you do need
to have "kernel-modules" in your image install variables to get the
right modules onto the target.

Bruce

>
> also. Dec 16 05:58:53 qemuarm64 dockerd[628]: time="2019-12-16T05:58:53.499510946Z" level=warning msg="Running modprobe bridge br_netfilter failed with message: modprobe: WARNING: Module br_netfilter not found
> in directory /lib/modules/5.0.19-yocto-standard\n, error: exit status 1"
>
> Any help will be much appreciated.
>
> Thanks
> Aj
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#47693): https://lists.yoctoproject.org/g/yocto/message/47693
> Mute This Topic: https://lists.yoctoproject.org/mt/68726097/1050810
> Group Owner: yocto+owner@...
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [bruce.ashfield@...]
> -=-=-=-=-=-=-=-=-=-=-=-



--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


Re: Docker Error on Yocto Build on ARM

Bruce Ashfield
 

On Mon, Dec 16, 2019 at 7:23 AM Aj Cit <aj.ci.01.239@...> wrote:

Hi,

We are getting the following error while building yocto -warrior QEMUarm64; however we are getting the following error while running the docker service.:
The meta-virtualization list is the right place to ask questions about docker.

systemctl status docker, returned error.
Dec 16 09:00:19 qemuarm64 dockerd[340]: Error starting daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program NAT chain: Failed to inject DOCKER in PRERO
UTING chain: iptables failed: iptables --wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER: iptables: No chain/target/match by that name.
This is almost always a side effect the kernel not being configured
correctly, and even more often, the kernel modules are not installed
in your image.

If you are using linux-yocto, and you have virtualization in your
DISTRO_FEATURES, the kernel config is taken care of. But you do need
to have "kernel-modules" in your image install variables to get the
right modules onto the target.

Bruce


also. Dec 16 05:58:53 qemuarm64 dockerd[628]: time="2019-12-16T05:58:53.499510946Z" level=warning msg="Running modprobe bridge br_netfilter failed with message: modprobe: WARNING: Module br_netfilter not found
in directory /lib/modules/5.0.19-yocto-standard\n, error: exit status 1"

Any help will be much appreciated.

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

View/Reply Online (#47693): https://lists.yoctoproject.org/g/yocto/message/47693
Mute This Topic: https://lists.yoctoproject.org/mt/68726097/1050810
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [bruce.ashfield@...]
-=-=-=-=-=-=-=-=-=-=-=-


--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


Docker Error on Yocto Build on ARM

Aj Cit
 

Hi,

We are getting the following error while building yocto -warrior QEMUarm64; however we are getting the following error while running the docker service.:

systemctl status docker, returned error.
Dec 16 09:00:19 qemuarm64 dockerd[340]: Error starting daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program NAT chain: Failed to inject DOCKER in PRERO
UTING chain: iptables failed: iptables --wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER: iptables: No chain/target/match by that name.


also. Dec 16 05:58:53 qemuarm64 dockerd[628]: time="2019-12-16T05:58:53.499510946Z" level=warning msg="Running modprobe bridge br_netfilter failed with message: modprobe: WARNING: Module br_netfilter not found
in directory /lib/modules/5.0.19-yocto-standard\n, error: exit status 1"

Any help will be much appreciated.

Thanks
Aj


Audit 2.3.2 BitBake generates rpm but unable to run it

Varun A <vashok890@...>
 

Hi all,

I have installed audit 2.3.2 rpm that I have generated using 2.3.2 BitBake file I did
 service auditd start >>>>>>>No errors

 The command does not throw any errors. But 

service auditd status
auditd is not running >>>>>>>>>>>shown as not running

But status shows as not running.Can anyone help out with this?

Regards
Varun


Re: Appending to recipe created by BBCLASSEXTEND

Quentin Schulz
 

Hi Tuomas,

On Mon, Dec 16, 2019 at 06:33:02AM +0000, Tuomas Huuki wrote:
Hello,
I'm using yocto warrior and have a recipe that is extended via BBCLASSEXTEND in to -native and -nativesdk. I also need an append for this recipe, including the "unextended" recipe. For example:
my-recipe_1.0.0.bb includes BBCLASSEXTEND = "native" and thus generates my-recipe and my-recipe-native
I also have a my-recipe_1.0.0.bbappend where I append a path to the recipe. The issue is, that it only works for the my-recipe, and not the extenend -native or -nativesdk.
Please explain what you're doing exactly, maybe even the content of your
bbappend and/or the original recipe and what you're expecting to happen,
your description is too vague.

FYI, variables and tasks can be overriden per "class" in the same
recipe.

FOO = "a"
FOO_class-target = "b"
FOO_class-native = "c"
FOO_class-nativesdk = "d"

In that case, FOO will never be `a` (except if there is another class in
BBCLASSEXTEND).

So maybe your "path" or variable is overridden for the native recipe and
you need to do the same trick for FOO_class-native.

Regards,
Quentin


Appending to recipe created by BBCLASSEXTEND

Tuomas Huuki <tuomas.huuki@...>
 

Hello,

I’m using yocto warrior and have a recipe that is extended via BBCLASSEXTEND in to –native and –nativesdk. I also need an append for this recipe, including the “unextended” recipe. For example:

my-recipe_1.0.0.bb includes BBCLASSEXTEND = “native” and thus generates my-recipe and my-recipe-native

I also have a my-recipe_1.0.0.bbappend where I append a path to the recipe. The issue is, that it only works for the my-recipe, and not the extenend –native or –nativesdk.  

I also tried creating my-recipe-native_1.0.0.bbappend, but that does not append to the extended recipe either.

 

So, is this a bug or is there a proper way of appending extended recipes?

 

Regards,

Tuomas

 




Enerpac Tool Group Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.


gstreamer bitbake introspection issue

amit kumar
 

Hi, 
I am building gstreamer 1.12 for aarch64, with poky and need immediate help. 
bitbake gobject-introspection is success and package is built successfully, still I get this error on bitbake gstreamer1.0
×***×*******×***************
ERROR: gstreamer1.0-1.12.2-r0 do_configure: Function failed: do_configure (log file /poky/build/tmp-glibc/work/aarch64-oe-linux/gstreamer1.0/1.12.2-r0/temp/log.do_configure.14926)
ERROR: Logfile of failure stored in:

/poky/build/tmp-glibc/work/aarch64-oe-linux/gstreamer1.0/1.12.2-r0/temp/log.do_configure.14926
Log data follows:
| DEBUG: SITE files ['endian-little', 'bit-64', 'arm-common', 'arm-64', 'common-linux', 'common-glibc', 'aarch64-linux', 'common']
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function autotools_aclocals
| DEBUG: SITE files ['endian-little', 'bit-64', 'arm-common', 'arm-64', 'common-linux', 'common-glibc', 'aarch64-linux', 'common']
| DEBUG: Python function autotools_aclocals finished
| DEBUG: Executing shell function delete_pkg_m4_file
| DEBUG: Shell function delete_pkg_m4_file finished
| DEBUG: Executing shell function patch_gtk_doc_makefiles
| DEBUG: Shell function patch_gtk_doc_makefiles finished
| DEBUG: Executing shell function do_configure
| cp: cannot stat '/poky/build/tmp-glibc/work/aarch64-oe-linux/gstreamer1.0/1.12.2-r0/recipe-sysroot//usr/share/aclocal/introspection.m4’: No such file or directory
| WARNING: /poky/build/tmp-glibc/work/aarch64-oe-linux/gstreamer1.0/1.12.2-r0/temp/run.do_configure.14926:1 exit 1 /poky/build/tmp-glibc/work/aarch64-oe-linux/gstreamer1.0/1.12.2-r0/recipe-sysroot//usr/share/aclocal/introspection.m4 /poky/build/tmp-glibc/work/aarch64-oe-linux/gstreamer1.0/1.12.2-r0/gstreamer-1.12.2/m4'
*************************************
Thanks, 
Amit


Re: [ Error ] python3-psycopg2-native recipe build error #yocto #python

Jussi Kukkonen
 

On Mon, 9 Dec 2019 at 07:47, <dishant.arora1996@...> wrote:
Recipe --> python3-psycopg2-native --> https://layers.openembedded.org/layerindex/recipe/72275/
Added this recipe using `IMAGE_INSTALL` variable in `sjpl-image.bb` file 

Adding a native package into a target image does not make sense. What are you trying to achieve?

 - Jussi


Got following errors while building the image :  

ERROR: Task do_populate_sdk in /home/ubuntu/build-torizon/meta-sjpl/recipes-sjpl/images/sjpl-image.bb rdepends upon non-existent task do_package_write_ipk in /home/ubuntu/layers/openembedded-core/meta-spdxscanner/recipes-devtools/python/python3-psycopg2-native_2.6.1.bb

ERROR: Command execution failed: 1

How can this error be resolved ?

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

View/Reply Online (#47596): https://lists.yoctoproject.org/g/yocto/message/47596
Mute This Topic: https://lists.yoctoproject.org/mt/67787853/3618313
Mute #yocto: https://lists.yoctoproject.org/mk?hashtag=yocto&subid=6691875
Mute #python: https://lists.yoctoproject.org/mk?hashtag=python&subid=6691875
Group Owner: yocto+owner@...
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [jku@...]
-=-=-=-=-=-=-=-=-=-=-=-


Re: QA notification for completed autobuilder build (yocto-3.1_M1.rc8)

Sangeeta Jain
 

Hello All,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.1_M1.rc8.
We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
3. BSP-Qemu

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. MPC8315e-rdb
7. Beaglebone

ETA for completion is next Wednesday, December 18.

Thanks & Regards,
Sangeeta Jain

-----Original Message-----
From: yocto@... <yocto@...> On Behalf
Of pokybuild@...
Sent: Friday, 13 December, 2019 3:15 PM
To: yocto@...
Cc: otavio@...; yi.zhao@...; Sangal, Apoorv
<apoorv.sangal@...>; Yeoh, Ee Peng <ee.peng.yeoh@...>; Chan,
Aaron Chun Yew <aaron.chun.yew.chan@...>; Ang, Chin Huat
<chin.huat.ang@...>; richard.purdie@...;
akuster808@...; sjolley.yp.pm@...; Jain, Sangeeta
<sangeeta.jain@...>
Subject: [yocto] QA notification for completed autobuilder build (yocto-
3.1_M1.rc8)


A build flagged for QA (yocto-3.1_M1.rc8) was completed on the autobuilder
and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.1_M1.rc8


Build hash information:

bitbake: 99d46107ccfcec576238d32cfe7903440857038d
meta-gplv2: a67a5fd160f97129a6afd65f107cd2cbdfec41e7
meta-intel: e1b373f3cbb9acd71efe84d782675025d59b6035
meta-mingw: 126efdad243e1a3bead5b695df6656e94353dd46
oecore: 0f04e81c797d5d337ece4e8638a6b71c75bc0a00
poky: 1abffc542a0571f0d1512b92c1a59d138cf3ea6a



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...



[RFC][yocto-autobuilder2][PATCH] config.py: Add meta-security to AB

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@...>
---
config.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/config.py b/config.py
index 14358aa..3ce5e7b 100644
--- a/config.py
+++ b/config.py
@@ -12,6 +12,7 @@ buildertorepos = {
"qa-extras": ["poky", "meta-mingw"],
"meta-oe": ["poky", "meta-openembedded"],
"meta-virt": ["poky", "meta-openembedded", "meta-virtualization"],
+ "meta-security": ["poky", "meta-openembedded", "meta-security"],
"meta-intel": ["poky", "meta-intel"],
"qemuarm-oecore": ["oecore", "bitbake"],
"checkuri": ["poky"],
@@ -83,7 +84,7 @@ trigger_builders_wait_releases = {

# Builders which are individually triggered
builders_others = [
- "meta-oe", "meta-virt", "meta-intel",
+ "meta-oe", "meta-virt", "meta-intel", "meta-security",
"bringup",
"qemuarm-armhost"
]
--
2.7.4


[RFC][yocto-autobuilder-helper][PATCH] config.json: Add mete-security option

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@...>
---
config.json | 15 +++++++++++++++
1 file changed, 15 insertions(+)

diff --git a/config.json b/config.json
index 5730f85..2a6aa9b 100644
--- a/config.json
+++ b/config.json
@@ -748,6 +748,21 @@
"DISTRO_FEATURES_append = ' virtualization'"
]
},
+ "meta-security" : {
+ "NEEDREPOS" : ["poky", "meta-openembedded", "meta-security"],
+ "MACHINE" : "qemux86-64",
+ "BBTARGETS" : "world -k",
+ "ADDLAYER" : [
+ "${BUILDDIR}/../meta-openembedded/meta-oe",
+ "${BUILDDIR}/../meta-openembedded/meta-python",
+ "${BUILDDIR}/../meta-openembedded/meta-perl",
+ "${BUILDDIR}/../meta-openembedded/meta-networking",
+ "${BUILDDIR}/../meta-security"
+ ],
+ "extravars" : [
+ "DISTRO_FEATURES_append = ' systemd'"
+ ]
+ },
"qa-extras" : {
"MACHINE" : "qemux86-64",
"step1" : {
--
2.7.4

9681 - 9700 of 57384