Signed-off-by: Zang Ruochen
---
.../xorg-lib/{libxfont2_2.0.3.bb => libxfont2_2.0.4.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-graphics/xorg-lib/{libxfont2_2.0.3.bb =>
libxfont2_2.0.4.bb} (81%)
diff --git
Hi Richard
>
> This is heading in the right direction but this patch still makes the
> nativesdk-rpm
> recipe machine specific and we can't do that.
>
In this patch, config file is same as v3 patch, and v3 patch has been accepted,
but why this time is " makes the nativesdk-rpm recipe machine
Signed-off-by: Khem Raj
---
.../gnu-efi-3.0.9-fix-clang-build.patch | 24 +++
meta/recipes-bsp/gnu-efi/gnu-efi_3.0.9.bb | 1 +
2 files changed, 25 insertions(+)
create mode 100644
meta/recipes-bsp/gnu-efi/gnu-efi/gnu-efi-3.0.9-fix-clang-build.patch
diff --git
On 9/19/19 8:07 PM, Muminul Islam wrote:
> Signed-off-by: Muminul Islam
> ---
> meta/recipes-devtools/gcc/gcc-8.2.inc | 3 +
> .../gcc/gcc-8.2/CVE-2019-15847_p1.patch | 223 ++
> .../gcc/gcc-8.2/CVE-2019-15847_p2.patch | 47
>
Signed-off-by: Zang Ruochen
---
meta/recipes-core/expat/{expat_2.2.8.bb => expat_2.2.9.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-core/expat/{expat_2.2.8.bb => expat_2.2.9.bb} (81%)
diff --git a/meta/recipes-core/expat/expat_2.2.8.bb
Signed-off-by: Zang Ruochen
---
meta/recipes-devtools/librepo/{librepo_1.10.5.bb => librepo_1.10.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/librepo/{librepo_1.10.5.bb => librepo_1.10.6.bb}
(93%)
diff --git
Signed-off-by: Zang Ruochen
---
meta/recipes-extended/msmtp/{msmtp_1.8.5.bb => msmtp_1.8.6.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/msmtp/{msmtp_1.8.5.bb => msmtp_1.8.6.bb} (86%)
diff --git a/meta/recipes-extended/msmtp/msmtp_1.8.5.bb
On 10/1/19 11:12 AM, shuag...@gmail.com wrote:
> From: Shubham Agrawal
I cleaned up the patch to conform to the patch guide.
see
https://git.openembedded.org/openembedded-core-contrib/commit/?h=stable/thud-nmut=c0c66d213b4b6deb0a5e9a688810d2e9674d3ecf
as an example of what was meant.
-
-libpcap/0001-pcap-usb-linux.c-add-missing-limits.h-for-musl-syste.patch
Removed since this is included in 1.9.1.
Signed-off-by: Zang Ruochen
---
...nux.c-add-missing-limits.h-for-musl-syste.patch | 29 --
.../libpcap/{libpcap_1.9.0.bb => libpcap_1.9.1.bb} | 5 ++--
2
Affects <= qemu 3.1.0
[Yocto #13577]
This fixes the following error:
TOPDIR/tmp/work/x86_64-linux/qemu-native/3.1.0-r0/qemu-3.1.0/linux-user/syscall.c:254:16:
error: static declaration of ‘gettid’ follows non-static declaration
254 | _syscall0(int, gettid)
|^~
A perl module recipe extending to provide native version causes target
perl dependencies to be pulled into native build if the module recipe
has RDEPENDS_${PN} = "perl-module-" e.g. libxml-sax-base-perl
recipe.
The reason is that native bbclass empties out PACKAGES_DYNAMIC and
perl's
== Series Details ==
Series: qemu: fix build issue on new hosts with glibc 2.30
Revision: 1
URL : https://patchwork.openembedded.org/series/20318/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have
This fixes the following error:
TOPDIR/tmp/work/x86_64-linux/qemu-native/3.1.0-r0/qemu-3.1.0/linux-user/syscall.c:254:16:
error: static declaration of ‘gettid’ follows non-static declaration
254 | _syscall0(int, gettid)
|^~
Signed-off-by: Dan Tran
[Fix up against lastest warrior]
Signed-off-by: Armin Kuster
---
meta/recipes-devtools/qemu/qemu.inc| 1 +
.../recipes-devtools/qemu/qemu/CVE-2019-8934.patch | 215 +
2 files changed, 216 insertions(+)
create mode 100644
From: Jan Klare
Currently systemd 241 does break for kernels 5.2+ with the error described here:
* https://github.com/systemd/systemd/issues/12784
The issue has been fixed in master and will be fixed in the release 243. The
necessary patches have been backported to systemd/systemd-stable in the
From: Dan Tran
Signed-off-by: Dan Tran
Signed-off-by: Armin Kuster
---
.../unzip/unzip/CVE-2019-13232_p1.patch| 33 ++
.../unzip/unzip/CVE-2019-13232_p2.patch| 356 +
.../unzip/unzip/CVE-2019-13232_p3.patch| 121 +++
From: Alexander Kanavin
License-update: copyright years
Signed-off-by: Alexander Kanavin
Signed-off-by: Richard Purdie
[ Backported patches removed. ]
Signed-off-by: Adrian Bunk
[Bug fix only update]
Signed-off-by: Armin Kuster
---
...ysconfig-append-STAGING_LIBDIR-python-sys.patch | 2
From: Anuj Mittal
Also fixes CVE-2019-9740, CVE-2019-9948. For details, see:
https://docs.python.org/3.7/whatsnew/changelog.html#python-3-7-4-final
Signed-off-by: Anuj Mittal
Signed-off-by: Richard Purdie
[ Backported patch removed. ]
Signed-off-by: Adrian Bunk
[Bug fix only update]
From: Adrian Bunk
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
Next series to review.
Please comment by Monday.
All these have already been sent to the list so short review period.
The following changes since commit acc0f4a6a99fe9367e57a5c2a4f995b6f4db4a9f:
runqemu: Add support for kvm on aarch64 (2019-10-01 10:48:46 +0100)
are available in the git
From: Andrii Bordunov via Openembedded-core
There's INITRAMFS_FSTYPES that can be set differently.
Signed-off-by: Böszörményi Zoltán
Signed-off-by: Armin Kuster
---
meta/classes/image-live.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Can you please add:
http://git.openembedded.org/openembedded-core/commit/?id=f7a470531d4bcc2888cbb9a7b197b86174f3aba2
it does apply cleanly in warrior.
Thanks
On Sun, Oct 6, 2019 at 5:24 PM Armin Kuster wrote:
> Next series to review.
>
> Please comment by Monday.
> All these have already
On 10/6/19 9:38 AM, Martin Jansa wrote:
> Can you please add:
> http://git.openembedded.org/openembedded-core/commit/?id=f7a470531d4bcc2888cbb9a7b197b86174f3aba2
>
> it does apply cleanly in warrior.
queued up.
thanks
>
> Thanks
>
> On Sun, Oct 6, 2019 at 5:24 PM Armin Kuster
On 10/4/19 12:47 AM, Alexandre Bard wrote:
> When systemd is built without internal resolver, it does not make
> sense to expose it as a resolv-conf alternative and can even break
> images where this alternative would be chosen, because of an
> invalid symlink.
Does Master have this issue?
-
24 matches
Mail list logo
