[OE-core] [meta-oe][PATCH] llvm: set LLVM_HOST_TRIPLE for cross-compilation

From: Haseeb Ashraf The correct way to configure cmake for cross-compilation includes setting the LLVM_HOST_TRIPLE as well. Documentation Ref: https://github.com/llvm/llvm-project/blob/llvmorg-19.1.6/llvm/docs/HowToCrossCompileLLVM.rst#configuring-cmake This fixes bug when LLVM is cross-compile

Re: [OE-core] [meta-lts-mixins][scarthgap/rust][PATCH] classes: rename to classes-recipes/

On Mon, 20 Jan 2025, Enrico Scholz wrote: > Scott Murray writes: > > >> bitbake looks first in 'classes-recipes/' and then in 'classes/'. > >> Hence, content had no effect and was just ignored. > >> > >> Rename folder so that it overrides the OE-core classes. > >> > >> Signed-off-by: Enrico Schol

[OE-core] [meta-selinux] [scarthgap] [PATCH] selinux: Mark CVE-2020-10751 as Patched

Bug Details: https://nvd.nist.gov/vuln/detail/CVE-2020-10751 Type: Security Advisory CVE: CVE-2020-10751 Score: 6.1 Patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fb73974172ff Analysis: - This is a selinux cve which is addressed in kernel. - The fix is availa

Re: [OE-core] [meta-oe][PATCH] Sanity test for cpp toolchain

Hi Randy, On Mon Jan 13, 2025 at 11:02 PM CET, Randy MacLeod wrote: [...] >> + >> +output_binary = cpp_file_name + ".out" >> +compile_command = ['g++', '-std=c++17', cpp_file_name, '-o', >> output_binary] > > Maybe use BUILD_CC here? > > Oddly, that variable isn't in the docs but

Re: [OE-core] [meta-oe][PATCH] Sanity test for cpp toolchain

Hello Christos! I agree with Randy, this is a good start :) Le 13/01/2025 à 21:44, Christos Gavros via lists.openembedded.org a écrit : > Some users have reported issues which were caused because they were missing > the right libstdc++-version-dev in their system. > A new function with the name

Re: [OE-core] [meta-oe][PATCH] Sanity test for cpp toolchain

On 2025-01-13 3:44 p.m., Christos Gavros via lists.openembedded.org wrote: Some users have reported issues which were caused because they were missing the right libstdc++-version-dev in their system. A new function with the name 'check_cpp_toolchain' was added in sanity.bbclass in order to ver

[OE-core] [meta-oe][PATCH] Sanity test for cpp toolchain

Some users have reported issues which were caused because they were missing the right libstdc++-version-dev in their system. A new function with the name 'check_cpp_toolchain' was added in sanity.bbclass in order to verify that the host system can compile and link successfully a 'hello world' c

[OE-core] [meta-oe][PATCH] systemd: PACKAGECONFIG mountfsd and nsresourced

systemd v256 introduces `mountfsd` and `nsresourced` as meson options, make them PACKAGECONFIG so recipes could enable or disable the feature by selecting PACKAGECONFIGs. Signed-off-by: Lei YU --- meta/recipes-core/systemd/systemd_257.1.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/me

Re: [OE-core] [meta][kirkstone][PATCH] pseudo: Fix compile error on centos7

From: Richard Purdie Sent: Monday, January 6, 2025 6:22 PM To: He, Guocai (CN) ; openembedded-core@lists.openembedded.org Subject: Re: [OE-core] [meta][kirkstone][PATCH] pseudo: Fix compile error on centos7 CAUTION: This email comes from a non Wind River email account! Do not

Re: [OE-core] [meta-openembedded] [scarthgap] [PATCH] wireshark 4.2.7: Fix CVE-2024-9781

(spushpka - E INFOCHIPS PRIVATE LIMITED at Cisco) Cc: openembedded-core@lists.openembedded.org ; xe-linux-external(mailer list) Subject: Re: [OE-core] [meta-openembedded] [scarthgap] [PATCH] wireshark 4.2.7: Fix CVE-2024-9781 Wrong mailing list! Please send to openembedded-de

Re: [OE-core] [meta-openembedded] [scarthgap] [PATCH] wireshark 4.2.7: Fix CVE-2024-9781

Wrong mailing list! Please send to openembedded-de...@lists.openembedded.org Thanks, Steve On Tue, Jan 7, 2025 at 3:35 AM Shubham Pushpkar via lists.openembedded.org wrote: > > Upstream Repository: https://gitlab.com/wireshark/wireshark.git > > Bug Details: https://nvd.nist.gov/vuln/detail/CVE

[OE-core] [meta-openembedded] [scarthgap] [PATCH] wireshark 4.2.7: Fix CVE-2024-9781

