Re: [yocto] trouble with rootfs generation with mxnet package
On 17/10/2019 03:45, karthik poduval wrote: Upon looking at the build/tmp/work/aarch64-xilinx-linux/mxnet/1.5.0-r0/packages-split directory I find that the mxnet sub directory is empty, mxnet-dev, mxnet-staticdev have libmxnet.so and libmxnet.a respectively under usr/lib. Don't set PACKAGES, as that's the default anyway. So it *looks* like the mxnet recipe doesn't ship versioned libraries, which is very bad form for something from Apache. If this is the case then read https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries#Non-versioned_Libraries. If they do ship versioned libraries (by which I mean the library is libxmnet.so.1.2.3 or similar) then remove FILES and INSANE_SKIP, and let the packaging happen normally. You've likely got the library package renamer enabled (it's on out of the box) so the resulting package will be libmxnet1 or similar, depending on the soname of the library. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux] [Warrior] [PATCH] Revert glib-2.0: fix configure error for meson build
On Warrior branch, glib-2.0 is in version 2.58.3 so we need to revert commit
[bb0c9c3abcb] until then.
Signed-off-by: Vincent Prince
---
classes/meson-enable-selinux.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/classes/meson-enable-selinux.bbclass
b/classes/meson-enable-selinux.bbclass
index 91c2a2b..77a763a 100644
--- a/classes/meson-enable-selinux.bbclass
+++ b/classes/meson-enable-selinux.bbclass
@@ -1,4 +1,4 @@
inherit selinux
PACKAGECONFIG_append = " ${@target_selinux(d)}"
-PACKAGECONFIG[selinux] = "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
+PACKAGECONFIG[selinux] = "-Dselinux=true,-Dselinux=false,libselinux,"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Help needed add own variable to toolchain environment
Hello,
i have trouble to add a own variable to the toolchain environment
I see that environment-setup-i586-poky-linx script calls all files in
sysroot//environment-setup.d/*
But what is the simples and correct way to add follow line (export KSRC...)
do_something() {
mkdir -p ${D}${SDKPATHNATIVE}/environment-setup.d/
script=${D}${SDKPATHNATIVE}/environment-setup.d/sigmatek.sh
echo '# own environment settings' > $script
echo 'export
KSRC="${OECORE_NATIVE_SYSROOT}/lib/modules/${KERNEL_VERSION}/build"' >> $script
}
Is the best way for create a new bb file.
Thanks
Johann
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc1)
A build flagged for QA (yocto-2.6.4.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc1 Build hash information: bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575 meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964 meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5 oecore: bace400528115927ed0efa3cd941c9f9f128a555 poky: 47925dc5f93c19d44dcecacb3afb5893a851a4e4 This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.pur...@linuxfoundation.org -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] layer.conf: Add zeus to compat layer
From: Chunrong Guo Signed-off-by: Chunrong Guo --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 89b9468..30b0518 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -21,7 +21,7 @@ BBFILE_PRIORITY_selinux = "5" # cause compatibility issues with other layers LAYERVERSION_selinux = "1" -LAYERSERIES_COMPAT_selinux = "thud warrior" +LAYERSERIES_COMPAT_selinux = "thud warrior zeus" LAYERDEPENDS_selinux = " \ core \ -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH] layer.conf: Add zeus to compat layer
From: Chunrong Guo Signed-off-by: Chunrong Guo --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 89b9468..30b0518 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -21,7 +21,7 @@ BBFILE_PRIORITY_selinux = "5" # cause compatibility issues with other layers LAYERVERSION_selinux = "1" -LAYERSERIES_COMPAT_selinux = "thud warrior" +LAYERSERIES_COMPAT_selinux = "thud warrior zeus" LAYERDEPENDS_selinux = " \ core \ -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-selinux | meson-enable-selinux breaks
Hi,
I just built Yocto (warrior) with meta-selinux and got this error:
> meson.build:1:0: ERROR: Value disabled is not boolean (true or false).
It appears the file *classes/meson-enable-selinux.bbclass* has incorrect
values.
Attached a patch that fixes the problem.
Itay
[image: Argus Logo]
*Itay Sperling* *|* Software Engineer, *Argus **Cyber Security Ltd.*
itay.sperl...@argus-sec.com *|*
www.argus-sec.com *|*
From fb16c433ada55283f9259fe578a073dc5566bc77 Mon Sep 17 00:00:00 2001
From: Itay Sperling
Date: Tue, 15 Oct 2019 16:27:21 +0300
Subject: meson values 'disabled' and 'enabled' are not valid.
ERROR: Value disabled is not boolean (true or false).
---
classes/meson-enable-selinux.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/classes/meson-enable-selinux.bbclass b/classes/meson-enable-selinux.bbclass
index 91c2a2b..77a763a 100644
--- a/classes/meson-enable-selinux.bbclass
+++ b/classes/meson-enable-selinux.bbclass
@@ -1,4 +1,4 @@
inherit selinux
PACKAGECONFIG_append = " ${@target_selinux(d)}"
-PACKAGECONFIG[selinux] = "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
+PACKAGECONFIG[selinux] = "-Dselinux=true,-Dselinux=false,libselinux,"
--
2.17.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux] Warrior branch glib/meson problem
Hi Team, I have a problem with meta-selinux layer on warrior branch, especially building glib-2.0 with meson. This commit introduces enabled/disabled flags instead of true/false: http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?h=warrior&id=bb0c9c3abcb935e4b362eb57985e1ee7fec0bfe0 But current glib-2.0 is not 2.60 yet: https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/glib-2.0/?h=warrior Can we revert this patch on warrior? Best regards, Vincent -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux] [Warrior] [PATCH] Revert glib-2.0: fix configure error for meson build
On Warrior branch, glib-2.0 is in version 2.58.3 so we need to revert commit
[bb0c9c3abcb] until then.
Signed-off-by: Vincent Prince
---
classes/meson-enable-selinux.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/classes/meson-enable-selinux.bbclass
b/classes/meson-enable-selinux.bbclass
index 91c2a2b..77a763a 100644
--- a/classes/meson-enable-selinux.bbclass
+++ b/classes/meson-enable-selinux.bbclass
@@ -1,4 +1,4 @@
inherit selinux
PACKAGECONFIG_append = " ${@target_selinux(d)}"
-PACKAGECONFIG[selinux] = "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
+PACKAGECONFIG[selinux] = "-Dselinux=true,-Dselinux=false,libselinux,"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-selinux | meson-enable-selinux breaks
See patch here https://patchwork.openembedded.org/series/20519/# Le jeu. 17 oct. 2019 à 17:19, Itay Sperling a écrit : > Hi, > I just built Yocto (warrior) with meta-selinux and got this error: > >> meson.build:1:0: ERROR: Value disabled is not boolean (true or false). > > > It appears the file *classes/meson-enable-selinux.bbclass* has incorrect > values. > > Attached a patch that fixes the problem. > > Itay > > [image: Argus Logo] > *Itay Sperling* *|* Software Engineer, *Argus **Cyber Security Ltd.* > itay.sperl...@argus-sec.com *|* > www.argus-sec.com *|* > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] trouble with rootfs generation with mxnet package
Hi Ross, Thanks a lot, your analysis was spot on, I followed the recommendation from that wiki you pointed to and it fixed my issue. Really appreciate the quick response. -- Regards, Karthik Poduval On Thu, Oct 17, 2019 at 2:28 AM Ross Burton wrote: > > On 17/10/2019 03:45, karthik poduval wrote: > > Upon looking at the > > build/tmp/work/aarch64-xilinx-linux/mxnet/1.5.0-r0/packages-split > > directory > > I find that the mxnet sub directory is empty, mxnet-dev, > > mxnet-staticdev have libmxnet.so and libmxnet.a respectively under > > usr/lib. > > Don't set PACKAGES, as that's the default anyway. > > So it *looks* like the mxnet recipe doesn't ship versioned libraries, > which is very bad form for something from Apache. If this is the case > then read > https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries#Non-versioned_Libraries. > > If they do ship versioned libraries (by which I mean the library is > libxmnet.so.1.2.3 or similar) then remove FILES and INSANE_SKIP, and let > the packaging happen normally. > > You've likely got the library package renamer enabled (it's on out of > the box) so the resulting package will be libmxnet1 or similar, > depending on the soname of the library. > > Ross > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Regards, Karthik Poduval -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] qmlimportscanner missing from sdk
When I build an sdk using do_populate_sdk with a static built meta-qt5, I do not end up with athe qmlimportscanner in my sdk in the usr/bin folder. What am I missing? Qmake is correctly built. Thanks for any help -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] apparmor: ptest fail to build on arm
exclude arm and aarch64 ptest tasks
Signed-off-by: Armin Kuster
---
recipes-mac/AppArmor/apparmor_2.13.3.bb | 22 ++
1 file changed, 22 insertions(+)
diff --git a/recipes-mac/AppArmor/apparmor_2.13.3.bb
b/recipes-mac/AppArmor/apparmor_2.13.3.bb
index d434fd3..ba7065b 100644
--- a/recipes-mac/AppArmor/apparmor_2.13.3.bb
+++ b/recipes-mac/AppArmor/apparmor_2.13.3.bb
@@ -42,6 +42,8 @@ PACKAGECONFIG[aa-decode] = ",,,bash"
PAMLIB="${@bb.utils.contains('DISTRO_FEATURES', 'pam', '1', '0', d)}"
HTTPD="${@bb.utils.contains('PACKAGECONFIG', 'apache2', '1', '0', d)}"
+#Building ptest on arm fails.
+
python() {
if 'apache2' in d.getVar('PACKAGECONFIG').split() and \
'webserver' not in d.getVar('BBFILE_COLLECTIONS').split():
@@ -50,6 +52,10 @@ python() {
DISABLE_STATIC = ""
+do_configure_ptest_base_aarch64[noexec] = "1"
+do_compile_ptest_base_aarch64[noexec] = "1"
+do_install_ptest_base_aarch64[noexec] = "1"
+
do_configure() {
cd ${S}/libraries/libapparmor
aclocal
@@ -123,6 +129,14 @@ do_install () {
fi
}
+do_compile_ptest_aarch64 () {
+ :
+}
+
+do_compile_ptest_arm () {
+ :
+}
+
do_compile_ptest () {
oe_runmake -C ${B}/tests/regression/apparmor
oe_runmake -C ${B}/parser/tst
@@ -150,6 +164,14 @@ do_install_ptest () {
cp -rf ${B}/binutils ${t}
}
+do_install_ptest_aarch64 () {
+ :
+}
+
+do_install_ptest_arm() {
+ :
+}
+
pkg_postinst_ontarget_${PN} () {
if [ ! -d /etc/apparmor.d/cache ] ; then
mkdir /etc/apparmor.d/cache
--
2.17.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][v2][PATCH] apparmor: ptest fail to build on arm
exclude arm and aarch64 ptest tasks
Signed-off-by: Armin Kuster
---
recipes-mac/AppArmor/apparmor_2.13.3.bb | 22 ++
1 file changed, 22 insertions(+)
diff --git a/recipes-mac/AppArmor/apparmor_2.13.3.bb
b/recipes-mac/AppArmor/apparmor_2.13.3.bb
index d434fd3..ba7065b 100644
--- a/recipes-mac/AppArmor/apparmor_2.13.3.bb
+++ b/recipes-mac/AppArmor/apparmor_2.13.3.bb
@@ -42,6 +42,8 @@ PACKAGECONFIG[aa-decode] = ",,,bash"
PAMLIB="${@bb.utils.contains('DISTRO_FEATURES', 'pam', '1', '0', d)}"
HTTPD="${@bb.utils.contains('PACKAGECONFIG', 'apache2', '1', '0', d)}"
+#Building ptest on arm fails.
+
python() {
if 'apache2' in d.getVar('PACKAGECONFIG').split() and \
'webserver' not in d.getVar('BBFILE_COLLECTIONS').split():
@@ -50,6 +52,10 @@ python() {
DISABLE_STATIC = ""
+do_configure_ptest_base_aarch64[noexec] = "1"
+do_compile_ptest_base_aarch64[noexec] = "1"
+do_install_ptest_base_aarch64[noexec] = "1"
+
do_configure() {
cd ${S}/libraries/libapparmor
aclocal
@@ -123,6 +129,14 @@ do_install () {
fi
}
+do_compile_ptest_aarch64 () {
+ :
+}
+
+do_compile_ptest_arm () {
+ :
+}
+
do_compile_ptest () {
oe_runmake -C ${B}/tests/regression/apparmor
oe_runmake -C ${B}/parser/tst
@@ -150,6 +164,14 @@ do_install_ptest () {
cp -rf ${B}/binutils ${t}
}
+do_install_ptest_aarch64 () {
+ :
+}
+
+do_install_ptest_arm() {
+ :
+}
+
pkg_postinst_ontarget_${PN} () {
if [ ! -d /etc/apparmor.d/cache ] ; then
mkdir /etc/apparmor.d/cache
--
2.17.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][v3][PATCH] apparmor: ptest fail to build on arm
exclude arm and aarch64 ptest tasks
[v2&3]
Sent before committing.
Signed-off-by: Armin Kuster
---
recipes-mac/AppArmor/apparmor_2.13.3.bb | 18 ++
1 file changed, 18 insertions(+)
diff --git a/recipes-mac/AppArmor/apparmor_2.13.3.bb
b/recipes-mac/AppArmor/apparmor_2.13.3.bb
index d434fd3..60d5e68 100644
--- a/recipes-mac/AppArmor/apparmor_2.13.3.bb
+++ b/recipes-mac/AppArmor/apparmor_2.13.3.bb
@@ -123,6 +123,15 @@ do_install () {
fi
}
+#Building ptest on arm fails.
+do_compile_ptest_aarch64 () {
+ :
+}
+
+do_compile_ptest_arm () {
+ :
+}
+
do_compile_ptest () {
oe_runmake -C ${B}/tests/regression/apparmor
oe_runmake -C ${B}/parser/tst
@@ -150,6 +159,15 @@ do_install_ptest () {
cp -rf ${B}/binutils ${t}
}
+#Building ptest on arm fails.
+do_install_ptest_aarch64 () {
+ :
+}
+
+do_install_ptest_arm() {
+ :
+}
+
pkg_postinst_ontarget_${PN} () {
if [ ! -d /etc/apparmor.d/cache ] ; then
mkdir /etc/apparmor.d/cache
--
2.17.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)
A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2 Build hash information: bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575 meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964 meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5 oecore: cd7cf933b3235560ec71576d8f3836dff736a39f poky: 51f6145f8f99a02df1dad937684f014b0172e72a This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.pur...@linuxfoundation.org -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)
Can we get 2.6.4-rc2 in a QA queue for the next dot release? - armin On 10/17/19 2:17 PM, Poky Build User wrote: > A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and > is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2 > > > Build hash information: > > bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb > meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575 > meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964 > meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5 > oecore: cd7cf933b3235560ec71576d8f3836dff736a39f > poky: 51f6145f8f99a02df1dad937684f014b0172e72a > > > > This is an automated message from the Yocto Project Autobuilder > Git: git://git.yoctoproject.org/yocto-autobuilder2 > Email: richard.pur...@linuxfoundation.org > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)
>-Original Message- >From: yocto-boun...@yoctoproject.org On >Behalf Of akuster >Sent: Friday, 18 October, 2019 6:53 AM >To: yocto@yoctoproject.org >Cc: akuster...@gmail.com; Chan, Aaron Chun Yew >; ota...@ossystems.com.br >Subject: Re: [yocto] QA notification for completed autobuilder build (yocto- >2.6.4.rc2) > >Can we get 2.6.4-rc2 in a QA queue for the next dot release? Do you mean that we should wait for 2.7.2 before starting QA for 2.6.4-rc2? > >- armin > Thanks & Regards, Sangeeta Jain >On 10/17/19 2:17 PM, Poky Build User wrote: >> A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and >is available at: >> >> >> https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2 >> >> >> Build hash information: >> >> bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb >> meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575 >> meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964 >> meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5 >> oecore: cd7cf933b3235560ec71576d8f3836dff736a39f >> poky: 51f6145f8f99a02df1dad937684f014b0172e72a >> >> >> >> This is an automated message from the Yocto Project Autobuilder >> Git: git://git.yoctoproject.org/yocto-autobuilder2 >> Email: richard.pur...@linuxfoundation.org >> >> >> > >-- >___ >yocto mailing list >yocto@yoctoproject.org >https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)
On 10/17/19 7:01 PM, Jain, Sangeeta wrote: > > >> -Original Message- >> From: yocto-boun...@yoctoproject.org On >> Behalf Of akuster >> Sent: Friday, 18 October, 2019 6:53 AM >> To: yocto@yoctoproject.org >> Cc: akuster...@gmail.com; Chan, Aaron Chun Yew >> ; ota...@ossystems.com.br >> Subject: Re: [yocto] QA notification for completed autobuilder build (yocto- >> 2.6.4.rc2) >> >> Can we get 2.6.4-rc2 in a QA queue for the next dot release? > Do you mean that we should wait for 2.7.2 before starting QA for 2.6.4-rc2? Not to wait for 2.7.2, there is an outstanding issue needing resolution. 2.6.4 is a ready to go. regards, Armin >> - armin >> > Thanks & Regards, > Sangeeta Jain > >> On 10/17/19 2:17 PM, Poky Build User wrote: >>> A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder >>> and >> is available at: >>> >>> https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2 >>> >>> >>> Build hash information: >>> >>> bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb >>> meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575 >>> meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964 >>> meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5 >>> oecore: cd7cf933b3235560ec71576d8f3836dff736a39f >>> poky: 51f6145f8f99a02df1dad937684f014b0172e72a >>> >>> >>> >>> This is an automated message from the Yocto Project Autobuilder >>> Git: git://git.yoctoproject.org/yocto-autobuilder2 >>> Email: richard.pur...@linuxfoundation.org >>> >>> >>> >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)
Hello All, Intel and WR YP QA is planning for QA execution for YP build yocto-2.6.4.rc2. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw 3. BSP-Qemu Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. MPC8315e-rdb 7. Beaglebone ETA for completion is next Wednesday, October 23. Thanks & Regards, Sangeeta Jain >-Original Message- >From: Yeoh, Ee Peng >Sent: Friday, 18 October, 2019 9:05 AM >To: Jain, Sangeeta >Subject: FW: QA notification for completed autobuilder build (yocto-2.6.4.rc2) > >FYI > >-Original Message- >From: Poky Build User >Sent: Friday, October 18, 2019 5:18 AM >To: yocto@yoctoproject.org >Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv >; Yeoh, Ee Peng ; Chan, >Aaron Chun Yew ; Ang, Chin Huat >; richard.pur...@linuxfoundation.org; >akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta > >Subject: QA notification for completed autobuilder build (yocto-2.6.4.rc2) > > >A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and >is >available at: > > >https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2 > > >Build hash information: > >bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb >meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575 >meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964 >meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5 >oecore: cd7cf933b3235560ec71576d8f3836dff736a39f >poky: 51f6145f8f99a02df1dad937684f014b0172e72a > > > >This is an automated message from the Yocto Project Autobuilder >Git: git://git.yoctoproject.org/yocto-autobuilder2 >Email: richard.pur...@linuxfoundation.org > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
