This is a stable bugfix release. Detailed release notes available at:
https://www.mesa3d.org/relnotes/19.1.7.html
Signed-off-by: Otavio Salvador
---
.../mesa/{mesa-gl_19.1.6.bb => mesa-gl_19.1.7.bb} | 0
meta/recipes-graphics/mesa/{mesa_19.1.6.bb => mesa_19.1.7.bb} | 4 ++--
2
This works just like the already existing --no-clean option to the
`devtool reset` command.
Signed-off-by: Peter Kjellerstedt
---
scripts/lib/devtool/standard.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/scripts/lib/devtool/standard.py
From: Niclas Svensson
The _get_patchset_revs() function returns the patches in an
OrderedDict to keep them ordered. However, this information was lost
when the patches were added to the bbappend file.
Signed-off-by: Niclas Svensson
Signed-off-by: Peter Kjellerstedt
---
From: Dan Tran
Fixes CVE-2018-18954, CVE-2019-3812, CVE-2019-6778, and CVE-2019-8934.
Also deleted duplicated patch and cleanup.
Signed-off-by: Dan Tran
---
.../qemu/qemu/CVE-2018-10839.patch| 2 +-
.../qemu/qemu/CVE-2018-17958.patch| 52 -
From: Trevor Gamblin
CVE reference: https://nvd.nist.gov/vuln/detail/CVE-2019-14973
Upstream merge: https://gitlab.com/libtiff/libtiff/commit/2218055c
Signed-off-by: Trevor Gamblin
---
.../libtiff/tiff/CVE-2019-14973.patch | 415 ++
== Series Details ==
Series: tiff: fix CVE-2019-14973
Revision: 1
URL : https://patchwork.openembedded.org/series/20085/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the
From: Trevor Gamblin
CVE reference: https://nvd.nist.gov/vuln/detail/CVE-2019-14973
Upstream merge: https://gitlab.com/libtiff/libtiff/commit/2218055c
Signed-off-by: Trevor Gamblin
---
.../libtiff/tiff/CVE-2019-14973.patch | 411 ++
== Series Details ==
Series: libsolv: Security fix for CVEs:
Revision: 1
URL : https://patchwork.openembedded.org/series/20084/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on
Signed-off-by: Muminul Islam
---
...0003-Fix-Dereference-of-null-pointer.patch | 26 +++
.../0004-Fix-Add-va_end-before-return.patch | 28
.../libsolv/0005-Fix-Memory-leaks.patch | 151 ++
.../libsolv/0006-Fix-testsolv-segfault.patch | 33
From: Trevor Gamblin
pip3 depends on pickle, so add python3-pickle to RDEPENDS.
Without it, errors such as the following occur:
>>> import pip._internal
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib64/python3.7/site-packages/pip/internal/init_.py", line 40, in
from
On Fri, Sep 20, 2019 at 01:38:29PM +, mikko.rap...@bmw.de wrote:
> On Fri, Sep 20, 2019 at 03:13:44PM +0200, Andrey Zhizhikin wrote:
> > Hello Raj,
> >
> > On Tue, Sep 17, 2019 at 8:50 PM Khem Raj wrote:
> > >
> > > with openSSL 1.1.1d we start seeing errors like
> > >
> > > Error Generating
On Fri, Sep 20, 2019 at 3:38 PM wrote:
>
>
> Do you have rng-tools on the image? That helped me with the kernel random pool
> initialization for sshd in iMX8 and openssl 1.1.1x.
No, but I would definitely try it! Thanks a lot for the tip here!
>
> I don't see how 53b5654d6e could change this
On Fri, Sep 20, 2019 at 03:13:44PM +0200, Andrey Zhizhikin wrote:
> Hello Raj,
>
> On Tue, Sep 17, 2019 at 8:50 PM Khem Raj wrote:
> >
> > with openSSL 1.1.1d we start seeing errors like
> >
> > Error Generating Key
> > 139979727451584:error:2406C06E:random number
> >
Hello Raj,
On Tue, Sep 17, 2019 at 8:50 PM Khem Raj wrote:
>
> with openSSL 1.1.1d we start seeing errors like
>
> Error Generating Key
> 139979727451584:error:2406C06E:random number
> generator:RAND_DRBG_instantiate:error retrieving
> entropy:../openssl-1.1.1d/crypto/rand/drbg_lib.c:342:
>
>
Remember to add the Upstream-Status:
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/kexec/kexec-syscall.h?id=b54816eff272324320c490d62dc36b27d2838732
Ross
On 20/09/2019 11:14, quanyang.w...@windriver.com wrote:
From: Wang Quanyang
Once use kexec in arm arch, it
Signed-off-by: Ross Burton
---
meta/recipes-devtools/json-c/json-c_0.13.1.bb | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
b/meta/recipes-devtools/json-c/json-c_0.13.1.bb
index 9654e60a3d2..8ee9437af16 100644
---
On Tue, 2019-09-17 at 09:27 +0800, Yeoh Ee Peng wrote:
> In running QA testing, we sometime need to select custom provider
> for
> virtual/kernel and version. To track the selected virtual/kernel
> provider
> and version used during test, we need to add these information to
> testresult.
>
>
On 20/09/2019 12:26, Adrian Bunk wrote:
Upstream tag names are appending the date to the version,
making "devtool check-upgrade-status" with this patch result in
INFO: json-c0.13.1 UNKNOWN_BROKEN Yi Zhao
I totally tested this and it worked, somehow. Obviously
== Series Details ==
Series: "json-c: use GitHub for upstrea..." and 1 more
Revision: 1
URL : https://patchwork.openembedded.org/series/20079/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
Users of distcc are rarely both clients and servers, so split the package.
distcc is the client, the new distcc-server package is the server.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/distcc/distcc_3.3.3.bb | 33 +---
1 file changed, 14 insertions(+), 19 deletions(-)
--make-me-a-botnet is worrying, --enable-tcp-insecure is clearer and doesn't
scare people glancing at 'ps'.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/distcc/files/default | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/distcc/files/default
Remove the local copy of the desktop file, instead apply a patch from upstream
to fix the file. This also fixes the install paths, so update the recipe.
Remove glibc-specific installation as this was due to uclibc failures.
Refresh and submit upstream the out-of-tree build fix.
Signed-off-by:
On Fri, Sep 20, 2019 at 12:16:01PM +0100, Ross Burton wrote:
> Signed-off-by: Ross Burton
> ---
> meta/recipes-devtools/json-c/json-c_0.13.1.bb | 8 +---
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
>
Tidy the indentation of EXTRA_OECONF.
Remove the deletion of config.status which hasn't been in the tarballs since
0.12.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/json-c/json-c_0.13.1.bb | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git
Signed-off-by: Ross Burton
---
meta/recipes-devtools/json-c/json-c_0.13.1.bb | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/meta/recipes-devtools/json-c/json-c_0.13.1.bb
b/meta/recipes-devtools/json-c/json-c_0.13.1.bb
index 9654e60a3d2..fcc3e4337ea 100644
---
== Series Details ==
Series: kexec-tools: fix arm kexec failure for __NR_kexec_file_load
Revision: 1
URL : https://patchwork.openembedded.org/series/20078/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several
From: Wang Quanyang
Once use kexec in arm arch, it will throw out the error info as below:
Could not find a free area of memory of 0xc78e744 bytes...
This is because that kexec use kexec_file_load to load image by default
but arm doesn't support it. So add this patch to avoid use
In recent years AMD CPUs have had various problems with RDRAND
giving either non-random data or no result at all, which is
problematic if either build or target machine has a CPU with
this problem.
The fallback is /dev/urandom, and I'd trust the kernel here.
--enable-rdrand was added in an
28 matches
Mail list logo