Upstream Repository: https://gitlab.com/wireshark/wireshark.git Bug Details: https://nvd.nist.gov/vuln/detail/CVE-2024-9781 Type: Security Fix CVE: CVE-2024-9781 Score: 7.8 Patch: https://gitlab.com/wireshark/wireshark/-/commit/cad248ce3bf5 Signed-off-by: Shubham Pushpkar --- .../wireshark/file

Re: [OE-core] [meta][kirkstone][PATCH] pseudo: Fix compile error on centos7

On Thu, 2025-01-02 at 13:44 +0800, guocai he via lists.openembedded.org wrote: > From: Guocai He > > When host is centos7, fix the following build errors: > > In file included from pseudolog.c:21: > /usr/include/sys/stat.h:366:31: error: array type has incomlete element type > > In file include

[OE-core] [meta][kirkstone][PATCH] pseudo: Fix compile error on centos7

From: Guocai He When host is centos7, fix the following build errors: In file included from pseudolog.c:21: /usr/include/sys/stat.h:366:31: error: array type has incomlete element type In file included from pseudolog.c:21: /usr/include/sys/stat.h:366:31: error: array type has incomplete element

[OE-core] [meta-oe][PATCH 03/12] apache2: remove old version references from CVEs

From: Peter Marko These were not updated on recipe upgrade. To make maintenance easier, remove exact versions. Signed-off-by: Peter Marko --- .../recipes-httpd/apache2/apache2_2.4.62.bb| 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/meta-webserver/rec

Re: [OE-core] [meta-oe][PATCH 00/12] ignore or mark fixed several CVEs

nembedded.org > Cc: Marko, Peter (FT D EU SK BFS1) > Subject: [OE-core] [meta-oe][PATCH 00/12] ignore or mark fixed several CVEs > > This series handles all CVEs in meta-openembedded master report which I > think that can be removed from reports without doing an upgrade or patc

[OE-core] [meta-oe][PATCH 09/12] apache2: ignore disputed CVE CVE-2007-0086

From: Peter Marko This CVE is officially disputed by Redhat with official statement in https://nvd.nist.gov/vuln/detail/CVE-2007-0086 Red Hat does not consider this issue to be a security vulnerability. The pottential attacker has to send acknowledgement packets periodically to make server gener

[OE-core] [meta-oe][PATCH 12/12] emlog: set CVE_PRODUCT

From: Peter Marko This will remove false-positive CVE-2024-50655 from reports. There are different emlog components from other vendors around. Signed-off-by: Peter Marko --- meta-oe/recipes-core/emlog/emlog.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-oe/recipes-core/emlog/em

[OE-core] [meta-oe][PATCH 06/12] monkey: ignore CVE-2013-1771

From: Peter Marko This is gentoo specific CVE. NVD tracks this as version-less CVE. Signed-off-by: Peter Marko --- meta-webserver/recipes-httpd/monkey/monkey_1.6.9.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-webserver/recipes-httpd/monkey/monkey_1.6.9.bb b/meta-webserver/recip

[OE-core] [meta-oe][PATCH 10/12] swagger-ui: mark CVE-2016-1000229 as fixed

From: Peter Marko as per https://github.com/swagger-api/swagger-ui/issues/1865 NVD tracks this CVE as version-less. Signed-off-by: Peter Marko --- meta-webserver/recipes-devtools/swagger-ui/swagger-ui_5.18.2.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-webserver/recipes-devtoo

[OE-core] [meta-oe][PATCH 11/12] memcached: ignore disputed CVE-2022-26635

From: Peter Marko Per [1] this is a problem of applications using memcached inproperly. This should not be a CVE against php-memcached, but for whatever software the issue was actually found in. php-memcached and libmemcached provide a VERIFY_KEY flag if they're too lazy to filter untrusted user

[OE-core] [meta-oe][PATCH 08/12] spice-gtk: mark CVE-2012-4425 as fixed

From: Peter Marko It is fixed by [1] since 0.15.3. NVD tracks this CVE as version-less. [1] https://cgit.freedesktop.org/spice/spice-gtk/commit/?id=efbf867bb88845d5edf839550b54494b1bb752b9 Signed-off-by: Peter Marko --- meta-networking/recipes-support/spice/spice-gtk_0.42.bb | 2 ++ 1 file c

[OE-core] [meta-oe][PATCH 07/12] redis: ignore CVE-2022-0543

From: Peter Marko This is Debian-specific CVE. NVD tracks this CVE as version-less. Signed-off-by: Peter Marko --- meta-oe/recipes-extended/redis/redis_7.2.6.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-oe/recipes-extended/redis/redis_7.2.6.bb b/meta-oe/recipes-extended/redis/r

[OE-core] [meta-oe][PATCH 05/12] gattlib: mark CVE-2019-6498 as fixed

From: Peter Marko Our hash does not point to exact tag and CVE patch is already in. We use: 33a8a275928b186381bb0aea0f9778e330e57ec3 Fix: https://github.com/labapart/gattlib/commit/60b813a770e42fdb0e85c1d2da7a55327784b8d6 git describe --tags --match=v0.2 33a8a275928b186381bb0aea0f9778e330e57ec

