Fixes a build issue seen with latest gcc trunk.
Fixes
| ../../elfutils-0.189/tests/elfstrmerge.c: In function 'main':
| ../../elfutils-0.189/tests/elfstrmerge.c:450:32: error: 'calloc' sizes
specified with 'sizeof' in the earlier argument and not in the later argument
There are two types of cases: executables and POSIX shell scripts.
All test cases PASS.
Add xz-ptest to PTESTS_FAST because test duration less than 30s
on qemux86-64.
root@qemux86-64:~# ptest-runner xz
START: ptest-runner
2024-01-26T03:32
BEGIN: /usr/lib/xz/ptest
=== test_bcj_exact_size.c ===
Changelog:
https://lwn.net/Articles/957396/
Drop 2 backported patches and 1 implemented differently upstream.
Signed-off-by: Denys Dmytriyenko
---
...-and-cpu_core_id-moved-in-linux-6.7..patch | 79 ---
...per-fdtable-adjust-fd-lookup-to-v6.7.patch | 35
From: Lee Chee Yang
Signed-off-by: Lee Chee Yang
---
.../xwayland/xwayland/CVE-2023-6377.patch | 82 +++
.../xwayland/xwayland/CVE-2023-6478.patch | 66 +++
.../xwayland/xwayland_22.1.8.bb | 2 +
3 files changed, 150 insertions(+)
create mode
From: Wang Mingyu
Changelog:
==
-Fix compiler error when checking if required blocks in parent templates are
empty.
-xmlattr filter does not allow keys with spaces.
-Make error messages stemming from invalid nesting of {% trans %} blocks more
helpful
(cherry picked from OE-Core rev:
From: Alexander Kanavin
(cherry picked from OE-Core rev: 1e58fa1fff649a4ab07290d2b0e5a8d69d51ef16)
Signed-off-by: Alexander Kanavin
Signed-off-by: Luca Ceresoli
Signed-off-by: Richard Purdie
Signed-off-by: Lee Chee Yang
---
.../python/{python3-jinja2_3.1.1.bb => python3-jinja2_3.1.2.bb} |
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/RFC-RESEND-cve-update-nvd2-native-make-an-error-if-the-DB-file-is-not-present-at-the-end-of-do_fetch.patch
FAIL:
From: Yuta Hayama
Signed-off-by: Yuta Hayama
---
Please do not apply this. For now, this is just my question.
I think the issue of [YOCTO #14929] is partially still there.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14929
Certainly, now that 8efe99214d has been applied, do_cve_check no
Overview of Changes in 4.12.5, 17-01-2024
=
* GtkColumnView:
- Fix a crash on dispose
* GtkEmojiChooser:
- Update to CLDR v44
- Add more translations
* GtkFileDialog:
- Return an error if no file is selected
- Make closing the portal file chooser
On Thu, 2024-01-25 at 22:41 +0100, Alexander Kanavin wrote:
> Initial release of Ubuntu 18.04 had 4.15 alright. Later point releases
> offered much newer kernels. It’s also altogether EOL since end of may 2023.
>
> Why should oe-core carry these? It’s RP’s call as qemu maintainer but my vote
>
QEMU is a symptom of the real problem.
SDK_OLDEST_KERNEL is set to 3.2.0. If that is what we keep it as, then we need
to make sure that the nativesdk tooling works on a pre 4.17 kernel.
If that value moves to 4.17 then we can't use the same uninative /
buildtools-tarball with older (LTS)
On 1/25/24 3:42 PM, Martin Jansa wrote:
I did something similar for LGE when we were using 18.04 ubuntu, but IIRC it's
not about the kernel version, but glibc being older than 2.27.
18.04 is already unsupported for a while, I don't think oe-core should support
unsupported host OS versions
I did something similar for LGE when we were using 18.04 ubuntu, but IIRC
it's not about the kernel version, but glibc being older than 2.27.
18.04 is already unsupported for a while, I don't think oe-core should
support unsupported host OS versions (that's why I've never send my
version).
To
Initial release of Ubuntu 18.04 had 4.15 alright. Later point releases
offered much newer kernels. It’s also altogether EOL since end of may 2023.
Why should oe-core carry these? It’s RP’s call as qemu maintainer but my
vote is a firm no, unless additional arguments are put forward.
Alex
On Thu
We were attempting to build qemu on an Ubuntu 18.04 system and ran into
an issue where certain (newer) MMAP flags were not defined. After further
tracking it was determined that QEMU 8.1 moved forward and only supports
usage on kernel 4.17 or newer.
Using the patch included with this, you can
From: Mark Hatle
Linux kernel 4.17 introduced two new mmap flags, MAP_FIXED_NOREPLACE and
MAP_SHARED_VALIDATE. Starting with QEMU 8.1, these flags are now used
and required for proper system operation. In order to build and run on a
system older then 4.17, we need to emulate this new behavior.
The task for fstypes with compression is the same as the task for the
uncompressed fstypes, e.g. when adding tar.xz to `IMAGE_FSTYPES`, it will
be included into the do_image_tar task and not creating a separate
do_image_tar.xz task.
This commit fixes `LIVE_ROOTFS_TYPE` with compressed fstypes by
From: Fabio Estevam
Update to the latest piglit revision.
Signed-off-by: Fabio Estevam
---
meta/recipes-graphics/piglit/piglit_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/piglit/piglit_git.bb
b/meta/recipes-graphics/piglit/piglit_git.bb
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/python3-numpy-Use-Large-File-Support-version-of-fallocate.patch
FAIL: test Signed-off-by presence: A patch file
This was supposed to always be the case from upstream but was exposed
by the 64-bit-time QA checker when file function scanning was enabled.
Signed-off-by: Ola x Nilsson
---
...le-fallocate-on-32-bit-linux-platfor.patch | 49 +++
.../python/python3-numpy_1.26.2.bb|
From: Yash Shinde
* Enable rust oe-selftest.
* Include the dependent patches for rust oe-selftest in
meta/recipes-devtools/rust/rust-source.inc
* Disable rust oe-selftest for mips32 target (Rust upstream has classified it
into tier 3 target,
for which the Rust project does not build or
From: Yash Shinde
Fixes: thread 'main' panicked at 'assertion failed: `(left == right)`
left: `x86_64-unknown-linux-gnu`,
right: `x86_64-poky-linux-gnu`: Cannot obtain compiler for non-native
build triple at stage 0', compile.rs:1474:13
Add correct target value for cross-compiled
From: Yash Shinde
Add newly failing tests cases in the exclude list for
rust oe-selftest.
Signed-off-by: Yash Shinde
---
meta/lib/oeqa/selftest/cases/rust.py | 38 +++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/selftest/cases/rust.py
From: Yash Shinde
To avoid overlap and redundancy of rust tests, remove the test cases whose
parent dir is already excluded.
Tests which are failing from below dirs are removed as these dirs are
already present in exclude list
tests/run-make
tests/rustdoc
From: Yash Shinde
Fixes: error: the option `Z` is only accepted on the nightly compiler
When rust.channel is set to either beta or stable, we can't use
nightly features on bootstrap without RUSTC_BOOTSTRAP.
Set RUSTC_BOOTSTRAP=1 to use nightly features on stable or beta.
Signed-off-by: Yash
From: Yash Shinde
Fixes: thread 'main' panicked at 'failed to gather the target spec
for '-unknown-linux-gnu', synthetic_targets.rs:66:9
Detect and fetch custom target configurations when rustc is
bootstrapped in rust oe-selftest.
Signed-off-by: Yash Shinde
---
From: Yash Shinde
Fixes: Exception: no cargo executable found at
`${B}/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo`
Fix the cargo binary path error on oe-selftest and path set to rust-snapshot
dir.
Patch sent to upstream-
In this particular case the line should be removed IMO.
On Thu, Jan 25, 2024 at 2:04 PM Etienne Cordonnier via
lists.openembedded.org wrote:
> Hi Robert,
> for this kind of things I usually run bitbake -e dropbear >
> out-before.txt, remove the line, then run bitbake -e dropbear >
>
Hi Robert,
for this kind of things I usually run bitbake -e dropbear > out-before.txt,
remove the line, then run bitbake -e dropbear > out-after.txt, and finally
vimdiff out-before.txt out-after.txt
Etienne
On Thu, Jan 25, 2024 at 12:22 PM Robert P. J. Day
wrote:
>
> (NOTE: i'm currently
I don't think so.
git pw series list --submitter "Vyacheslav Yurkov"
Shows the latest series 21353 from me.
Regards,
Slava
On 22.01.2024 16:35, Lukas Funke wrote:
Is this the reason why I cannot find the series on patchwork? This
makes it kinda tricky to review/test IMHO.
Please provide a
(NOTE: i'm currently tutoring some colleagues in the basics of OE
and using standard OE recipes as examples of good programming
practice, so occasionally i run across something that looks strange
and i just want to clarify so i don't have to say, "i don't know, i
guess there's a reason for
Doesn't this also break PV monotonically increasing?
Alex
On Thu, 25 Jan 2024 at 10:26, Yu, Mingli wrote:
>
> From: Mingli Yu
>
> Update the version to make package version consistent and there is
> indeed the source as blktool_4.orig.tar.gz [1].
> Before the patch:
> # rpm -qa | grep
This breaks upstream version check and automated updates, I can't accept that:
$ devtool latest-version icu
INFO: Current version: 74.1
INFO: Latest version: 74-2
It also breaks PV monotonically increasing.
Alex
On Thu, 25 Jan 2024 at 10:26, Yu, Mingli wrote:
>
> From: Mingli Yu
>
> Update
On Thu, 25 Jan 2024 at 10:25, Yu, Mingli wrote:
>
> From: Mingli Yu
>
> Correct the PV to make the version consistent.
> SRCREV = "d97db4fae4c1cd099b506970b285dc2afd818ea2"
> -PV = "0.29.2+git"
> +PV = "0.29.2"
0.29.2 release tag maps to a different commit, so we cannot drop +git:
From: Mingli Yu
Update the version to make package version consistent and there is
indeed the source as blktool_4.orig.tar.gz [1].
Before the patch:
# rpm -qa | grep blktool
blktool-4+7.1-r0.core2_64
# blktool
blktool version 4
usage: blktool [options] DEVICE COMMAND [args...]
From: Mingli Yu
Correct the PV to make the version consistent.
Before the patch:
# rpm -qa | grep pkgconfig
pkgconfig-0.29.2+git0+d97db4fae4-r0.core2_64
# rpm -ql pkgconfig
/usr
/usr/bin
/usr/bin/pkg-config
/usr/bin/x86_64-wrs-linux-gnu-pkg-config
/usr/share
/usr/share/aclocal
From: Mingli Yu
Update the version in the bb name to make the version consistent.
Before the patch:
# rpm -qa | grep icu
icu-74+1-r0.core2_64
# rpm -ql icu
/usr
/usr/bin
/usr/bin/derb
[snip]
# derb --version
derb version 1.1 (ICU version 74.1).
Copyright (C) 2016 and later: Unicode,
On Thu, 25 Jan 2024 at 03:55, Xu, Chi wrote:
> > I still don't understand this part. If these scripts are executed as a part
> > of
> > standard in-tree unit testing, what prints PASS/FAIL in that context?
> > Shouldn't
> > we reuse that, to replicate the in-tree testing sequence as much as
>
38 matches
Mail list logo
