Attached patch file also.
From: openembedded-core@lists.openembedded.org
on behalf of Virendra Thakur via
lists.openembedded.org
Sent: Saturday, October 1, 2022 11:20 AM
To: openembedded-core@lists.openembedded.org
Cc: st...@sakoman.com
Subject: [OE-Core][kir
Add patch to fix CVE-2021-3750
Signed-off-by: Virendra Thakur
---
meta/recipes-devtools/qemu/qemu.inc | 3 +
.../qemu/qemu/CVE-2021-3750-1.patch | 59 +++
.../qemu/qemu/CVE-2021-3750-2.patch | 65
.../qemu/qemu/CVE-2021-3750-3.patch | 156
On Fri, Sep 30, 2022 at 3:15 PM Jon Mason wrote:
>
> On Fri, Sep 30, 2022 at 09:29:24AM -0400, Bruce Ashfield wrote:
> > On Thu, Sep 29, 2022 at 11:23 PM Jon Mason wrote:
> > >
> > > Most machine features have corresponding kernel config fragments, but
> > > only a few have an entry in the kernel
Hello Markus,
This causes the following failure:
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/4140/steps/14/logs/stdio
On 30/09/2022 06:18:07+0200, Markus Volk wrote:
> wic imager is able to add entries for the partitions to fstab. This patch also
> creates an entry for the r
Thanks Alex, I will rework it.
On Fri, Sep 30, 2022 at 1:44 PM Alexandre Belloni
wrote:
>
> Hello,
>
> This caused many issues on the autobuilders, similar to those:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/5982/steps/11/logs/stdio
> https://autobuilder.yoctoproject.o
Hello,
This caused many issues on the autobuilders, similar to those:
https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/5982/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/96/builds/3796/steps/11/logs/stdio
On 29/09/2022 21:16:14-0700, Khem Raj wrote:
On Fri, Sep 30, 2022 at 09:29:24AM -0400, Bruce Ashfield wrote:
> On Thu, Sep 29, 2022 at 11:23 PM Jon Mason wrote:
> >
> > Most machine features have corresponding kernel config fragments, but
> > only a few have an entry in the kernel recipe to be automatically added.
> > Adding the majority of
Alexander Kanavin escreveu no dia sexta,
30/09/2022 à(s) 19:02:
> On Fri, 30 Sept 2022 at 20:01, Jose Quaresma
> wrote:
> > Forgot to remove the patch! Will send a v2 but I can't run the
> reproducibility now.
>
> You should, I believe the patch was added in the first place to fix
> the reproduc
On Fri, 30 Sept 2022 at 20:01, Jose Quaresma wrote:
> Forgot to remove the patch! Will send a v2 but I can't run the
> reproducibility now.
You should, I believe the patch was added in the first place to fix
the reproducibility issues, and won't be accepted if its removal
breaks that.
Alex
-=-
Hi Alex,
Alexander Kanavin escreveu no dia sexta,
30/09/2022 à(s) 18:57:
> You need to remove the actual patch, and run the reproducibility test.
>
Forgot to remove the patch! Will send a v2 but I can't run the
reproducibility now.
Jose
> Alex
>
> On Fri, 30 Sept 2022 at 19:55, Jose Quaresma
Hi Qi,
With patch in place I have seen some build issues mainly in
meta-virtualization
with ti am62xx-evm, am64xx-evm and riscv64 machines.
Propose to remove the patch as it seams to fix the issue and I don't see
any side effect after
testing it in some weeks.
https://lists.openembedded.org/g/ope
You need to remove the actual patch, and run the reproducibility test.
Alex
On Fri, 30 Sept 2022 at 19:55, Jose Quaresma wrote:
>
> With patch in place I have see some build issues mainly in meta-virtualization
> with ti am62xx-evm, am64xx-evm and riscv64 machines.
>
> All the mahines fails to b
The component has been reimplemented in rust, and comes
with a large list of dependencies in Cargo.toml/Cargo.lock.
Rather than list them by hand, use a file generated with
cargo-update-recipe-crates class.
Signed-off-by: Alexander Kanavin
---
.../python/python3-bcrypt-crates.inc | 53
For better or worse, more and more rust components are appearing that do
not include their dependencies in tarballs (or git trees), and rely on cargo
to fetch them. On the other hand, bitbake does not use cargo (and quite possible
won't ever be able to), and relies on having each item explicitly li
Improve the fatal error message of the yocto-kernel-tools symbol_why.py
and shows the command that generate the error as it can help understand
the root cause of the error.
Signed-off-by: Jose Quaresma
---
meta/classes-recipe/kernel-yocto.bbclass | 15 +--
1 file changed, 9 insertion
Prevents the default dependencies, namely the C compiler and standard C library
(libc),
from being added to DEPENDS. This variable is usually used within recipes that
do not
require any compilation using the C compiler.
This also improves the speed as it will not populate the
native sysroot with
With patch in place I have see some build issues mainly in meta-virtualization
with ti am62xx-evm, am64xx-evm and riscv64 machines.
All the mahines fails to build the following recipes:
| Summary: 5 tasks failed:
|
/srv/oe/build/conf/../../layers/meta-virtualization/recipes-containers/runc/runc
On Fri, Sep 30, 2022 at 10:10 AM Khem Raj wrote:
>
> On Fri, Sep 30, 2022 at 10:08 AM Khem Raj wrote:
> >
> > On Fri, Sep 30, 2022 at 10:01 AM Ross Burton wrote:
> > >
> > >
> > > > On 30 Sep 2022, at 17:42, Khem Raj wrote:
> > > > > Good point I will check in think it worked fine with glibc bu
On Fri, Sep 30, 2022 at 10:08 AM Khem Raj wrote:
>
> On Fri, Sep 30, 2022 at 10:01 AM Ross Burton wrote:
> >
> >
> > > On 30 Sep 2022, at 17:42, Khem Raj wrote:
> > > > Good point I will check in think it worked fine with glibc but not with
> > > > musl based images I see that Perl-modules is f
On Fri, Sep 30, 2022 at 10:01 AM Ross Burton wrote:
>
>
> > On 30 Sep 2022, at 17:42, Khem Raj wrote:
> > > Good point I will check in think it worked fine with glibc but not with
> > > musl based images I see that Perl-modules is fully empty in
> > > packages-split area so soMething does not a
> On 30 Sep 2022, at 17:42, Khem Raj wrote:
> > Good point I will check in think it worked fine with glibc but not with
> > musl based images I see that Perl-modules is fully empty in packages-split
> > area so soMething does not add up
>
> It will be empty as it’s a metapackage, but it shoul
On Fri, Sep 30, 2022 at 9:30 AM Ross Burton wrote:
>
>
> > On 30 Sep 2022, at 17:03, Khem Raj via lists.openembedded.org gmail@lists.openembedded.org> wrote:
> >
> > Good point I will check in think it worked fine with glibc but not with
> musl based images I see that Perl-modules is fully e
> On 30 Sep 2022, at 17:03, Khem Raj via lists.openembedded.org
> wrote:
>
> Good point I will check in think it worked fine with glibc but not with musl
> based images I see that Perl-modules is fully empty in packages-split area so
> soMething does not add up
It will be empty as it’s a m
On Fri, Sep 30, 2022 at 3:37 AM Ross Burton wrote:
>
>
> > On 30 Sep 2022, at 11:16, Ross Burton via lists.openembedded.org
> wrote:
> >
> > On 30 Sep 2022, at 05:16, Khem Raj via lists.openembedded.org gmail@lists.openembedded.org> wrote:
> >> -RDEPENDS:${PN}-ptest += "openssl-bin perl per
This is a version update with some API changes, so further review
would be appreciated before I can take this.
To help with review, here are the changes in this release:
Software configuration changes
Handle absolute paths in pkg-config file (issue #333)
Correct fix for the pkgconf file relativ
As discussed in the MR you filed originally with libinput, this udev rule is
far too broad. If you can demonstrate that every user of this touchscreen has
the input inverted then add a quirk to libinput, otherwise keep this in your
own layer.
Ross
> On 30 Sep 2022, at 16:08, philippe.co...@as
The last two patches in this series do a version upgrade with added
and changed APIs, which is typically not OK for an LTS release.
However I'd like to get some feedback on whether people think this is
an acceptable risk for the CVEs that it fixes.
To help with reviewing this, I've cut pasted the
From: Philippe Coval
For unsupported screens (which X axis is inverted)
For the record issue was observed with this CVL1010 device:
http://www.cartft.com/en/catalog/il/1589#
For more details check related links:
Forwarded: https://lists.openembedded.org/g/openembedded-core/message/171179
Rela
On Thu, Sep 29, 2022 at 11:23 PM Jon Mason wrote:
>
> Most machine features have corresponding kernel config fragments, but
> only a few have an entry in the kernel recipe to be automatically added.
> Adding the majority of them here.
>
> Signed-off-by: Jon Mason
> ---
> meta/recipes-kernel/linu
License names were updated in commit 2456f523cfbb (after the dunfell
release) to match the current SPDX license list. We don't want to do any
wholesale renaming on the dunfell stable branch but we should add
mappings for the newer '*-only' names to allow for layers which support
both dunfell and ne
> On 30 Sep 2022, at 11:16, Ross Burton via lists.openembedded.org
> wrote:
>
> On 30 Sep 2022, at 05:16, Khem Raj via lists.openembedded.org
> wrote:
>> -RDEPENDS:${PN}-ptest += "openssl-bin perl perl-modules bash sed"
>> +RDEPENDS:${PN}-ptest += "bash sed openssl-bin \
>> +
On 30 Sep 2022, at 05:16, Khem Raj via lists.openembedded.org
wrote:
> -RDEPENDS:${PN}-ptest += "openssl-bin perl perl-modules bash sed"
> +RDEPENDS:${PN}-ptest += "bash sed openssl-bin \
> + perl perl-modules \
I thought the point of perl-modules was to depend on the ent
Yeah, this is a Docker issue. Fix your docker.
Ross
> On 30 Sep 2022, at 09:48, Changqing Li via lists.openembedded.org
> wrote:
>
> From: Changqing Li
>
> After commit [1], start a unprivileged container (docker run without
> --privileged),
> close file will fail.
>
> This is actually an
We're seeing "cmd" static libs being sometimes present and sometimes not.
The issue depends whether BUILD == TARGET so they're present for qemux86-64
on x86-64 hosts but not for qemux86-64 on an aarch64 system.
Add an extra deletion to make the files consistent between the different
hosts.
Signed
From: Changqing Li
After commit [1], start a unprivileged container (docker run without
--privileged),
close file will fail.
This is actually an docker issue, see [2]. But this issue will
block yocto build in docker with glibc2.35+. so add this local patch.
[1]
https://gitlab.gnome.org/GNOME/
From: Kai Kang
0001-nir-nir_opt_move-fix-ALWAYS_INLINE-compiler-error.patch is not
needed by target mesa any more. But it still fails to compile
mesa-native without this patch when DEBUG_BUILD is enabled on Ubuntu
18.04 with gcc 7.5.0:
| ../mesa-22.1.6/src/compiler/nir/nir_inline_helpers.h: In f
From: Teoh Jay Shen
CVE fixed :
-CVE-2022-2795
-CVE-2022-2881
-CVE-2022-2906
-CVE-2022-3080
-CVE-2022-38178
Notes for BIND 9.18.7
[https://downloads.isc.org/isc/bind9/9.18.7/doc/arm/html/notes.html#notes-for-bind-9-18-7]
(From OE-Core rev: 5b87b79c6bb155d23ad4eab3243118b98a3b5906)
Signed-off-
From: wangmy
(From OE-Core rev: f7061fc14cbc4388b1fd0cf6233b1a2e743e20e5)
Signed-off-by: Wang Mingyu
Signed-off-by: Luca Ceresoli
Signed-off-by: Richard Purdie
---
.../0001-avoid-start-failure-with-bind-user.patch | 0
.../0001-named-lwresd-V-and-start-log-hide-build-options.pa
38 matches
Mail list logo
