Re: [linux-yocto] [PATCH 1/1] aufs5:fix:avoid to access rw_sem.owner in RT kernel

2021-03-29 Thread Yongxin Liu
Hi Bruce,

Please review whether this patch should also be applied to 
v5.10/standard/preempt-rt.

Thanks,
Yongxin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9621): 
https://lists.yoctoproject.org/g/linux-yocto/message/9621
Mute This Topic: https://lists.yoctoproject.org/mt/71883581/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Can't build gatesgarth after PSEUDO_IGNORE_PATHS change in poky

2021-03-29 Thread Ramsay, Lincoln via lists.yoctoproject.org
Hi,

Just to follow up on this, I eventually figured out the root cause, but I still 
don't understand why PSEUDO_IGNORE_PATHS was allowing it to work...

When I setup my PC, I created the user and then changed the UID of the user 
(for NFS auth reasons). The end result of this is that my user has UID  but 
GID 1000.

I do all of my building in Docker and a user is created that (in theory) 
matches my real user so that ownership for bind-mounted locations “just works”. 
However, the in-Docker user has UID  but GID .

When bb.utils.copyfile tries to copy files, it is copying from a source 
directory that is /1000 into a target directory that would be /. I 
still don’t quite know how, but that seems to be behind the chmod failing.

The chmod failing is (as already noted) why the +x is lost on the 
postinstall_intercept script, which is why I got failing builds instead of just 
the chmod warnings.

I have fixed this by updating my Docker creation scripts (to ensure the 
in-Docker user has GID 1000) and to find and update all the files with GID  
to have GID 1000 instead.

find . -gid  -print0 | xargs -0 chgrp -h 1000

I can once again build without patching poky :)

Lincoln

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52961): https://lists.yoctoproject.org/g/yocto/message/52961
Mute This Topic: https://lists.yoctoproject.org/mt/81590884/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] eula-downloads.yoctoproject.org down???

2021-03-29 Thread anthony.l via lists.yoctoproject.org
Getting a message today
Fetcher failure for URL: 'https://eula-downloads.yoctoproject.org/index.php'. 
URL https://eula-downloads.yoctoproject.org/index.php doesn't work. Please 
ensure your network is configured correctly.

Can't ping the url?  Anyone have an ETA on this being back up?  Just trying to 
get some urgent builds done today.

Many thanks.
Anthony

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52960): https://lists.yoctoproject.org/g/yocto/message/52960
Mute This Topic: https://lists.yoctoproject.org/mt/81714256/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 WW13

2021-03-29 Thread Stephen Jolley
All,

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


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  10693

Add a testcase for multilib eSDK on the autobuilder

randy.macl...@windriver.com

qi.c...@windriver.com

3.3

3.4 M1


 

  13025

WIC image install support

randy.macl...@windriver.com

kexin@windriver.com

3.3

3.4 M1


 

  13980

Investigate replacements for PhantomJS for buildperf output

randy.macl...@windriver.com

trevor.gamb...@windriver.com

3.3

3.3 M1


 

 

 

 

3.3 M1

3.4 M1


 

  14099

PACKAGE_EXCLUDE not removing packages when PACKAGE_CLASSES = "package_deb"

randy.macl...@windriver.com

stacygaikov...@gmail.com

3.3 M3

