That amounts to dropping x32 support because as soon as we remove these tests, it will bitrot. There is still some value in the project being able to support different architectures and different

Note: this update fails on x32 with | configure: error: unrecognized GNU build triplet linux-gnux32 This time I want to put my foot down and suggest that we just drop the whole x32 variant from the

This is not what I asked for (which was output of 'env'). Also, this shows the output of bitbake -c testimage, not of runqemu with nographic parameter. Alex

Hello Alexander, Please find the output file in attachment . Thanks

Hello Khem Raj , After rebooting i am getting same error .

I am using the AM572x evaluation module with the TI SDK, which uses the linaro toolchain. I am trying to enable UTF-8 so that I can use tmux. I am enabling it using the follow method: unset

maybe you should reboot the host machine, sometimes system updates without rebooting the machine can also result in such errors.

Hello everyone, Intel and WR YP QA is planning for QA execution for YP build yocto-4.1_M2.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

A build flagged for QA (yocto-4.1_M2.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.1_M2.rc1 Build hash information: bitbake:

Can I see the output of 'env' please? Alex

We are moving the hash equivalence server to dedicated servers. As part of the change we need to change the domain. Please update any BB_HASHSERVE_UPSTREAM variables from "typhoon.yocto.io:8687" to

Hello Alexander Yes I have tried that already but i am getting same error. If anyone could it would be great. Thanks in advance

You can try adding nographic option to runqemu if you do not need to see graphical output from your image. Alex

Hello Alexander, Thanks for your precious time . I applied you suggestion and it worked and i setup tap interface with following command: sudo

Richard, Quentin, I'd vote for such a solution, as it would allow to move on to newer versions of Sphinx without breaking existing documentation, causing a lot of extra work that's distracting us

Current Dev Position: YP 4.1 M3 Next Deadline: 22nd August 2022 YP 4.1 M3 Build Next Team Meetings: Bug Triage meeting Thursday July 21st 7:30 am PDT

This is optional, enabled by default, and allows easy extraction of patches and other information to one's local disk (no need to go over individual maintainer emails). Signed-off-by: Alexander

MIMEBase should not be used directly and results in sending raw binary data without encoding it with base64. Signed-off-by: Alexander Kanavin <alex@...> --- modules/utils/emailhandler.py |

Hi Quentin That's brilliant, thanks a lot! Just a few comments below... Don't forget to add your name to the authors at the beginning of the script and what the script does now. Thanks

Master branch of the yocto-docs now autogenerates the releases.rst file and the file therefore does not exist anymore. Signed-off-by: Quentin Schulz <foss+yocto@...> --- scripts/run-docs-build