yocto@lists.yoctoproject.org

KERNEL_DEVICETREE cannot be appended?

Matthias Klein

#56529

Hello,

I am trying to add a device tree in a yocto based on the meta-raspberrypi layer.

Adding the device tree via a patch in a bbapend of the kernel recipe is no problem.

But all attempts to add the file in the local.conf of the variable KERNEL_DEVICETREE replace all other device trees.

I.e. on the device is then only my new file. It seems that the "append" works like a "="?

#KERNEL_DEVICETREE:raspberrypi3-64:append = " broadcom/my-custom-tree.dtb"

KERNEL_DEVICETREE:raspberrypi3-64 += " broadcom/my-custom-tree.dtb"

Is there any way to add the device tree?

Preferably without having to create a custom machine for it?

Best regards,
Matthias

Yocto Project Status WW12`22

Stephen Jolley

#56528

Current Dev Position: YP 3.5 M4

Next Deadline: 4th April. 2022 YP 3.5 M4 build

Next Team Meetings:

Bug Triage meeting Thursday Mar. 24th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
Monthly Project Meeting Tuesday Apr. 5th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 )
Weekly Engineering Sync Tuesday Mar. 22nd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 )
Twitch - See https://www.twitch.tv/theyoctojester

Key Status/Updates:

YP 3.1.15 is due to be released
YP 3.4.3 is due to build
We decided to merge in a number of python recipes which allow us to build the sphinx documentation. These are used by our documentation build process and many of the dependencies were things which likely should have been in core anyway.
There was a small performance tweak to bitbake’s codeparser cache code which seems to show around a 10% parsing speed improvement
We have continued to take other minimal impact upgrades and this is having a positive impact on CVE numbers. We are looking likely to take the recently released libtool 2.4.7 since this is similar to 2.4.6 but keeps us current with upstream. Some recipes may need to clear out stale libtool m4 macros if version mismatch errors are seen.
Toaster has seen further fixes and should be ready for release.
The AVAILABLE_LICENSES variable was removed since it has parsing overhead, had bad implications for task hashes and is no longer needed by any of the core code.
Some changes are being proposed to the documentation build process which should make version handling in releases easier and less error prone.
If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
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

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_Enhancements.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/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 us resolve CVE issues: CVE metrics

YP 3.5 Milestone Dates:

YP 3.5 M4 build date 2022/04/04
YP 3.5 M4 Release date 2022/04/29

Upcoming dot releases:

YP 3.1.15 is near release.
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 2680 (last week 2668) (https://wiki.yoctoproject.org/charts/combo.html)
OE-Core/Poky Patch Metrics

Total patches found: 1189 (last week 1204)
Patches in the Pending State: 340 (29%) [last week 340 (28%)]

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: sjolley.yp.pm@...

Re: SSTATE corruption

Alexander Kanavin

#56527

No and no.

Alex

Show quoted text

On Tue, 22 Mar 2022 at 14:48, Rusty Howell <rustyhowell@...> wrote:

Is the sstate cache sensitive to different releases and or the ordering of the bblayers?   We are upgrading our Yocto-based distro from dunfell to hardknott.  So for a while we will be building our distro on both releases.   Do we need to keep the sstate caches separate for these builds?

Another related question... Does changing the order of the bblayers corrupt the sstate cache (ie require a fresh sstate)?
Thanks

SSTATE corruption

Rusty Howell

#56526

Is the sstate cache sensitive to different releases and or the ordering of the bblayers? We are upgrading our Yocto-based distro from dunfell to hardknott. So for a while we will be building our distro on both releases. Do we need to keep the sstate caches separate for these builds?

Another related question... Does changing the order of the bblayers corrupt the sstate cache (ie require a fresh sstate)?

Thanks

#bitbake #sdk #bitbake #sdk

Hariom@...

#56525

Hi,

I came to know about the package feed feature, through which we can update the application in the target image by using apt-get commands. I just read about it on following link.
https://subscription.packtpub.com/book/virtualization-and-cloud/9781784395186/1/ch01lvl1sec21/setting-up-a-package-feed.

This link at high level ask user to set up a server for build/tmp/deploy/deb repo and updating /etc/apt/sources.list file at target with repo path.

I followed the steps and I am able to update the application on target using apt-get commands

For my work i use Yocto SDK for building the application software as a result i get application executable that i deploy in target using SCP command.

So my question is, Can I also setup a package feed for my target if I use Yocto SDK ? If yes, Can you please guide me how can I set it up and update the application easily on the target using apt-get commands.

Re: Strange sporadic build issues (incremental builds in docker container)

Alexander Kanavin

#56524

It's hard to say without the full error message, and the build
directory of the affected recipe. The easy way out is to simply wipe
tmp/ before each build.

Alex

Show quoted text

On Tue, 22 Mar 2022 at 09:51, Matthias Klein <matthias.klein@...> wrote:

Hello together,

I am building various kirkstone/master yoctos every night via Jenkins inside a Debian Bullseye Docker container.
These are incremental builds, reusing the build directory and sstate-cache of the previous build. The different yoctos are built in order. Each time, a new Docker container is launched.
(The same environment builds dunfell yoctos without any problems).

Now it happens sporadically that one of the builds aborts with the following message:

stderr: The series file no longer matches the applied patches. Please run 'quilt pop -a'.

They are usually alternating packages where the patch step fails with the above message. Also different yoctos are affected. But it is always the above message.
If I then restart the failed build it usually builds cleanly.

Does anyone have an idea in which direction the problem goes?

Many greetings,
Matthias

[meta-zephyr][PATCH] meta-zephyr-core: drop obsolete patches

Naveen Saini

#56523

These patches are not being applied and not required any more.

Already part of zephyr 2.7.1 and zephyr 3.0.0

Signed-off-by: Naveen Saini <naveen.kumar.saini@...>
---
 ...0001-cmake-added-missing-file-ext-to.patch | 42 ----------------
 ...rduino-nano-33-ble-storage-partition.patch | 49 -------------------
 2 files changed, 91 deletions(-)
 delete mode 100644 meta-zephyr-core/recipes-kernel/zephyr-kernel/files/0001-cmake-added-missing-file-ext-to.patch
 delete mode 100644 meta-zephyr-core/recipes-kernel/zephyr-kernel/files/arduino-nano-33-ble-storage-partition.patch

diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/files/0001-cmake-added-missing-file-ext-to.patch b/meta-zephyr-core/recipes-kernel/zephyr-kernel/files/0001-cmake-added-missing-file-ext-to.patch
deleted file mode 100644
index 6aeca14..0000000
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/files/0001-cmake-added-missing-file-ext-to.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-From 783c1f78c8e39751fe89d0883c8bce7336f55e94 Mon Sep 17 00:00:00 2001
-From: Torsten Rasmussen <Torsten.Rasmussen@...>
-Date: Thu, 19 Aug 2021 08:53:00 +0200
-Subject: [PATCH] cmake: added missing file ext to
- lv_font_dejavu_16_persian_hebrew.c
-
-CMake >= 3.20 requires file extensions explicitly added to source files.
-
-See CMP0115:
-> Starting in CMake 3.20, CMake prefers all source files to have their
-> extensions explicitly listed:
-
-In the CMakeLists.txt, the file lv_font_dejavu_16_persian_hebrew.c
-was added without its .c extension, causing never CMakes ti fail
-discovering the file.
-
-This has been fixed by correctly add the file as:
-lv_font_dejavu_16_persian_hebrew.c
-
-Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@...>
----
-Upstream-status: Accepted
-
- CMakeLists.txt | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/CMakeLists.txt b/CMakeLists.txt
-index 57b07c84..0f433edc 100644
---- a/CMakeLists.txt
-+++ b/CMakeLists.txt
-@@ -58,7 +58,7 @@ zephyr_library_sources(
-     src/lv_misc/lv_utils.c
- 
-     src/lv_font/lv_font.c
--    src/lv_font/lv_font_dejavu_16_persian_hebrew
-+    src/lv_font/lv_font_dejavu_16_persian_hebrew.c
-     src/lv_font/lv_font_fmt_txt.c
-     src/lv_font/lv_font_loader.c
-     src/lv_font/lv_font_montserrat_12.c
--- 
-Gitee
-
diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/files/arduino-nano-33-ble-storage-partition.patch b/meta-zephyr-core/recipes-kernel/zephyr-kernel/files/arduino-nano-33-ble-storage-partition.patch
deleted file mode 100644
index 4568a41..0000000
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/files/arduino-nano-33-ble-storage-partition.patch
+++ /dev/null
@@ -1,49 +0,0 @@
-commit 6c9945aafa00c09149e2052a9c2bccad16dd1d8a
-Author: Stefan Schmidt <stefan.schmidt@...>
-Date:   Fri May 7 11:47:44 2021 +0200
-
-    boards/arduino_nano_33_ble: add storage partition at end of flash
-    
-    Change default partition table to allow for application which need
-    storage. One use case is running the OpenThread integration which has
-    a dependency on this.
-
-    Upstream-Status: Backported [https://github.com/zephyrproject-rtos/zephyr/commit/6c9945aafa00c09149e2052a9c2bccad16dd1d8a]
-    
-    Signed-off-by: Stefan Schmidt <stefan.schmidt@...>
-    Signed-off-by: Naveen Saini <naveen.kumar.saini@...>
-
-diff --git a/boards/arm/arduino_nano_33_ble/arduino_nano_33_ble.dts b/boards/arm/arduino_nano_33_ble/arduino_nano_33_ble.dts
-index d09b66ec43..d11d800eb5 100644
---- a/boards/arm/arduino_nano_33_ble/arduino_nano_33_ble.dts
-+++ b/boards/arm/arduino_nano_33_ble/arduino_nano_33_ble.dts
-@@ -44,15 +44,27 @@
- 
- 		boot_partition: partition@0 {
- 			label = "sam-ba";
--			reg = <0x0 0x10000>;
-+			reg = <0x00000000 0x00010000>;
- 			read-only;
- 		};
- 
- 		code_partition: partition@10000 {
- 			label = "code";
--			reg = <0x10000 0xf0000>;
-+			reg = <0x00010000 0x000e8000>;
- 			read-only;
- 		};
-+
-+		/*
-+		 * The flash starting at 0x000f8000 and ending at
-+		 * 0x000fffff is reserved for use by the application.
-+		 *
-+		 * Storage partition will be used by FCB/LittleFS/NVS
-+		 * if enabled.
-+		 */
-+		storage_partition: partition@f8000 {
-+			label = "storage";
-+			reg = <0x000f8000 0x00008000>;
-+		};
- 	};
- };
- 
-- 
2.17.1

Strange sporadic build issues (incremental builds in docker container)

Matthias Klein

#56522

Hello together,

I am building various kirkstone/master yoctos every night via Jenkins inside a Debian Bullseye Docker container.
These are incremental builds, reusing the build directory and sstate-cache of the previous build. The different yoctos are built in order. Each time, a new Docker container is launched.
(The same environment builds dunfell yoctos without any problems).

Now it happens sporadically that one of the builds aborts with the following message: 

stderr: The series file no longer matches the applied patches. Please run 'quilt pop -a'.

They are usually alternating packages where the patch step fails with the above message. Also different yoctos are affected. But it is always the above message.
If I then restart the failed build it usually builds cleanly.

Does anyone have an idea in which direction the problem goes?

Many greetings,
Matthias

M+ & H bugs with Milestone Movements WW12

Stephen Jolley

#56521

All,

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

Priority	Bug ID	Short Description	Changer	Owner	Was	Became
Medium+	5389	bitbake/lib/bb/fetch2: filename too long	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	10061	Ctrl+C during BB_HASHCHECK_FUNCTION execution does not interrupt processing nicely	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	10731	bitbake --observe-only doesn't work with memres	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	11781	bitbake --observe-only may get KeyError	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	11899	broken 'bitbake --status-only' and 'bitbake -m'	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	12290	cross recipe kernel module dependency generation stopped working	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	12342	lib32-core-image-sato -ctestimage failed due to wrong package names	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	12374	do_rootfs failed when len(TMPDIR) == 410	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	12367	moving or removing tmp breaks persistent bitbake server	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	12760	CMake Toolchain File Has Wrong Module Path	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	12963	nativesdk-opkg prefixes all internal paths with $SDKPATH and won't work	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13008	toaster testing	david.reyna@...	david.reyna@...	3.5 M3	3.6 M1
	13109	Implement CPE to package to Release mapping	david.reyna@...	david.reyna@...	3.5 M3	3.6 M1
	13181	persist_data sqlite database mixed with forking is irreparably broken	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13236	sstate for host native packages	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13279	Make sure users/groups exist for package_write_* tasks	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13285	YoctoProject Compatibility script improvements needed	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13338	SDK build fails if image contains bash	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13353	bitbake git fetcher does not honour BB_FETCH_PREMIRRORONLY	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13419	recipes that add users to groups cannot rely on other recipes creating those groups (when population from sstate happens)	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13425	Add bblock and bbunlock helper tools	randy.macleod@...	newcomer@...	3.5 M3	3.6 M1
	13463	test linux-yocto-rt kernels too	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13550	username/password specified to gitsm:// does not get propagated to submodules	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13674	master dnf failures on qemumips	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13705	master] bitbake and hashserve.sock left behind when ^C a build	randy.macleod@...	unassigned@...	3.5 M3	3.5 M4
	13722	Debugging With the GNU Project Debugger enhancements	randy.macleod@...	john.kaldas.enpj@...	3.5 M3	3.5 M4
	13735	Performing Automated Runtime Testing with a custom hardware target / BeagleBone Hardware target	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13819	No clue when CONNECTIVITY_CHECK_URIS is unaccessible	randy.macleod@...	newcomer@...	3.5 M3	3.6 M1
	13843	bitbake worker stuck using 100% cpu on aborted build	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13868	Python cache files get lost in packages	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13897	POSTINST_INTERCEPTS_DIR broken by undocumented POSTINST_INTERCEPTS_PATHS since thud	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13910	Intermittent host UID contamination highlighted by devtool tests	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13919	Multi License GPLv3 -lic cannot be installed into the image because it has incompatible license	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13920	uninative tarball license compliance in ESDK	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13934	Apparent duplication of libtirpc package causes failure in "bitbake linux-yocto -c menuconfig"	randy.macleod@...	unassigned@...	3.5 M3	3.5 M4
	13954	Invalid layerindex data causing backtrace in `bitbake-layers layerindex-fetch`	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	13964	bitbake stuck doing nothing after hitting disk-full condition	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14015	URL Arguments in MIRROR/PREMIRROR get encoded	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14020	environment-setup script in multilib eSDK doesn't work for multilib variant	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14066	bitbake core-image-base -c populate_sdk fails when image contains bash, core-utils and package_deb is used	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14099	PACKAGE_EXCLUDE not removing packages when PACKAGE_CLASSES = "package_deb"	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14127	cve-check falsely indicates a vulnerabily to be patched	randy.macleod@...	unassigned@...	3.5 M3	3.5 M4
	14126	resolvconf incompatible with busybox flock	randy.macleod@...	newcomer@...	3.5 M3	3.5 M4
	14136	If u-boot defconfig is incomplete, 'bitbake u-boot -c configure' hangs and eats all memory	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14150	devtool: modify: fails for gstreamer1.0-plugins-good	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14151	devtool build fails for python3	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14154	yocto-check-layer fails incorrectly with kernel hash changes	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14155	yocto-check-layer fails with hash changes if license added	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14157	git fetcher: consider using different git commands for repo packing, eliminating "git pack-redundant"	randy.macleod@...	newcomer@...	3.5 M3	3.6 M1
	14206	oe-selftest perl errors on rpm based distros	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14218	Recipe rebuilds can contaminate builds	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14274	dnf parselogs failed on qemux86-64 due to networking error	randy.macleod@...	unassigned@...	3.5 M3	3.5 M4
					3.5 M4	3.6 M1
	14383	archiver.bbclass:do_ar_mirror copies entire contents of ${DL_DIR} to ${WORKDIR} when used with npm.bbclass	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14386	patchelf breaks go -native executables	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14446	devtool add malformed PACKAGECONFIG	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14461	devtool sdk-update do not clean old version files	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14462	devtool sdk-update does not update sstate-cache	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14520	A qemuboot.conf file isn't generated if the rootfs wasn't modified	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14528	remove floppy controller from qemu	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14553	insane.bbclass: host-user-contaminated QA doesn't skip the home directory	randy.macleod@...	unassigned@...	3.5 M3	3.5 M4
	14609	Unable to build on a host with FIPS mode enabled	randy.macleod@...	unassigned@...	3.5 M3	3.6 M1
	14642	Yocto-check-layer add patch Upstream-Status check	randy.macleod@...	unassigned@...	3.5 M3	3.5 M4

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

* Email: sjolley.yp.pm@...

Enhancements/Bugs closed WW12!

Stephen Jolley

#56520

All,

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

Who	Count
randy.macleod@...	3
michael.opdenacker@...	1
sundeep.kokkonda@...	1
ross@...	1
Grand Total	6

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

* Email: sjolley.yp.pm@...

Current high bug count owners for Yocto Project 3.5

Stephen Jolley

#56519

All,

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

Who	Count
michael.opdenacker@...	34
ross@...	28
randy.macleod@...	19
david.reyna@...	14
tim.orling@...	13
sakib.sajal@...	13
bruce.ashfield@...	12
richard.purdie@...	10
mhalstead@...	9
saul.wold@...	7
trevor.gamblin@...	7
bluelightning@...	6
kai.kang@...	5
chee.yang.lee@...	4
JPEWhacker@...	4
hongxu.jia@...	4
jon.mason@...	3
Qi.Chen@...	3
pgowda.cve@...	2
mshah@...	2
alejandro@...	2
akuster808@...	2
mostthingsweb@...	1
andrei@...	1
pavel@...	1
open.source@...	1
thomas.perrot@...	1
Martin.Jansa@...	1
mingli.yu@...	1
liezhi.yang@...	1
sundeep.kokkonda@...	1
yi.zhao@...	1
mark.hatle@...	1
aehs29@...	1
jay.shen.teoh@...	1
matthewzmd@...	1
TicoTimo@...	1
pokylinux@...	1
jaskij@...	1
raj.khem@...	1
martin.beeger@...	1
john.kaldas.enpj@...	1
nicolas.dechesne@...	1
alexandre.belloni@...	1
Grand Total	225

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

* Email: sjolley.yp.pm@...

Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley

#56518

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 399 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.5" and then “3.6”.

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.pm@...) 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.pm@...

Re: Multiconfig dependency

Oleh Kravchenko

#56517

Hello Manuel,
Thank you for your reply.

It isn't missing.
Here is a cut from manual:

A "default" configuration already exists by definition. This configuration is named: "" (i.e. empty string) and is defined by the variables coming from your local.conf file.


21.03.22 08:02, Manuel Wagesreither пише:

Show quoted text

Hi Oleh,
Am Do, 17. Mär 2022, um 21:29, schrieb Oleh Kravchenko:
  do_install[mcdepends] = "mc:initramfs::core-image-minimal:do_image_complete"I have zero practical experience with multiconfig, but isn't this missing one argument?
See here:
https://github.com/JPEWdev/meta-multiconfig-demos/blob/main/recipes-misc/arthur-embed/arthur-embed.bb#L21https://youtu.be/YvtlGjWrL-M?list=PLD4M5FoHz-TwWYbaJwduH8ZYNYvva76QQ&t=5030
Regards,
Manuel

Re: [yocto-autobuilder-helper] [PATCH] scripts/run-docs-build: Support auto generation of switchers.js and poky.yaml

Michael Opdenacker

#56516

Hi Richard,

On 3/19/22 16:28, Richard Purdie wrote:
This uses the set_versions.py script from the docs master branch to handle
creation of the swictchers.js version information as well as the data in
poky.yaml.

This allows patches to those sections of the docs to be dropped.

It is assumed the patch to use set_versions is applied to the docs transitions
branch so that it's switchers.js files no longer need to be tweaked.

This does lead to user visible changes on the website:

- Older versioned released docs gain their current version and the
  latest version listed in the switcher rather than being unlisted
- The list of releases is normally filtered down to our active ones
  (hardknott, honister and dev right now)
- 3.3's doc references to gatesgath are corrected to hardknott
- Docs for unversioned release branches (not linked on the website) now
  use 3.1.999 versioning instead of confusing them with the last relased version
- 3.1.13 refers to 3.1.13 instead of 3.1.12

all of which seem to be reasonable improvements.

The big advantage of these changes is that with a single change to the script
in the master branch, the right thing should happen for all the current docs
and at release time, only a docs rebuild should need to be triggered after tags
are pushed.

Signed-off-by: Richard Purdie <richard.purdie@...>
---
 ...01-releases-update-to-include-3.1.14.patch | 41 ------------
 ...umentation-update-for-3.1.14-release.patch | 23 -------
 ...umentation-prepare-for-3.3.5-release.patch | 53 ---------------
 .../0001-conf-update-for-release.patch        | 17 -----
 ...honister-updates-for-recent-releases.patch | 67 -------------------
 ...001-releases-update-to-include-3.4.2.patch | 63 -----------------
 .../0001-conf-update-for-release.patch        | 17 -----
 scripts/run-docs-build                        | 24 +++++--
 8 files changed, 20 insertions(+), 285 deletions(-)
 delete mode 100644 scripts/docs-build-patches/yocto-3.1.14/0001-releases-update-to-include-3.1.14.patch
 delete mode 100644 scripts/docs-build-patches/yocto-3.4.2/0001-releases-update-to-include-3.4.2.patch
Looks good to me. Thanks for the simplification.

Reviewed-by: Michael Opdenacker <michael.opdenacker@...>
Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: [PATCH yocto-autobuilder-helper 6/6] scripts: run-docs-build: factor out yocto-docs tags and branches building

Michael Opdenacker

#56515

On 3/18/22 17:36, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>

Except patching which is specific to tags and yocto- tag prefix
stripping, the logic is identical, so let's merge both loops together.

Cc: Quentin Schuls <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
 scripts/run-docs-build | 36 ++++++++++++------------------------
 1 file changed, 12 insertions(+), 24 deletions(-)
Reviewed-by: Michael Opdenacker <michael.opdenacker@...>
Thanks for making the script much more readable :-)
Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: [PATCH yocto-autobuilder-helper 5/6] scripts: run-docs-build: simplify sphinx-buildable yocto-docs tag list fetching

Michael Opdenacker

#56514

On 3/18/22 17:36, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>

The commit that introduced Sphinx support in yocto-docs is
01dd5af7954e24552aca022917669b27bb0541ed. Any tag containing this commit
is buildable by sphinx.

Dunfell tags don't all have Sphinx support. However, all tags containing
the introducing commit c25fe058b88b893b0d146f3ed27320b47cdec236 are
buildable by sphinx.

Therefore, let's just list all tags which contains either of those two
commits instead of the complex series of pipes and shell commands.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
 scripts/run-docs-build | 36 +++++++++++++++++-------------------
 1 file changed, 17 insertions(+), 19 deletions(-)
Thanks for the simplification!
Reviewed-by: Michael Opdenacker <michael.opdenacker@...>
Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: [PATCH yocto-autobuilder-helper 4/6] scripts: run-docs-build: automatically build new yocto-docs branches

Michael Opdenacker

#56513

On 3/18/22 17:36, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>

Since commit 01dd5af7954e24552aca022917669b27bb0541ed, all later
releases of yocto-docs can be built with Sphinx. Instead of manually
updating this list, let's have git return the list of remote branches
which contains the commit.

dunfell branch was initially released without Sphinx support but was
later patched, hence why it's explicitly listed.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
 scripts/run-docs-build | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)
Reviewed-by: Michael Opdenacker <michael.opdenacker@...>
Many thanks
Michael.
-- 

Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: [PATCH yocto-autobuilder-helper 3/6] scripts: run-docs-build: factor out all yocto-docs branches building

Michael Opdenacker

#56512

On 3/18/22 17:36, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>

master, master-next and transition only differ from other branches by
their output directory name. Let's put everything in common and only
have a check on whether the branch is master, master-next or transition
and modify the output dir in those cases.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
 scripts/run-docs-build | 35 +++++++++++------------------------
 1 file changed, 11 insertions(+), 24 deletions(-)
Reviewed-by: Michael Opdenacker <michael.opdenacker@...>
Thanks!
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: [PATCH yocto-autobuilder-helper 2/6] scripts: run-docs-build: automatically build new Bitbake branches

Michael Opdenacker

#56511

On 3/18/22 17:36, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>

Since commit 84ccba0f4aff91528f764523fe1205a354c889ed, docs of all later
releases can be built with Sphinx. Instead of manually updating this
list, let's have git return the list of remote branches which contains
this commit.

1.46 branch was initially released without Sphinx support but was later
patched, hence why it's explicitly listed.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
 scripts/run-docs-build | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index f7b5f97..d8d77c7 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -37,7 +37,12 @@ mkdir $outputdir/bitbake
 # https://lists.yoctoproject.org/g/docs/message/2193
 # We copy the releases.rst file from master so that all versions of the docs
 # see the latest releases.
-for branch in 1.46 1.48 1.50 1.52 master master-next; do
+first_sphinx_commit=84ccba0f4aff91528f764523fe1205a354c889ed
+for branch in 1.46 $(git branch --remote --contains "$first_sphinx_commit" --format '%(refname:lstrip=3)'); do
+    if [ "$branch" = "HEAD" ]; then
+        continue
+    fi
+
     echo Building bitbake $branch branch
     git checkout $branch
     git checkout master releases.rst
Very good idea! I learned a new git option today.
Reviewed-by: Michael Opdenacker <michael.opdenacker@...>
Thanks!
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: [PATCH yocto-autobuilder-helper 1/6] scripts: run-docs-build: factor out all bitbake branches building

Michael Opdenacker

#56510

Hi Quentin

On 3/18/22 17:36, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>

master and master-next only differ from other branches by their output
directory name. Let's put everything in common and only have a check on
whether the branch is master or master-next and modify the output dir in
those cases.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>Thanks for the useful patch!

Reviewed-by: Michael Opdenacker <michael.opdenacker@...>
Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com