3.3 M4

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 (#52959): https://lists.yoctoproject.org/g/yocto/message/52959
Mute This Topic: https://lists.yoctoproject.org/mt/81709618/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] 3Enhancements/Bugs closed WW13!

2021-03-29 Thread Stephen Jolley
All,

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


Who

Count


randy.macl...@windriver.com

5


richard.pur...@linuxfoundation.org

2


r...@burtonini.com

2


yifan...@windriver.com

2


raj.k...@gmail.com

1


kexin@windriver.com

1


dorindabas...@gmail.com

1


nicolas.deche...@linaro.org

1


sjolley.yp...@gmail.com

1


kai.k...@windriver.com

1


Grand Total

17

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 (#52958): https://lists.yoctoproject.org/g/yocto/message/52958
Mute This Topic: https://lists.yoctoproject.org/mt/81709602/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.3

2021-03-29 Thread Stephen Jolley
All,

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


Who

Count


r...@burtonini.com

17


bluelightn...@bluelightning.org

14


richard.pur...@linuxfoundation.org

9


mark.mor...@windriver.com

7


jpewhac...@gmail.com

7


akuster...@gmail.com

5


raj.k...@gmail.com

4


chee.yang@intel.com

4


idad...@gmail.com

3


qi.c...@windriver.com

3


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

3


trevor.gamb...@windriver.com

3


mostthings...@gmail.com

3


matthew...@posteo.net

2


limon.ani...@gmail.com

2


randy.macl...@windriver.com

2


ydir...@free.fr

2


jeanmarie.lemeta...@gmail.com

2


sakib.sa...@windriver.com

2


nicolas.deche...@linaro.org

2


alejan...@enedino.org

2


jae...@xilinx.com

2


yoctoproj...@cookiesoft.de

1


mhalst...@linuxfoundation.org

1


bruce.ashfi...@gmail.com

1


twoer...@gmail.com

1


mister...@web.de

1


pokyli...@reliableembeddedsystems.com

1


open.sou...@oleksandr-kravchuk.com

1


devendra.tew...@gmail.com

1


dorindabas...@gmail.com

1


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

1


stacygaikov...@gmail.com

1


hongxu@windriver.com

1


yifan...@windriver.com

1


matt.ranos...@konsulko.com

1


john.kaldas.e...@gmail.com

1


aeh...@gmail.com

1


kerg...@gmail.com

1


ms...@mvista.com

1


Grand Total

118

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 (#52957): https://lists.yoctoproject.org/g/yocto/message/52957
Mute This Topic: https://lists.yoctoproject.org/mt/81709515/21656
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

2021-03-29 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  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

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 362
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.2", "3.3, "3.99" and "Future", the more pressing/urgent issues
being in "3.2" and then "3.3".

 

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 (#52956): https://lists.yoctoproject.org/g/yocto/message/52956
Mute This Topic: https://lists.yoctoproject.org/mt/81709470/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto-announce] [ANNOUNCEMENT]Milestone 3 for Yocto Project 3.3 (yocto-3.3_M3) now available

2021-03-29 Thread Vineela
Hello,

We are pleased to announce the third milestone release for Yocto Project 3.3 
(yocto-3.3_M3) is now available for download.

Download:

http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.3_M3

bitbake: ed8e1fd4cf9d5ac8a8203638add99d686b4b3521
meta-arm: ac1dc0b894642101a80235a920bdc3bbe6d74558
meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
meta-intel: 6fea44c695730129df8bd744b0e22ccd62a725c2
meta-kernel: 29329d7cacc71595cecfdd05a455a0cfb164564d
meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
oecore: 7ae12e4278e98c5b916a1067ae0b48c2da6e82cd
poky: ea455ca8671d3bc2a1097989bfaabe92f3ca37ab

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.3_M3/testreport.txt

Thank you.

Vineela Tummalapalli,
Yocto Project Build and Release
vineela.tummalapa...@intel.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#213): 
https://lists.yoctoproject.org/g/yocto-announce/message/213
Mute This Topic: https://lists.yoctoproject.org/mt/81708914/21656
Group Owner: yocto-announce+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto-announce/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [ANNOUNCEMENT]Milestone 3 for Yocto Project 3.3 (yocto-3.3_M3) now available

2021-03-29 Thread Vineela
Hello,

We are pleased to announce the third milestone release for Yocto Project 3.3 
(yocto-3.3_M3) is now available for download.

Download:

http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.3_M3

bitbake: ed8e1fd4cf9d5ac8a8203638add99d686b4b3521
meta-arm: ac1dc0b894642101a80235a920bdc3bbe6d74558
meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
meta-intel: 6fea44c695730129df8bd744b0e22ccd62a725c2
meta-kernel: 29329d7cacc71595cecfdd05a455a0cfb164564d
meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
oecore: 7ae12e4278e98c5b916a1067ae0b48c2da6e82cd
poky: ea455ca8671d3bc2a1097989bfaabe92f3ca37ab

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.3_M3/testreport.txt

Thank you.

Vineela Tummalapalli,
Yocto Project Build and Release
vineela.tummalapa...@intel.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52955): https://lists.yoctoproject.org/g/yocto/message/52955
Mute This Topic: https://lists.yoctoproject.org/mt/81708765/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Naming images

2021-03-29 Thread Quentin Schulz
Hi Damien,

On Mon, Mar 29, 2021 at 03:33:09PM +0300, Damien LEFEVRE wrote:
> Hi,
> 
> In my build system the generated images are in this format:
> 
> imagename-machine-timestamp.img
> 
> For release builds, I'd like to replace the time stamp with the image
> version. I could rename the image after the build but is there a better way?
> 

IMAGE_NAME variable is the one specifying the name which should be used
for the final image. c.f. 
https://docs.yoctoproject.org/ref-manual/variables.html#term-IMAGE_NAME

By default, its value is "${IMAGE_BASENAME}-${MACHINE}${IMAGE_VERSION_SUFFIX}"

IMAGE_VERSION_SUFFIX is by default set to "-${DATETIME}" as documented
here: 
https://docs.yoctoproject.org/ref-manual/variables.html#term-IMAGE_VERSION_SUFFIX

Therefore to put the image version, you just need to change
IMAGE_VERSION_SUFFIX to what you want it to contain.

Cheers,
Quentin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52954): https://lists.yoctoproject.org/g/yocto/message/52954
Mute This Topic: https://lists.yoctoproject.org/mt/81694699/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Package indexes for package feeds, ipk and rpm

2021-03-29 Thread Ross Burton
That's just how RPM and opkg work, Yocto can't control or alter that.

Ross

On Mon, 29 Mar 2021 at 10:36, keydi  wrote:
>
> Regarding package feed packages index I learned one difference between rpm 
> and ipk.
> For ipk plain-text files named Packages are generated and placed to 
> architecture-subdirectories in tmp/deploy/ipk tree.
> For rpm I see just one file named Packages, it is a binary file yet located 
> in one image arch-subdir within tmp/deploy/rpm tree.
>
> Is this difference the result how Poky/OE handles both
> or rather coming already from package management systems?
>
> I wonder also how could the chances be to have Packages files in RPM in same 
> form
> as for IPK - plain-text yet provided for each architecture build artifacts 
> sub-tree?
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52953): https://lists.yoctoproject.org/g/yocto/message/52953
Mute This Topic: https://lists.yoctoproject.org/mt/81692219/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Naming images

2021-03-29 Thread Damien LEFEVRE
Hi,

In my build system the generated images are in this format:

imagename-machine-timestamp.img

For release builds, I'd like to replace the time stamp with the image
version. I could rename the image after the build but is there a better way?

I found a BUILDNAME variable but it has no effect.

Also should the timestamp written in /etc/version match the one from the
image name?

For some reason for me it doesn't. /etc/version is 20180309123456 while the
one from the image name is 20210329064542.

-Damien

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52952): https://lists.yoctoproject.org/g/yocto/message/52952
Mute This Topic: https://lists.yoctoproject.org/mt/81694699/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [meta-zephyr][PATCH 1/1] zephyr-kernel-src.inc: Support samples from external layers

2021-03-29 Thread Andrei Gherzan
From: Andrei Gherzan 

The inc file references patch(es) local to the inc file. Including this
file from another recipe as part of an external layer, will make bitbake
fail finding the files referenced in zephyr-kernel-src.inc's SRC_URI.

By including an explicit path to the files directory in FILESEXTRAPATHS,
we make sure that any recipe including this inc file will inherit the
needed path.

Signed-off-by: Andrei Gherzan 
---
 recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 5 +
 1 file changed, 5 insertions(+)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
index 39cbc10..8c987bb 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -7,6 +7,11 @@ include 
zephyr-kernel-src-${PREFERRED_VERSION_zephyr-kernel}.inc
 
 inherit cmake
 
+# This file might be included from other places (like other layers) and not
+# having an explicit path to the patches directory, will make bitbake fail to
+# find the patch(es) in SRC_URI.
+FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
+
 SRC_URI = "\
 
git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=master;name=default
 \
 
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis
 \
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52951): https://lists.yoctoproject.org/g/yocto/message/52951
Mute This Topic: https://lists.yoctoproject.org/mt/81694508/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Package indexes for package feeds, ipk and rpm

2021-03-29 Thread keydi
Regarding package feed packages index I learned one difference between rpm and 
ipk.
For ipk plain-text files named Packages are generated and placed to 
architecture-subdirectories in tmp/deploy/ipk tree.
For rpm I see just one file named Packages, it is a binary file yet located in 
one image arch-subdir within tmp/deploy/rpm tree.

