Re: [OE-core] tinymembench: fix patch fuzz

Hi Alex, many thanks for your reply. Will follow it. -Mircea On Tue, Jul 14, 2020 at 2:22 PM Alexander Kanavin wrote: > You can start here: > https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded > > Alex > > On Tue, 14 Jul 2020 at 20:50, Mircea Carausu via lists.openembedded.o

Re: [OE-core] tinymembench: fix patch fuzz

You can start here: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Alex On Tue, 14 Jul 2020 at 20:50, Mircea Carausu via lists.openembedded.org wrote: > Hello, > I am new to the list and up-streaming activities. > Could you please kindly guide me how to submit a fix for

[OE-core] [PATCH 2/4] qemu: fix CVE-2020-13659

Signed-off-by: Sakib Sajal --- meta/recipes-devtools/qemu/qemu.inc | 1 + .../qemu/qemu/CVE-2020-13659.patch| 58 +++ 2 files changed, 59 insertions(+) create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13659.patch diff --git a/meta/recipes-devtoo

[OE-core] [PATCH 3/4] qemu: fix CVE-2020-13800

Signed-off-by: Sakib Sajal --- meta/recipes-devtools/qemu/qemu.inc | 1 + .../qemu/qemu/CVE-2020-13800.patch| 63 +++ 2 files changed, 64 insertions(+) create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13800.patch diff --git a/meta/recipes-devtoo

[OE-core] [PATCH 1/4] qemu: fix CVE-2020-13362

Signed-off-by: Sakib Sajal --- meta/recipes-devtools/qemu/qemu.inc | 1 + .../qemu/qemu/CVE-2020-13362.patch| 55 +++ 2 files changed, 56 insertions(+) create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13362.patch diff --git a/meta/recipes-devtoo

[OE-core] [PATCH 4/4] qemu: fix CVE-2020-13791

Signed-off-by: Sakib Sajal --- meta/recipes-devtools/qemu/qemu.inc | 1 + .../qemu/qemu/CVE-2020-13791.patch| 53 +++ 2 files changed, 54 insertions(+) create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13791.patch diff --git a/meta/recipes-devtoo

[OE-core] ERROR: ruby-2.7.1-r0 do_compile: oe_runmake failed

Hi. i am trying to build sato-image on RPI but i am getting following error w.r.t ruby.i have added ruby & ruby-dev package via image_install,what wrong could be happened with this can someone help?? :~/ORASP$ bitbake core-image-sato Parsing recipes: 100% |##

[OE-core] tinymembench: fix patch fuzz

Hello, I am new to the list and up-streaming activities. Could you please kindly guide me how to submit a fix for the existing tinymembench.patch (meta-openembedded/meta-oe/recipes-benchmark/tinymembench/tinymembench/0001-asm-Delete-.func-.endfunc-directives.patch) Problem: tinymembench patch does

Re: [OE-core] [PATCH v3] ppp: Allow arbitrary interface names to be specified in pppd config

Nope. However, I want to throw this whole thing away. The patches in question have been merged upstream in 2.4.8, and I don't know how I missed that. I was building from dunfell, which is at 2.4.7. Sorry for the noise, everyone. Best Regards, Mark Deneen Saucon Technologies - On Jul 14,

[OE-core] ✗ patchtest: failure for ppp: Allow arbitrary interface names to be specified in pppd config

== Series Details == Series: ppp: Allow arbitrary interface names to be specified in pppd config Revision: 1 URL : https://patchwork.openembedded.org/series/25133/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Sev

Re: [OE-core] [PATCH v3] ppp: Allow arbitrary interface names to be specified in pppd config

On 7/14/20 10:08 AM, Mark Deneen wrote: > pppd is patched in most Linux distributions to allow arbitrary naming > of ppp interfaces, allowing users to create consistent firewall rules > rather than having interfaces named "ppp0", "ppp1", etc. Yocto is > missing this option. > > This patch, orig

[OE-core] [PATCH v3] ppp: Allow arbitrary interface names to be specified in pppd config

pppd is patched in most Linux distributions to allow arbitrary naming of ppp interfaces, allowing users to create consistent firewall rules rather than having interfaces named "ppp0", "ppp1", etc. Yocto is missing this option. This patch, originally from SUSE, adds this option to pppd. It is not

Re: [OE-core] [PATCH 2/2] insane: improve arch test messages

On 7/14/20 10:02 AM, Ross Burton wrote: > From: Ross Burton > > The messages from the ELF 'arch' test are not obvious, clarify the > messages and prune output paths. > > Signed-off-by: Ross Burton > --- > meta/classes/insane.bbclass | 12 ++-- > 1 file changed, 6 insertions(+), 6 del

[OE-core] [PATCH 2/2] insane: improve arch test messages

From: Ross Burton The messages from the ELF 'arch' test are not obvious, clarify the messages and prune output paths. Signed-off-by: Ross Burton --- meta/classes/insane.bbclass | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/meta/classes/insane.bbclass b/meta/c

[OE-core] [PATCH 1/2] init-ifupdown: always make machine-specific

From: Ross Burton We make this recipe machine-specific for all qemu targets, but otherwise defaults to tune-specific. However the network configuration is typically machine-specific, so do this in the recipe directly so that BSPs don't need to do it themselves. Signed-off-by: Ross Burton ---

[OE-core] [[PATCH v2] ppp: Allow arbitrary interface names to be specified in pppd config

pppd is patched in most Linux distributions to allow arbitrary naming of ppp interfaces, allowing users to create consistent firewall rules rather than having interfaces named "ppp0", "ppp1", etc. Yocto is missing this option. This patch, originally from SUSE, adds this option to pppd. It is not

[OE-core] ✗ patchtest: failure for Allow arbitrary interface names to be specified in pppd config

== Series Details == Series: Allow arbitrary interface names to be specified in pppd config Revision: 1 URL : https://patchwork.openembedded.org/series/25131/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several

[OE-core] [PATCH] Allow arbitrary interface names to be specified in pppd config

pppd is patched in most Linux distributions to allow arbitrary naming of ppp interfaces, allowing users to create consistent firewall rules rather than having interfaces named "ppp0", "ppp1", etc. Yocto is missing this option. This patch, originally from SUSE, adds this option to pppd. It is not

Re: [OE-core] [PATCH] ppp: Add support for setting ifname in ppp options

Quentin, Thanks for the feedback, and I will resend this. I started off with a patch which contained the original authors, but that was lost in the process of applying the patch, since it is a patch of a patch. I was attempting to avoid patch fuzzing, since it had previously been applied to pppd

[OE-core] ✗ patchtest: failure for ppp: Add support for setting ifname in ppp options

== Series Details == Series: ppp: Add support for setting ifname in ppp options Revision: 1 URL : https://patchwork.openembedded.org/series/25130/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have b

Re: [OE-core] [PATCH] ppp: Add support for setting ifname in ppp options

Hi Mark, On Tue, Jul 14, 2020 at 11:04:41AM -0400, Mark Deneen wrote: > pppd is patched in most Linux distributions to allow arbitrary naming > of ppp interfaces, allowing users to create consistent firewall rules > rather than having interfaces named "ppp0", "ppp1", etc. Yocto is > missing this

Re: [OE-core] How to install individual -lic packages

In the meantime I could answer the question myself: Am Freitag, 10. Juli 2020, 23:16:39 CEST schrieb Christian Eggers: > [...] > I think this is not what I require. How can I install -lic packages > directly? In order to known by other (image) recipes, -lic packages must be added to PACKAGES_DYNA

[OE-core] [PATCH] ppp: Add support for setting ifname in ppp options

pppd is patched in most Linux distributions to allow arbitrary naming of ppp interfaces, allowing users to create consistent firewall rules rather than having interfaces named "ppp0", "ppp1", etc. Yocto is missing this option. This patch, originally from SUSE, adds this option to pppd. It is not

[OE-core] Yocto Project Status WW28'20

Current Dev Position: YP 3.2 M2 Next Deadline: YP 3.2 M2 build date 2020/7/27 Next Team Meetings: * Bug Triage meeting Thursday July 16th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Aug. 4th at 8am PDT (

Re: [OE-core] [yocto] Stable Warrior branch

On Thu, Jun 04, 2020 at 09:28:00PM -0700, akuster wrote: > Hello, > > The Warrior branch of Poky has had its last official dot release. It > will be moving to Community support and EOL within 6 weeks if no one > steps up. > If someone is interested in taking on the responsibilities of > maintainin

Re: [OE-core][dunfell 08/15] kernel.bbclass: make dependency on lzop-native conditional

Note that the kernel config CONFIG_KERNEL_LZO must also be present to have the compressed part in the zImage using LZO compression. E.g. the i.MX defconfig uses that: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/configs/imx_v6_v7_defconfig?h=v5.8-rc5#n1 I perso

Re: [OE-core] [RFC PATCH] devtool: remove _PYTHON_SYSCONFIGDATA_NAME to fix do_unpack

On Tue, 14 Jul 2020 at 03:47, Taras Kondratiuk (takondra) < takon...@cisco.com> wrote: > 2. If a recipe needs python3-native only, then it inherits > python3native which exports _PYTHON_SYSCONFIGDATA_NAME=_sysconfigdata. > This doesn't work, because python3-native will fail to > find _sysconfigdat

[OE-core] ✗ patchtest: failure for [zeus] nss: Fix CVE-2020-12399

== Series Details == Series: [zeus] nss: Fix CVE-2020-12399 Revision: 1 URL : https://patchwork.openembedded.org/series/25124/ 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

[OE-core] [zeus][PATCH 1/1] nss: Fix CVE-2020-12399

Master (nss version 3.54) is not affected by this issue. This is a backport from nss version 3.54. NSS has shown timing differences when performing DSA signatures, which was exploitable and could eventually leak private keys. This vulnerability affects Thunderbird < 68.9.0, Firefox < 77, and Firef

Re: [OE-core] [PATCH v4 01/12] Move rpm manifest to its own subdir

Thank you, just let me know if I can make it any easier to review this, I know it's a big patch. BR Fredrik From: Paul Barker Sent: Thursday, July 9, 2020 6:19 PM To: Fredrik Gustafsson Cc: openembedded-core@lists.openembedded.org; tools-cfpbuild-internal;