Hi Bruce
This results in kernel-selftest failure regression
errors.yoctoproject.org/Errors/Build/100385/
and also same errors as reported here
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867596
I have fixed them via three patches that are here
https://git.openembedded.org/openembedded
Ping.
On 3/16/2020 11:03 PM, Jeremy A. Puhlman wrote:
From: Jeremy Puhlman
The updates to the tests are done in do_install instead of do_install_ptest,
so the changes need to consider ptest not being turned on.
Signed-off-by: Jeremy A. Puhlman
---
meta/recipes-core/glib-2.0/glib.inc | 2 ++
On Mon, 2020-03-23 at 23:44 +, Anuj Mittal wrote:
> Please note that this one is for master. I had sent separate patch
> for zeus as well.
master was upgraded instead. Not sure of the new version still needs a
CVE fix or not.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all me
Please note that this one is for master. I had sent separate patch for
zeus as well.
Thanks,
Anuj
On Fri, 2020-03-20 at 09:01 +0800, Anuj Mittal wrote:
> Signed-off-by: Anuj Mittal
> ---
> .../icu/icu/CVE-2020-10531.patch | 122
> ++
> meta/recipes-support/icu/icu_
Distros which want to enable LTO can utilize this file, it only covers
packages from OE-Core, other layers should include there own exclusion
list for recipe which dont work with LTO
Signed-off-by: Khem Raj
---
meta/conf/distro/include/lto.inc | 23 +++
1 file changed, 23 ins
Hello,
Yes that was the V2. Changes included adding the CVE tag and Signed-off-by in
the included patch.
From: Denys Dmytriyenko
Sent: March 23, 2020 4:32 PM
To: Sajal, Sakib
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] libpng: F
Fix memory leak in png_create_info_struct.
Upstream-Status: Submitted [https://github.com/glennrp/libpng/pull/293]
CVE: CVE-2019-6129
Signed-off-by: Sakib Sajal
---
.../libpng/0001-Repair-of-CVE-2019-6129.patch | 28 +++
.../libpng/libpng_1.6.37.bb | 5 +++-
2
Hi,
Is this v2? Should say so in the subject. Also, should mention the changes
from v1 under the commit log.
On Mon, Mar 23, 2020 at 02:28:23PM -0700, Sakib Sajal wrote:
> Fix memory leak in png_create_info_struct.
>
> Upstream-Status: Submitted [https://github.com/glennrp/libpng/pull/293]
BT
Fix memory leak in png_create_info_struct.
Upstream-Status: Submitted [https://github.com/glennrp/libpng/pull/293]
CVE: CVE-2019-6129
Signed-off-by: Sakib Sajal
---
.../libpng/0001-Repair-of-CVE-2019-6129.patch | 27 +++
.../libpng/libpng_1.6.37.bb | 5 +++-
2
Fix of memory leak in png_create_info_struct.
Upstream-Status: Submitted [https://github.com/glennrp/libpng/pull/293]
CVE: CVE-2019-6129
Signed-off-by: Sakib Sajal
---
.../libpng/0001-Repair-of-CVE-2019-6129.patch | 25 +++
.../libpng/libpng_1.6.37.bb | 5 +++-
On Thu, 5 Mar 2020 22:56:15 +
"Freihofer, Adrian" wrote:
> On Thu, 2020-03-05 at 09:42 +, Paul Barker wrote:
> > On Wed, 4 Mar 2020 12:30:10 +
> > "Freihofer, Adrian" wrote:
> >
> > > -Original Message-
> > > From: Paul Barker
> > > To: "Freihofer, Adrian"
> > > Cc: open
From: Bartosz Golaszewski
This variable is already defined in image.bbclass and there's not need
to redefine it here.
Signed-off-by: Bartosz Golaszewski
---
meta/classes/qemuboot.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bb
From: Bartosz Golaszewski
Make each IMAGE_CMD task an sstate task with its own IMGDEPLOYDIR
override. This way each generated set of artifacts is deployed as soon
as it's ready instead of the do_image_complete task handling the entire
deployement. This allows us to better fine-tune dependencies e
From: Bartosz Golaszewski
Hi Richard,
please take a look at the following patch series. It's a follow up to
my previous attempt[1] and is also related to the dm-verity problem I
described on the list[2].
This time instead of having hardcoded two stages of deployment for simple
and composed imag
On Mon, 23 Mar 2020 13:03:55 -0400 (EDT)
"rpj...@crashcourse.ca" wrote:
>
> Signed-off-by: Robert P. J. Day
>
> ---
>
> diff --git a/meta/lib/oeqa/selftest/cases/archiver.py
> b/meta/lib/oeqa/selftest/cases/archiver.py
> index c036e0cbe2..606eaabcb0 100644
> --- a/meta/lib/oeqa/selftest/case
bitbake dropped support for this piece of functionality (the test was
the only user), drop the test too.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/tinfoil.py | 13 -
1 file changed, 13 deletions(-)
diff --git a/meta/lib/oeqa/selftest/cases/tinfoil.py
b/meta/lib
Printing a warning for something which is harmless just causes the
people monitoring the autobuilder more work. Silently ignore this race.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/utils/qemurunner.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/utils
On Mon, 23 Mar 2020, Adrian Bunk wrote:
> On Mon, Mar 23, 2020 at 12:26:04PM -0400, rpj...@crashcourse.ca wrote:
> >...
> > in that case, i notice this line from bitbake.conf regarding
> > ASSUME_PROVIDED:
> >
> > # gzip-native should be listed above?
> >
> > which seems like a reasonable ques
On Mon, Mar 23, 2020 at 12:26:04PM -0400, rpj...@crashcourse.ca wrote:
>...
> in that case, i notice this line from bitbake.conf regarding
> ASSUME_PROVIDED:
>
> # gzip-native should be listed above?
>
> which seems like a reasonable question since both gzip and gunzip are
> listed in HOSTTOO
Signed-off-by: Robert P. J. Day
---
diff --git a/meta/lib/oeqa/selftest/cases/archiver.py
b/meta/lib/oeqa/selftest/cases/archiver.py
index c036e0cbe2..606eaabcb0 100644
--- a/meta/lib/oeqa/selftest/cases/archiver.py
+++ b/meta/lib/oeqa/selftest/cases/archiver.py
@@ -208,7 +208,7 @@ class Archi
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#N
On Mon, 23 Mar 2020, Richard Purdie wrote:
> On Mon, 2020-03-23 at 12:06 -0400, Robert P. J. Day wrote:
> > On Mon, 23 Mar 2020, Richard Purdie wrote:
> >
> > > On Mon, 2020-03-23 at 09:28 -0400, rpj...@crashcourse.ca wrote:
> > > > continuing my travels, ran across "PRIORITY" variable that i
>
(given some spare time these days, i'm trying to clean up some docs,
so yet another question regarding some OE variables.)
i'm trying to organize OE variables into related sub-categories, and
there are a few related to using host tools i can see:
ASSUME_PROVIDED
HOSTTOOLS
HOSTTOOLS_DIR
On Mon, 2020-03-23 at 12:06 -0400, Robert P. J. Day wrote:
> On Mon, 23 Mar 2020, Richard Purdie wrote:
>
> > On Mon, 2020-03-23 at 09:28 -0400, rpj...@crashcourse.ca wrote:
> > > continuing my travels, ran across "PRIORITY" variable that i
> > > was
> > > not
> > > aware of, was introduced in b
On Mon, 23 Mar 2020, Richard Purdie wrote:
> On Mon, 2020-03-23 at 09:28 -0400, rpj...@crashcourse.ca wrote:
> > continuing my travels, ran across "PRIORITY" variable that i was
> > not
> > aware of, was introduced in bitbake.conf way back in 2005 in
> > oelint.bbclass, but there are only a few
On Mon, 2020-03-23 at 09:28 -0400, rpj...@crashcourse.ca wrote:
> continuing my travels, ran across "PRIORITY" variable that i was
> not
> aware of, was introduced in bitbake.conf way back in 2005 in
> oelint.bbclass, but there are only a few lonely references to it
> these days:
>
> meta/conf/d
Backported patch removed.
Signed-off-by: Adrian Bunk
---
.../openssl/openssl/CVE-2019-1551.patch | 758 --
.../{openssl_1.1.1d.bb => openssl_1.1.1e.bb} | 4 +-
2 files changed, 1 insertion(+), 761 deletions(-)
delete mode 100644
meta/recipes-connectivity/openssl/openss
continuing my travels, ran across "PRIORITY" variable that i was not
aware of, was introduced in bitbake.conf way back in 2005 in
oelint.bbclass, but there are only a few lonely references to it
these days:
meta/conf/documentation.conf:PRIORITY[doc] = "Indicates the importance
of a package. Th
Fixes:
ERROR: nfs-utils-2.4.3-r0 do_package: QA Issue: nfs-utils:
Files/directories were installed but not shipped in any package:
/usr/lib/libnfsidmap/nsswitch.so
/usr/lib/libnfsidmap/static.so
Please set FILES such that these items are packaged. Alternatively if
they are unneeded, avoid installin
cleaning up docs, and just noticed this from several months back:
commit 4ff058226cfc3e7d5bf9a873d1de4475f65ef2f2
Author: Andre McCurdy
Date: Fri Aug 23 13:51:32 2019 -0700
bitbake.conf: drop FETCHCMD, GITDIR, etc fetcher over-rides
This completes cleanup originally proposed in 201
hi there,
we have put in place a dashboard that shows our community engagement and
stats. We are using a service from Bitergia for that, and they are using
open source tools from the LF CHAOSS project [1].
The dashboard is publicly available at [2]. Feel free to have a look at the
data, the tool
From: Changqing Li
Signed-off-by: Changqing Li
---
...-rarely-reproduced-parallel-build-problem.patch | 40 ++
meta/recipes-extended/sysklogd/sysklogd.inc| 1 +
2 files changed, 41 insertions(+)
create mode 100644
meta/recipes-extended/sysklogd/files/0001-fix-one-
From: Chee Yang Lee
fix CVE-2020-7211 for qemu slirp submodule
see :
https://www.openwall.com/lists/oss-security/2020/01/17/2
https://gitlab.freedesktop.org/slirp/libslirp/commit/14ec36e107a8c9af7d0a80c3571fe39b291ff1d4
Signed-off-by: Chee Yang Lee
---
meta/recipes-devtools/qemu/qemu.inc
33 matches
Mail list logo
