Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/v2-create-spdx-3.0-populate_sdk_base-Add-SDK_CLASSES-inherit-mechanism-to-fix-tarball-SPDX-manifests.patch
FAIL: te
Currently, "tarball" sdk based recipes don't generate SPDX manifests as they
don't include the rootfs generation classes. Split the SPDX 3.0 image class into
two so the SDK components can be included where needed.
To do this, introduce an SDK_CLASSES variable similar to IMAGE_CLASSES which
the SDK
Update to a new revision which includes "Bugfix for Linux open(O_CREAT|O_EXCL)"
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/pseudo/pseudo_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/pseudo/pseudo_git.bb
b/meta/recipes-devtools/pse
ping
On 7/16/24 11:24, Changqing Li via lists.openembedded.org wrote:
From: Changqing Li
Fix following error:
File "/usr/lib64/rt-tests/ptest/./rt_bmark.py", line 287, in
run_cyclictest_once
m = rex.search(line)
TypeError: cannot use a string pattern on a byte
From: Peter Marko
This CVE status should have been removed on version update.
CPE says >=2.34 and <2.39 while our version is already 2.40.
Signed-off-by: Peter Marko
---
meta/recipes-core/glibc/glibc-version.inc | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta/recipes-core/glibc/glibc
From: Mark Hatle
Newlib generally requires additional components to function. Skip the
cases where newlib is known to not work.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
I'm not entirely sure the patch is right, but it provides a mechanism to
exclude specific TCLIBCs from certa
Upstream has a pyproject.toml but it's marked as experimental and does
not currently work at all with the meson-python release we currently
have.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/python/python3-numpy_1.26.4.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipe
Enable the new pep517-backend warning from setuptools3, initially as a
warning so as not to break builds straight away.
Signed-off-by: Ross Burton
---
meta/classes-global/insane.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes-global/insane.bbclass
b/meta
Some recipes use setuptools3 but should be using a PEP517-compliant
backend, be it the setuptools itself via python_setuptools_build_meta or
an alternative backend such as flit/hatch/poetry.
As we can't currently assume Python 3.11 on the build host we need to
parse the pyproject.toml manually, bu
Whilst bmaptool has a pyproject.toml that uses poetry, the setuptools
build path appears to be more complete. Upstream has moved to hatch and
removed setup.py entirely so the next release can drop this.
Signed-off-by: Ross Burton
---
meta/recipes-support/bmaptool/bmaptool_git.bb | 3 +++
1 file
On Thu, 2024-07-25 at 16:48 +0200, mrybczyn...@syslinbit.com wrote:
> On 25.07.2024 16:29, Richard Purdie wrote:
> > Hi Marta,
> >
> >
> > With the v3 series applied we did just see this on the autobuilder
> > unfortunately so I'm not sure that problem is addressed:
> >
> > https://autobuilder.y
Hi Marta,
With the v3 series applied we did just see this on the autobuilder
unfortunately so I'm not sure that problem is addressed:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/7004/steps/14/logs/stdio
ERROR: m4-native-1.4.19-r0 do_cve_check: Error executing a python fun
[Edited Message Follows]
I am analyzing the following failure and adding my observations here for any
help/suggestions.
https://lists.openembedded.org/g/openembedded-core/message/201312.
Traceback (most recent call last):
File
"/home/pokybuild/yocto-worker/genericx86-64/build/meta/lib/oeqa/sdk/
[Edited Message Follows]
I am analyzing the following failure and adding my observations here for any
help/suggestions.
https://lists.openembedded.org/g/openembedded-core/message/201312.
Traceback (most recent call last):
File
"/home/pokybuild/yocto-worker/genericx86-64/build/meta/lib/oeqa/sdk/
I am analyzing the following failure and adding my observations here for any
help/suggestions.
https://lists.openembedded.org/g/openembedded-core/message/201312.
Traceback (most recent call last):
File
"/home/pokybuild/yocto-worker/genericx86-64/build/meta/lib/oeqa/sdk/cases/rust.py",
line 34
I'm getting the following error at build time:
ERROR: libarchive-native-3.7.4-r0 do_patch: Applying patch
'CVE-2024-26256.patch' on target directory
'/home/steve/builds/poky-contrib-scarthgap/build/tmp/work/x86_64-linux/libarchive-native/3.7.4/libarchive-3.7.4'
CmdError('quilt --quiltrc
/home/stev
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/v8-3-3-libssh2-fix-ptest-regression-with-openssh-9.8p1.patch
FAIL: test commit message presence: Please include a c
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/v8-2-3-openssh-upgrade-9.7p1---9.8p1.patch
FAIL: test CVE tag format: Missing or incorrectly formatted CVE tag in p
Drop our sd-notify patch and switch to the upstream standalone
implementation that does not depend on libsystemd.
Signed-off-by: Jose Quaresma
---
v4:
- split update of Upstream-Status in new patches in the serie
v5:
- use the upstream solution
v6:
- sshd socket service runs with '-i' and d
- drop the CVE-2024-6387 [backported patch]
- drop systemd notify [backported patch]
- fix musl build [backported patch]
- fix ptest regression [submited patch]
- sshd now had the sshd-session
Release notes at https://www.openssh.com/txt/release-9.8
Security
This release contains fixes
Signed-off-by: Jose Quaresma
---
...t-drop-ssh-dss-openssh_server-config.patch | 30 +++
.../recipes-support/libssh2/libssh2_1.11.0.bb | 1 +
2 files changed, 31 insertions(+)
create mode 100644
meta/recipes-support/libssh2/libssh2/0001-test-drop-ssh-dss-openssh_server-config.p
The implementation uses the append operator to include
GLIBC_64BIT_TIME_FLAGS in TARGET_CC_ARCH, but it places the space in
the GLIBC_64BIT_TIME_FLAGS assignment in order to avoid a 'spurious
space' when the value is empty.
68b50d3 time64: Remove leading whitespace from GLIBC_64BIT_TIME_FLAGS
The
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/create-spdx-3.0-populate_sdk_base-Add-SDK_CLASSES-inherit-mechanism-to-fix-tarball-SPDX-manifests.patch
FAIL: test
Currently, "tarball" sdk based recipes don't generate SPDX manifests as they
don't include the rootfs generation classes. Split the SPDX 3.0 image class into
two so the SDK components can be included where needed.
To do this, introduce an SDK_CLASSES variable similar to IMAGE_CLASSES which
the SDK
On Wed, 2024-07-24 at 17:08 +0100, Ross Burton via
lists.openembedded.org wrote:
> Sort the entries for OCD reasons.
>
> Signed-off-by: Ross Burton
> ---
> meta/conf/distro/include/ptest-packagelists.inc | 15 ---
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/me
25 matches
Mail list logo
