From: Dmitry Eremin-Solenikov
If one has provided external key/certificate for modules signing, Kbuild
will skip creating signing_key.pem and will write only signing_key.x509
certificate. Thus we have to check for .x509 file existence rather than
.pem one.
Signed-off-by: Dmitry Eremin-Solenikov
On Sat, Jul 27, 2019 at 01:49:26PM -0700, Armin Kuster wrote:
> Even releases are stable and supported for 1 year.
>...
9.11 upstream support covers the whole lifetime of Yocto 2.8,
9.14 upstream support does not.
Eve worse, Yocto 2.9 would ship with 9.14 that might become EOL around
the time
From: Bartosz Golaszewski
The build fails on qemu-native if we're using kernels after commit
0768e17073dc527ccd18ed5f96ce85f9985e9115. This adds an upstream
patch that fixes the issue.
Signed-off-by: Bartosz Golaszewski
---
NOTE: Resending this because I sent it to the wrong list previously.
On 7/27/19 8:44 PM, Mittal, Anuj wrote:
> This is causing errors:
>
> | Makefile:557: recipe for target 'alloc.lo' failed
> | make[2]: *** [alloc.lo] Error 1
> | In file included from ../includes/dhcpd.h:91,
> | from conflex.c:29:
> | ../includes/omapip/isclib.h:51:10: fatal
All that was left was
inherit gnomebase gtk-icon-cache gconf mime
and especially inheriting the obsolete gconf is usually unwanted.
Signed-off-by: Adrian Bunk
---
Documentation changes will be sent separately.
Users in meta-openembedded have already been fixed.
---
meta/classes/gnome.bbclass
-The original file mdmonitor.service is as follows:
...
|[Service]
|Environment= MDADM_MONITOR_ARGS=--scan
|EnvironmentFile=-/run/sysconfig/mdadm
|ExecStartPre=-/usr/lib/mdadm/mdadm_env.sh
|ExecStart=/sbin/mdadm --monitor -y $MDADM_MONITOR_ARGS
...
-It has a syntax error and it doesn't work
On 2019/7/27 下午4:35, Alexander Kanavin wrote:
I think you need to re-generate the image first (it goes to qemuboot
config file). It is already used in ptest images, so it’s good to be
consistent.
Thank. It works for testimage with setting QB_MEM. For the other 2
images which has been set
* For changes in this version, see:
http://git.savannah.gnu.org/cgit/grub.git/tree/NEWS?h=grub-2.04
* Remove backported patches and refresh others.
* Remove the musl patch as it's no longer needed.
* Use configure option --disable-werror instead of passing through CFLAGS.
Signed-off-by: Anuj
License-Update: Change in Copyright Year.
Refresh the patch to apply on configure.ac instead of .in.
Signed-off-by: Anuj Mittal
---
.../libsdl2/libsdl2/more-gen-depends.patch | 37 +++---
.../{libsdl2_2.0.9.bb => libsdl2_2.0.10.bb}| 6 ++--
2 files changed, 28
== Series Details ==
Series: Remove the gnome class
Revision: 1
URL : https://patchwork.openembedded.org/series/18942/
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: Ross Burton
Fix the following CVEs by backporting patches from upstream:
- CVE-2019-119
- CVE-2019-120
- CVE-2018-1000877
- CVE-2018-1000878
- CVE-2018-1000879
- CVE-2018-1000880
(From OE-Core rev: ea251020304b9c18f31c39de867a47311b1bb46c)
Signed-off-by: Ross Burton
From: Ovidiu Panait
It was discovered that the ghostscript /invalidaccess checks fail under
certain conditions. An attacker could possibly exploit this to bypass
the -dSAFER protection and, for example, execute arbitrary shell commands
via a specially crafted PostScript document.
It was found
Also include a patch to fix regression caused by it. See:
https://gitlab.com/federicomenaquintero/bzip2/issues/24
Signed-off-by: Anuj Mittal
---
.../bzip2/bzip2-1.0.6/CVE-2019-12900.patch | 33 +
.../fix-regression-CVE-2019-12900.patch| 82 ++
Fixes CVE-2019-7572, CVE-2019-7574, CVE-2019-7575, CVE-2019-7576,
CVE-2019-7577, CVE-2019-7578, CVE-2019-7635, CVE-2019-7637,
CVE-2019-7638.
Signed-off-by: Anuj Mittal
---
.../libsdl/libsdl-1.2.15/CVE-2019-7572.patch | 114
.../libsdl/libsdl-1.2.15/CVE-2019-7574.patch |
From: Ross Burton
(From OE-Core rev: 480f15850820746cecdfe0b8450b2be484c1f8f9)
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
---
.../libcroco/libcroco/CVE-2017-7961.patch | 45 ++
meta/recipes-support/libcroco/libcroco_0.6.12.bb | 4 +-
2 files
Signed-off-by: Anuj Mittal
---
meta/recipes-core/expat/expat/CVE-2018-20843.patch | 26 ++
meta/recipes-core/expat/expat_2.2.6.bb | 1 +
2 files changed, 27 insertions(+)
create mode 100644 meta/recipes-core/expat/expat/CVE-2018-20843.patch
diff --git
Signed-off-by: Anuj Mittal
---
.../gstreamer1.0-plugins-base/CVE-2019-9928.patch | 33 ++
.../gstreamer/gstreamer1.0-plugins-base_1.14.4.bb | 1 +
2 files changed, 34 insertions(+)
create mode 100644
Indeed; I think we should wait for 9.16, and take the latest in 9.11
meanwhile.
Alex
On Sun, 28 Jul 2019 at 11:29, Adrian Bunk wrote:
> On Sat, Jul 27, 2019 at 01:49:26PM -0700, Armin Kuster wrote:
> > Even releases are stable and supported for 1 year.
> >...
>
> 9.11 upstream support covers
On 7/28/19 2:28 AM, Adrian Bunk wrote:
On Sat, Jul 27, 2019 at 01:49:26PM -0700, Armin Kuster wrote:
Even releases are stable and supported for 1 year.
...
9.11 upstream support covers the whole lifetime of Yocto 2.8,
9.14 upstream support does not.
dhcp server would need porting to 9.14 as
On 7/28/19 12:08 AM, akuster808 wrote:
On 7/27/19 8:44 PM, Mittal, Anuj wrote:
This is causing errors:
| Makefile:557: recipe for target 'alloc.lo' failed
| make[2]: *** [alloc.lo] Error 1
| In file included from ../includes/dhcpd.h:91,
| from conflex.c:29:
|
20 matches
Mail list logo
