yocto@lists.yoctoproject.org

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

Hi All, This is the full report for yocto-3.1.7.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone

By Sangeeta Jain · #53185 ·

Re: Yocto Dunfell: u-boot-fw-utils ERROR #imx6 #yocto #dunfell #swupdtae #libubootenv

Hi, Multiple ways to fix this. One is to switch to using dunfell branches for the BSP SW stack, if they are available. Alternatively you can use the old zeus based BSP SW stack but for that you need

By Mikko Rapeli <mikko.rapeli@...> · #53184 ·

Yocto Dunfell: u-boot-fw-utils ERROR #imx6 #yocto #dunfell #swupdtae #libubootenv

Hello, I'm actually migrating a yocto project zeus version to dunfell LTS to build my imx6 Linux system on this LTS release. Almost all works fine except the following message I try to understand when

By anthony.marchand@... · #53183 ·

[PATCH] [yocto-autobuilder-helper 2/2] scripts/utils.py: Add reporting for yocto-check-layer

The default behavior is to look for a bitbake command, which fails and produces a confusing output of [-1:]. [YOCTO #14208] Signed-off-by: Yi Fan Yu <yifan.yu@...> --- scripts/utils.py |

By Yi Fan Yu · #53182 ·

[PATCH] [yocto-autobuilder-helper 1/2] config.json: Add default MACHINE qemux86-64

This is the default oe-core MACHINE value. Prevent error-reporting tool to report simply False. It was seen in check-layer where the MACHINE wasn't specified. [YOCTO #14208] Signed-off-by: Yi Fan

By Yi Fan Yu · #53181 ·

M+ & H bugs with Milestone Movements WW16

All, YP M+ or high bugs which moved to a new milestone in WW16 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 14334 open-vm-tools not present in layer

By Stephen Jolley · #53180 ·

Enhancements/Bugs closed WW16!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count ross@... 2 akuster808@... 2 randy.macleod@... 2 richard.purdie@... 1 Grand Total 7 Thanks,

By Stephen Jolley · #53179 ·

Current high bug count owners for Yocto Project 3.4

All, Below is the list as of top 50 bug owners as of the end of WW16 of who have open medium or higher bugs and enhancements against YP 3.4. There are 135 possible work days left until the final

By Stephen Jolley · #53178 ·

Yocto Project Newcomer & Unassigned Bugs - Help Needed

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

By Stephen Jolley · #53177 ·

Re: [meta-gplv2] [PATCH] conf/distro: Add removal of btrfs-tools from util-linux ptest depends

Just to clarify, btrfs-tools has always had an LGPL-3.0 library (libbtrfsutil), the recipe just never declared it before. Upstream is relicensing that library to LGPL-2.1+, which should be done for

By Robert Joslyn · #53176 ·

[ANNOUNCEMENT] Yocto Project 3.3 (hardknott-25.0.0) is Released

Hello, We are pleased to announce the Yocto Project 3.3 (hardknott-25.0.0) Release is now available for

By Vineela · #53175 ·

Re: [meta-gplv2] [PATCH] conf/distro: Add removal of btrfs-tools from util-linux ptest depends

+1. Ross <richard.purdie@...> wrote:

By Ross Burton <ross@...> · #53174 ·

[meta-gplv2] [PATCH] conf/distro: Add removal of btrfs-tools from util-linux ptest depends

btrfs-tools has changed to LGPL-3.1 so to allow util-linux to build, remove the dependency from its ptest package. This may regress some ptests but keeps the gplv2 layer working. Signed-off-by:

By Richard Purdie · #53173 ·

Re: what to include in a "hardware bringup image"?

Hi Robert, Having the device tree compiler on the target has been useful for me in the past to check the actual content of the device tree using commands such as: * dtc -I fs -O dts

By Laurent Gauthier · #53172 ·

Re: what to include in a "hardware bringup image"?

Hi, ethtool can be used to check the network cable connection status and the autonegotiated link speed. That way you can make sure the port was soldered on correctly. Regards, Manuel Am Do, 15. Apr

By Manuel Wagesreither · #53171 ·

Wrong OELAYOUT_ABI in poky dunfell 3.1.6 suppresses message

Hi all, I recently upgraded my project from dunfell 3.1.5 to 3.1.6 and saw errors about pseudo path mismatches on various build machines. Removing TMPDIR solved the problem, but I did some digging to

By Nicolas Jeker · #53170 ·

[meta-networking][gatesgarth] keepalived exec_python_func() error

Hello, We are experiencing a build failures only on our build servers, but not using the same containerised build environment locally, which is confusing to say the least. We have already tried the

By Morgan Hill · #53169 ·

Verifying Yocto image in beaglebone

Hello I have built the Yocto gatesgarth image for Beaglebone black. Then I loaded the image in SD card and booted with beagle. Is there any way to check whether the image is built and working with

By Murugesh M · #53168 ·

Re: [yocto-rocko] : fsl-community-bsp X11 build touch screen calibration issue on iMX6UL

Hello , I am experiencing same issue for Rocko build rootfs with QT application for X11. I have tried the solution provided by Max , but it did not worked for me. as Per my log : Using calibration

By rohit jadhav · #53167 ·

[meta-security] [dunfell] [PATCH 3/3] initramfs-framework-ima: introduce IMA_FORCE

From: Ming Liu <liu.ming50@...> Introduce IMA_FORCE to allow the IMA policy be applied forcely even 'no_ima' boot parameter is available. This ensures the end users have a way to disable

By Ming Liu <liu.ming50@...> · #53166 ·

Messages