Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ovmf* to *edk2-stable202302* has Failed (devtool error). Detailed error information:

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *coreutils* to *9.2* has Succeeded. Next steps: - apply the patch: git am 0001-coreuti

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *bind* to *9.18.13* has Succeeded. Next steps: - apply the patch: git am 0001-bind-upg

* Allow to independently set P_V for llvm* recipes and actual llvm version used in other places * This is needed for meta-clang which provides different llvm version from clang recipes, see: https://g

Add a patch to gstreamer1.0-libav to address an API compatibility fail. Signed-off-by: Alexander Kanavin <alex@...> --- ...c-stop-accessing-out-of-bounds-frame.patch | 89 --------------- ...c-stop-acc

From: Frederic Martinsons <frederic.martinsons@...> There is no need to do such things, Cargo.lock file has to be at the root of CARGO_LOCK_SRC_DIR. This avoid finding other possible Cargo.lock that w

From: Frederic Martinsons <frederic.martinsons@...> This recipe is for showing a "real world" example of a crate that depends on some git repositories. Usually, this kind of crate is built within a gl

From: Frederic Martinsons <frederic.martinsons@...> This recipe is for showing a "real world" example of a crate that depends on some git repositories. Usually, this kind of crate is built within a gl

From: Frederic Martinsons <frederic.martinsons@...> A project can have multiple Cargo.lock (provides multiple binaries for example) and each one can depends on differenct version of the same crates. E

From: Frederic Martinsons <frederic.martinsons@...> This is for a specific case where: - A recipe use a subpath on a git repo (e.g. git://repo.git/projects;subpath=subproject) - The recipe contains a

From: Frederic Martinsons <frederic.martinsons@...> Without that, the possible git urls that are in SRC_URI of a recipe are removed from SRC_URI during devtool process and so the cargo_common_do_patch

From: Frederic Martinsons <frederic.martinsons@...> To handle url like git://git@repo/project Signed-off-by: Frederic Martinsons <frederic.martinsons@...> --- meta/classes-recipe/cargo_common.bbclass

From: Alex Kiernan <alex.kiernan@...> Since disable network was added cargo configurations which reference git repos fail as they attempt to fetch across the network as part of do_compile, even if EXT

From: Frederic Martinsons <frederic.martinsons@...> This series brings the support of local git repository inside a cargo based recipe. It also enables devtool capacity to such a recipe along with an

Add new fetcher for the NVD database using the 2.0 API [1]. The implementation changes as little as possible, keeping the current database format (but using a different database file for the transitio

Absent maintainer entries are as well a frequent source of friction, as they are checked only in selftest, and so aren revealed until autobuilder runs. The selftest is retained as it also checks for o

hwclock.sh had default update-rc parameters which made it run after other tasks that work with the clock such as connman. This causes a time obtained by NTP to be clobbered by a potentially incorrect

When we do not enter password during login, it is expected to display message "Login timed out after 60 seconds". But it prints only first few bytes(like "Login t") when write is immediately followed

Fixes [YOCTO #14127] NVD DB store version and update in the same value, separated by '_'. The proposed patch check if the version from NVD DB contains a "_", ie 9.2.0_p1 is convert to 9.2.0p1 before v

The following changes since commit a04b207c4ffa900313a0b5e3079ad2eec7d31f27: base-files: Drop localhost.localdomain from hosts file (2023-03-20 16:38:51 -1000) are available in the Git repository at: