Re: [OE-core] [PATCH] acl: Add attr to RDEPENDS:${PN}-ptest

On 6/27/24 14:23, Chen, Qi wrote: Just one question: the testcase's name looks like it's supposed to be run on some NFS. Does it? Yes, It's designed for nfs root with acl support. But the cases are mainly some basic setting like set the file access control lists(setfacl) or get file access

Re: [OE-core] [PATCH v2] acl: Fix nfs ptest failure

On 27/06/2024 14:15:56+0800, Yu, Mingli wrote: > > > On 6/27/24 07:09, Alexandre Belloni wrote: > > CAUTION: This email comes from a non Wind River email account! > > Do not click links or open attachments unless you recognize the sender and > > know the content is safe. > > > > Hello, this fai

Re: [OE-core] [PATCH] acl: Add attr to RDEPENDS:${PN}-ptest

Just one question: the testcase's name looks like it's supposed to be run on some NFS. Does it? Regards, Qi -Original Message- From: openembedded-core@lists.openembedded.org On Behalf Of Yu, Mingli via lists.openembedded.org Sent: Thursday, June 27, 2024 2:18 PM To: openembedded-core@

[OE-core] [PATCH] acl: Add attr to RDEPENDS:${PN}-ptest

From: Mingli Yu * Add attr which provides getfattr to RDEPENDS:${PN}-ptest to fix below test/nfs/nfsacl failure. [19] $ getfattr -m- test/sub -- failed\n' 'Can\'t exec "getfattr": Nosuch file or directory at ./test/run line ' 369, line 24. != # file: test/sub\n' 'getfat

Re: [OE-core] [PATCH v2] acl: Fix nfs ptest failure

On 6/27/24 07:09, Alexandre Belloni wrote: CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello, this fails on the autobuilders: https://autobuilder.yoctoproject.org/typhoon/#

Re: [OE-core] [PATCH v2] acl: Fix nfs ptest failure

Hello, this fails on the autobuilders: https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/6574/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6751/steps/12/logs/stdio On 26/06/2024 13:56:37+0800, Yu, Mingli wrote: > From: Mingli Yu > > * The

Re: [OE-core][kirkstone][PATCH] xz: Update LICENSE variable for xz packages

On Mon, 2024-05-06 at 17:32 +0200, Marta Rybczynska via lists.openembedded.org wrote: > I'm not a copyright lawyer, but from what I understand public domain > is not a licence. For a discussion > see https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Publ > ic_Domain_within_SPDX_Files >

[OE-core] mc: broken source link

Hi, Source link of Midnight Commander is broken since long time. https://layers.openembedded.org/layerindex/recipe/5603/ http://www.midnight-commander.org/downloads/mc-4.8.31.tar.bz2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#201179): https:/

Re: [OE-core] [scarthgap][PATCH] python3: Fix CVE-2024-4032

On Wed, Jun 26, 2024 at 11:22 AM Guðni Már Gilbert via lists.openembedded.org wrote: > > Isn't this fixed in Python 3.12.4? gh-113171 is referenced in the release > notes: > https://docs.python.org/3.12/whatsnew/changelog.html#python-3-12-4-final > > > Python 3.12.4 has been merged into master,

Re: [OE-core] [scarthgap][PATCH] python3: Fix CVE-2024-4032

Isn't this fixed in Python 3.12.4? gh-113171 is referenced in the release notes: https://docs.python.org/3.12/whatsnew/changelog.html#python-3-12-4-final ( https://docs.python.org/3.12/whatsnew/changelog.html#python-3-12-4-final ) Python 3.12.4 has been merged into master, perhaps it can be backp

[yocto] OpenEmbedded Happy Hour June 26 9pm/2100 UTC

All, You are invited to our regularly scheduled OpenEmbedded Happy Hour later today, June 26 for Asia/Pacific timezones at 2100/9pm UTC (5pm ET/2pm PT) https://www.openembedded.org/wiki/Calendar https://www.openembedded.org/wiki/Happy_Hours https://www.timeanddate.com/worldclock/fixedtime.html?m

[OE-core] [PATCH] gstreamer1.0: disable flaky baseparser tests

There are three baseparser tests which are causing trouble on the AB, so disable them as we've filed an upstream bug. Also fix a typo when we were attempting to disable parser_pull_short_read where a colon was used instead of a comma. Signed-off-by: Ross Burton --- meta/recipes-multimedia/gstre

[OE-core] [PATCH] llvm: Update to 18.1.8

Brings following fixes * 3b5b5c1ec4a3 [libcxx] Align `__recommend() + 1` by __endian_factor (#90292) * 72c9425a79fd [libc++][NFC] Rewrite function call on two lines for clarity (#79141) * 443e23eed24d Bump version to 18.1.8 (#95458) * 768118d1ad38 [clang-format] Fix a bug in formatting goto labe

[OE-core][scarthgap][PATCH] python3: Fix CVE-2024-4032

Upstream-Status: Backport from [https://github.com/python/cpython/commit/ba431579efdcbaed7a96f2ac4ea0775879a332fb] CVE: CVE-2024-4032 Signed-off-by: Ashish Sharma --- .../python/python3/CVE-2024-4032.patch| 346 ++ .../recipes-devtools/python/python3_3.12.3.bb | 1 + 2

[OE-core][kirkstone][PATCH] python3: Fix CVE-2024-4032

Upstream-Status: Backport from [https://github.com/python/cpython/commit/ba431579efdcbaed7a96f2ac4ea0775879a332fb] CVE: CVE-2024-4032 Signed-off-by: Ashish Sharma --- .../python/python3/CVE-2024-4032.patch| 346 ++ .../python/python3_3.10.14.bb | 1 + 2

[OE-core] [PATCH] oeqa/runtime/parselogs: Add some kernel log trigger keywords

During testing we're finding some kernel oops messages and other key kernel errors such as irq issues are not triggering our log parsing. Add those keywords to the list of things to scan for, making such failures much more visible. Signed-off-by: Richard Purdie --- meta/lib/oeqa/runtime/cases/p

[OE-core] [kirkstone][PATCH] linuxloader: add -armhf on arm only for TARGET_FPU 'hard'

There are two types of soft FPU options for arm, soft and softfp, and if using the latter the wrong dynamic loader will be used. E.g. go will link against ld-linux-armhf.so.3, but libc6 will only ship a ld-linux.so.3, so go programs will fail to start. Fix this by instead checking for TARGET_FPU

[OE-core] [scarthgap][PATCH] linuxloader: add -armhf on arm only for TARGET_FPU 'hard'

There are two types of soft FPU options for arm, soft and softfp, and if using the latter the wrong dynamic loader will be used. E.g. go will link against ld-linux-armhf.so.3, but libc6 will only ship a ld-linux.so.3, so go programs will fail to start. Fix this by instead checking for TARGET_FPU

Re: [OE-core] [PATCH] package.bbclass: Add Requires.private field in package_do_pkgconfig()

The reason for the failure in master is that the functionality has been moved from package.bbclass to package.py. I have created the patch for master and sent it for review. Cheers Sreejith On Wed, Jun 26, 2024 at 2:40 PM Sreejith Ravi via lists.openembedded.org wrote: > Patch is created from t

Re: [OE-core] [PATCH] u-boot.inc: WORKDIR -> UNPACKDIR transition

On Wed, 2024-06-26 at 15:34 +0200, Quentin Schulz wrote: > Hi Richard, > > On 6/26/24 3:20 PM, Richard Purdie via lists.openembedded.org wrote: > > On Mon, 2024-06-24 at 00:32 +0300, Leon Anavi via lists.openembedded.org > > wrote: > > > Replace references of WORKDIR with UNPACKDIR for U-Boot scr

[OE-core] [PATCH] package.py: Add Requires.private field in process_pkgconfig

Currently, the process_pkgconfig() only handles the "Requires" key field from the .pc file and ignores the "Requires.private" field while generating the dev dependency chain. This results in a broken dependency list and requires the installation of recommended packages to resolve the build dependen

Re: [OE-core] [PATCH] package.bbclass: Add Requires.private field in package_do_pkgconfig()

Patch is created from the Kirkstone branch. Cheers Sreejith On Wed, Jun 26, 2024 at 2:37 PM Richard Purdie wrote: > On Tue, 2024-06-25 at 19:15 +, Sreejith Ravi via > lists.openembedded.org wrote: > > Currently, the package_do_pkgconfig() only handles the "Requires" key > > field from the .

Re: [OE-core] [PATCH] package.bbclass: Add Requires.private field in package_do_pkgconfig()

On Tue, 2024-06-25 at 19:15 +, Sreejith Ravi via lists.openembedded.org wrote: > Currently, the package_do_pkgconfig() only handles the "Requires" key > field from the .pc file and ignores the "Requires.private" field > while > generating the dev dependency chain. This results in a broken > dep

Re: [OE-core] [PATCH] u-boot.inc: WORKDIR -> UNPACKDIR transition

Hi Richard, On 6/26/24 3:20 PM, Richard Purdie via lists.openembedded.org wrote: On Mon, 2024-06-24 at 00:32 +0300, Leon Anavi via lists.openembedded.org wrote: Replace references of WORKDIR with UNPACKDIR for U-Boot script and variable UBOOT_ENV_BINARY, for example for boot.scr. Signed-off-by

Re: [OE-core] [PATCH] package.bbclass: Add Requires.private field in package_do_pkgconfig()

On Wed, 2024-06-26 at 13:41 +0100, Richard Purdie via lists.openembedded.org wrote: > On Wed, 2024-06-26 at 10:07 +0100, Sreejith Ravi wrote: > > No, static libraries were not enabled. I am using only the -dev > > IPK, > > which has only the shared libraries. With this change, it is > > successfull

Re: [OE-core] [PATCH] u-boot.inc: WORKDIR -> UNPACKDIR transition

On Mon, 2024-06-24 at 00:32 +0300, Leon Anavi via lists.openembedded.org wrote: > Replace references of WORKDIR with UNPACKDIR for U-Boot script > and variable UBOOT_ENV_BINARY, for example for boot.scr. > > Signed-off-by: Leon Anavi > --- >  meta/recipes-bsp/u-boot/u-boot.inc | 6 +++--- >  1 fil

Re: [OE-core] [PATCH] package.bbclass: Add Requires.private field in package_do_pkgconfig()

On Wed, 2024-06-26 at 10:07 +0100, Sreejith Ravi wrote: > No, static libraries were not enabled. I am using only the -dev IPK, > which has only the shared libraries. With this change, it is > successfully building. Also, if it links to the static library, it > will fail as I am not installing the s

Re: [OE-core] [scarthgap][PATCH] go: fix CVE-2024-24789

Hi Hitendra, I sent a backport with the latest golang 1.22.4 from master https://lists.openembedded.org/g/openembedded-core/message/201157 Jose Hitendra Prajapati via lists.openembedded.org escreveu (quarta, 26/06/2024 à(s) 05:36): > Upstream-Status: Backport from > https://github.com/golang/g

[OE-core][scarthgap][PATCH 3/3] go: drop the old 1.4 bootstrap C version

From: Jose Quaresma Bootstrap [1] As mentioned in the Go 1.20 release notes, Go 1.22 now requires the final point release of Go 1.20 or later for bootstrap. We expect that Go 1.24 will require the final point release of Go 1.22 or later for bootstrap. The default recipe for bootstrap is the go

[OE-core][scarthgap][PATCH 2/3] go: upgrade 1.22.3 -> 1.22.4

From: Jose Quaresma Include fixes for CVE-2024-24790 Upgrade to latest 1.22.x release [1]: $ git --no-pager log --oneline go1.22.3..go1.22.4 ace5bb40d0 (tag: go1.22.4) [release-branch.go1.22] go1.22.4 12d5810cdb [release-branch.go1.22] net/netip: check if address is v6 mapped in Is methods 745

[OE-core][scarthgap][PATCH 1/3] go: upgrade 1.22.2 -> 1.22.3

From: Jose Quaresma Upgrade to latest 1.22.x release [1]: $ git --no-pager log --oneline go1.22.2..go1.22.3 adbfb672ba (tag: go1.22.3) [release-branch.go1.22] go1.22.3 fa0292d252 [release-branch.go1.22] cmd/go: disallow -lto_library in LDFLAGS 947e43e371 [release-branch.go1.22] Revert "cmd/compi

[OE-core] [PATCH] testimage: Gate artifact collection with variable

It does not always make sense to collect artifacts and data from the target on failure, e.g. if testing firmware or if the target is not running an SSH server. Introduce the variable TESTIMAGE_RUN_FAILURE_POST_ACTIONS, which defaults to "1". If this variable is not true, skip the failed test post

Re: [OE-core] [PATCH] package.bbclass: Add Requires.private field in package_do_pkgconfig()

No, static libraries were not enabled. I am using only the -dev IPK, which has only the shared libraries. With this change, it is successfully building. Also, if it links to the static library, it will fail as I am not installing the static IPK. In the latest pkgconf commit, it looks like Requires

Re: [OE-core][kirkstone][PATCH] xz: Update LICENSE variable for xz packages

Hello, Change is addressed and upstreamed to master and scarthgap as well, as suggested by Alexander Kanavin. Link: https://lists.openembedded.org/g/openembedded-core/message/201152 [https://lists.openembedded.org/g/openembedd

[OE-core][master][scarthgap][PATCH] xz: Update LICENSE variable for xz packages

Update LICENSE defined for xz packages to match the license information provided in the xz COPYING file. The License information from PACKAGERS file of xz mentions packages with lzma files are in public domain.They ask to use GPLv2+, if only it's not possible to mention "PD and GPLv2+". Include P