[OE-core] [meta-oe][PATCH 02/12] apache2: ignore CVE-1999-0678 and CVE-1999-1412

From: Peter Marko These CVEs are specific to Debian and MAC OS X respectively. Signed-off-by: Peter Marko --- meta-webserver/recipes-httpd/apache2/apache2_2.4.62.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-webserver/recipes-httpd/apache2/apache2_2.4.62.bb b/meta-webserver/re

[OE-core] [meta-oe][PATCH 04/12] spice: ignore CVE-2016-0749

From: Peter Marko NVD tracks this as version-less CVE for spice. It was fixed by [1] and [2] included in 0.13.2. [1] https://gitlab.freedesktop.org/spice/spice/-/commit/6b32af3e1746988bb5a5123263bcf61b65e5be7e [2] https://gitlab.freedesktop.org/spice/spice/-/commit/359ac42a7ac02dcd101375755929

[OE-core] [meta-oe][PATCH 01/12] ace: ignore CVE-2009-1147

From: Peter Marko This CVE is for vmware ace. Signed-off-by: Peter Marko --- meta-oe/recipes-connectivity/ace/ace_8.0.1.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-oe/recipes-connectivity/ace/ace_8.0.1.bb b/meta-oe/recipes-connectivity/ace/ace_8.0.1.bb index c79fba323c..88df

[OE-core] [meta-oe][PATCH 00/12] ignore or mark fixed several CVEs

This series handles all CVEs in meta-openembedded master report which I think that can be removed from reports without doing an upgrade or patch. Peter Marko (12): ace: ignore CVE-2009-1147 apache2: ignore CVE-1999-0678 and CVE-1999-1412 apache2: remove old version references from CVEs spi

[OE-core] [meta-something][scarthgap][PATCH] qemu: set CVE-2024-6505 to fixed

From: Peter Marko CVE patch was removed on last upgrade as fixing commit was backported to stable 8.2.x branch. NVD DB has this CVE as version-less (with "-"). So explicit status set is needed to mark it as fixed. (From OE-Core rev: 64359ec3b60ae68d39c2e6444f903fd20e397cff) Signed-off-by: Pete

[OE-core] [meta-oe][PATCH 2/2] wireshark: use inherit_defer for conditional cases

From: Ghislain Mangé Conditionnal inherit may be missed when PACKAGECONFIG qt5 is activated after this inherit, eg in .bbappend. see patch [0] [0]: https://lists.openembedded.org/g/bitbake-devel/message/16815 Reviewed-by: Yoann Congal Signed-off-by: Ghislain Mangé --- meta-networking/recipes

[OE-core] [meta-oe][PATCH 1/2] wireshark: fix Qt5/6 configuration

From: Ghislain Mangé Wireshark is built with Qt6 by default when Qt is enabled. Forcibly disable Qt6 in our Qt5 PACKAGECONFIG Github issue: https://github.com/openembedded/meta-openembedded/issues/844 Reported-by: Ludovic Jozeau Reviewed-by: Yoann Congal Signed-off-by: Ghislain Mangé --- met

Re: [OE-core] [meta-gnome][PATCH] gdm: allow to unlock keyring when logging in

sorry, wrong list. Resent to meta-oe On Wed, Nov 20 2024 at 07:25:52 PM +01:00:00, Markus Volk wrote: Signed-off-by: Markus Volk > --- meta-gnome/recipes-gnome/gdm/gdm_47.0.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-gnome/recipes-gnome/gdm/gdm_47.0

[OE-core] [meta-gnome][PATCH] gdm: allow to unlock keyring when logging in

Signed-off-by: Markus Volk --- meta-gnome/recipes-gnome/gdm/gdm_47.0.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-gnome/recipes-gnome/gdm/gdm_47.0.bb b/meta-gnome/recipes-gnome/gdm/gdm_47.0.bb index aede4b071..45f23b49b 100644 --- a/meta-gnome/recipes-gnome/gdm/gdm_47.0.bb +++ b

Re: [OE-core] [meta-oe][PATCH] curl: upgrade 8.10.1 -> 8.11.0

