linux/poky.git/meta/classes, branch yocto-4.0.5

classes: files: Extend overlayfs-etc class

2022-10-29T15:32:24+00:00

Add the ability to expose the lower layer of /etc when mounting overlay. This is the similar to what overlayroot script from initramfs-framework does. By default, this option is turned off to keep an old behavior intact. (From OE-Core rev: 6ad25304abefcbe538db7745e17ac213fa7d0719) Signed-off-by: Vyacheslav Yurkov Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 791e8a8bacce5a7f31f4d7bcbfb17df2967fd258) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

own-mirrors: add crate

2022-10-20T14:36:02+00:00

Support downloading crate files from a mirror at SOURCE_MIRROR_URL. (From OE-Core rev: d1edc5882955508827a19c4f507d97dca398f3fa) Signed-off-by: Adrian Freihofer Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

image_types_wic.bbclass: fix cross binutils dependency

2022-10-20T14:36:02+00:00

Enable multilib and wic at the same time and we'll meet the following error. ERROR: Nothing PROVIDES 'virtual/i686-wrsmllib32-linux-binutils' Adjust the dependency to take multilib into consideration. (From OE-Core rev: f5713addbe47eb6c998cfe1514a537acbd367c3e) Signed-off-by: Chen Qi Signed-off-by: Luca Ceresoli (cherry picked from commit 958ee0eede859bdba659e3343856b1c226207854) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

kernel-yocto: allow patch author date to be commit date

2022-09-28T07:02:10+00:00

In situations where a buid needs to be reproducible, it is sometimes desireable to use a patches author date, versus the time when it is applied. This generates a consistent hash between different patch applications. We leverage the existing KERNEL_DEBUG_TIMESTAMPS to trigger the use of a new option to kgit-s2q. This allows us to use the author date in a reproducible configuration, but disable it if we need the current time/date. (From OE-Core rev: 8dbce9b13960acfd6889567c11456e3c73a783b5) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie (cherry picked from commit ebe2411ce78d5e4ea49b9b4cb732b461ecc32ca6) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

externalsrc: Don't wipe out src dir when EXPORT_FUNCTIONS is used.

2022-09-16T16:53:23+00:00

When 73fa855f6af5ef9c3 was introduced, the "cleandirs" variable flag started applying to functions exported using EXPORT_FUNCTIONS. The externalsrc class is supposed to remove cleandirs in order to prevent wiping out an external src folder (home directory?), but doesn't take the previous point into account. The result is that cleandirs is still in effect. To fix this, apply the cleandirs manipulation to all variables, not just predefined ones. This is expensive, but since it executes inside an `if externalsrc` clause, and EXTERNALSRC is usually only set for specific single recipes, it won't affect most recipes. Richard Purdie is the original author of this patch. I just submitted it under my name for blame purposes, and also we have been testing it a lot in my company. This is the original discussion: https://lists.openembedded.org/g/openembedded-core/topic/91374926 (From OE-Core rev: 70f7575bfe7e3b136125b1db7ad5549074e7fd1c) Signed-off-by: Kristian Amlie Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 74ad497a55007960a4869905878e3ccbd11e4369) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

rootfs-postcommands.bbclass: avoid moving ssh host keys if etc is writable

2022-09-16T16:53:22+00:00

When using IMAGE_FEATURE read-only-rootfs ssh host keys are moved to volatile storage. If the feature overlayfs-etc is used in addition to read-only-rootfs /etc is writable and the move is not wanted. But in the case also the IMAGE_FEATURE stateless-rootfs is used the keys will be moved as storage of keys should not be wanted in a stateless-rootfs. This change only takes effect in the case IMAGE_FEATURE contains read-only-rootfs. In adddition the following cases are handled: IMAGE_FEATURES = "read-only-rootfs" --> ssh keys/config handled as ro root IMAGE_FEATURES = "read-only-rootfs overlayfs-etc" --> ssh keys/config handled as rw root IMAGE_FEATURES = "read-only-rootfs stateless-rootfs" --> ssh keys/config handled as ro root IMAGE_FEATURES = "read-only-rootfs overlayfs-etc stateless-rootfs" --> ssh keys/config handled as ro root (From OE-Core rev: 31cff4d182faed31747d00cc82c1cf0a05a81431) Signed-off-by: Peter Bergin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit d2ad7aa1f2153955adc044ea4eb11c48086a01d1) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

core-image.bbclass: Exclude openssh complementary packages

2022-09-16T16:53:22+00:00

Openssh (main) package may be marked for installation via complementary packages mechanism if sftp-server is installed and this causes conflict with dropbear [Yocto #14858] [1]. Excluding openssh complementary packages if packagegroup-core-ssh-dropbear is in PACKAGE_INSTALL fixes this issue. To install openssh complementary packages in the images with ssh-server-dropbear they may be added manually into the list because they will be excluded from the installation even if corresonding class (dev-pkg or dbg-pkgs) inherited. [1] Error: Problem: problem with installed package dropbear-2020.81-r0.core2_64 - package dropbear-2020.81-r0.core2_64 conflicts with openssh provided by openssh-8.9p1-r0.core2_64 - package openssh-8.9p1-r0.core2_64 conflicts with dropbear provided by dropbear-2020.81-r0.core2_64 - package openssh-ptest-8.9p1-r0.core2_64 requires openssh, but none of the providers can be installed - conflicting requests (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages) (From OE-Core rev: a09725442d4b53bb9d417ef9f43b12db2545aa54) Signed-off-by: Pavel Zhukov Signed-off-by: Pavel Zhukov Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit fa08030b32c2bf77889c23f964892f46e84994a3) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

kernel: Use consistent make flags for menuconfig

2022-09-16T16:53:22+00:00

We're currently only passing in a subset of the kernel make flags to menuconfig. Fix this to be consistent with all the other kernel operations since these are becomming increasingly reliant on host compilers and flags and target toolchains as well. (From OE-Core rev: e36f3c3c7de052945edbb62bb2d6de7639360c47) Signed-off-by: Richard Purdie (cherry picked from commit 8c616bc090d1834a21073a33209323220c05d2e5) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

kernel: Always set CC and LD for the kernel build

2022-09-16T16:53:22+00:00

It as been bothering me a bit that we don't set CC and LD consistently for the kernel make calls and this can lead to interesting bugs as the kernel increases in complexity. Add them to EXTRA_OEMAKE so they're always passed in. This makes everything slightly more consistent and less likely to break in future. (From OE-Core rev: 0872e11ede2469a7d176c791395b139158bd22a3) Signed-off-by: Richard Purdie (cherry picked from commit afe8c318843e4033dcc07e4f10198df241d8e4f6) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

npm: use npm_registry to cache package

2022-09-12T07:41:48+00:00

With nodejs 16, the simple 'npm cache add' approach does not work anymore because its fetcher implementation downloads also meta information from the registry. We have to generate these information and add them to the cache. There is no direct support in 'npm' for task so we have to implement it manually. This implementation consists of a openembedded python module (in oe-core) and a nodejs version specific helper (in oe-meta). (From OE-Core rev: bfce90b1260d07f01a8dc2998c9e63ca36d4ebbe) Signed-off-by: Enrico Scholz Signed-off-by: Richard Purdie (cherry picked from commit 019b9c341d539939098962c228c1fd5c99331312) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie