Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

On Thu, 13 Feb 2025 at 00:04, Yoann Congal wrote: > I did not find a magic silver bullet that would solve everything (I > discovered that Gitlab is way more flexible on this subject). > I guess we need to find a compromise between what a github user sees and the > effort we are willing to put i

Re: [OE-core] [RFC PATCH 06/30] lib: oe: vendor: add cargo support

Am 12.02.2025 um 18:48 schrieb Frédéric Martinsons: Le mer. 12 févr. 2025, 17:29, Stefan Herbrechtsmeier a écrit : Am 12.02.2025 um 13:45 schrieb Frédéric Martinsons: On Tue, 11 Feb 2025 at 16:01, Stefan Herbrechtsmeier via lists.openembedded.org

[OE-core][scarthgap][PATCH 1/3] curl: fix CVE-2024-11053

From: Yogita Urade When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has an entry that matches the redire

[OE-core][scarthgap][PATCH 2/3] curl: fix CVE-2025-0167

From: Yogita Urade When asked to use a `.netrc` file for credentials *and* to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has a `default` entry that omits both l

[OE-core][scarthgap][PATCH 3/3] curl: fix CVE-2025-0725

From: Yogita Urade When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the `CURLOPT_ACCEPT_ENCODING` option, **using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow would make libcurl perform a buffer overflow. Reference: https://

[OE-core] [PATCH] libsdl2: upgrade 2.30.11 -> 2.30.12

This is a stable bugfix release, with the following changes: Improved XInput controller detection on Windows Added support for the 8BitDo Ultimate 2C Wireless in Bluetooth mode Fixed Steam Deck controller not being visible to games running on Proton 9 and older Fixed a crash when hot-plug

Re: [OE-core] [bitbake-devel] [RFC PATCH 00/30] Add vendor support for go, npm and rust

Am 12.02.2025 um 15:11 schrieb Bruce Ashfield: On Wed, Feb 12, 2025 at 3:41 AM Stefan Herbrechtsmeier wrote: Am 12.02.2025 um 00:14 schrieb Bruce Ashfield via lists.openembedded.org : In message: [bitbake-devel] [RFC PATCH 00/30] Add vendor suppor

Re: [OE-core] [PATCH] python3-license-expression: fix ptest installation

On 12 Feb 2025, at 22:56, Khem Raj wrote: >> +ln -s ${PYTHON_SITEPACKAGES_DIR}/license_expression/ >> ${D}${PTEST_PATH}/src/ > > should this be ln -sf ? We’re working in a fresh directory so there is no destination file to forcible remove. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive a

Re: [OE-core] [RFC PATCH 21/30] python3-bcrypt: mirgrate to vendor cargo class

Am 12.02.2025 um 18:45 schrieb Bruce Ashfield: On Wed, Feb 12, 2025 at 12:24 PM Stefan Herbrechtsmeier wrote: Am 12.02.2025 um 16:07 schrieb Bruce Ashfield: On Wed, Feb 12, 2025 at 9:36 AM Stefan Herbrechtsmeier via lists.openembedded.org

Re: [OE-core] [PATCH] package_ipk: Use preferred for of --force-postinstall

> Op 10 feb 2025, om 17:46 heeft Richard Purdie via lists.openembedded.org > het volgende > geschreven: [OE-core] [PATCH] package_ipk: Use preferred for of --force-postinstall Nitpick: the subject lacks the 'm' in for(m). regards, Koen > > opkg accepts both - and _ in its options but us

Re: [OE-core] [PATCH] systemd: move systemctl utility to separate subpackage

On Thu, 13 Feb 2025 at 08:00, Oleksiy Obitotskyy -X (oobitots - GLOBALLOGIC INC at Cisco) wrote: > > > Is it trying to save space on target device, or trying to save space > > on the build host? You really do need to describe your process in more > > detail. > > It's attempt to save space on build

Re: [OE-core] [PATCH v3] linux-firmware: upgrade 20250109 -> 20250211

On Thu, Feb 13, 2025 at 03:38:14PM +0530, Vivek Puar wrote: > On 2/13/2025 3:29 PM, Dmitry Baryshkov wrote: > > On Thu, Feb 13, 2025 at 12:16:18PM +0530, Vivek Puar wrote: > > > Add DSP firmware for Qualcomm SA8775P / QCS9100 > > > platforms to ${PN}-qcom-sa8775p-{audio, compute, generalpurpose} >

Re: [OE-core] [PATCH v3] linux-firmware: upgrade 20250109 -> 20250211

On 2/13/2025 3:50 PM, Dmitry Baryshkov via lists.openembedded.org wrote: On Thu, Feb 13, 2025 at 03:38:14PM +0530, Vivek Puar wrote: On 2/13/2025 3:29 PM, Dmitry Baryshkov wrote: On Thu, Feb 13, 2025 at 12:16:18PM +0530, Vivek Puar wrote: Add DSP firmware for Qualcomm SA8775P / QCS9100 platfor

Re: [OE-core][PATCH] classes/create-spdx-2.2: Fix SPDXDIR affecting multiconfig machines

If you want I can disable on my side this patch in order to reproduce it and copy paste the files to which are causing the issue. czw., 13 lut 2025 o 09:56 Piotr Łobacz napisał(a): > > Nope. It is on the scarthgap and I have set it in the subject when git > send-mail, but somehow it has been cut.

Re: [OE-core][PATCH] classes/create-spdx-2.2: Fix SPDXDIR affecting multiconfig machines

Nope. It is on the scarthgap and I have set it in the subject when git send-mail, but somehow it has been cut... śr., 12 lut 2025 o 23:07 Joshua Watt napisał(a): > > Based on this patch, I'm guessing you're not working off of master? > The patch doesn't apply to the latest master version because

[OE-core][kirkstone][PATCH 1/1] python3: Treat UID/GID overflow as failure

From: Khem Raj This fixes ptest failures on 32bit architectures AssertionError: Failed ptests: {'python3': ['test_extractall_none_gid', 'test_extractall_none_gname', 'test_extractall_none_mode', 'test_extractall_none_mtime', 'test_extractall_no

Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

Le jeu. 13 févr. 2025 à 11:03, Richard Purdie < richard.pur...@linuxfoundation.org> a écrit : > On Thu, 2025-02-13 at 10:54 +0100, Alexander Kanavin wrote: > > On Thu, 13 Feb 2025 at 10:53, Yoann Congal > wrote: > > > > > I don't think the github repo is going to work for either YP or OE > > > >

Re: [OE-core] [PATCH v3] linux-firmware: upgrade 20250109 -> 20250211

On Thu, Feb 13, 2025 at 12:16:18PM +0530, Vivek Puar wrote: > Add DSP firmware for Qualcomm SA8775P / QCS9100 > platforms to ${PN}-qcom-sa8775p-{audio, compute, generalpurpose} > packages, and updating it with correct license information. > > Add QCA6698AQ package ${PN}-ath11k-qca6698aq > to ath11

Re: [OE-core][PATCH 5/5] util-linux/util-linux-libuuid: upgrade from 2.40.2 to 2.40.4

On Thu Feb 13, 2025 at 7:00 AM CET, Chen Qi via lists.openembedded.org wrote: > From: Chen Qi > > The following two patches are dropped because they are in the new version: > - 0001-autotools-fix-securedir-and-pam_lastlog2-install.patch > - util-linux/libfdisk-cfdisk-and-sfdisk-sector-size-improve

Re: [OE-core] [PATCH v3][OE-core 0/4] cve-check: allow feed selection

On Mon, Feb 10, 2025 at 9:50 PM Ross Burton wrote: > On 5 Feb 2025, at 14:34, Marta Rybczynska via lists.openembedded.org > wrote: > > > > This series is allowing choice of the NVD feed to use, you can > > configure them using the NVD_DB_VERSION variable in local.conf > > > > Available feeds: >

Re: [OE-core] [PATCH] package_ipk: Use preferred for of --force-postinstall

On Thu, 2025-02-13 at 14:04 +0100, Koen Kooi wrote: > > > > Op 10 feb 2025, om 17:46 heeft Richard Purdie via lists.openembedded.org > > het volgende > > geschreven: > > [OE-core] [PATCH] package_ipk: Use preferred for of --force-postinstall > > Nitpick: the subject lacks the 'm' in for(m).

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

On Wed Feb 12, 2025 at 5:35 AM CET, Zoltán Böszörményi wrote: > This ships a crypto policy file for rpm-sequoia. > > Signed-off-by: Zoltán Böszörményi > --- Hi Zoltán, I believe we have a new issue with this version: | python/build-crypto-policies.py --reloadcmds policies output | /tmp/tmpqvyry

[OE-core][kirkstone][PATCH 1/1] ruby: fix CVE-2024-41946

From: Divya Chellam REXML is an XML toolkit for Ruby. The REXML gem 3.3.2 has a DoS vulnerability when it parses an XML that has many entity expansions with SAX2 or pull parser API. The REXML gem 3.3.3 or later include the patch to fix the vulnerability. Reference: https://nvd.nist.gov/vuln/deta

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

2025. 02. 13. 14:36 keltezéssel, Mathieu Dubois-Briand írta: On Wed Feb 12, 2025 at 5:35 AM CET, Zoltán Böszörményi wrote: This ships a crypto policy file for rpm-sequoia. Signed-off-by: Zoltán Böszörményi --- Hi Zoltán, I believe we have a new issue with this version: | python/build-crypto

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

2025. 02. 13. 15:20 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta: 2025. 02. 13. 14:36 keltezéssel, Mathieu Dubois-Briand írta: On Wed Feb 12, 2025 at 5:35 AM CET, Zoltán Böszörményi wrote: This ships a crypto policy file for rpm-sequoia. Signed-off-by: Zoltán Böszörményi -

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

2025. 02. 13. 15:32 keltezéssel, Richard Purdie írta: On Thu, 2025-02-13 at 15:20 +0100, Böszörményi Zoltán wrote: 2025. 02. 13. 14:36 keltezéssel, Mathieu Dubois-Briand írta: On Wed Feb 12, 2025 at 5:35 AM CET, Zoltán Böszörményi wrote: This ships a crypto policy file for rpm-sequoia. Signed

[OE-core] [PATCH] kea: make kea environment available to lfc

If using KEA_LOCKFILE_DIR to change the location of the logging lock file, kea-dhcp works properly, but lfc spawned by it does not inherit the value and uses the default path[1]. Backport a patch to fix this issue[2]. [1] https://gitlab.isc.org/isc-projects/kea/-/issues/3450 [2] https://gitlab.is

[OE-core][kirkstone 0/3] Patch review

Please review this set of changes for kirkstone and have comments back by end of day Friday, February 14 Passed a-full on autobuilder: https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1003 The following changes since commit bd12abeff6ee14385fba63fa5ba15d9fadec4d0e: cmake: ap

[OE-core][kirkstone 1/3] openssl: upgrade 3.0.15 -> 3.0.16

From: Peter Marko Release information: https://github.com/openssl/openssl/blob/openssl-3.0/NEWS.md#major-changes-between-openssl-3015-and-openssl-3016-11-feb-2025 All CVEs were already patched, so this upgrade fixes only minor bugs. Remove CVE patches included in the new version. Signed-off-by

[OE-core][kirkstone 3/3] classes-global/insane: Look up all runtime providers for file-rdeps

From: Joshua Watt Uses the new foreach_runtime_provider_pkgdata() API to look up all possible runtime providers of a given dependency when resolving file-rdeps. This allows the check to correctly handle RPROVIDES for non-virtual dependencies (From OE-Core rev: 018fa1b7cb5e6a362ebb45b93e52b0909a7

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

On Thu, 2025-02-13 at 15:20 +0100, Böszörményi Zoltán wrote: > 2025. 02. 13. 14:36 keltezéssel, Mathieu Dubois-Briand írta: > > On Wed Feb 12, 2025 at 5:35 AM CET, Zoltán Böszörményi wrote: > > > This ships a crypto policy file for rpm-sequoia. > > > > > > Signed-off-by: Zoltán Böszörményi > > >

[OE-core][kirkstone 2/3] lib/packagedata.py: Add API to iterate over rprovides

From: Joshua Watt Adds an API that makes it easier to iterate over the package data for a all providers of a runtime dependency. (From OE-Core rev: 68bdc219a4a819e83217f5b54c463624af8d3b9e) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman --- meta/lib/oe

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

On Thu, 2025-02-13 at 15:43 +0100, Böszörményi Zoltán wrote: > 2025. 02. 13. 15:20 keltezéssel, Zoltan Boszormenyi via > lists.openembedded.org írta: > > 2025. 02. 13. 14:36 keltezéssel, Mathieu Dubois-Briand írta: > > > On Wed Feb 12, 2025 at 5:35 AM CET, Zoltán Böszörményi wrote: > > > > This shi

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

2025. 02. 13. 15:43 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta: 2025. 02. 13. 15:20 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta: 2025. 02. 13. 14:36 keltezéssel, Mathieu Dubois-Briand írta: On Wed Feb 12, 2025 at 5:35 AM CET, Zoltán Böszörményi wrote:

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

2025. 02. 13. 16:06 keltezéssel, Richard Purdie írta: On Thu, 2025-02-13 at 15:43 +0100, Böszörményi Zoltán wrote: 2025. 02. 13. 15:20 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta: 2025. 02. 13. 14:36 keltezéssel, Mathieu Dubois-Briand írta: On Wed Feb 12, 2025 at 5:35 AM CE

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

On Thu, 2025-02-13 at 16:14 +0100, Böszörményi Zoltán wrote: > 2025. 02. 13. 16:06 keltezéssel, Richard Purdie írta: > > On Thu, 2025-02-13 at 15:43 +0100, Böszörményi Zoltán wrote: > > > 2025. 02. 13. 15:20 keltezéssel, Zoltan Boszormenyi via > > > lists.openembedded.org írta: > > > > 2025. 02. 13

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

Generally it's best to resend the whole patchset, as sending individual follow up patches doesn't scale for maintainers, they can easily lose track of how to combine everything into a non-broken set of commits if many people start sending partial patches at the same time. Alex On Thu, 13 Feb 2025

[OE-core][PATCH v12.1 1/5] rpm-sequoia-crypto-policy: New recipe

This ships a crypto policy file for rpm-sequoia. Signed-off-by: Zoltán Böszörményi --- meta/conf/distro/include/maintainers.inc | 1 + .../rpm-sequoia-crypto-policy_git.bb | 38 +++ 2 files changed, 39 insertions(+) create mode 100644 meta/recipes-devtools/rpm-se

[OE-core][PATCH v12.1 4/5] dnf: Set SEQUOIA_CRYPTO_POLICY in wrapped tools

Point to the crypto policy file so dnf can work with signed packages. Signed-off-by: Zoltán Böszörményi --- meta/recipes-devtools/dnf/dnf_4.22.0.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/dnf/dnf_4.22.0.bb b/meta/recipes-devtools/dnf/dnf_4.22.0.bb index f9d6ea1

[OE-core][PATCH v12.1 2/5] rpm-sequoia: New recipe for version 1.7.0

rpm 4.20 removed the built-in code to handle signed packages and uses rpm-sequoia as a more feature complete library. Runtime-depend on rpm-sequoia-crypto-policy. Signed-off-by: Zoltán Böszörményi --- meta/conf/distro/include/maintainers.inc | 1 + .../rpm-sequoia/rpm-sequoia-crates.inc

[OE-core][PATCH v12.1 1/5] rpm-sequoia-crypto-policy: New recipe

This ships a crypto policy file for rpm-sequoia. Signed-off-by: Zoltán Böszörményi --- meta/conf/distro/include/maintainers.inc | 1 + .../rpm-sequoia-crypto-policy_git.bb | 38 +++ 2 files changed, 39 insertions(+) create mode 100644 meta/recipes-devtools/rpm-se

[OE-core][PATCH v12.1 3/5] rpm: Set SEQUOIA_CRYPTO_POLICY in wrapped tools

Point to the crypto policy file so RPM signing may work. Signed-off-by: Zoltán Böszörményi --- meta/recipes-devtools/rpm/rpm_4.20.0.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/rpm/rpm_4.20.0.bb b/meta/recipes-devtools/rpm/rpm_4.20.0.bb index 45487ad32c..281fde1c

Re: [OE-core][PATCH 3/5] diffutils: upgrade from 3.10 to 3.11

On Thu Feb 13, 2025 at 6:59 AM CET, Chen Qi via lists.openembedded.org wrote: > From: Chen Qi > > Upgrade diffutils from 3.10 to 3.11. > > Signed-off-by: Chen Qi > --- Hi, Not an issue with the patch, just to notify Joshua: this will break meta-mingw if merged: 4024 ERROR: nativesdk-diffutils-

[OE-core][PATCH v12.1 5/5] oeqa/selftest/cases/signing.py: Re-enable self-test

With all the pieces in place, the self test can be re-enabled. Signed-off-by: Zoltán Böszörményi --- meta/lib/oeqa/selftest/cases/signing.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/lib/oeqa/selftest/cases/signing.py b/meta/lib/oeqa/selftest/cases/signing.py in

Re: [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe

2025. 02. 13. 16:16 keltezéssel, Alexander Kanavin írta: Generally it's best to resend the whole patchset, as sending individual follow up patches doesn't scale for maintainers, they can easily lose track of how to combine everything into a non-broken set of commits if many people start sending p

Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

Hello, Le jeu. 13 févr. 2025 à 09:49, Alexander Kanavin a écrit : > On Thu, 13 Feb 2025 at 00:04, Yoann Congal wrote: > > > I did not find a magic silver bullet that would solve everything (I > discovered that Gitlab is way more flexible on this subject). > > I guess we need to find a compromis

Re: [OE-core] [PATCH] cross-localedef-native : fixup filesystem check error

Hi Khem， I'm glad to do the format and PR. But I need some help. This is my first time submitting a patch, and my English is not very good, so I might have made some mistakes, but I'm not sure. I read https://docs.yoctoproject.org/dev/contributor-guide/recipe-style-guide.html and http

Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

On Thu, 13 Feb 2025 at 10:45, Richard Purdie wrote: > I don't think the github repo is going to work for either YP or OE > since there are repositories in both that use pull requests and we > can't have a one size fits all message. I think that means we would > have to do this with a .github direc

Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

Le jeu. 13 févr. 2025 à 10:50, Alexander Kanavin a écrit : > On Thu, 13 Feb 2025 at 10:45, Richard Purdie > wrote: > > I don't think the github repo is going to work for either YP or OE > > since there are repositories in both that use pull requests and we > > can't have a one size fits all mess

Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

On Thu, 13 Feb 2025 at 10:53, Yoann Congal wrote: >> > I don't think the github repo is going to work for either YP or OE >> > since there are repositories in both that use pull requests and we >> > can't have a one size fits all message. I think that means we would >> > have to do this with a .gi

Re: [OE-core] [PATCH v3] linux-firmware: upgrade 20250109 -> 20250211

On 2/13/2025 3:29 PM, Dmitry Baryshkov wrote: On Thu, Feb 13, 2025 at 12:16:18PM +0530, Vivek Puar wrote: Add DSP firmware for Qualcomm SA8775P / QCS9100 platforms to ${PN}-qcom-sa8775p-{audio, compute, generalpurpose} packages, and updating it with correct license information. Add QCA6698AQ pa

Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

On Thu, 13 Feb 2025 at 11:03, Richard Purdie wrote: > I'm wondering if we should set up that default repo saying "no pull > requests" then ask repos that do accept them to override the message > with their own pull request file? The default repo is only used as a > fallback. Does an empty file do

Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

On Thu, 2025-02-13 at 09:48 +0100, Alexander Kanavin wrote: > On Thu, 13 Feb 2025 at 00:04, Yoann Congal > wrote: > > > I did not find a magic silver bullet that would solve everything (I > > discovered that Gitlab is way more flexible on this subject). > > I guess we need to find a compromise be

Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

On Thu, 2025-02-13 at 10:54 +0100, Alexander Kanavin wrote: > On Thu, 13 Feb 2025 at 10:53, Yoann Congal wrote: > > > > I don't think the github repo is going to work for either YP or OE > > > > since there are repositories in both that use pull requests and we > > > > can't have a one size fits a

[OE-core] 'vendor' fetching discussion cont.

I've pulled this to a separate email/thread since I'd like to take a slight step back and put some different ideas into the mix as well as explain where my own thoughts are right now. I'm also doing this so that we can focus the discussion and give others a place to catch up from. For that reason I

[OE-core][scarthgap][PATCH v1] ppp: Revert lock path to /var/lock

ppp version 2.5.0 fails to run properly if an expected /run/pppd/lock directory does not exist, which is not usually created in a yocto built OS. Backport the patch from upstream version 2.5.1 that fixes the issue by reverting back to /var/lock. The related github issue upstream was: "lock direct

Re: [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

On 11/02/25 23:36 +, Richard Purdie via lists.openembedded.org wrote: > You used to be able to disable pull requests for six month periods, it > looks like you can no longer do that and it was a pain having to try > and remember anyway. Isn't this just 'Settings -> Moderation Options -> Intera

[OE-core] [PATCH] python3-setuptools-scm: respect GIT_CEILING_DIRECTORIES

From: Etienne Cordonnier Fixes https://bugzilla.yoctoproject.org/show_bug.cgi?id=15740 python3-setuptools-scm was ignoring GIT_CEILING_DIRECTORIES which is set by poky, and it was thus finding a wrong value of "toplevel" in ./src/setuptools_scm/_file_finders/git.py The code is supposed to gene

Re: [OE-core] 'vendor' fetching discussion cont.

I did some replies to the other threads before seeing this, we can feel free to let those other threads go unanswered, to unify things here. On Thu, Feb 13, 2025 at 5:43 AM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > I've pulled this to a separate email/thread since I'd like to

Re: [OE-core] [bitbake-devel] [RFC PATCH 00/30] Add vendor support for go, npm and rust

On Thu, Feb 13, 2025 at 3:36 AM Stefan Herbrechtsmeier < stefan.herbrechtsmeier-...@weidmueller.com> wrote: > Am 12.02.2025 um 15:11 schrieb Bruce Ashfield: > > > > On Wed, Feb 12, 2025 at 3:41 AM Stefan Herbrechtsmeier < > stefan.herbrechtsmeier-...@weidmueller.com> wrote: > >> Am 12.02.2025 um 0

Re: [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)

Le jeu. 13 févr. 2025 à 20:13, Justin Bronder via lists.openembedded.org a écrit : > On 11/02/25 23:36 +, Richard Purdie via lists.openembedded.org wrote: > > You used to be able to disable pull requests for six month periods, it > > looks like you can no longer do that and it was a pain havi

[OE-core][PATCH] spdx30: Improve os.walk() handling

There have been errors seen when assembling root file system SPDX documents where they will references files that don't exist in the package SPDX. The speculation is that this is caused by os.walk() ignoring errors when walking, causing files to be omitted. Improve the code by adding an error hand

Re: [OE-core] [RFC PATCH 21/30] python3-bcrypt: mirgrate to vendor cargo class

On Thu, Feb 13, 2025 at 7:45 AM Stefan Herbrechtsmeier < stefan.herbrechtsmeier-...@weidmueller.com> wrote: > Am 12.02.2025 um 18:45 schrieb Bruce Ashfield: > > > > On Wed, Feb 12, 2025 at 12:24 PM Stefan Herbrechtsmeier < > stefan.herbrechtsmeier-...@weidmueller.com> wrote: > >> Am 12.02.2025 um

Re: [OE-core] [bitbake-devel] 'vendor' fetching discussion cont.

Am 13.02.2025 um 11:43 schrieb Richard Purdie via lists.openembedded.org: I've pulled this to a separate email/thread since I'd like to take a slight step back and put some different ideas into the mix as well as explain where my own thoughts are right now. I'm also doing this so that we can focu

[OE-core] [PATCH 2/4] systemd-serialgetty: use existing unit files in systemd

Now that systemd isn't deleting the serial-getty@.service unit template files, we can simply symlink to the files provided by systemd instead of shipping a copy of them in this recipe. Signed-off-by: Ross Burton --- .../systemd/systemd-serialgetty.bb| 12 + .../systemd-serialgett

Re: [OE-core] [bitbake-devel] 'vendor' fetching discussion cont.

On Thu, 2025-02-13 at 17:33 +0100, Stefan Herbrechtsmeier wrote: >  Am 13.02.2025 um 11:43 schrieb Richard Purdie via lists.openembedded.org: > > > Most of the concerns I've seen are about how easy it is to understand > > what is going on behind the scenes. The move of code to OE and > > splitting

[OE-core][PATCH] curl: upgrade 8.12.0 -> 8.12.1

From: Peter Marko Rebase patch which needs it. Signed-off-by: Peter Marko --- meta/recipes-support/curl/curl/no-test-timeout.patch | 2 +- meta/recipes-support/curl/{curl_8.12.0.bb => curl_8.12.1.bb} | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-support/

[OE-core] [PATCH 4/4] sysvinit-inittab: exec getty from the wrapper

Instead of forking, the start_getty wrapper can use exec to replace itself. This results in one less process in ps per getty. Signed-off-by: Ross Burton --- meta/recipes-core/sysvinit/sysvinit-inittab/start_getty | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-co

[OE-core] [PATCH 1/4] systemd: if getty generator is disabled remove the generator, not the units

If the getty generator is disabled then it's neater to remove just the generator tool instead of the unit files as the unit files are still useful. Signed-off-by: Ross Burton --- meta/recipes-core/systemd/systemd_257.1.bb | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git

[OE-core] [PATCH 3/4] systemd-serialgetty: don't set a default SERIAL_CONSOLES

bitbake.conf defines a default value, so there's no value in setting another default here that doesn't match the rest of the system. Signed-off-by: Ross Burton --- meta/recipes-core/systemd/systemd-serialgetty.bb | 2 -- 1 file changed, 2 deletions(-) diff --git a/meta/recipes-core/systemd/syst

Re: [OE-core][PATCH 5/5] util-linux/util-linux-libuuid: upgrade from 2.40.2 to 2.40.4

Got it! Thanks. I'll look into it. Regards, Qi -Original Message- From: openembedded-core@lists.openembedded.org On Behalf Of Mathieu Dubois-Briand via lists.openembedded.org Sent: Thursday, February 13, 2025 9:33 PM To: Chen, Qi ; openembedded-core@lists.openembedded.org Subject: Re:

[OE-core][scarthgap][PATCH v1] ppp: Revert lock path to /var/lock

ppp version 2.5.0 fails to run properly if an expected /run/pppd/lock directory does not exist, which is not usually created in a yocto built OS. Backport the patch from upstream version 2.5.1 that fixes the issue by reverting back to /var/lock. The related github issue upstream was: "lock direct