Re: [yocto] [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

[Alexander Kanavin]

On Thu, 28 Sept 2023 at 18:49, Richard Purdie
 wrote:

> I'm curious to see what you find with analysis of bitbake-whatchanged.

I've taken a look a the script. It obtains the current location of
STAMPS_DIR, then runs this:

# Generate the new stamps dir
print("Generating the new stamps ... (need several minutes)")
cmdline = "STAMPS_DIR=%s bitbake -S none %s" % (new_stampsdir,
args.recipe)

Then it walks both trees, matching up file names with a regex:

# Match the stamp's filename
# group(1): PE_PV (may no PE)
# group(2): PR
# group(3): TASK
# group(4): HASH
stamp_re = 
re.compile("(?P.*)-(?Pr\d+)\.(?Pdo_\w+)\.(?P[^\.]*)")

Then there's some code that finds out what changed in the above
between the two sets.

I don't see a way to make it work: messing about with STAMPS_DIR like
that isn't supported, and will either do nothing, or remove the
original stamps. Also stamp filenames aren't really a 'public API',
are they?

Should the script simply be removed, or is there some better way to
re-implement answering the 'what has changed' question in a way that
doesn't flood the console with task hashes? I'd be glad to get
suggestions for this.


Alex

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

Re: [yocto] [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

[Richard Purdie]

On Fri, 2023-09-29 at 14:06 +0200, Alexander Kanavin wrote:
> On Thu, 28 Sept 2023 at 18:49, Richard Purdie
>  wrote:
> 
> > I'm curious to see what you find with analysis of bitbake-whatchanged.
> 
> I've taken a look a the script. It obtains the current location of
> STAMPS_DIR, then runs this:
> 
> # Generate the new stamps dir
> print("Generating the new stamps ... (need several minutes)")
> cmdline = "STAMPS_DIR=%s bitbake -S none %s" % (new_stampsdir,
> args.recipe)
> 
> Then it walks both trees, matching up file names with a regex:
> 
> # Match the stamp's filename
> # group(1): PE_PV (may no PE)
> # group(2): PR
> # group(3): TASK
> # group(4): HASH
> stamp_re = 
> re.compile("(?P.*)-(?Pr\d+)\.(?Pdo_\w+)\.(?P[^\.]*)")
> 
> Then there's some code that finds out what changed in the above
> between the two sets.
> 
> I don't see a way to make it work: messing about with STAMPS_DIR like
> that isn't supported, and will either do nothing, or remove the
> original stamps. Also stamp filenames aren't really a 'public API',
> are they?
> 
> Should the script simply be removed, or is there some better way to
> re-implement answering the 'what has changed' question in a way that
> doesn't flood the console with task hashes? I'd be glad to get
> suggestions for this.

I'd prefer to see some dedicated bitbake API used even if we need to
create/add it. tinfoil and some of the bblock/unlock work shows we can
get stamp data, the question would be how to get it without
"disturbing" the existing build.

By using dedicated API, we'd be able to control the console output.

Cheers,

Richard



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

Re: [yocto] [meta-rockchip][PATCH v4 0/2] rock-5b: add

[Trevor Woerner]

On Tue 2023-09-26 @ 10:42:18 PM, Trevor Woerner wrote:
> Version 4 of the patch to add Radxa's Rock 5B.
> 
> v4:
> - add a patch before the "rock 5b: add" patch to rename the U-Boot
>   variables to not be TF-A specific
> - clean up the U-Boot initial binary blob dependency variable name, the
>   EXTRA_OEMAKE handling, and remove the rk3588's dependency on tf-a (which
>   it does not have)
> 
> v3:
> - change name from "rock5b" to "rock-5b", there seem to be more instances
>   of the latter on the manufacturer's website than the former
> - fix the MACHINEOVERRIDE in conf/machine/include/rk3588s.inc to be
>   "rk3588s" and not "rk3588"
> 
> v2:
> - fix the logic behind the MACHINEOVERRIDES to get the content, and
>   ordering, correct
> - improved the commit message around TF-A/rkbin
> - correct Quentin's SoB line
> 
> Trevor Woerner (2):
>   u-boot: rename firmware dependency
>   rock-5b: add
> 
>  README|  1 +
>  conf/machine/include/rk3588.inc   |  6 ++
>  conf/machine/include/rk3588s.inc  | 17 
>  conf/machine/rock-5b.conf | 12 +++
>  recipes-bsp/rkbin/rockchip-rkbin_git.bb   | 37 
>  recipes-bsp/u-boot/u-boot%.bbappend   | 17 ++--
>  recipes-kernel/linux/linux-yocto-dev.bbappend |  3 +
>  .../rockchip/remove-non-rockchip-arch-arm.cfg | 85 +++
>  .../rockchip/remove-non-rockchip-arch-arm.scc |  1 +
>  .../remove-non-rockchip-arch-arm64.cfg| 66 ++
>  .../remove-non-rockchip-arch-arm64.scc|  1 +
>  11 files changed, 240 insertions(+), 6 deletions(-)
>  create mode 100644 conf/machine/include/rk3588.inc
>  create mode 100644 conf/machine/include/rk3588s.inc
>  create mode 100644 conf/machine/rock-5b.conf
>  create mode 100644 recipes-bsp/rkbin/rockchip-rkbin_git.bb
>  create mode 100644 recipes-kernel/linux/linux-yocto-dev.bbappend
>  create mode 100644 
> recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm.cfg
>  create mode 100644 
> recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm.scc
>  create mode 100644 
> recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm64.cfg
>  create mode 100644 
> recipes-kernel/linux/linux-yocto-dev/rockchip-kmeta/bsp/rockchip/remove-non-rockchip-arch-arm64.scc

Applied to meta-rockchip, master branch.

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

Re: [yocto] [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

[Alexander Kanavin]

On Fri, 29 Sept 2023 at 14:27, Richard Purdie
 wrote:

> I'd prefer to see some dedicated bitbake API used even if we need to
> create/add it. tinfoil and some of the bblock/unlock work shows we can
> get stamp data, the question would be how to get it without
> "disturbing" the existing build.
>
> By using dedicated API, we'd be able to control the console output.

I just noticed that compare_sigfiles() has a 'collapsed' argument,
which, when set to True, omits most or all of the task hash printing,
and with that its output should approximate what bitbake-whatchanged
is aiming to do. This is currently used only by buildhistory, but it
could be used by -S printdiff too, e.g. by having verbose and concise
modes.

I'll run some experiments, and let's see what the overall output looks
like in real scenarios (e.g. 4.3_M3 vs current master).

Alex

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

[yocto] How to use updated npm version in my image

[MOHAMMED HASSAN]

Hi guys,
I am using yocto dunfell for my image. I am able to install nodejs 14 and
npm version 6.something.
I want it to instead install 9.8.1 with my image. At present I have to
manually install it after loading the image. Is there a way to update it in
the recipe file? My recipe file name is nodejs_12.22.12.bb.


Thanks and regards,
Hassan

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

[yocto] Yocto Project Summit CFP closes Monday, October 2nd

[Josef Holzmayr]

The countdown is ticking! At the moment the CFP for the Yocto Project
Summit 2023.11 is still open, but will close on Monday, October 2nd, 2023.
So made sure to submit this weekend!

https://summit.yoctoproject.org/yocto-project-summit-2023-11/cfp

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

[yocto] [layerindex-web] layerindex/urls.py: fix submit/thanks/ url

[Tim Orling]

The url returned by the reverse lookup ends in /submit/thanks/ but
the regex was improperly searching for a string without the terminating "/".

Thank you to Pawel Zalewski for reporting the 404 error.

Signed-off-by: Tim Orling 
---
 layerindex/urls.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/layerindex/urls.py b/layerindex/urls.py
index de15bb0..82af699 100644
--- a/layerindex/urls.py
+++ b/layerindex/urls.py
@@ -59,7 +59,7 @@ urlpatterns = [
 url(r'^classes/$',
 RedirectView.as_view(url=reverse_lazy('class_search', 
args=('master',)), permanent=False)),
 url(r'^submit/$', edit_layer_view, {'template_name': 
'layerindex/submitlayer.html'}, name="submit_layer"),
-url(r'^submit/thanks$',
+url(r'^submit/thanks/$',
 TemplateView.as_view(
 template_name='layerindex/submitthanks.html'),
 name="submit_layer_thanks"),
-- 
2.34.1


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

[yocto] [layerindex-web] build(deps): bump gitpython from 3.1.32 to 3.1.37

[Tim Orling]

This release contains another security fix that further improves validation
of symbolic references and thus properly fixes this CVE:
https://github.com/advisories/GHSA-cwvm-v4w8-q58c (CVE-2023-41040).

https://github.com/gitpython-developers/GitPython/blob/main/doc/source/changes.rst

Signed-off-by: Tim Orling 
---
 requirements.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/requirements.txt b/requirements.txt
index b86ac6e..5bc4659 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -16,7 +16,7 @@ django-reversion-compare==0.14.1
 django-simple-captcha==0.5.14
 djangorestframework==3.13.1
 gitdb==4.0.9
-GitPython==3.1.32
+GitPython==3.1.37
 kombu==5.2.3
 mysqlclient==2.1.0
 Pillow==9.3.0
-- 
2.34.1


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

Re: [yocto] SPDX generation fails every second time the image is created

[David Daniel]

Thank you for your replies and sorry for the long delay. I cannot reproduce the 
issue now. If I come over it again I will use the linked patch and check if I 
can see the root cause.

Thank you.

Von: Joshua Watt 
Gesendet: Donnerstag, 28. September 2023 20:36
An: David Daniel 
Cc: yocto@lists.yoctoproject.org 
Betreff: Re: [yocto] SPDX generation fails every second time the image is 
created

David,

I just pushed a patch to the ML to provide better debugging when this
happens; it will at least tell us which document is missing. Is there
any way you can run you build again with that patch applied?

https://lists.openembedded.org/g/openembedded-core/message/188378

Thanks,

On Thu, Sep 28, 2023 at 8:20 AM David Daniel  wrote:
>
> Hello
>
> Something changed in master the last days that makes the image creation
> fail. When I create the image with bitbake, every second time the image
> creation fails with:
>
>Exception: AttributeError: 'NoneType' object has no attribute 'open'
>
> Funnily this only happens every 2nd time - afterwards I cannot build
> the image anymore. Up to now I "solve" this by deleting the entire
> build folder and start over again.
> I attached the log of the build that shows the error - I don't
> understand where this comes from.
>
> Any idea what's causing this?
>
> Have a great day,
> BR
> David
>
> 
>

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

[yocto] Yocto Project security work in progress: call for contributions

[Marta Rybczynska]

Hello all,
There's an ongoing work on the YP security and we have had an
interesting discussion during the weekly meeting on September 26.
Slides used are available from the wiki [1]. If you're interested i
security subjects, please comment on the content.

Two processes are currently in the works:
- the vulnerability reporting process and the security team [2]
(complete, ready for review)
- the CVE synchronization [3] (work in progress)

They are working for your feedback!

We are also searching for people who will like to join the group
experimenting with CVE work synchronization.

Kind regards,
Marta

[1] 
https://wiki.yoctoproject.org/wiki/File:Yocto_Project_Security_-_26_09_2023.pdf
[2] https://wiki.yoctoproject.org/wiki/Security_private_reporting
[3] https://wiki.yoctoproject.org/wiki/Synchronization_CVEs

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

[yocto] [ANNOUNCEMENT] Yocto Project 3.1.28 (dunfell-23.0.28) is Released

[Lee Chee Yang]

Hi

We are pleased to announce the Yocto Project 3.1.28 (dunfell-23.0.28) Release 
is now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.28/poky-dunfell-23.0.28.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.28/poky-dunfell-23.0.28.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.28/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.28/testreport.txt

Thank you for everyone's contributions to this release.

Chee Yang Lee chee.yang@intel.com
Yocto Project Build and Release


- --
yocto-3.1.28 Release Notes
- --


- --
Repositories/Downloads
- --

Repository Name: poky
Repository Location: https://git.yoctoproject.org/git/poky
Branch: dunfell
Tag: yocto-3.1.28
Git Revision: 926eb08fe325e2ea13098f99d920840b9354ceb9
Release Artefact: poky-dunfell-23.0.28
sha: b5461aed3119ad77ba0c40b3121b4d57f98651e2c95d34b50ce6819c6cbc021d
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.28/poky-dunfell-23.0.28.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.28/poky-dunfell-23.0.28.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: dunfell
Tag: yocto-3.1.28
Git Revision: 8b91c463fb3546836789e1890b3c68acf69c162a
Release Artefact: oecore-dunfell-23.0.28
sha: 9721b274f2ccef1241b0901407c51d9ea9d757db92584c73950fb2aa5160e994
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.28/oecore-dunfell-23.0.28.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.28/oecore-dunfell-23.0.28.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/git/meta-mingw
Branch: dunfell
Tag: yocto-3.1.28
Git Revision: 524de686205b5d6736661d4532f5f98fee8589b7
Release Artefact: meta-mingw-dunfell-23.0.28
sha: 0a34205f358a587db3884bfeb046600447805ffa19e188359e570219e01ceb38
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.28/meta-mingw-dunfell-23.0.28.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.28/meta-mingw-dunfell-23.0.28.tar.bz2

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: dunfell
Tag: yocto-3.1.28
Git Revision: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
Release Artefact: meta-gplv2-dunfell-23.0.28
sha: 48d88b7a4827fb441bb718ad1de8471fce44bbb358ad1e06f213aaf48274b600
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.28/meta-gplv2-dunfell-23.0.28.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.28/meta-gplv2-dunfell-23.0.28.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: dunfell
Tag: yocto-3.1.28
Git Revision: b60c7085ec370473bea9b3b4b65826a17638837f
Release Artefact: bitbake-dunfell-23.0.28
sha: 2ea8e93482b8553efbb2097f5e7384fd2f65b577ffc4e369ff4faf792adf
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.28/bitbake-dunfell-23.0.28.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.28/bitbake-dunfell-23.0.28.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/git/yocto-docs
Branch: dunfell
Tag: yocto-3.1.28
Git Revision: 628be0aa38ea9fe03cd4843278c201a0c4f6aa44


- ---
Known Issues
- ---
N/A


- ---
Security Fixes
- ---
bind: Fix CVE-2023-2828
curl: Fix CVE-2023-32001
dmidecode: Fix CVE-2023-30630
elfutils: Fix CVE-2021-33294
ghostscript: Fix CVE-2023-38559
go: Fix CVE-2023-29406 CVE-2023-29409
inetutils: Fix CVE-2023-40303
libarchive: Ignore CVE-2023-30571
libjpeg-turbo: Fix CVE-2023-2804
libpcre2: Fix CVE-2022-41409
openssh: Fix CVE-2023-38408
openssl: Fix CVE-2023-3446 CVE-2023-3817
procps: Fix CVE-2023-4016
python3: Ignore CVE-2023-36632
qemu: Fix CVE-2020-35505 CVE-2023-0330 CVE-2023-3180 CVE-2023-3354
ruby: Fix CVE-2021-33621
tiff: Fix CVE-2022-4645 CVE-2023-2908 CVE-2023-3316 CVE-2023-3618 
CVE-2023-25433 CVE-2023-25434 CVE-2023-25435 CVE-2023-26965 CVE-2023-26966 
CVE-2023-30774


- ---
Fixes
- ---
build-appliance-image: Update to dunfell head revision
cve-update-nvd2-native: always pass str for json.loads()
documentation: update for 3.1.28
gawk: remove load-sensitive tests
glibc/check-test-wrapper: don't emit warnings from ssh
grub2.inc: remove '-O2' from CFLAGS
harfbuzz: Resolve backported commit bug.
kernel: Fix path comparison in kernel staging dir symlinking
kernel: skip installing fitImage when using Initramfs bundles
libnss-nis: upgrade to 3.2
linux-firmware : Add firmware of RTL8822 serie
linux-firmware: Fix mediatek mt7601u firmware path
linux-firmware: package firmare for Dragonboard 410c
linux-firmware: split platform-specific Adreno shaders to separate 

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

[Jing Hui Tham]

Hi All,
 
QA for yocto-4.0.13.rc2 is completed. This is the full report for this release: 
 
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
 
=== Summary 
No high milestone defects.
 
No new issue found. 
 
Thanks,
Jing Hui



> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Monday, September 25, 2023 2:49 PM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-4.0.13.rc2)
> 
> 
> A build flagged for QA (yocto-4.0.13.rc2) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-4.0.13.rc2
> 
> 
> Build hash information:
> 
> bitbake: 41b6684489d0261753344956042be2cc4adb0159
> meta-agl: 666f141563fd7fc12b7638479d5c0cd38dae5006
> meta-arm: b187fb9232ca0a6b5f8f90b4715958546fc41d73
> meta-aws: 60891e535ce219b3c473a89d8ae89cdba1d396f4
> meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a
> meta-intel: 1342bcdc5bfc6620737e7d195e7d9bd744348577
> meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1
> meta-openembedded: a88cb922f91fda95e8a584cee3092083d5ad3e98
> meta-virtualization: 2d8b3cba8ff27c9ec2187a52b6a551fe1dcfaa07
> oecore: d90e4d5e3cca9cffe8f60841afc63667a9ac39fa
> poky: e51bf557f596c4da38789a948a3228ba11455e3c
> 
> 
> 
> 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 (#61173): https://lists.yoctoproject.org/g/yocto/message/61173
Mute This Topic: https://lists.yoctoproject.org/mt/101672224/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-