Yocto Project Status 10 June. 2025 (WW23)

Yocto Project Status 10 June. 2025 (WW23)

[Stephen K Jolley]

[-- Attachment #1: Type: text/plain, Size: 7154 bytes --]

Current Dev Position: YP 5.3 M1

Next Deadline: YP 5.3 M1 Build date 2025-06-09

Next Team Meetings:

   -

   Bug Triage meeting - Thursday June 12th 7:30 am PDT (
   https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
   -

   Weekly Project Engineering Sync  - Tuesday June 10th 8 am PDT (
   https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
   <https://zoom.us/j/990892712>
   -

   Yocto Project Patch Review - Thursday June 12th 10am GMT and Monday June
   16th 9am PDT (
   https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1
   <https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1>)


Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

   -

   YP 4.0.27 and YP 5.2.1 were released.
   -

   YP 5.0.10 is due to be released.
   -

   YP 5.3 M1 is now due to build
   -

   Patches continue to merge into master for upgrades and fixes.
   -

   The clang build time and size increases continue to cause significant
   concern.
   -

   Patches for changing the workdir layout for unpack have been proposed
   with potentially significant impact for git based recipes. Feedback/review
   is welcome.
   -

   Network access outside of do_fetch now causes yocto-check-layer to fail
   which is a new change/requirement for Yocto Compatible v3. We need to work
   out how to handle this for go recipes in particular in meta-openembedded.
   -

   Patches were sent out for a proposed toolchain selection mechanism
   implementation, feedback/review is welcome.
   -

   Icecc.bbclass was removed.
   -

   lz4 was removed from HOSTTOOLS as it was unneeded.
   -

   Fitimage restructuring was merged, thanks Adrian.
   -

   The project has switched to a different CDN setup with a different URL.
   This is proving reliable on the autobuilder so far, huge thanks to Michael
   Halstead for working on this.


Ways to contribute:

   -

   As people are likely aware, the project has a number of components which
   are either unmaintained, or have people with little to no time trying to
   keep them alive. These components include: devtool, toaster, wic, oeqa,
   autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help
   is welcome in trying to better look after these components!
   -

   There is an issue open upstream with the openssl project related to
   making path relocation of openssl easier (as used in our buildtools tarball
   and SDK). We’d love assistance in moving this forward and getting some kind
   of upstream feature merged to make this easier:
   https://github.com/openssl/openssl/pull/19260
   -

   There are bugs identified as possible for newcomers to the project:
   https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
   -

   There are bugs that are currently unassigned for YP 5.3. See:
   https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs
   -

   We’d welcome new maintainers for recipes in OE-Core. Please see the list
   at:
   http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
   and discuss with the existing maintainer, or ask on the OE-Core mailing
   list. We will likely move a chunk of these to “Unassigned” soon to help
   facilitate this.
   -

   Help is very much welcome in trying to resolve our autobuilder
   intermittent issues. You can see the list of failures we’re continuing to
   see by searching for the “AB-INT” tag in bugzilla:
   https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
   -

   Help us resolve CVE issues: CVE metrics
   <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
   -

   We have a growing number of bugs in bugzilla, any help with them is
   appreciated.
   -

   Regarding bugs, even if you can’t fix a bug, submitting a failing test
   case that can reproduce the issue significantly improves the chances it
   might get fixed.
   -

   Further help on optimizing build disk usage would be most welcome.
   -

   Ongoing project development plans are being developed in this document:
   https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing

We need to continue to develop this as it will allow us to potentially find
ways to fund specific work items.

Tracking Metrics:

   -

   WDD 2740 (last week 2778) (
   https://wiki.yoctoproject.org/charts/combo.html)
   -

   OE-Core/Poky Patch Metrics
   -

      Total patches found: 1089 (last week 1089)
      -

      Patches in the Pending State: 157 (14%) [last week 157 (14%)]
      -

      https://autobuilder.yocto.io/pub/non-release/patchmetrics/


YP 5.3 Milestone Dates:

   -

   YP 5.3 M1 Build Date 2025-06-09
   -

   YP 5.3 M1 Release Date 2025-06-20
   -

   YP 5.3 M2 Build Date 2025-07-21
   -

   YP 5.3 M2 Release Date 2025-08-01
   -

   YP 5.3 M3 Build Date 2025-09-01
   -

   YP 5.3 M3 Release Date 2025-09-12
   -

   YP 5.3 M4 Build Date 2025-10-06
   -

   YP 5.3 M4 Release Date 2025-10-31


Upcoming dot releases:.

   -

   YP 4.0.27 was released.
   -

   YP 5.2.1 was released.
   -

   YP 5.0.10  is ready for release.
   -

   YP 4.0.28 Build Date 2025-06-30
   -

   YP 4.0.28 Release Date 2025-07-11
   -

   YP 5.2.2 Build Date 2025-07-07
   -

   YP 5.2.2 Release Date 2025-07-18
   -

   YP 5.0.11 Build Date 2025-07-14
   -

   YP 5.0.11 Release Date 2025-07-25
   -

   YP 4.0.29 Build Date 2025-08-11
   -

   YP 4.0.29 Release Date 2025-08-25
   -

   YP 5.2.3 Build Date 2025-08-18
   -

   YP 5.2.3 Release Date 2025-08-29
   -

   YP 5.0.12 Build Date 2025-08-25
   -

   YP 5.0.12 Release Date 2025-09-05
   -

   YP 4.0.30 Build Date 2025-09-22
   -

   YP 4.0.30 Release Date 2025-10-03
   -

   YP 5.2.4 Build Date 2025-09-29
   -

   YP 5.2.4 Release Date 2025-10-10
   -

   YP 5.0.13 Build Date 2025-10-13
   -

   YP 5.0.13 Release Date 2025-10-24
   -

   YP 4.0.31 Build Date 2025-11-03
   -

   YP 4.031 Release Date 2025-11-14
   -

   YP 5.0.14 Build Date 2025-11-17
   -

   YP 5.0.14 Release Date 2025-11-28
   -

   YP 4.0.32 Build Date 2025-12-15
   -

   YP 4.0.32 Release Date 2025-12-24
   -

   YP 5.0.15 Build Date 2026-01-05
   -

   YP 5.0.15 Release Date 2026-01-16


The Yocto Project’s technical governance is through its Technical Steering
Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on this
weekly status update, let us know!]

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(    *Cell*:                (208) 244-4460

* *Email*:                 *s
<stephen.k.jolley@intel.com>jolley.yp.pm@gmail.com <jolley.yp.pm@gmail.com>*

[-- Attachment #2: Type: text/html, Size: 59951 bytes --]

Re: [yocto] Yocto Project Status 10 June. 2025 (WW23)

[Gyorgy Sarvari]

On 6/10/25 16:40, Stephen Jolley via lists.yoctoproject.org wrote:
>
> Current Dev Position: YP 5.3 M1
>
> Next Deadline: YP 5.3 M1 Build date 2025-06-09
>
>
> Next Team Meetings:
>
>  *
>
>     Bug Triage meeting - Thursday June 12th 7:30 am PDT
>     (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09
>     <https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>)
>
>  *
>
>     Weekly Project Engineering Sync  - Tuesday June 10th 8 am PDT
>     (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
>     <https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>)
>     <https://zoom.us/j/990892712>
>
>  *
>
>     Yocto Project Patch Review - Thursday June 12th 10am GMT and
>     Monday June 16th 9am PDT
>     (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1
>     <https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1>)
>
>
> Project data dashboard: https://dashboard.yoctoproject.org/
> <https://dashboard.yoctoproject.org/> 
>
>
> Key Status/Updates:
>
>  *
>
>     YP 4.0.27 and YP 5.2.1 were released.
>
>  *
>
>     YP 5.0.10 is due to be released.
>
>  *
>
>     YP 5.3 M1 is now due to build
>
>  *
>
>     Patches continue to merge into master for upgrades and fixes.
>
>  *
>
>     The clang build time and size increases continue to cause
>     significant concern.
>

Is there more info available on this somewhere? I'd be interested if
there are any concrete recipes/configurations where this is showing
prominently and could be used as a benchmark. Or is it more like an
overall "lot of small things add up to a big one" issue?

>  *
>
>     Patches for changing the workdir layout for unpack have been
>     proposed with potentially significant impact for git based
>     recipes. Feedback/review is welcome.
>
>  *
>
>     Network access outside of do_fetch now causes yocto-check-layer to
>     fail which is a new change/requirement for Yocto Compatible v3. We
>     need to work out how to handle this for go recipes in particular
>     in meta-openembedded.
>
>  *
>
>     Patches were sent out for a proposed toolchain selection mechanism
>     implementation, feedback/review is welcome.
>
>  *
>
>     Icecc.bbclass was removed.
>
>  *
>
>     lz4 was removed from HOSTTOOLS as it was unneeded.
>
>  *
>
>     Fitimage restructuring was merged, thanks Adrian.
>
>  *
>
>     The project has switched to a different CDN setup with a different
>     URL. This is proving reliable on the autobuilder so far, huge
>     thanks to Michael Halstead for working on this.
>
>
> Ways to contribute:
>
>  *
>
>     As people are likely aware, the project has a number of components
>     which are either unmaintained, or have people with little to no
>     time trying to keep them alive. These components include: devtool,
>     toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and
>     more. Many have open bugs. Help is welcome in trying to better
>     look after these components!
>
>  *
>
>     There is an issue open upstream with the openssl project related
>     to making path relocation of openssl easier (as used in our
>     buildtools tarball and SDK). We’d love assistance in moving this
>     forward and getting some kind of upstream feature merged to make
>     this easier: https://github.com/openssl/openssl/pull/19260
>     <https://github.com/openssl/openssl/pull/19260>
>
>  *
>
>     There are bugs identified as possible for newcomers to the
>     project:
>     https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
>     <https://dashboard.yoctoproject.org/bugtriage/#newcomer-container>
>
>  *
>
>     There are bugs that are currently unassigned for YP 5.3. See:
>     https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs
>     <https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs>
>
>  *
>
>     We’d welcome new maintainers for recipes in OE-Core. Please see
>     the list at:
>     http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
>     <http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc>and
>     discuss with the existing maintainer, or ask on the OE-Core
>     mailing list. We will likely move a chunk of these to “Unassigned”
>     soon to help facilitate this.
>
>  *
>
>     Help is very much welcome in trying to resolve our autobuilder
>     intermittent issues. You can see the list of failures we’re
>     continuing to see by searching for the “AB-INT” tag in bugzilla:
>     https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
>     <https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT>.
>
>  *
>
>     Help us resolve CVE issues: CVE metrics
>     <https://autobuilder.yocto.io/pub/non-release/patchmetrics/> 
>
>  *
>
>     We have a growing number of bugs in bugzilla, any help with them
>     is appreciated.
>
>  *
>
>     Regarding bugs, even if you can’t fix a bug, submitting a failing
>     test case that can reproduce the issue significantly improves the
>     chances it might get fixed.
>
>  *
>
>     Further help on optimizing build disk usage would be most welcome.
>
>  *
>
>     Ongoing project development plans are being developed in this
>     document:
>     https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
>     <https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing>
>
> We need to continue to develop this as it will allow us to potentially
> find ways to fund specific work items.
>
>
> Tracking Metrics:
>
>  *
>
>     WDD 2740 (last week 2778)
>     (https://wiki.yoctoproject.org/charts/combo.html
>     <https://wiki.yoctoproject.org/charts/combo.html>)
>
>  *
>
>     OE-Core/Poky Patch Metrics
>
>      o
>
>         Total patches found: 1089 (last week 1089)
>
>      o
>
>         Patches in the Pending State: 157 (14%) [last week 157 (14%)]
>
>      o
>
>         https://autobuilder.yocto.io/pub/non-release/patchmetrics/
>         <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
>
>
> YP 5.3 Milestone Dates:
>
>  *
>
>     YP 5.3 M1 Build Date 2025-06-09
>
>  *
>
>     YP 5.3 M1 Release Date 2025-06-20
>
>  *
>
>     YP 5.3 M2 Build Date 2025-07-21
>
>  *
>
>     YP 5.3 M2 Release Date 2025-08-01
>
>  *
>
>     YP 5.3 M3 Build Date 2025-09-01
>
>  *
>
>     YP 5.3 M3 Release Date 2025-09-12
>
>  *
>
>     YP 5.3 M4 Build Date 2025-10-06
>
>  *
>
>     YP 5.3 M4 Release Date 2025-10-31
>
>
> Upcoming dot releases:.
>
>  *
>
>     YP 4.0.27 was released.
>
>  *
>
>     YP 5.2.1 was released.
>
>  *
>
>     YP 5.0.10  is ready for release.
>
>  *
>
>     YP 4.0.28 Build Date 2025-06-30
>
>  *
>
>     YP 4.0.28 Release Date 2025-07-11
>
>  *
>
>     YP 5.2.2 Build Date 2025-07-07
>
>  *
>
>     YP 5.2.2 Release Date 2025-07-18
>
>  *
>
>     YP 5.0.11 Build Date 2025-07-14
>
>  *
>
>     YP 5.0.11 Release Date 2025-07-25
>
>  *
>
>     YP 4.0.29 Build Date 2025-08-11
>
>  *
>
>     YP 4.0.29 Release Date 2025-08-25
>
>  *
>
>     YP 5.2.3 Build Date 2025-08-18
>
>  *
>
>     YP 5.2.3 Release Date 2025-08-29
>
>  *
>
>     YP 5.0.12 Build Date 2025-08-25
>
>  *
>
>     YP 5.0.12 Release Date 2025-09-05
>
>  *
>
>     YP 4.0.30 Build Date 2025-09-22
>
>  *
>
>     YP 4.0.30 Release Date 2025-10-03
>
>  *
>
>     YP 5.2.4 Build Date 2025-09-29
>
>  *
>
>     YP 5.2.4 Release Date 2025-10-10
>
>  *
>
>     YP 5.0.13 Build Date 2025-10-13
>
>  *
>
>     YP 5.0.13 Release Date 2025-10-24
>
>  *
>
>     YP 4.0.31 Build Date 2025-11-03
>
>  *
>
>     YP 4.031 Release Date 2025-11-14
>
>  *
>
>     YP 5.0.14 Build Date 2025-11-17
>
>  *
>
>     YP 5.0.14 Release Date 2025-11-28
>
>  *
>
>     YP 4.0.32 Build Date 2025-12-15
>
>  *
>
>     YP 4.0.32 Release Date 2025-12-24
>
>  *
>
>     YP 5.0.15 Build Date 2026-01-05
>
>  *
>
>     YP 5.0.15 Release Date 2026-01-16
>
>
> The Yocto Project’s technical governance is through its Technical
> Steering Committee, more information is available at:
>
> https://wiki.yoctoproject.org/wiki/TSC
> <https://wiki.yoctoproject.org/wiki/TSC>
>
>
> The Status reports are now stored on the wiki at:
> https://wiki.yoctoproject.org/wiki/Weekly_Status
> <https://wiki.yoctoproject.org/wiki/Weekly_Status>
>
>
> [If anyone has suggestions for other information you’d like to see on
> this weekly status update, let us know!]
>
>
> Thanks,
>
>  
>
> */Stephen K. Jolley/*
>
> *Yocto Project Program Manager*
>
> (    *Cell*:                (208) 244-4460
>
> * *Email*:                 _s
> <mailto:stephen.k.jolley@intel.com>jolley.yp.pm@gmail.com_
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#65497): https://lists.yoctoproject.org/g/yocto/message/65497
> Mute This Topic: https://lists.yoctoproject.org/mt/113570840/6084445
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [yocto] Yocto Project Status 10 June. 2025 (WW23)

[Mimo Ghosh]

[-- Attachment #1: Type: text/plain, Size: 10304 bytes --]

Why am getting those mail not sure. Which is not related to my queries.
Unexpectedly getting those. I was registered to get help. But it is
diverting to another way... Fuck of those silly sitts thing..... looking
for unsubscribe....

On Tue, 10 Jun 2025, 20:16 Gyorgy Sarvari via lists.yoctoproject.org,
<skandigraun=gmail.com@lists.yoctoproject.org> wrote:

> On 6/10/25 16:40, Stephen Jolley via lists.yoctoproject.org wrote:
> >
> > Current Dev Position: YP 5.3 M1
> >
> > Next Deadline: YP 5.3 M1 Build date 2025-06-09
> >
> >
> > Next Team Meetings:
> >
> >  *
> >
> >     Bug Triage meeting - Thursday June 12th 7:30 am PDT
> >     (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09
> >     <https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>)
> >
> >  *
> >
> >     Weekly Project Engineering Sync  - Tuesday June 10th 8 am PDT
> >     (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
> >     <https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>)
> >     <https://zoom.us/j/990892712>
> >
> >  *
> >
> >     Yocto Project Patch Review - Thursday June 12th 10am GMT and
> >     Monday June 16th 9am PDT
> >     (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1
> >     <https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1
> >)
> >
> >
> > Project data dashboard: https://dashboard.yoctoproject.org/
> > <https://dashboard.yoctoproject.org/>
> >
> >
> > Key Status/Updates:
> >
> >  *
> >
> >     YP 4.0.27 and YP 5.2.1 were released.
> >
> >  *
> >
> >     YP 5.0.10 is due to be released.
> >
> >  *
> >
> >     YP 5.3 M1 is now due to build
> >
> >  *
> >
> >     Patches continue to merge into master for upgrades and fixes.
> >
> >  *
> >
> >     The clang build time and size increases continue to cause
> >     significant concern.
> >
>
> Is there more info available on this somewhere? I'd be interested if
> there are any concrete recipes/configurations where this is showing
> prominently and could be used as a benchmark. Or is it more like an
> overall "lot of small things add up to a big one" issue?
>
> >  *
> >
> >     Patches for changing the workdir layout for unpack have been
> >     proposed with potentially significant impact for git based
> >     recipes. Feedback/review is welcome.
> >
> >  *
> >
> >     Network access outside of do_fetch now causes yocto-check-layer to
> >     fail which is a new change/requirement for Yocto Compatible v3. We
> >     need to work out how to handle this for go recipes in particular
> >     in meta-openembedded.
> >
> >  *
> >
> >     Patches were sent out for a proposed toolchain selection mechanism
> >     implementation, feedback/review is welcome.
> >
> >  *
> >
> >     Icecc.bbclass was removed.
> >
> >  *
> >
> >     lz4 was removed from HOSTTOOLS as it was unneeded.
> >
> >  *
> >
> >     Fitimage restructuring was merged, thanks Adrian.
> >
> >  *
> >
> >     The project has switched to a different CDN setup with a different
> >     URL. This is proving reliable on the autobuilder so far, huge
> >     thanks to Michael Halstead for working on this.
> >
> >
> > Ways to contribute:
> >
> >  *
> >
> >     As people are likely aware, the project has a number of components
> >     which are either unmaintained, or have people with little to no
> >     time trying to keep them alive. These components include: devtool,
> >     toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and
> >     more. Many have open bugs. Help is welcome in trying to better
> >     look after these components!
> >
> >  *
> >
> >     There is an issue open upstream with the openssl project related
> >     to making path relocation of openssl easier (as used in our
> >     buildtools tarball and SDK). We’d love assistance in moving this
> >     forward and getting some kind of upstream feature merged to make
> >     this easier: https://github.com/openssl/openssl/pull/19260
> >     <https://github.com/openssl/openssl/pull/19260>
> >
> >  *
> >
> >     There are bugs identified as possible for newcomers to the
> >     project:
> >     https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
> >     <https://dashboard.yoctoproject.org/bugtriage/#newcomer-container>
> >
> >  *
> >
> >     There are bugs that are currently unassigned for YP 5.3. See:
> >
> https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs
> >     <
> https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs
> >
> >
> >  *
> >
> >     We’d welcome new maintainers for recipes in OE-Core. Please see
> >     the list at:
> >
> http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
> >     <
> http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
> >and
> >     discuss with the existing maintainer, or ask on the OE-Core
> >     mailing list. We will likely move a chunk of these to “Unassigned”
> >     soon to help facilitate this.
> >
> >  *
> >
> >     Help is very much welcome in trying to resolve our autobuilder
> >     intermittent issues. You can see the list of failures we’re
> >     continuing to see by searching for the “AB-INT” tag in bugzilla:
> >     https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
> >     <https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT>.
> >
> >  *
> >
> >     Help us resolve CVE issues: CVE metrics
> >     <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
> >
> >  *
> >
> >     We have a growing number of bugs in bugzilla, any help with them
> >     is appreciated.
> >
> >  *
> >
> >     Regarding bugs, even if you can’t fix a bug, submitting a failing
> >     test case that can reproduce the issue significantly improves the
> >     chances it might get fixed.
> >
> >  *
> >
> >     Further help on optimizing build disk usage would be most welcome.
> >
> >  *
> >
> >     Ongoing project development plans are being developed in this
> >     document:
> >
> https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
> >     <
> https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
> >
> >
> > We need to continue to develop this as it will allow us to potentially
> > find ways to fund specific work items.
> >
> >
> > Tracking Metrics:
> >
> >  *
> >
> >     WDD 2740 (last week 2778)
> >     (https://wiki.yoctoproject.org/charts/combo.html
> >     <https://wiki.yoctoproject.org/charts/combo.html>)
> >
> >  *
> >
> >     OE-Core/Poky Patch Metrics
> >
> >      o
> >
> >         Total patches found: 1089 (last week 1089)
> >
> >      o
> >
> >         Patches in the Pending State: 157 (14%) [last week 157 (14%)]
> >
> >      o
> >
> >         https://autobuilder.yocto.io/pub/non-release/patchmetrics/
> >         <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
> >
> >
> > YP 5.3 Milestone Dates:
> >
> >  *
> >
> >     YP 5.3 M1 Build Date 2025-06-09
> >
> >  *
> >
> >     YP 5.3 M1 Release Date 2025-06-20
> >
> >  *
> >
> >     YP 5.3 M2 Build Date 2025-07-21
> >
> >  *
> >
> >     YP 5.3 M2 Release Date 2025-08-01
> >
> >  *
> >
> >     YP 5.3 M3 Build Date 2025-09-01
> >
> >  *
> >
> >     YP 5.3 M3 Release Date 2025-09-12
> >
> >  *
> >
> >     YP 5.3 M4 Build Date 2025-10-06
> >
> >  *
> >
> >     YP 5.3 M4 Release Date 2025-10-31
> >
> >
> > Upcoming dot releases:.
> >
> >  *
> >
> >     YP 4.0.27 was released.
> >
> >  *
> >
> >     YP 5.2.1 was released.
> >
> >  *
> >
> >     YP 5.0.10  is ready for release.
> >
> >  *
> >
> >     YP 4.0.28 Build Date 2025-06-30
> >
> >  *
> >
> >     YP 4.0.28 Release Date 2025-07-11
> >
> >  *
> >
> >     YP 5.2.2 Build Date 2025-07-07
> >
> >  *
> >
> >     YP 5.2.2 Release Date 2025-07-18
> >
> >  *
> >
> >     YP 5.0.11 Build Date 2025-07-14
> >
> >  *
> >
> >     YP 5.0.11 Release Date 2025-07-25
> >
> >  *
> >
> >     YP 4.0.29 Build Date 2025-08-11
> >
> >  *
> >
> >     YP 4.0.29 Release Date 2025-08-25
> >
> >  *
> >
> >     YP 5.2.3 Build Date 2025-08-18
> >
> >  *
> >
> >     YP 5.2.3 Release Date 2025-08-29
> >
> >  *
> >
> >     YP 5.0.12 Build Date 2025-08-25
> >
> >  *
> >
> >     YP 5.0.12 Release Date 2025-09-05
> >
> >  *
> >
> >     YP 4.0.30 Build Date 2025-09-22
> >
> >  *
> >
> >     YP 4.0.30 Release Date 2025-10-03
> >
> >  *
> >
> >     YP 5.2.4 Build Date 2025-09-29
> >
> >  *
> >
> >     YP 5.2.4 Release Date 2025-10-10
> >
> >  *
> >
> >     YP 5.0.13 Build Date 2025-10-13
> >
> >  *
> >
> >     YP 5.0.13 Release Date 2025-10-24
> >
> >  *
> >
> >     YP 4.0.31 Build Date 2025-11-03
> >
> >  *
> >
> >     YP 4.031 Release Date 2025-11-14
> >
> >  *
> >
> >     YP 5.0.14 Build Date 2025-11-17
> >
> >  *
> >
> >     YP 5.0.14 Release Date 2025-11-28
> >
> >  *
> >
> >     YP 4.0.32 Build Date 2025-12-15
> >
> >  *
> >
> >     YP 4.0.32 Release Date 2025-12-24
> >
> >  *
> >
> >     YP 5.0.15 Build Date 2026-01-05
> >
> >  *
> >
> >     YP 5.0.15 Release Date 2026-01-16
> >
> >
> > The Yocto Project’s technical governance is through its Technical
> > Steering Committee, more information is available at:
> >
> > https://wiki.yoctoproject.org/wiki/TSC
> > <https://wiki.yoctoproject.org/wiki/TSC>
> >
> >
> > The Status reports are now stored on the wiki at:
> > https://wiki.yoctoproject.org/wiki/Weekly_Status
> > <https://wiki.yoctoproject.org/wiki/Weekly_Status>
> >
> >
> > [If anyone has suggestions for other information you’d like to see on
> > this weekly status update, let us know!]
> >
> >
> > Thanks,
> >
> >
> >
> > */Stephen K. Jolley/*
> >
> > *Yocto Project Program Manager*
> >
> > (    *Cell*:                (208) 244-4460
> >
> > * *Email*:                 _s
> > <mailto:stephen.k.jolley@intel.com>jolley.yp.pm@gmail.com_
> >
> >
> >
> >
>
>
> 
>
>

[-- Attachment #2: Type: text/html, Size: 16947 bytes --]

Re: [yocto] Yocto Project Status 10 June. 2025 (WW23)

[Mimo Ghosh]

[-- Attachment #1: Type: text/plain, Size: 10707 bytes --]

Why am getting those mail not sure. Which is not related to my queries.
Unexpectedly getting those. I was registered to get help. But it is
diverting to another way... Fuck of those silly sitts thing..... looking
for unsubscribe....

On Tue, 10 Jun 2025, 20:16 Gyorgy Sarvari via lists.yoctoproject.org,
<skandigraun=gmail.com@lists.yoctoproject.org> wrote:

> On 6/10/25 16:40, Stephen Jolley via lists.yoctoproject.org wrote:
> >
> > Current Dev Position: YP 5.3 M1
> >
> > Next Deadline: YP 5.3 M1 Build date 2025-06-09
> >
> >
> > Next Team Meetings:
> >
> >  *
> >
> >     Bug Triage meeting - Thursday June 12th 7:30 am PDT
> >     (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09
> >     <https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>)
> >
> >  *
> >
> >     Weekly Project Engineering Sync  - Tuesday June 10th 8 am PDT
> >     (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
> >     <https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>)
> >     <https://zoom.us/j/990892712>
> >
> >  *
> >
> >     Yocto Project Patch Review - Thursday June 12th 10am GMT and
> >     Monday June 16th 9am PDT
> >     (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1
> >     <https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1
> >)
> >
> >
> > Project data dashboard: https://dashboard.yoctoproject.org/
> > <https://dashboard.yoctoproject.org/>
> >
> >
> > Key Status/Updates:
> >
> >  *
> >
> >     YP 4.0.27 and YP 5.2.1 were released.
> >
> >  *
> >
> >     YP 5.0.10 is due to be released.
> >
> >  *
> >
> >     YP 5.3 M1 is now due to build
> >
> >  *
> >
> >     Patches continue to merge into master for upgrades and fixes.
> >
> >  *
> >
> >     The clang build time and size increases continue to cause
> >     significant concern.
> >
>
> Is there more info available on this somewhere? I'd be interested if
> there are any concrete recipes/configurations where this is showing
> prominently and could be used as a benchmark. Or is it more like an
> overall "lot of small things add up to a big one" issue?
>
> >  *
> >
> >     Patches for changing the workdir layout for unpack have been
> >     proposed with potentially significant impact for git based
> >     recipes. Feedback/review is welcome.
> >
> >  *
> >
> >     Network access outside of do_fetch now causes yocto-check-layer to
> >     fail which is a new change/requirement for Yocto Compatible v3. We
> >     need to work out how to handle this for go recipes in particular
> >     in meta-openembedded.
> >
> >  *
> >
> >     Patches were sent out for a proposed toolchain selection mechanism
> >     implementation, feedback/review is welcome.
> >
> >  *
> >
> >     Icecc.bbclass was removed.
> >
> >  *
> >
> >     lz4 was removed from HOSTTOOLS as it was unneeded.
> >
> >  *
> >
> >     Fitimage restructuring was merged, thanks Adrian.
> >
> >  *
> >
> >     The project has switched to a different CDN setup with a different
> >     URL. This is proving reliable on the autobuilder so far, huge
> >     thanks to Michael Halstead for working on this.
> >
> >
> > Ways to contribute:
> >
> >  *
> >
> >     As people are likely aware, the project has a number of components
> >     which are either unmaintained, or have people with little to no
> >     time trying to keep them alive. These components include: devtool,
> >     toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and
> >     more. Many have open bugs. Help is welcome in trying to better
> >     look after these components!
> >
> >  *
> >
> >     There is an issue open upstream with the openssl project related
> >     to making path relocation of openssl easier (as used in our
> >     buildtools tarball and SDK). We’d love assistance in moving this
> >     forward and getting some kind of upstream feature merged to make
> >     this easier: https://github.com/openssl/openssl/pull/19260
> >     <https://github.com/openssl/openssl/pull/19260>
> >
> >  *
> >
> >     There are bugs identified as possible for newcomers to the
> >     project:
> >     https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
> >     <https://dashboard.yoctoproject.org/bugtriage/#newcomer-container>
> >
> >  *
> >
> >     There are bugs that are currently unassigned for YP 5.3. See:
> >
> https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs
> >     <
> https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs
> >
> >
> >  *
> >
> >     We’d welcome new maintainers for recipes in OE-Core. Please see
> >     the list at:
> >
> http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
> >     <
> http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
> >and
> >     discuss with the existing maintainer, or ask on the OE-Core
> >     mailing list. We will likely move a chunk of these to “Unassigned”
> >     soon to help facilitate this.
> >
> >  *
> >
> >     Help is very much welcome in trying to resolve our autobuilder
> >     intermittent issues. You can see the list of failures we’re
> >     continuing to see by searching for the “AB-INT” tag in bugzilla:
> >     https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
> >     <https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT>.
> >
> >  *
> >
> >     Help us resolve CVE issues: CVE metrics
> >     <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
> >
> >  *
> >
> >     We have a growing number of bugs in bugzilla, any help with them
> >     is appreciated.
> >
> >  *
> >
> >     Regarding bugs, even if you can’t fix a bug, submitting a failing
> >     test case that can reproduce the issue significantly improves the
> >     chances it might get fixed.
> >
> >  *
> >
> >     Further help on optimizing build disk usage would be most welcome.
> >
> >  *
> >
> >     Ongoing project development plans are being developed in this
> >     document:
> >
> https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
> >     <
> https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
> >
> >
> > We need to continue to develop this as it will allow us to potentially
> > find ways to fund specific work items.
> >
> >
> > Tracking Metrics:
> >
> >  *
> >
> >     WDD 2740 (last week 2778)
> >     (https://wiki.yoctoproject.org/charts/combo.html
> >     <https://wiki.yoctoproject.org/charts/combo.html>)
> >
> >  *
> >
> >     OE-Core/Poky Patch Metrics
> >
> >      o
> >
> >         Total patches found: 1089 (last week 1089)
> >
> >      o
> >
> >         Patches in the Pending State: 157 (14%) [last week 157 (14%)]
> >
> >      o
> >
> >         https://autobuilder.yocto.io/pub/non-release/patchmetrics/
> >         <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
> >
> >
> > YP 5.3 Milestone Dates:
> >
> >  *
> >
> >     YP 5.3 M1 Build Date 2025-06-09
> >
> >  *
> >
> >     YP 5.3 M1 Release Date 2025-06-20
> >
> >  *
> >
> >     YP 5.3 M2 Build Date 2025-07-21
> >
> >  *
> >
> >     YP 5.3 M2 Release Date 2025-08-01
> >
> >  *
> >
> >     YP 5.3 M3 Build Date 2025-09-01
> >
> >  *
> >
> >     YP 5.3 M3 Release Date 2025-09-12
> >
> >  *
> >
> >     YP 5.3 M4 Build Date 2025-10-06
> >
> >  *
> >
> >     YP 5.3 M4 Release Date 2025-10-31
> >
> >
> > Upcoming dot releases:.
> >
> >  *
> >
> >     YP 4.0.27 was released.
> >
> >  *
> >
> >     YP 5.2.1 was released.
> >
> >  *
> >
> >     YP 5.0.10  is ready for release.
> >
> >  *
> >
> >     YP 4.0.28 Build Date 2025-06-30
> >
> >  *
> >
> >     YP 4.0.28 Release Date 2025-07-11
> >
> >  *
> >
> >     YP 5.2.2 Build Date 2025-07-07
> >
> >  *
> >
> >     YP 5.2.2 Release Date 2025-07-18
> >
> >  *
> >
> >     YP 5.0.11 Build Date 2025-07-14
> >
> >  *
> >
> >     YP 5.0.11 Release Date 2025-07-25
> >
> >  *
> >
> >     YP 4.0.29 Build Date 2025-08-11
> >
> >  *
> >
> >     YP 4.0.29 Release Date 2025-08-25
> >
> >  *
> >
> >     YP 5.2.3 Build Date 2025-08-18
> >
> >  *
> >
> >     YP 5.2.3 Release Date 2025-08-29
> >
> >  *
> >
> >     YP 5.0.12 Build Date 2025-08-25
> >
> >  *
> >
> >     YP 5.0.12 Release Date 2025-09-05
> >
> >  *
> >
> >     YP 4.0.30 Build Date 2025-09-22
> >
> >  *
> >
> >     YP 4.0.30 Release Date 2025-10-03
> >
> >  *
> >
> >     YP 5.2.4 Build Date 2025-09-29
> >
> >  *
> >
> >     YP 5.2.4 Release Date 2025-10-10
> >
> >  *
> >
> >     YP 5.0.13 Build Date 2025-10-13
> >
> >  *
> >
> >     YP 5.0.13 Release Date 2025-10-24
> >
> >  *
> >
> >     YP 4.0.31 Build Date 2025-11-03
> >
> >  *
> >
> >     YP 4.031 Release Date 2025-11-14
> >
> >  *
> >
> >     YP 5.0.14 Build Date 2025-11-17
> >
> >  *
> >
> >     YP 5.0.14 Release Date 2025-11-28
> >
> >  *
> >
> >     YP 4.0.32 Build Date 2025-12-15
> >
> >  *
> >
> >     YP 4.0.32 Release Date 2025-12-24
> >
> >  *
> >
> >     YP 5.0.15 Build Date 2026-01-05
> >
> >  *
> >
> >     YP 5.0.15 Release Date 2026-01-16
> >
> >
> > The Yocto Project’s technical governance is through its Technical
> > Steering Committee, more information is available at:
> >
> > https://wiki.yoctoproject.org/wiki/TSC
> > <https://wiki.yoctoproject.org/wiki/TSC>
> >
> >
> > The Status reports are now stored on the wiki at:
> > https://wiki.yoctoproject.org/wiki/Weekly_Status
> > <https://wiki.yoctoproject.org/wiki/Weekly_Status>
> >
> >
> > [If anyone has suggestions for other information you’d like to see on
> > this weekly status update, let us know!]
> >
> >
> > Thanks,
> >
> >
> >
> > */Stephen K. Jolley/*
> >
> > *Yocto Project Program Manager*
> >
> > (    *Cell*:                (208) 244-4460
> >
> > * *Email*:                 _s
> > <mailto:stephen.k.jolley@intel.com>jolley.yp.pm@gmail.com_
> >
> >
> >
> >
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#65498):
> https://lists.yoctoproject.org/g/yocto/message/65498
> Mute This Topic: https://lists.yoctoproject.org/mt/113570840/9854945
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> mimoghosh9@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 17845 bytes --]

Re: [yocto] Yocto Project Status 10 June. 2025 (WW23)

[Quentin Schulz]

Hi Mimo,

On 6/10/25 4:56 PM, Mimo Ghosh via lists.yoctoproject.org wrote:
> You don't often get email from mimoghosh9=gmail.com@lists.yoctoproject.org. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
> Why am getting those mail not sure. Which is not related to my queries.
> Unexpectedly getting those. I was registered to get help. But it is diverting to another way... Fuck of those silly sitts thing..... looking for unsubscribe....
> 

You need to be subscribed to post but you can disable receiving any mail 
if you want via settings on lists.openembedded.org

Once logged in, go to the group you want to modify (Your Groups, top 
left) then you'll see a Subscription menu on the left navigation panel, 
click to expand, then Settings. In there you'll have an Email Delivery 
section, just select No Email for example.

Cheers,
Quentin

Re: [OE-core] [yocto] Yocto Project Status 10 June. 2025 (WW23)

[Alexander Kanavin]

On Tue, 10 Jun 2025 at 16:46, Gyorgy Sarvari via
lists.openembedded.org <skandigraun=gmail.com@lists.openembedded.org>
wrote:
> >     The clang build time and size increases continue to cause
> >     significant concern.
> >
>
> Is there more info available on this somewhere? I'd be interested if
> there are any concrete recipes/configurations where this is showing
> prominently and could be used as a benchmark. Or is it more like an
> overall "lot of small things add up to a big one" issue?

Please trim quotation lines when replying.

It's simply the build time of clang-native and clang target recipes. A
huge pile of c++ code, probably the heaviest recipe to build in
oe-core. At the same time clang is a critical path item for mesa (and
thus, anything graphical).

Alex

Re: [OE-core] [yocto] Yocto Project Status 10 June. 2025 (WW23)

[Gyorgy Sarvari]

On 6/10/25 17:04, Alexander Kanavin wrote:
> On Tue, 10 Jun 2025 at 16:46, Gyorgy Sarvari via
> lists.openembedded.org <skandigraun=gmail.com@lists.openembedded.org>
> wrote:
>>>     The clang build time and size increases continue to cause
>>>     significant concern.
>>>
>> Is there more info available on this somewhere? I'd be interested if
>> there are any concrete recipes/configurations where this is showing
>> prominently and could be used as a benchmark. Or is it more like an
>> overall "lot of small things add up to a big one" issue?
> Please trim quotation lines when replying.
>
> It's simply the build time of clang-native and clang target recipes. A
> huge pile of c++ code, probably the heaviest recipe to build in
> oe-core. At the same time clang is a critical path item for mesa (and
> thus, anything graphical).
>
> Alex
Ahh, so this is not a regression that could be bisected, but the cost of
the new dependencies.
Thanks.

Re: [OE-core] [yocto] Yocto Project Status 10 June. 2025 (WW23)

[Etienne Cordonnier]

[-- Attachment #1: Type: text/plain, Size: 2839 bytes --]

A good starting point in my opinion is to check those 2 things:
- usage of "LLVM_TARGETS_TO_BUILD=" to reduce the number of archs being
built. This is quite low impact however.
- usage of "LLVM_PROJECTS = "clang;lld${LLDB}" to remove clang-tools-extra
from the build per default (last time I checked the recipe didn't build
when removing clang-tools-extra, so the recipe probably needs to be changed
for this to work). This was quite high impact on my test setup.

Étienne

On Tue, Jun 10, 2025 at 5:13 PM Gyorgy Sarvari via lists.yoctoproject.org
<skandigraun=gmail.com@lists.yoctoproject.org> wrote:

> On 6/10/25 17:04, Alexander Kanavin wrote:
> > On Tue, 10 Jun 2025 at 16:46, Gyorgy Sarvari via
> > lists.openembedded.org <skandigraun=gmail.com@lists.openembedded.org>
> > wrote:
> >>>     The clang build time and size increases continue to cause
> >>>     significant concern.
> >>>
> >> Is there more info available on this somewhere? I'd be interested if
> >> there are any concrete recipes/configurations where this is showing
> >> prominently and could be used as a benchmark. Or is it more like an
> >> overall "lot of small things add up to a big one" issue?
> > Please trim quotation lines when replying.
> >
> > It's simply the build time of clang-native and clang target recipes. A
> > huge pile of c++ code, probably the heaviest recipe to build in
> > oe-core. At the same time clang is a critical path item for mesa (and
> > thus, anything graphical).
> >
> > Alex
> Ahh, so this is not a regression that could be bisected, but the cost of
> the new dependencies.
> Thanks.
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#65502):
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproject.org_g_yocto_message_65502&d=DwIFaQ&c=ncDTmphkJTvjIDPh0hpF_4vCHvabgGkICC2epckfdiw&r=AhkbNonVuMIGRfPx_Qj9TsRih1DULJTKUkSGa66m67E&m=lNilmzl9NGIAACt9plQHwA29jv7jLEhRC5R5lTyL5jJkvrAUDPw5GGKk1simqOou&s=x-7lAyA_L3PnW-RnepCxBlSrFglTAHQcwyYBf0Bne_0&e=
> Mute This Topic:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproject.org_mt_113571342_7048771&d=DwIFaQ&c=ncDTmphkJTvjIDPh0hpF_4vCHvabgGkICC2epckfdiw&r=AhkbNonVuMIGRfPx_Qj9TsRih1DULJTKUkSGa66m67E&m=lNilmzl9NGIAACt9plQHwA29jv7jLEhRC5R5lTyL5jJkvrAUDPw5GGKk1simqOou&s=sUZCGh57KvDCIWkQnVVdz6FMUyMlpVa35X3BWlLWHyw&e=
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproject.org_g_yocto_unsub&d=DwIFaQ&c=ncDTmphkJTvjIDPh0hpF_4vCHvabgGkICC2epckfdiw&r=AhkbNonVuMIGRfPx_Qj9TsRih1DULJTKUkSGa66m67E&m=lNilmzl9NGIAACt9plQHwA29jv7jLEhRC5R5lTyL5jJkvrAUDPw5GGKk1simqOou&s=L-KOIYXVkjWWV7JqXS9AHATZCwsy-N_tdvXEXcBBf0M&e=
> [ecordonnier@snap.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 4892 bytes --]