[yocto] M+ & H bugs with Milestone Movements WW05

[Stephen Jolley]

All,

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


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  12368

persistent bitbake server does not re-parse if previous build was ctrl+C'd

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

3.5 M2

3.5 M3


 

  12723

mysql requires unicode and char length filtering

david.re...@windriver.com

david.re...@windriver.com

3.5 M2

3.5 M3


 

  13103

[Bug][QA 2.7 M1 rc1][Toaster] "Recipes" table  and  "machines" table are not 
getting populated after clicking on imported layer as well as after clicking 
Machines Tab on project page

david.re...@windriver.com

david.re...@windriver.com

3.5 M2

3.5 M3


 

  13123

package.PackageTests.test_gdb_hardlink_debug failed

randy.macl...@windriver.com

randy.macl...@windriver.com

3.5 M2

3.5 M3


 

  13278

If git protocol doesn't work, you get a tar.gz clone from PREMIRROR which has 
git protocol origin

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

3.5 M2

3.5 M3


 

  13424

devupstream doesn't work with mutilib

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

3.5 M2

3.5 M3


 

  13599

Enhancement: Detect variables that shouldn't be defined in image scope, but in 
global (distro) scope

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

3.5 M2

3.5 M3


 

  13888

Toaster is not starting for Django-3

david.re...@windriver.com

david.re...@windriver.com

3.5 M2

3.5 M3


 

  13908

segfault in mb-wm on qemux86-64 intermittently

randy.macl...@windriver.com

r...@burtonini.com

3.5 M2

3.5 M3


 

  14085

Toaster UI should know when bitbake crashed

david.re...@windriver.com

david.re...@windriver.com

3.5 M2

3.5 M3


 

  14156

fetch/gitsm: submodules are fetched as mirrored and not working as expected

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

3.5 M2

3.5 M3


 

  14163

AB-INT PTEST ARM: libevent arm ptest intermittent failure

randy.macl...@windriver.com

r...@burtonini.com

3.5 M2

3.5 M3


 

  14165

AB-INT PTEST: strace ptest intermittent failure in qual_fault-syscall.test

randy.macl...@windriver.com

randy.macl...@windriver.com

3.5 M2

3.5 M3


 

  14311

AB-INT PTEST: valgrind drd/tests ptest intermittent failure

randy.macl...@windriver.com

yf...@uwaterloo.ca

3.5 M2

3.5 M3


 

  14381

AB-INT PTEST ARM: openssl ptest intermittent failure

randy.macl...@windriver.com

r...@burtonini.com

3.5 M2

3.5 M3


 

  14385

mode of sstate files created under pseudo

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

3.5 M2

3.5 M3


 

  14388

AB-INT PTEST: valgrind failed  helgrind/tests/hg05_race2

randy.macl...@windriver.com

randy.macl...@windriver.com

3.5 M2

3.5 M3


 

  14486

qemu rootfs copy is taking too much time

randy.macl...@windriver.com

randy.macl...@windriver.com

3.5 M2

3.5 M3


 

  14522

qemuppc doesn't shutdown within timeout (serial console issues)

randy.macl...@windriver.com

sakib.sa...@windriver.com

3.5 M2

3.5 M3


 

  14560

AB-INT PTEST ARM: tcl timer.test failure

randy.macl...@windriver.com

r...@burtonini.com

3.5 M2

3.5 M4


 

  14556

Running dates tests in systemd images causes loss of networking

randy.macl...@windriver.com

r...@burtonini.com

3.5 M2

3.5 M4


 

  14564

parselogs.ParseLogsTest.test_parselogs udev failure

randy.macl...@windriver.com

trevor.gamb...@windriver.com

3.5 M2

3.5 M3


 

  14596

AB-INT PTEST ARM: strace ptest intermittent failure in strace-T.test

randy.macl...@windriver.com

r...@burtonini.com

3.5 M2

3.5 M3


 

 

[yocto] Enhancements/Bugs closed WW05!

[Stephen Jolley]

All,

 

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


Who

Count


mhalst...@linuxfoundation.org

1


trevor.gamb...@windriver.com

1


randy.macl...@windriver.com

1


richard.pur...@linuxfoundation.org

1


Grand Total

4

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

[Stephen Jolley]

All,

 

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


Who

Count


r...@burtonini.com

38


michael.opdenac...@bootlin.com

35


randy.macl...@windriver.com

25


david.re...@windriver.com

22


bruce.ashfi...@gmail.com

17


sakib.sa...@windriver.com

13


tim.orl...@konsulko.com

13


trevor.gamb...@windriver.com

12


richard.pur...@linuxfoundation.org

10


mhalst...@linuxfoundation.org

9


kai.k...@windriver.com

7


bluelightn...@bluelightning.org

6


saul.w...@windriver.com

6


jpewhac...@gmail.com

4


hongxu@windriver.com

4


chee.yang@intel.com

4


qi.c...@windriver.com

3


jon.ma...@arm.com

3


alejan...@enedino.org

3


kiran.surend...@windriver.com

2


alexandre.bell...@bootlin.com

2