Is this difference the result how Poky/OE handles both
or rather coming already from package management systems?

I wonder also how could the chances be to have Packages files in RPM in same 
form
as for IPK - plain-text yet provided for each architecture build artifacts 
sub-tree?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52950): https://lists.yoctoproject.org/g/yocto/message/52950
Mute This Topic: https://lists.yoctoproject.org/mt/81692219/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] To burn 'bitbake package-index' into build process

2021-03-29 Thread keydi
Thanks for hint.
Which qualities might current implementation output still miss?

I tried to ask in meantime three Yocto books for help 
but no clear help got. My search went toward distribution-level meta-data,
this can be however wrong direction as package index is not built for
target system distribution/image.

I get the impression as of time being the only solution
will be to start one small script additionally to main script
to respawn Bitbake environment once again to do bitbake package-index.

Regards
k.d.



> -Original Message-
> From: Ross Burton [mailto:r...@burtonini.com]
> Sent: Samstag, 27. März 2021 22:20
> To: DUDZIAK Krzysztof 
> Cc: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] To burn 'bitbake package-index' into build process
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/index
> is close to what you want, but I didn't quite finish it off!
> 
> Ross
> 
> On Fri, 26 Mar 2021 at 16:45, keydi 
> wrote:
> >
> > Should it be feasible to burn execution of 'bitbake package-index'
> > into distribution/image build process by conducting an adaption of meta-
> data ?
> > I mean high-level script is used to spawn Bitbake environment then start
> Bitbake image target.
> > I am unhappy to mess up high-level script to add that step to build process.
> > I am unhappy to make detail that level be visible in high-level script.
> > Rather I prefer to modify meta-data.
> >
> > 
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52949): https://lists.yoctoproject.org/g/yocto/message/52949
Mute This Topic: https://lists.yoctoproject.org/mt/81661767/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



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

2021-03-29 Thread Sangeeta Jain
Hi all,

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

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

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

ETA for completion is next Thursday, April 01

Thanks,
Sangeeta

> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Monday, 29 March, 2021 11:49 AM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder 
> build
> (yocto-3.2.3.rc1)
> 
> 
> A build flagged for QA (yocto-3.2.3.rc1) was completed on the autobuilder and 
> is
> available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-3.2.3.rc1
> 
> 
> Build hash information:
> 
> bitbake: 5d02c98489d3a5836676b9c3fb3bd0157449db2b
> meta-arm: e219ef606e297b98512887c96522d8d8c536bd6b
> meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
> meta-intel: 76e0a427e58d068d0758fa052d2d1548067cf592
> meta-kernel: 29329d7cacc71595cecfdd05a455a0cfb164564d
> meta-mingw: 352d8b0aa3c7bbd5060a4cc2ebe7c0e964de4879
> oecore: fdae970656cc421c542af9856bc9ae038c61db13
> poky: 08665a81dcd41069eed1468f1587abe6b5893471
> 
> 
> 
> 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 (#52948): https://lists.yoctoproject.org/g/yocto/message/52948
Mute This Topic: https://lists.yoctoproject.org/mt/81691219/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-