e is blocked by python3 compatibility issue. Peter > -Original Message- > From: Mathieu Dubois-Briand > Sent: Tuesday, November 12, 2024 20:55 > To: ross.bur...@arm.com > Cc: Marko, Peter (FT D EU SK BFS1) ; > openembedded-core@lists.openembedded.org > Subject: Re: [OE-

Re: [OE-core] [meta-oe][PATCH] curl: upgrade 8.10.1 -> 8.11.0

On Mon, Nov 11, 2024 at 12:14:48PM +, Ross Burton via lists.openembedded.org wrote: > curl 8.11.0 is known to have some regressions in, for example from the > curl-distros list: > > “”" > As you probably know, there were some regressions in the latest release > 8.11.0. > Hi, Yes, I confi

Re: [OE-core] [meta-oe][PATCH] curl: upgrade 8.10.1 -> 8.11.0

curl 8.11.0 is known to have some regressions in, for example from the curl-distros list: “”" As you probably know, there were some regressions in the latest release 8.11.0. These are the patches we decided to pull in order to package it on Debian: netrc: support large file, longer lines, longe

[OE-core] [meta-oe][PATCH] curl: upgrade 8.10.1 -> 8.11.0

From: Peter Marko Solves CVE-2024-9681 * refresh patch * add patch for buildpaths issue * add new options for ipfs and websockets, keep them configure as they were previously configures * drop notexists.pl from ptest install as it was removed and code was integrated into the test framework i

Re: [OE-core] [meta-oe][PATCH] drm-info: add recipe

On Sun, Nov 03, 2024 at 07:24:39PM +0100, Martin Jansa wrote: > meta-oe patches should go to openembedded-devel ML as README says. Sorry about that, I sent it to openembedded-devel ML now. > > On Sun, Nov 3, 2024 at 7:21 PM Hiago De Franco via > lists.openembedded.org > wrote: > > > > From: Hia

Re: [OE-core] [meta-oe][PATCH] drm-info: add recipe

meta-oe patches should go to openembedded-devel ML as README says. On Sun, Nov 3, 2024 at 7:21 PM Hiago De Franco via lists.openembedded.org wrote: > > From: Hiago De Franco > > This recipe provides information about DRM devices, useful for debugging > and checking information about DRM. > > Sig

[OE-core] [meta-oe][PATCH] drm-info: add recipe

From: Hiago De Franco This recipe provides information about DRM devices, useful for debugging and checking information about DRM. Signed-off-by: Hiago De Franco --- meta-oe/recipes-graphics/drm/drm-info_2.7.0.bb | 13 + 1 file changed, 13 insertions(+) create mode 100644 meta-oe/

Re: [OE-core] [meta][PATCH v3] python3-cryptography: upgrade 42.0.8 -> 43.0.1

Hello, Le 15/10/2024 à 12:36, Tom Geelen via lists.openembedded.org a écrit : > Correct, as discussed in the mail conversation on the previous iteration > (https://lists.openembedded.org/g/openembedded-core/message/205784 > ) the >

Re: [OE-core] [meta][PATCH v3] python3-cryptography: upgrade 42.0.8 -> 43.0.1

On Tue, 15 Oct 2024 at 00:17, Tom Geelen via lists.openembedded.org wrote: > --- a/meta/recipes-devtools/python/python3-cryptography_42.0.8.bb > +++ b/meta/recipes-devtools/python/python3-cryptography_43.0.1.bb > @@ -8,43 +8,21 @@ LIC_FILES_CHKSUM = > "file://LICENSE;md5=8c3617db4fb6fae01f1d253ab

Re: [OE-core] [meta][PATCH v3] python3-cryptography: upgrade 42.0.8 -> 43.0.1

Correct, as discussed in the mail conversation on the previous iteration ( https://lists.openembedded.org/g/openembedded-core/message/205784) the reproducibility issue will be tackled in a different patch. Tom On Tue, Oct 15, 2024, 10:05 AM Alexander Kanavin wrote: > This still doesn't include t

Re: [OE-core] [meta][PATCH v3] python3-cryptography: upgrade 42.0.8 -> 43.0.1

This still doesn't include the reproducibility fix, and so can't be merged. Alex On Tue, 15 Oct 2024 at 00:17, Tom Geelen via lists.openembedded.org wrote: > > python3-cryptography-vectors: upgrade 42.0.8 -> 43.0.1 > > Changelog: > - https://cryptography.io/en/latest/changelog/#v43-0-0 > - https

[OE-core] [meta][PATCH v3] python3-cryptography: upgrade 42.0.8 -> 43.0.1

python3-cryptography-vectors: upgrade 42.0.8 -> 43.0.1 Changelog: - https://cryptography.io/en/latest/changelog/#v43-0-0 - https://cryptography.io/en/latest/changelog/#v43-0-1 Change build tool to use python3-maturin-native as specified in pyproject.toml file. Performed linting on the recipe and

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1 -> reproducibility doc improvement

Yes, I'll push a V3 of the patch with the comments of Tim added this evening. On Mon, Oct 14, 2024, 4:14 PM Tim Orling wrote: > > > On Mon, Oct 14, 2024 at 4:33 AM Alexander Kanavin > wrote: > >> On Mon, 14 Oct 2024 at 13:22, Yoann Congal wrote: >> > > 1) Maturin creates a .whl (zip archive) w

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1 -> reproducibility doc improvement

On Mon, Oct 14, 2024 at 4:33 AM Alexander Kanavin wrote: > On Mon, 14 Oct 2024 at 13:22, Yoann Congal wrote: > > > 1) Maturin creates a .whl (zip archive) where files are listed in a > > > non-deterministic order in the archive index. I'm not 100% sure if > > > your patch addresses this problem

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1 -> reproducibility doc improvement

On Mon, 14 Oct 2024 at 13:22, Yoann Congal wrote: > > 1) Maturin creates a .whl (zip archive) where files are listed in a > > non-deterministic order in the archive index. I'm not 100% sure if > > your patch addresses this problem - does it? Are the files supplied to > > the zip writer in sorted o

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1 -> reproducibility doc improvement

Hi, Le 14/10/2024 à 12:42, Alexander Kanavin a écrit : > On Mon, 14 Oct 2024 at 04:00, Tim Orling wrote: > >> Yoann and I were able to figure out a promising fix for maturin which is the >> root cause of the reproducibility issues. It needs a little more testing and >> rewording the commit mes

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1 -> reproducibility doc improvement

On Mon, 14 Oct 2024 at 04:00, Tim Orling wrote: > Yoann and I were able to figure out a promising fix for maturin which is the > root cause of the reproducibility issues. It needs a little more testing and > rewording the commit message before we submit upstream (I mentioned data.tar > which i

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1 -> reproducibility doc improvement

On Sun, Oct 13, 2024 at 6:18 AM Yoann Congal wrote: > Hi, > > On Sat, Oct 12, 2024, 8:32 PM Tim Orling wrote: > > We need to capture more of how to do this in the documentation. I > > did what seemed to be what the variable names would indicate. In the > > past, I always ran the full reproducibl

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1 -> reproducibility doc improvement

Hi, On Sat, Oct 12, 2024, 8:32 PM Tim Orling wrote: > We need to capture more of how to do this in the documentation. I > did what seemed to be what the variable names would indicate. In the > past, I always ran the full reproducible builds without restricting > to “one recipe” (slow). Le 12/10/

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

That the documentation could be more elaborate I agree on, this is my first attempt at pushing a fix I Poky and there is a lot of things to take into account. It makes it daunting to contribute as I'll be making a lot of mistakes. On Sat, Oct 12, 2024, 8:32 PM Tim Orling wrote: > > > On Sat, Oct

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

On Sat, Oct 12, 2024 at 1:57 AM Alexander Kanavin wrote: > On Sat, 12 Oct 2024 at 00:05, Tom Geelen wrote: > > > So if I understand correctly you say that the reproducible error is > > not appearing anymore? That is good news. > > It's definitely still there. Thanks for correcting my optimistic

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

On Sat, Oct 12, 2024 at 8:03 AM Yoann Congal wrote: > > > Le 11/10/2024 à 19:28, Tim Orling via lists.openembedded.org a écrit : > > The ptests are not passing on core-image-ptest-python3-cryptography > > (which only has the recipe dependencies and not full python3 and all the > > modules). > > >

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

Le 11/10/2024 à 19:28, Tim Orling via lists.openembedded.org a écrit : > The ptests are not passing on core-image-ptest-python3-cryptography > (which only has the recipe dependencies and not full python3 and all the > modules). > > https://snips.sh/f/9C7acm_o35 >

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

On Sat, 12 Oct 2024 at 00:05, Tom Geelen wrote: > So if I understand correctly you say that the reproducible error is > not appearing anymore? That is good news. It's definitely still there. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

So if I understand correctly you say that the reproducible error is not appearing anymore? That is good news. Question though: - I added missing ptest RDEPENDS packages, but not all are in meta (like python3-pytest-cov, python3-pytest-benchmark and python3-pytest-xdist). Some are in meta-python. Is

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

The ptests are not passing on core-image-ptest-python3-cryptography (which only has the recipe dependencies and not full python3 and all the modules). https://snips.sh/f/9C7acm_o35 ModuleNotFoundError: No module named '__pypy__' ModuleNotFoundError: No module named 'timeit' I tested this by: bitb

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

You need to build the recipe twice in two different build directories (you can reuse the sstate for everything else except the recipe itself), and compare the output. And no, it wasn't caused by other 3.13 issues, in fact it was made clear that 3.13 was not relevant (I first thought it was fixing

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

I have checked the report of the issues that were encountered on the previous upgrade try and if I understand correctly those were likely caused by other Python 3.13 issues. So to address your question, do I wait for the autobuilder output for an answer or is there a way on how I can test the issue

Re: [OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

Does this address the reproducibility issues Tim mentioned? Alex On Thu 10. Oct 2024 at 23.51, Tom Geelen via lists.openembedded.org wrote: > python3-cryptography-vectors: upgrade 42.0.8 -> 43.0.1 > > Changelog: > - https://cryptography.io/en/latest/changelog/#v43-0-0 > - https://cryptography.i

[OE-core] [meta][PATCH v2] python3-cryptography: upgrade 42.0.8 -> 43.0.1

python3-cryptography-vectors: upgrade 42.0.8 -> 43.0.1 Changelog: - https://cryptography.io/en/latest/changelog/#v43-0-0 - https://cryptography.io/en/latest/changelog/#v43-0-1 Change build tool to use python3-maturin-native as specified in pyproject.toml file. Performed linting on the recipe and

[OE-core] [meta-oe][PATCH] python3-pip: add missing RDEPENDS

pip3 package is missing the runtime dependency on tomllib. Add python3-modules to the recipe's RDEPENDS. Signed-off-by: Bartosz Golaszewski --- meta/recipes-devtools/python/python3-pip_24.2.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/python/python3-pip_24.2.bb b

Re: [OE-core] [meta][PATCH] python3-cryptography 42.0.8 -> 43.0.1

Thank you for the update. We had reproducibility issues with 43.0.0 https://lore.kernel.org/openembedded-core/20240813031628.1123492-1-tim.orl...@konsulko.com/ Also, you didn’t report that ptests pass. This package is critical path for many other recipes, so we must take extra care. Linting is no

[OE-core] [meta][PATCH] python3-cryptography 42.0.8 -> 43.0.1

python3-cryptography-vectors 42.0.8 -> 43.0.1 Changelog: - https://cryptography.io/en/latest/changelog/#v43-0-0 - https://cryptography.io/en/latest/changelog/#v43-0-1 Change build tool to use python3-maturin-native as specified in pyproject.toml file. Performed linting on the recipe and removed

Re: [OE-core] [meta-oe][kirkstone][PATCHv2] kmscube: Add patch to fix -int-conversion build error

Hi Purushottam, This triggers Patchtest because you have "meta-oe" in the mail subject I believe. meta-oe patches are not handled on openembedded-core mailing list. That patch is for openembedded-core though as it's in OE-Core repo, c.f. https://git.openembedded.org/openembedded-core/tree/met

[OE-core] [meta-oe][kirkstone][PATCHv2] kmscube: Add patch to fix -int-conversion build error

On some platforms, `EGLNativeDisplayType` is an int instead of a pointer, in which case the void pointer will raise a `-Wint-conversion`. Signed-off-by: Purushottam Choudhary --- ...001-common-fix-cast-type-in-init_egl.patch | 34 +++ meta/recipes-graphics/kmscube/kmscube_git.bb

[OE-core] [meta-oe][PATCH] bpftool: Add support for riscv64

From: Harish Sadineni bpftool is supported for riscv64 and tested on qemuriscv64. Signed-off-by: Harish Sadineni --- meta-oe/recipes-kernel/bpftool/bpftool.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-kernel/bpftool/bpftool.bb b/meta-oe/recipes-kernel

[OE-core] [meta][kirkstone][PATCH] libsoup: fix compile error on centos7

From: Guocai He Backport a patch [1] to fix the below build failure. FAILED: libsoup/libsoup-2.4.so.1.11.0.p/soup-address.c.o In file included from /usr/include/glib-2.0/gio/gnetworking.h:40, from ../libsoup-2.72.0/libsoup/soup-address.c:14: /usr/include/resolv.h:75:15: error: u

[OE-core] [meta-multimeida][PATCH] libcamera: Add support for pycamera

Supply a libcamera-pycamera package to allow installing the libcamera python bindings. Signed-off-by: Kieran Bingham --- .../recipes-multimedia/libcamera/libcamera_0.3.0.bb | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/meta-multimedia/recipes-multimedia/libcame

[OE-core] [meta-oe][PATCH] python3-pytest-html: add missing runtime dependencies

Upstream toml file mentions Jinja2 and pytest-metadata as runtime dependencies. Link: https://github.com/pytest-dev/pytest-html/blob/cfd32d08488e2c6fb72f0617db94ab41d3fca8d0/pyproject.toml#L42 Signed-off-by: Grygorii Tertychnyi --- .../recipes-devtools/python/python3-pytest-html_4.1.1.bb

[OE-core] [meta-oe][PATCHv2] webkitgtk: update 2.42.5 -> 2.44.0

- add a PACKAGECONFIG for libbacktrace to avoid: | -- Could NOT find LibBacktrace (missing: LIBBACKTRACE_INCLUDE_DIR LIBBACKTRACE_LIBRARY) | CMake Error at Source/cmake/OptionsGTK.cmake:425 (message): | libbacktrace is required for USE_LIBBACKTRACE - while at it also add a PACKAGECONFIG f

[OE-core] [meta-oe][PATCH 1/2] buildstats: consider multiconfigs when collecting statistics.

When multiconfigs are used, statistics for the same package name but from the different multiconfigs is collected into the same file. This causes incorrect charts generated with pybootchartgui, when only the most recent part of statistics is shown. This patch adds custom multiconfig prefix to the

[OE-core] [meta-oe][PATCH 0/2] Buildstats improvements for using in Isar.

Isar project (https://github.com/ilbers/isar) borrows from OE some functionality including buildstats. Here are the changes that are mostly suitable to use in Isar but they should not break anything in OE/Yocto. Uladzimir Bely (2): buildstats: consider multiconfigs when collecting statistics.

[OE-core] [meta-oe][PATCH 2/2] buildstats: support of custom disk usage command

This helps to make buildstats code usage easier in third-party projects like Isar (https://github.com/ilbers/isar/). In Isar, rootfs is created with 'sudo' privileges and some subpaths like '/proc' may be mounted at build time. So, using "du -sh" on rootfs may produces multiple 'Permission denied'

Re: [OE-core] [meta-oe][PATCH v2] uninative-tarball.xz - reproducibility fix

On 2023-06-30 9:14 a.m., Robert Berger via lists.openembedded.org wrote: see: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15148 Signed-off-by: Robert Berger --- meta/classes-recipe/populate_sdk_base.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes

Re: [OE-core] [meta][kirkstone][PATCH] json-c: Add ptest

On Sun, Nov 26, 2023 at 8:53 PM Pawan Badganchi wrote: > > Hi, > > Could you please take this change ??? You previously asked me to ignore this patch! Steve > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#191389): https://lists.openembedde

Re: [OE-core] [meta][kirkstone][PATCH 2/2] rsync: Turn on -pedantic-errors at the end of 'configure'

On Sun, Nov 26, 2023 at 8:55 PM Pawan Badganchi wrote: > > Hi, > > Could you please take this change. This also has been in kirkstone since April: https://git.yoctoproject.org/poky/commit/?h=kirkstone&id=e628a4494da515096cddbd0b65298e3af8cd42ed Steve > > -=-=-=-=-=-=-=-=-=-=-=- Links: You re

Re: [OE-core] [meta][kirkstone][PATCH 1/2] rsync: Add missing prototypes to function declarations

On Sun, Nov 26, 2023 at 8:55 PM Pawan Badganchi wrote: > > Hi, > > Could you please take this change This has been in kirkstone since April: https://git.yoctoproject.org/poky/commit/?h=kirkstone&id=6e89e71679ebcc5cca9c25cddb6e46d488e41e5c Steve > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive

Re: [OE-core] [meta-oe][PATCH] rdfind: remove (move to oe-core)

please send it to oe-devel mailing list, On Mon, Nov 27, 2023 at 11:42 PM A. Sverdlin via lists.openembedded.org wrote: > > From: Alexander Sverdlin > > Newer linux-firmware (oe-core) requires rdfind-native, move the new > dependency to oe-core as well. > > Signed-off-by: Alexander Sverdlin > -

[OE-core] [meta-oe][PATCH] rdfind: remove (move to oe-core)

From: Alexander Sverdlin Newer linux-firmware (oe-core) requires rdfind-native, move the new dependency to oe-core as well. Signed-off-by: Alexander Sverdlin --- meta-oe/recipes-support/rdfind/rdfind_1.6.0.bb | 13 - 1 file changed, 13 deletions(-) delete mode 100644 meta-oe/recip

Re: [OE-core] [meta][kirkstone][PATCH 1/2] rsync: Add missing prototypes to function declarations

Hi, Could you please take this change -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#191256): https://lists.openembedded.org/g/openembedded-core/message/191256 Mute This Topic: https://lists.openembedded.org/mt/97945090/21656 Group Owner: openembe

Re: [OE-core] [meta][kirkstone][PATCH 2/2] rsync: Turn on -pedantic-errors at the end of 'configure'

Hi, Could you please take this change. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#191255): https://lists.openembedded.org/g/openembedded-core/message/191255 Mute This Topic: https://lists.openembedded.org/mt/97945091/21656 Group Owner: openemb

Re: [OE-core] [meta][kirkstone][PATCH] json-c: Add ptest

Hi, Could you please take this change -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#191254): https://lists.openembedded.org/g/openembedded-core/message/191254 Mute This Topic: https://lists.openembedded.org/mt/98039591/21656 Group Owner: openembe

Re: [OE-core] [meta-oe][PATCH v2 1/1] wic: extend empty plugin with options to write zeros to partiton

On Wed, 2023-11-22 at 11:47 +0100, Lukas Funke wrote: > From: Malte Schmidt > > Adds features to explicitly write zeros to the start of the > partition. This is useful to overwrite old content like > filesystem signatures which may be re-recognized otherwise. > > The new features can be enabled

Re: [OE-core] [meta-oe][PATCH v2 0/1] wic: extend empty plugin with options to write zeros to partiton

Hi, On 22.11.2023 11:47, Lukas Funke via lists.openembedded.org wrote: From: Lukas Funke Adds features to explicitly write zeros to the start of the partition. This is useful to overwrite old content like filesystem signatures which may be re-recognized otherwise. The new features can be enab

[OE-core] [meta-oe][PATCH v2 0/1] wic: extend empty plugin with options to write zeros to partiton

From: Lukas Funke Adds features to explicitly write zeros to the start of the partition. This is useful to overwrite old content like filesystem signatures which may be re-recognized otherwise. The new features can be enabled with '--soucreparams="[fill|size=[S|s|K|k|M|G]][,][bs=[S|s|K|k|M|G]]"'

[OE-core] [meta-oe][PATCH v2 1/1] wic: extend empty plugin with options to write zeros to partiton

From: Malte Schmidt Adds features to explicitly write zeros to the start of the partition. This is useful to overwrite old content like filesystem signatures which may be re-recognized otherwise. The new features can be enabled with '--soucreparams="[fill|size=[S|s|K|k|M|G]][,][bs=[S|s|K|k|M|G]]

Re: [OE-core] [meta-oe][PATCH v2 4/4] glibc: use nonarch libdir for tmpfiles.d

I am still seeing ERROR: glibc-2.38+git-r0 do_package: QA Issue: glibc: Files/directories were installed but not shipped in any package: /etc/tmpfiles.d /etc/tmpfiles.d/nscd.conf Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installin

Re: [OE-core] [meta-oe][PATCH v3] systemd: use nonarch libdir for tmpfiles.d

Please always resend the whole series so I don't have to cherrypick patches from various threads. Also, is this really for meta-oe? On 16/11/2023 13:50:59+0100, Lukas Funke wrote: > From: Malte Schmidt > > The documentation of systemd states that /etc/tmpfiles.d should be > reserved for the loca

[OE-core] [meta-oe][PATCH] classes: go-mod: do not pack go mod cache

From: Stefan Herbrechtsmeier Clean go module cache from builddir to prevent it of beeing packed. Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Lukas Funke --- meta/classes-recipe/go-mod.bbclass | 4 1 file changed, 4 insertions(+) diff --git a/meta/classes-recipe/go-mod.bbclass

[OE-core] [meta-oe][PATCH v3] systemd: use nonarch libdir for tmpfiles.d

From: Malte Schmidt The documentation of systemd states that /etc/tmpfiles.d should be reserved for the local administrator and packages should put their files in /usr/lib/tmpfiles.d [1]. [1] https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html Signed-off-by: Malte Schmidt Signed-o

Re: [OE-core] [meta-oe][PATCH v2 1/4] systemd: use nonarch libdir for tmpfiles.d

escreveu no dia quinta, 16/11/2023 à(s) 11:55: > From: Malte Schmidt > > The documentation of systemd states that /etc/tmpfiles.d should be > reserved for the local administrator and packages should put their files > in /usr/lib/tmpfiles.d [1]. > > [1] https://www.freedesktop.org/software/system

[OE-core] [meta-oe][PATCH v2 4/4] glibc: use nonarch libdir for tmpfiles.d

From: Stefan Herbrechtsmeier The documentation of systemd states that /etc/tmpfiles.d should be reserved for the local administrator and packages should put their files in /usr/lib/tmpfiles.d [1]. [1] https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html Signed-off-by: Stefan Herbrec

[OE-core] [meta-oe][PATCH v2 2/4] pam: use nonarch libdir for tmpfiles.d

From: Malte Schmidt The documentation of systemd states that /etc/tmpfiles.d should be reserved for the local administrator and packages should put their files in /usr/lib/tmpfiles.d [1]. [1] https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html Signed-off-by: Malte Schmidt Signed-o

[OE-core] [meta-oe][PATCH v2 3/4] sysstat: use nonarch libdir for tmpfiles.d

From: Malte Schmidt The documentation of systemd states that /etc/tmpfiles.d should be reserved for the local administrator and packages should put their files in /usr/lib/tmpfiles.d [1]. [1] https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html Signed-off-by: Malte Schmidt Signed-o

[OE-core] [meta-oe][PATCH v2 1/4] systemd: use nonarch libdir for tmpfiles.d

From: Malte Schmidt The documentation of systemd states that /etc/tmpfiles.d should be reserved for the local administrator and packages should put their files in /usr/lib/tmpfiles.d [1]. [1] https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html Signed-off-by: Malte Schmidt Signed-o

[OE-core] [meta-oe][PATCH v2 0/4] tmpfiles.d: use nonarch libdir

From: Lukas Funke The series intents to move tmpfiles.d configurations from /etc to /usr/lib. The documentation of systemd states that /etc/tmpfiles.d should be reserved for the local administrator and packages should put their files in /usr/lib/tmpfiles.d [1]. [1] https://www.freedesktop.org/s

Re: [OE-core] [meta-oe][PATCH v2] volatile-binds: Calculate the name of the /var/lib service

On 2023-10-28 4:17 a.m., Stéphane Veyret via lists.openembedded.org wrote: Hello, This patch and the previous one (https://lists.openembedded.org/g/openembedded-core/message/186778) have not been integrated yet. Have they been forgotten, should I do some modifications, or have they been defin

  1   2   3   4   5   6   7   8   9   10   >