pokyli...@reliableembeddedsystems.com

2


raj.k...@gmail.com

2


ms...@mvista.com

2


pgowda@gmail.com

2


shac...@vdoo.com

1


yf...@uwaterloo.ca

1


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

1


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

1


nicolas.deche...@linaro.org

1


yoctoproj...@neumann-web.eu

1


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

1


jay.shen.t...@intel.com

1


kexin@windriver.com

1


akuster...@gmail.com

1


thomas.per...@bootlin.com

1


martin.ja...@gmail.com

1


liezhi.y...@windriver.com

1


aeh...@gmail.com

1


ticot...@gmail.com

1


matthew...@posteo.net

1


mingli...@windriver.com

1


yi.z...@windriver.com

1


mostthings...@gmail.com

1


Grand Total

265

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

[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 398
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.5, "3.6", "3.99" and "Future", the more pressing/urgent
issues being in "3.4" and then "3.5".

 

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

[yocto] Yocto Project Status WW05`22

[Stephen Jolley]

Current Dev Position: YP 3.5 M3

Next Deadline: 21th Feb. 2022 YP 3.5 M3 build

 

Next Team Meetings:

*   Bug Triage meeting Thursday Feb. 3rd 7:30 am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday Feb. 1st at 8 am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday Feb. 8th at 8 am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 3.5 M2 has passed QA with one bug highlighted (14708). Due to
vacations in Asia the release, if approved, will be made next week.
*   YP 3.1.14 is ready for QA but the release will also be delayed until
next week.
*   Upstream glibc are now planning to remove prelink support in 2.36. I
think we will still want to remove prelink from OE-Core before our next
release though, particularly as it is an LTS.
*   An
 email
proposing inclusive language changes for bitbake and OE-Core has been sent
to the community for review. The aim is to implement this before M3.
*   We are seeing networking issues during image testing on the
centos8/stream8 workers, possibly due to recent changes in the distro. Help
with debugging this welcome.
*   We have also realized there is an issue with hash equivalence where
the current mechanism will not account for different headers inside the
sysroot added through indirect dependencies (e.g. linux-libc-headers via
glibc). This means something like rtcwake in util-linux which uses rtc.h can
have differing debug symbols due to differing line numbers yet otherwise be
identical. There is a potential fix with downsides in master-next.
*
 CVE metrics are still under control for master with
pending patches accounted for (thanks Ross!) but work still remains on the
various stable branches which have high counts.
*   Intermittent issues continue to be at record high levels and help is
very much welcome in trying to resolve them. 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

In particular, we're struggling to understand the intermittent network issue
with external hosts we're seeing very occasionally.

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.5. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhan
cements.2FBugs
*   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/main
tainers.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.

 

YP 3.5 Milestone Dates:

*   YP 3.5 M2 is out of QA
*   YP 3.5 M3 build date 2022/02/21
*   YP 3.5 M3 Release date 2022/03/04
*   YP 3.5 M4 build date 2022/04/04
*   YP 3.5 M4 Release date 2022/04/29

 

Upcoming dot releases:

*   YP 3.1.14 is built
*   YP 3.1.14 Release date 2022/02/04
*   YP 3.4.2 build date 2022/02/07
*   YP 3.4.2 Release date 2022/02/18
*   YP 3.3.5 build date 2022/02/14
*   YP 3.3.5 Release date 2022/02/25
*   YP 3.1.15 build date 2022/03/14
*   YP 3.1.15 Release date 2022/03/25
*   YP 3.4.3 build date 2022/03/21
*   YP 3.4.3 Release date 2022/04/01
*   YP 3.3.6 build date 2022/03/28
*   YP 3.3.6 Release date 2022/04/08
*   YP 3.1.16 build date 2022/04/25
*   YP 3.1.16 Release date 2022/05/06

 

Tracking Metrics:

*   WDD 2705 (last week 2700) (

https://wiki.yoctoproject.org/charts/combo.html)
*   OE-Core/Poky Patch Metrics

*   Total patches found: 1236 (last week 123.)
*   Patches in the Pending State: 342 (28%) [last week 340 (28%)]

 

The Yocto Project's technical governance is through its Tec

[yocto] QA notification for completed autobuilder build (yocto-3.1.14.rc1)

[Richard Purdie]

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


https://autobuilder.yocto.io/pub/releases/yocto-3.1.14.rc1


Build hash information: 

bitbake: be6ecc160ac4a8d9715257b9b955363cecc081ea
meta-agl: 7a644d636237459c54128a71d083cb6f9e1b8e60
meta-arm: ce535dfb96de4d2529f091d7d85a7172c626001c
meta-aws: 9979cfa676105cb68cfadfdaeabf044d7c919319
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 87984115eb6ed1a4c17204629dcb100f6b76fe82
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
meta-openembedded: ab9fca485e13f6f2f9761e1d2810f87c2e4f060a
oecore: f3be01483b01c88f8c4ba24ca73ccf1bcc33665c
poky: bba323389749ec3e306509f8fb12649f031be152



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

Re: [yocto] How to prevent auto start of matchbox-terminal at boot?

[Dave Beal via lists.yoctoproject.org]

Thanks, Alex!  That was it.  The script that started the matchbox-terminal is 
/usr/bin/mini-x-session.  I just edited this file and commented out the 
terminal line and another line that was setting my display to an incorrect 
resolution.

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

[yocto] Where setup KCONF_AUDIT_LEVEL value

[Mauro Ziliani via lists.yoctoproject.org]

Hi all.

The KCONF_AUDIT_LEVEL variable must be setup in a .conf file or I can 
change it in a recipe?



I try to understand why my file defconfig is not used my kernel configurator


MZ


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

Re: [yocto] boot script for barebox in build/deploy/images/$IMAGE_NAME/ directory

[Gary Huband via lists.yoctoproject.org]

In Zeus I have a recipe that installs the file (a u-boot boot.scr for me):

install -m 0644 boot.scr ${DEPLOYDIR}

Make sure the recipe is included in your image.  Then in my machine conf:

IMAGE_BOOT_FILES = "zImage oftree imx7d-phyboard-zeta-004.dtb 
imx7d-phyboard-zeta-004-m4.dtb boot.scr"

Gary


From: yocto@lists.yoctoproject.org  on behalf of 
Ivan Riabtsov via lists.yoctoproject.org 

Sent: Saturday, January 29, 2022 10:47 PM
To: Yocto-mailing-list 
Subject: [yocto] boot script for barebox in build/deploy/images/$IMAGE_NAME/ 
directory

Hello everyone, I need to put the boot.sh file in the
build/deploy/images/$IMAGE_NAME/ directory during the build, how can I
do this using the yocto build system?

Gary Huband
Sr. Software and Systems Engineer

Office: 434.284.8071 x720
Direct: 434.260.4995
g...@missionsecure.com

Follow Us!
LinkedIn  |  
Blog
  |  
Website

: : : : : : : : : : : : : : : : : : : : : : : : : : :

[MSi]

This email and any files transmitted with it are confidential and proprietary 
and intended solely for the use of the individual or entity to whom they are 
addressed. Any dissemination, distribution or copying of this communication is 
strictly prohibited without our prior permission. If you received this in 
error, please contact the sender and delete the material from any computer.


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

Re: [yocto] Fetch private gitlab repo using ssh with Yocto recipe #bitbake

[Sourabh Hegde]

Hello @Nicolas @Erik @Khem,

Update from my side:

After following some discussion from other posts, I added "config" file.

~/.ssh/config:

Host git.example.com
HostName git.example.com
User git
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519.pub
# LogLevel DEBUG3

Then I did "eval `ssh-agent -s`"

Then doing "ssh-add ~/.ssh/id_ed25519.pub" results in:

@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE!  @
@@@
Permissions 0644 for '/root/.ssh/id_ed25519.pub' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.

Whereas the permissions are set as:

ls -l -a ~/.ssh

-rw-r--r-- 1 root root  157 Jan 31 10:48 config
-rw--- 1 root root  464 Jan 20 15:26 id_ed25519
-rw-r--r-- 1 root root  109 Jan 20 15:26 id_ed25519.pub
-rw-r--r-- 1 root root  888 Jan 26 08:43 known_hosts

"ssh-agent" is running

ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-lcft54A4nriC/agent.2833; export SSH_AUTH_SOCK;
SSH_AGENT_PID=2834; export SSH_AGENT_PID;
echo Agent pid 2834;

After doing these changes, when I try to "ssh -v git.example.com" to test the 
connection before running bitbake, I get

OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f  31 Mar 2020
debug1: Reading configuration data /root/.ssh/config
debug1: /root/.ssh/config line 1: Applying options for git.example.com
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to git.example.com [116.203.241.xxx] port 22.
debug1: connect to address 116.203.241.xxx port 22: Connection refused
ssh: connect to host git.example.com port 22: Connection refused

I don't understand what is the issue here.

@Nicolas Can you please let me know where and how to run below commands? Do I 
need to run them every time before fetching from gitlab?
-v $SSH_AUTH_SOCK:/ssh.socket \
-e SSH_AUTH_SOCK=/ssh.socket \

And also I already have "known_hosts" file with matching entries for key/agent 
pair.

Can you please let me know how to make this working?

Your help will be much appreciated.

Thanks in advance.

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

Re: [yocto] How to prevent auto start of matchbox-terminal at boot?

[Alexander Kanavin]

The logs reveal that 'packagegroup-core-x11 packagegroup-core-x11-base
packagegroup-core-x11-xserver' are all installed. x11-base pulls in
recipes-graphics/mini-x-session/mini-x-session_0.1.bb which starts a
minimal session with a terminal. You should either drop x11-base, or tweak
mini-x-session script to do what you want.

Alex

On Mon, 31 Jan 2022 at 01:22, Dave Beal via lists.yoctoproject.org  wrote:

> Thanks, Alex.  The log file is attached.
>
> By the way, I'd be happy with a solution that involves changing a file on
> the target system after the Yocto build is complete.  The fix doesn't need
> to be in the Yocto build.
>
> = Dave
>
>
> 
>
>

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