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/3-3-gnu-efi-upgrade-3.0.17---3.0.18.patch
FAIL: test src uri left files: Patches not removed from tree. Remove
Changelog:
https://github.com/libsdl-org/SDL/releases/tag/release-2.30.3
This is a stable bugfix release, with the following changes:
- Fixed Win+V handling (pasting from clipboard history) on Windows
- Fixed Caps Lock and Backspace key mapping for the Colemak keyboard layout on
Windows
-
* Drop backport patches.
* Refresh patches.
Signed-off-by: Yi Zhao
---
...-parallel-make-failure-for-archives.patch} | 12 ---
...0001-riscv64-adjust-type-definitions.patch | 34 ---
.../0001-riscv64-ignore-unknown-relocs.patch | 32 -
Changelog:
https://matt.ucc.asn.au/dropbear/CHANGES
This release fixes build regressions in 2024.84:
- Fix build failure when SHA1 is disabled
- Fix build failure when DROPBEAR_CLI_PUBKEY_AUTH disabled
- Update debian/ directory with changed paths
Signed-off-by: Yi Zhao
---
Is there a recipe or explanation on how to integrate prebuilt nodejs and
node-gyp for an embedded platform?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199499):
https://lists.openembedded.org/g/openembedded-core/message/199499
Mute This Topic:
On Thu, May 16, 2024 at 10:05 PM Khem Raj wrote:
>
> On Wed, May 15, 2024 at 10:29 PM Martin Jansa via
> lists.openembedded.org
> wrote:
> >
> > Hi Peter,
> >
> > what about BSD-4-Clause-UC, BSD-3-Clause, ISC licenses included in glibc.
> >
> > I've suggested to add them long time ago in:
> >
On Wed, May 15, 2024 at 10:29 PM Martin Jansa via
lists.openembedded.org
wrote:
>
> Hi Peter,
>
> what about BSD-4-Clause-UC, BSD-3-Clause, ISC licenses included in glibc.
>
> I've suggested to add them long time ago in:
>
Hi Martin,
license handling is a very complicated topic, especially for historical
projects like glibc with ton of files with diverse origin.
License scanning programs will find 15+ different licenses here and some of
them may not be even available in yocto license list.
I submitted this
On Thu, May 16, 2024 at 4:27 AM Alexander Kanavin via
lists.openembedded.org
wrote:
>
> From: Alexander Kanavin
>
> Somewhere on the way it ceased to be necessary.
Thats due it being applied upstream [1] so mentioning that is perhaps
going to qualify this a bit more.
[1]
On Thu, 16 May 2024 at 17:57, Ross Burton via lists.openembedded.org
wrote:
> > I'm fine with moving out iso but hddimg has proven to be used by more
> > that you'd think. It also has fairly complex code in core which if
> > we're keeping it, I'd like a way to test it…
>
> Unfortunately an hddimg
On 16 May 2024, at 16:53, Richard Purdie
wrote:
> I'm fine with moving out iso but hddimg has proven to be used by more
> that you'd think. It also has fairly complex code in core which if
> we're keeping it, I'd like a way to test it…
Unfortunately an hddimg is an ISO on a FAT, so they’re
On Thu, 2024-05-16 at 13:47 +, Ross Burton via lists.openembedded.org wrote:
> oe-core has an ‘iso’ image type that creates ISO9660 images for
> booting from a CD/DVD. At the moment this is implemented using
> cdrtools (aka cdrecord) but this has “legal complications” meaning a
> number of
This overlaps with the following commit in kirkstone:
https://git.yoctoproject.org/poky/commit/?h=kirkstone=688f3725d2bc14f1343d2d3fb9b13c58c1140089
Please submit a V2 which omits the already fixed CVEs
Thanks!
Steve
On Tue, May 14, 2024 at 10:54 PM Soumya via lists.openembedded.org
wrote:
>
Marta Rybczynska via lists.yoctoproject.org escreveu (quinta, 16/05/2024 à(s) 14:20):
> Hello all,
> The prototype CVE check via the MITRE database is giving the following for
> scathgap today (adding maintainers of affected packages in copy):
>
> CVE-2024-32002.json: affected: git 2.44.0
>
Hi,
oe-core has an ‘iso’ image type that creates ISO9660 images for booting from a
CD/DVD. At the moment this is implemented using cdrtools (aka cdrecord) but
this has “legal complications” meaning a number of mainstream distributions
don’t use cdrtools [1], and the project is - generously
Thank you Marko for the feedback! For CVE-2024-34397 the reason is simple:
"affected": [
{
"vendor": "n/a",
"product": "n/a",
"versions": [
{
"version": "n/a",
Hello Marta,
Glibc fixes are already staged in scarthgap-nut.
Interesting would be to check why the prototype does not list glib-2.0
CVE-2024-34397 which is staged there, too.
Peter
From: yocto-secur...@lists.yoctoproject.org
On Behalf Of Marta Rybczynska via
lists.yoctoproject.org
Sent:
Hello all,
The prototype CVE check via the MITRE database is giving the following for
scathgap today (adding maintainers of affected packages in copy):
CVE-2024-32002.json: affected: git 2.44.0
CVE-2024-32004.json: affected: git 2.44.0
CVE-2024-32020.json: affected: git 2.44.0
> -Original Message-
> From: openembedded-core@lists.openembedded.org
> On Behalf Of Seungkyun Kim
> Sent: den 16 maj 2024 02:12
> To: openembedded-core@lists.openembedded.org
> Cc: seungkyun.kim
> Subject: [OE-core] [PATCH v4] ipk/rootfs: run sanity test of multilib in
> parallel
>
>
On 16-05-2024 13:41, Mike Looijmans via lists.openembedded.org wrote:
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topic.nl
W: www.topic.nl
Please
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topic.nl
W: www.topic.nl
Please consider the environment before printing this e-mail
On 16-05-2024 13:34,
On 16 May 2024, at 12:03, Mike Looijmans via lists.openembedded.org
wrote:
>
> Using scartgap branch, trying to create a kernel recipe for a custom LS1028
> machine.
>
> The recipe in meta-freescale for the ls1028ardb is hopelessly outdated and
> produces a 5.10 kernel.
>
> So for my custom
On Thu, 16 May 2024 at 13:00, Alexander Kanavin via
lists.openembedded.org
wrote:
> I'll send the ab patches that break the test suite later today; the
> request is to take them, and unbreak the test suite.
>
> Then you can rebase your upgrade work on top of that. And address the
> usability
From: Alexander Kanavin
Verified on qemuarm64/musl (as the patch says).
Signed-off-by: Alexander Kanavin
---
.../elfutils/elfutils_0.191.bb| 1 -
.../0006-Fix-build-on-aarch64-musl.patch | 58 ---
2 files changed, 59 deletions(-)
delete mode 100644
From: Alexander Kanavin
This is done via configure option, and makes
0004-configure.ac-only-check-conntrack-when-libnfnetlink-.patch
unnecessary, as both libnetfilter_conntrack and libnfnetlink
are enabled in lockstep.
Signed-off-by: Alexander Kanavin
---
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
---
.../libvorbis/libvorbis/0001-configure-Check-for-clang.patch| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/recipes-multimedia/libvorbis/libvorbis/0001-configure-Check-for-clang.patch
From: Alexander Kanavin
The mirror was out of date; meanwhile x264 remains in active development.
Drop unsuitable x32 patch and declare x264 incompatible with the target
(by every sign it's an extinct target; if not so please work with upstream
to develop a solution there).
Replace
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
---
.../0003-kexec-ARM-Fix-add_buffer_phys_virt-align-issue.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/recipes-kernel/kexec/kexec-tools/0003-kexec-ARM-Fix-add_buffer_phys_virt-align-issue.patch
From: Alexander Kanavin
Somewhere on the way it ceased to be necessary.
Signed-off-by: Alexander Kanavin
---
...ed.h-add-missing-sys.types.h-include.patch | 31 ---
.../iptables/iptables_1.8.10.bb | 1 -
2 files changed, 32 deletions(-)
delete mode 100644
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
---
...ption-to-enable-disable-libnfnetlink.patch | 44 +++
1 file changed, 26 insertions(+), 18 deletions(-)
diff --git
From: Alexander Kanavin
Verified on qemux86 and qemux86-64 with grub and grub-efi.
Signed-off-by: Alexander Kanavin
---
...ath-sse-as-well-when-SSE-is-disabled.patch | 44 ---
meta/recipes-bsp/grub/grub2.inc | 1 -
2 files changed, 45 deletions(-)
delete mode
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/perl/files/determinism.patch | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/perl/files/determinism.patch
b/meta/recipes-devtools/perl/files/determinism.patch
From: Alexander Kanavin
Somewhere on the way the issue solved itself.
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/gdb/gdb.inc | 1 -
...06-resolve-restrict-keyword-conflict.patch | 45 ---
2 files changed, 46 deletions(-)
delete mode 100644
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
---
.../grub-module-explicitly-keeps-symbole-.module_license.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/recipes-bsp/grub/files/grub-module-explicitly-keeps-symbole-.module_license.patch
From: Alexander Kanavin
The patch was submitted upstream
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28895
but further investigation revealed that the problem had been solved properly
in meson.class:
From: Alexander Kanavin
This as well has been solved via
https://git.yoctoproject.org/poky/commit/?id=f6a35934540e910794b8729ecc278189a39b710f
Signed-off-by: Alexander Kanavin
---
...-correctly-when-building-with-mingw3.patch | 80 ---
meta/recipes-core/glib-2.0/glib.inc
From: Alexander Kanavin
Setting it explicitly replaces rust's default choice which is rustdoc
(needed for example in selftests and otherwise expected to be present
in typical rust installations):
https://github.com/rust-lang/rust/blob/master/config.example.toml#L320
This addresses some of the
From: Alexander Kanavin
[YOCTO #15185]
Signed-off-by: Alexander Kanavin
---
...te-host-information-into-compilation.patch | 51 +++
meta/recipes-devtools/rust/rust-source.inc| 1 +
2 files changed, 52 insertions(+)
create mode 100644
From: Alexander Kanavin
This does not seem to be used in regular builds, but is beneficial
in rust selftest, where it allows dropping a custom patch
that is unsuitable for upstream (and was rejected by them).
Also remove an obsolete comment that seems related to the code
but describes something
From: Alexander Kanavin
Otherwise, use rust-native and cargo-native binaries as that allows
our native tweaks in them to be used for target/nativesdk rust -
same as for everything else written in rust.
In particular, this allows building target rust with
cargo-native that includes important
* Updated Unicode tables to version 15.1
Signed-off-by: Ross Burton
---
.../fribidi/{fribidi_1.0.13.bb => fribidi_1.0.14.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/fribidi/{fribidi_1.0.13.bb => fribidi_1.0.14.bb}
(89%)
diff --git
* Add .venv to the list of directories that cannot be traversed
* Output from the core Application utility now writes to stderr
Signed-off-by: Ross Burton
---
...{python3-hatchling_1.24.1.bb => python3-hatchling_1.24.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename
- Fix a build failure (Christian Heusel)
- Fix occasional build failures (Benjamin Gilbert)
- ani: Reject files with multiple INA or IART chunks (Benjamin Gilbert)
- ani: Reject files with multiple anih chunks (Benjamin Gilbert, CVE-2022-48622)
- ani: validate chunk size (Benjamin Gilbert)
-
Using scartgap branch, trying to create a kernel recipe for a custom LS1028
machine.
The recipe in meta-freescale for the ls1028ardb is hopelessly outdated and
produces a 5.10 kernel.
So for my custom board based on the ls1028 I want to create a recipe that
builds a mainline kernel (I don't
On Thu, 16 May 2024 at 12:57, Yash Shinde wrote:
> We have rust 1.76 and 1.77 upgrades along with test suite working
> locally. Currently, we are testing with 1.78 upgrade.
>
> IIUC, Alex has another series of AB fixes which breaks the test suite.
> Should we check the test suite with those
On 16-05-2024 15:53, Alexander Kanavin 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.
On Thu, 16 May 2024 at 12:15, Richard Purdie wrote:
There is an extra
Signed-off-by: Anuj Mittal
---
.../harfbuzz/{harfbuzz_8.4.0.bb => harfbuzz_8.5.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/harfbuzz/{harfbuzz_8.4.0.bb => harfbuzz_8.5.0.bb}
(95%)
diff --git
Signed-off-by: Anuj Mittal
---
meta/recipes-core/glib-networking/glib-networking/eagain.patch | 2 +-
.../{glib-networking_2.78.1.bb => glib-networking_2.80.0.bb}| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-core/glib-networking/{glib-networking_2.78.1.bb =>
Signed-off-by: Anuj Mittal
---
...Do-not-write-bindir-into-pkg-config-files.patch | 2 +-
.../0001-Fix-DATADIRNAME-on-uclibc-Linux.patch | 2 +-
...stall-gio-querymodules-as-libexec_PROGRAM.patch | 2 +-
...warning-about-deprecated-paths-in-schemas.patch | 2 +-
Signed-off-by: Anuj Mittal
---
.../stress-ng/{stress-ng_0.17.07.bb => stress-ng_0.17.08.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/stress-ng/{stress-ng_0.17.07.bb =>
stress-ng_0.17.08.bb} (94%)
diff --git
On Wed, 2024-05-15 at 17:42 +, Peter Kjellerstedt wrote:
>
> > diff --git a/meta/classes-global/base.bbclass b/meta/classes-
> > global/base.bbclass
> > index 066f3848f7c..cdce0538273 100644
> > --- a/meta/classes-global/base.bbclass
> > +++ b/meta/classes-global/base.bbclass
> > @@ -153,20
The regression of LICENSE being missing from the sdist is relatively minor (but
will be fixed in 1.2, there’s a queued MR), but this release has behavioural
changes which is breaking setuptools/poetry, so I suggest nobody else try to do
the upgrade until 1.2 is released.
Ross
On 15 May 2024,
On Thu, 16 May 2024 at 12:15, Richard Purdie wrote:
> There is an extra consideration to this unfortunately which is
> scarthgap. For better or worse we have an LTS release with a mostly
> working test suite and this arm/x86 issue is present.
>
> Should I take the patches to master, the next
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/compile: don't combine
On Thu, 2024-05-16 at 11:19 +0200, Alexander Kanavin via
lists.openembedded.org wrote:
> As explained elsewhere, rust selftest is going to be disabled to
> resolve sporadic autobuilder failures. This also gives everyone a
> chance to update rust to latest upstream release without having to
> fight
Hi All,
QA for yocto-5.0.1.rc2 is completed. This is the full report for this release:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Jing Hui
>
As explained elsewhere, rust selftest is going to be disabled to
resolve sporadic autobuilder failures. This also gives everyone a
chance to update rust to latest upstream release without having to
fight with the selftest.
Before selftest is re-enabled, I would ask for the following improvements:
The code adds significant complexity, and the patch is difficult to
understand. The commit message should explain what the temporary
installation does, and why is needed. What does 'sanity test' do, and
how is it parallelized? Is it a part of that 'temporary installation'?
How is 'Installing
Polite ping.
On 23/04/2024 11.57, Rasmus Villemoes via lists.openembedded.org wrote:
> From: Rasmus Villemoes
>
> Commit 6c2ae2346db0 (kern-tools: depend on git-replacement-native)
> broke our kernel builds. For saving space and time, we have a DL_DIR
> shared between multiple users/buildbots,
On Thu, 2024-05-16 at 09:18 +0200, Martin Hundebøll wrote:
> On Wed, 2024-05-15 at 12:56 +0100, Richard Purdie wrote:
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index b2c500d8739..75c850760f6 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@
Avoid code duplication by making `extract` a shared method (and
retrieving the package manager specific input via an abstract method).
Additionally, follow Python conventions and prefix class internal
methods with "_" to indicate that they shouldn't be called externally.
Signed-off-by: Philip
It turns out that the IPK payload tarball was actually cleaned up in the
concrete package manager implementation (most likely because at some
point Debian and IPK packages used different compression algorithms).
Globbing removes this ambiguity so move the removal of the payload into
the common
The OpkgDpkgPM class was introduced to share common functionality
between the Opkg and Debian package manager implementations. However,
for unknown reasons , the refactoring done in
5bc67f55028407de78ac09f97f9a47b165ae8760 duplicated the common class
into the deb and ipk modules. Undo this part of
This patch series fixes one issue which I missed in
"lib/package_manager/ipk: Do not hardcode payload compression algorithm"
(2ad05635a6da403b4fadcc126fe7734067c12c73). Default configurations using
zstd are not affected but I'd still like to make sure that things are
cleaned up.
Additionally,
On Wed, 2024-05-15 at 12:56 +0100, Richard Purdie wrote:
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index b2c500d8739..75c850760f6 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -405,7 +405,7 @@ STAMP =
>
From: Ricardo Simoes
This commit sets the CVE_PRODUCT variable to "libusb" to match the
product name used in the NIST CPE database [1].
[1]: https://nvd.nist.gov/products/cpe/search
Signed-off-by: Ricardo Simoes
Signed-off-by: Mark Jonas
---
meta/recipes-support/libusb/libusb1_1.0.27.bb | 2
66 matches
Mail list logo
