Re: [OE-core] [PATCH v2] staging.bbclass: Fix wrong library paths in sysroot_strip

ping... On 2019/11/16 22:12, Junling Zheng wrote: > Do not reset libdir and base_libdir in sysroot_strip, and just pass crude > paths as they will be reset later in strip_execs. > > Signed-off-by: Junling Zheng > --- > v2: > - Fix undefined variable error. > > meta/classes/staging.bbclass |

[OE-core] ✗ patchtest: failure for cronie:upgrade 1.5.4 -> 1.5.5 (rev2)

== Series Details == Series: cronie:upgrade 1.5.4 -> 1.5.5 (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/21308/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed

[OE-core] ✗ patchtest: failure for cronie:upgrade 1.5.4 -> 1.5.5

== Series Details == Series: cronie:upgrade 1.5.4 -> 1.5.5 Revision: 1 URL : https://patchwork.openembedded.org/series/21308/ 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

Re: [OE-core] [PATCH] cronie:upgrade 1.5.4 -> 1.5.5

Has this been tested with musl? I think would fail because anacron has now been enabled by default [1] which in turn needs obstack [2]. [1] https://github.com/cronie-crond/cronie/commit/a8920856869a4682ce2300368da623fc86645c7a [2]

[OE-core] [PATCH] kexec-tools: upgrade 2.0.19 -> 2.0.20

--- .../kexec/{kexec-tools_2.0.19.bb => kexec-tools_2.0.20.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-kernel/kexec/{kexec-tools_2.0.19.bb => kexec-tools_2.0.20.bb} (95%) diff --git a/meta/recipes-kernel/kexec/kexec-tools_2.0.19.bb

[OE-core] [PATCH] cronie:upgrade 1.5.4 -> 1.5.5

--- meta/recipes-extended/cronie/{cronie_1.5.4.bb => cronie_1.5.5.bb} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename meta/recipes-extended/cronie/{cronie_1.5.4.bb => cronie_1.5.5.bb} (94%) diff --git a/meta/recipes-extended/cronie/cronie_1.5.4.bb

[OE-core] [zeus][PATCH] bind: fix CVE-2019-6471 and CVE-2018-5743

From: Kai Kang Backport patches to fix CVE-2019-6471 and CVE-2018-5743 for bind. CVE-2019-6471 is fixed by 0001-bind-fix-CVE-2019-6471.patch and the other 6 patches are for CVE-2018-5743. And backport one more patch to fix compile error on arm caused by these 6 commits. (From OE-Core rev:

Re: [OE-core] [PATCH] librsvg: Fix build reproducibility

On Thu, Nov 21, 2019 at 5:40 PM Joshua Watt wrote: > > On Thu, Nov 21, 2019 at 7:14 PM Khem Raj wrote: > > > > On Thu, 2019-11-21 at 10:58 -0600, Joshua Watt wrote: > > > librsvg was encoding the path to the build directory in order to find > > > a > > > font file for testing. This wouldn't work

Re: [OE-core] [PATCH] librsvg: Fix build reproducibility

On Thu, Nov 21, 2019 at 7:14 PM Khem Raj wrote: > > On Thu, 2019-11-21 at 10:58 -0600, Joshua Watt wrote: > > librsvg was encoding the path to the build directory in order to find > > a > > font file for testing. This wouldn't work in OE anyway since the > > build > > directory isn't present at

Re: [OE-core] [PATCH] librsvg: Fix build reproducibility

On Thu, 2019-11-21 at 10:58 -0600, Joshua Watt wrote: > librsvg was encoding the path to the build directory in order to find > a > font file for testing. This wouldn't work in OE anyway since the > build > directory isn't present at that exact location on the target, so > remove > the offending

Re: [OE-core] How to backport openssl to Sumo

On 21/11/2019 08:05, mikko.rap...@bmw.de wrote: On Wed, Nov 20, 2019 at 03:53:14PM -0800, Andre McCurdy wrote: But anyway, in all cases, the way to debug what's going on isn't to try random recipe changes and then rebuild the final image. Instead you should build your chosen version of openssl,

Re: [OE-core] [PATCH] ghostscript: CVE-2019-14869

On 21/11/2019 15:28, Stefan Ghinea wrote: file://CVE-2019-14811-0001.patch \ file://CVE-2019-14817-0001.patch \ file://CVE-2019-14817-0002.patch \ +file://CVE-2019-14869-0001.patch \ + " Parsing recipes...ERROR:

Re: [OE-core] [PATCH 1/1] coreutils: add ptest

On Thu, Nov 21, 2019 at 9:43 AM Trevor Gamblin wrote: > > From: Trevor Gamblin > > coreutils has a large number of tests, (and potential RDEPENDS > to support them), including tests added with the flags > RUN_EXPENSIVE_TESTS and RUN_VERY_EXPENSIVE_TESTS that add > significant run time for their

Re: [OE-core] [PATCH] cmake-native:upgrade 3.15.3 -> 3.15.5

On 21/11/2019 08:55, Wang Mingyu wrote: --- .../cmake/{cmake-native_3.15.3.bb => cmake-native_3.15.5.bb} | 0 meta/recipes-devtools/cmake/cmake.inc | 4 ++-- 2 files changed, 2 insertions(+), 2 deletions(-) rename

Re: [OE-core] [PATCH 08/11] lrzsz: remove the recipe

On 21/11/2019 13:59, Phil Blundell wrote: Now, I am happy to accept that building it inside oe-core is somewhat more difficult, and regenerating the autotools bits using modern tools does look like it will require some patching, but I don't think we should exaggerate the extent to which "old

Re: [OE-core] [PATCH v2] tune-riscv: Add support for no float

On Thu, Nov 21, 2019 at 4:08 PM Alistair Francis wrote: > > Signed-off-by: Alistair Francis > --- > meta/conf/machine/include/riscv/arch-riscv.inc | 3 ++- > meta/conf/machine/include/riscv/tune-riscv.inc | 16 +++- > 2 files changed, 17 insertions(+), 2 deletions(-) > > diff --git

Re: [OE-core] [PATCH] gobject-introspection: Fix reproducibility

On 21/11/2019 16:58, Joshua Watt wrote: +Upstream-Status: Pending [https://gitlab.gnome.org/GNOME/gobject-introspection/merge_requests/192] If there's a merge request, the status is Submitted. Ross -- ___ Openembedded-core mailing list

Re: [OE-core] [PATCH v2] tune-riscv: Add support for no float

On Thu, Nov 21, 2019 at 4:08 PM Alistair Francis wrote: > > Signed-off-by: Alistair Francis > --- > meta/conf/machine/include/riscv/arch-riscv.inc | 3 ++- > meta/conf/machine/include/riscv/tune-riscv.inc | 16 +++- > 2 files changed, 17 insertions(+), 2 deletions(-) > > diff --git

Re: [OE-core] [PATCH 1/3] opkg: Add upstream fixes

On Thu, Nov 21, 2019 at 7:02 AM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > Signed-off-by: Richard Purdie > --- > .../opkg/opkg/open_inner.patch| 150 > .../opkg/opkg/opkg_archive.patch | 160 ++ >

Re: [OE-core] How to backport openssl to Sumo

On Thu, Nov 21, 2019 at 5:53 AM Ryan Harkin wrote: > On Thu, 21 Nov 2019 at 13:39, Nicolas Dechesne > wrote: >> On Thu, Nov 21, 2019 at 2:15 PM Ryan Harkin wrote: >> > On Wed, 20 Nov 2019 at 23:53, Andre McCurdy wrote: >> >> On Wed, Nov 20, 2019 at 2:41 PM Ryan Harkin >> >> wrote: >> >> >

[OE-core] [PATCH v2] tune-riscv: Add support for no float

Signed-off-by: Alistair Francis --- meta/conf/machine/include/riscv/arch-riscv.inc | 3 ++- meta/conf/machine/include/riscv/tune-riscv.inc | 16 +++- 2 files changed, 17 insertions(+), 2 deletions(-) diff --git a/meta/conf/machine/include/riscv/arch-riscv.inc

Re: [OE-core] [PATCH] systemd-bootchart: Add RISC-V support

On Thu, Nov 21, 2019 at 12:46 PM Richard Purdie wrote: > > On Thu, 2019-11-21 at 10:21 -0800, Khem Raj wrote: > > This is a partial backport from upstream systemd > > Partial in what regard? Its incomplete and doesn't work? or we don't > need some of it? :) Upstream code has been re-organised

[OE-core] [PATCH 5/5] oeqa/selftest/sstatetests: Ensure we don't use hashequiv for sstatesigs tests

Signed-off-by: Richard Purdie --- meta/lib/oeqa/selftest/cases/sstatetests.py | 12 1 file changed, 12 insertions(+) diff --git a/meta/lib/oeqa/selftest/cases/sstatetests.py b/meta/lib/oeqa/selftest/cases/sstatetests.py index 2867cb78abb..6757a0ec689 100644 ---

[OE-core] [PATCH 4/5] core-image-full-cmdline: Add less

Less was coming from busybox in these images, add the full version. [YOCTO #13630] Signed-off-by: Richard Purdie --- .../packagegroups/packagegroup-core-full-cmdline.bb | 1 + 1 file changed, 1 insertion(+) diff --git

[OE-core] [PATCH 2/5] opkg-utils: Fix silent empty/broken opkg package creation

opkg-build was failing on hosts where tar < 1.28 and reproducibile builds were enabled but it was doing this silently and generating corrupted (empty) ipk files. Add a fix for this (submitted upstream). The fix requires bash but if you're building ipk files this shoudn't be a problem.

[OE-core] [PATCH 3/5] sanity: Add check for tar older than 1.28

Older versions break opkg-build when reproducible builds are enabled. Rather than trying to be selective based on which features are enabled, lets just make this a minimum version. Signed-off-by: Richard Purdie --- meta/classes/sanity.bbclass | 5 - 1 file changed, 4 insertions(+), 1

[OE-core] [PATCH 1/5] opkg: Add upstream fixes for empty packages

An ipk with a zero size data.tar file caused opkg to crash with a double free abort. Add the upstream fixes for this. Signed-off-by: Richard Purdie --- .../opkg/opkg/open_inner.patch| 46 .../opkg/opkg/opkg_archive.patch | 54 +++

[OE-core] OpenEmbedded Workshop at FOSDEM20 CFP

We are proud to announce the inaugural OpenEmbedded Workshop. It is being held on 03 February 2020 in Brussels, Belgium. The day after FOSDEM. The Call for Participation is open now. For more information, go to https://pretalx.com/oe-workshop-2020/cfp Early-bird tickets coming soon! Thank you,

Re: [OE-core] [PATCH] systemd-bootchart: Add RISC-V support

On Thu, 2019-11-21 at 10:21 -0800, Khem Raj wrote: > This is a partial backport from upstream systemd Partial in what regard? Its incomplete and doesn't work? or we don't need some of it? :) > > Signed-off-by: Khem Raj > --- > ...itecture-Recognise-RISCV-32-RISCV-64.patch | 45 >

Re: [OE-core] [PATCH v3 00/17] NPM refactoring

On Thu, 2019-11-21 at 14:53 -0500, Jean-Marie LEMETAYER wrote: > On Nov 21, 2019, at 7:26 PM, Richard Purdie > richard.pur...@linuxfoundation.org wrote: > > On Wed, 2019-11-20 at 10:33 +0100, Jean-Marie LEMETAYER wrote: > > > The current NPM support have several issues: > > > - The current NPM

Re: [OE-core] [PATCH v3 00/17] NPM refactoring

Hi Richard, On Nov 21, 2019, at 7:26 PM, Richard Purdie richard.pur...@linuxfoundation.org wrote: > On Wed, 2019-11-20 at 10:33 +0100, Jean-Marie LEMETAYER wrote: >> The current NPM support have several issues: >> - The current NPM fetcher downloads the dependency tree but not the other >>

Re: [OE-core] [PATCH 3/3] sanity: Add check for tar older than 1.28

On Thu, 2019-11-21 at 13:14 -0600, Mark Hatle wrote: > On 11/21/19 12:09 PM, Richard Purdie wrote: > > On Thu, 2019-11-21 at 19:09 +0200, Adrian Bunk wrote: > > > On Thu, Nov 21, 2019 at 04:54:12PM +, Richard Purdie wrote: > > > > Any suggestions on how we fix it? > > > > > > My preferred

Re: [OE-core] [PATCH 3/3] sanity: Add check for tar older than 1.28

On 11/21/19 12:09 PM, Richard Purdie wrote: > On Thu, 2019-11-21 at 19:09 +0200, Adrian Bunk wrote: >> On Thu, Nov 21, 2019 at 04:54:12PM +, Richard Purdie wrote: >>> On Thu, 2019-11-21 at 17:50 +0200, Adrian Bunk wrote: On Thu, Nov 21, 2019 at 03:02:07PM +, Richard Purdie wrote:

Re: [OE-core] [PATCH v3 00/17] NPM refactoring

On Wed, 2019-11-20 at 10:33 +0100, Jean-Marie LEMETAYER wrote: > The current NPM support have several issues: > - The current NPM fetcher downloads the dependency tree but not the other >fetchers. The 'subdir' parameter was used to fix this issue. > - They are multiple issues with package

[OE-core] [PATCH] systemd-bootchart: Add RISC-V support

This is a partial backport from upstream systemd Signed-off-by: Khem Raj --- ...itecture-Recognise-RISCV-32-RISCV-64.patch | 45 +++ .../systemd-bootchart_233.bb | 1 + 2 files changed, 46 insertions(+) create mode 100644

Re: [OE-core] [PATCH 3/3] sanity: Add check for tar older than 1.28

On Thu, 2019-11-21 at 19:09 +0200, Adrian Bunk wrote: > On Thu, Nov 21, 2019 at 04:54:12PM +, Richard Purdie wrote: > > On Thu, 2019-11-21 at 17:50 +0200, Adrian Bunk wrote: > > > On Thu, Nov 21, 2019 at 03:02:07PM +, Richard Purdie wrote: > > > > Older versions break opkg-build when

Re: [OE-core] [PATCH 0/1] Adding coreutils ptest to oe-core

On Thu, 21 Nov 2019 at 18:43, Trevor Gamblin wrote: > MACHINE| PASS | FAIL | SKIP | TOTAL | > qemux86-64 | 481 |2 | 132 | 615 | > qemuarm64 | 481 |2 | 132 | 615 | > MACHINE| PASS | FAIL | SKIP | TOTAL | > qemux86-64 | 483 |1 | 131 | 615 | > qemuarm64 | 483 |

[OE-core] [PATCH 0/1] Adding coreutils ptest to oe-core

From: Trevor Gamblin Add ptests for coreutils, but omit the most expensive tests. core-image-minimal: MACHINE| PASS | FAIL | SKIP | TOTAL | qemux86-64 | 481 |2 | 132 | 615 | qemuarm64 | 481 |2 | 132 | 615 | core-image-sato: MACHINE| PASS | FAIL | SKIP | TOTAL |

[OE-core] [PATCH 1/1] coreutils: add ptest

From: Trevor Gamblin coreutils has a large number of tests, (and potential RDEPENDS to support them), including tests added with the flags RUN_EXPENSIVE_TESTS and RUN_VERY_EXPENSIVE_TESTS that add significant run time for their coverage. The RUN_VERY_EXPENSIVE_TESTS option has been omitted from

Re: [OE-core] [PATCH 3/3] sanity: Add check for tar older than 1.28

On Thu, Nov 21, 2019 at 04:54:12PM +, Richard Purdie wrote: > On Thu, 2019-11-21 at 17:50 +0200, Adrian Bunk wrote: > > On Thu, Nov 21, 2019 at 03:02:07PM +, Richard Purdie wrote: > > > Older versions break opkg-build when reproducible builds are > > > enabled. > > > Rather than trying to

Re: [OE-core] [PATCH 3/3] sanity: Add check for tar older than 1.28

On Thu, 21 Nov 2019 at 17:54, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > > Unfortunately a newer tar isn't in EPEL. > > I don't have a solution yet, I do know that silently creating empty > packages is much worst than telling a user something won't work though. > > Any

[OE-core] [PATCH] classes/cmake: Use relative RPATHs

In most cases, the RPATH is stripped out when the ELF file is packages, but by then the damage is done from a reproducible perspective because this absolute path is hashed as part of the build-id generated at link time ([1] has a good explanation). Fortunately, newer cmake has an option to

[OE-core] [PATCH] at-spi2-core: Fix reproducibility

Adds a patch to fix to make the -src packages reproducible Signed-off-by: Joshua Watt --- .../0001-Fix-source-reproducibility.patch | 32 +++ .../atk/at-spi2-core_2.32.1.bb| 3 +- 2 files changed, 34 insertions(+), 1 deletion(-) create mode 100644

[OE-core] [PATCH] librsvg: Fix build reproducibility

librsvg was encoding the path to the build directory in order to find a font file for testing. This wouldn't work in OE anyway since the build directory isn't present at that exact location on the target, so remove the offending path to make the build reproducible. Signed-off-by: Joshua Watt ---

[OE-core] [PATCH] gobject-introspection: Fix reproducibility

Adds a patch to remove build paths from gobject-introspection Signed-off-by: Joshua Watt --- .../0001-Fix-build-reproducibility.patch | 50 +++ .../gobject-introspection_1.62.0.bb | 1 + 2 files changed, 51 insertions(+) create mode 100644

[OE-core] [PATCH] pango: Fix reproducibility

Applies a patch to fix the build reproducibility of the -src package. Signed-off-by: Joshua Watt --- .../0001-Fix-build-reproducibility.patch | 31 +++ meta/recipes-graphics/pango/pango_1.44.6.bb | 3 +- 2 files changed, 33 insertions(+), 1 deletion(-) create mode

[OE-core] [PATCH] libjitterentropy: Upgrade 2.1.2 -> 2.2.0

Upstream has a patch that replaces "install -s" with an INSTALL_STRIP make variable, which can be used to replace the custom patch being carried. License checksum change was due to a date in the license text being updated. The actual contents are unchanged. Signed-off-by: Joshua Watt ---

Re: [OE-core] [PATCH 3/3] sanity: Add check for tar older than 1.28

On Thu, 2019-11-21 at 17:50 +0200, Adrian Bunk wrote: > On Thu, Nov 21, 2019 at 03:02:07PM +, Richard Purdie wrote: > > Older versions break opkg-build when reproducible builds are > > enabled. > > Rather than trying to be selective based on which features are > > enabled, > > lets just make

Re: [OE-core] [PATCH 08/11] lrzsz: remove the recipe

On Thu, 2019-11-21 at 17:36 +0200, Adrian Bunk wrote: > There are also two higher level topics that should be discussed: > > 1. Removal of maintainers.inc > There is some nitpicking that every recipe needs a maintainer. > For the package in question the maintainer is not involved in the >

Re: [OE-core] [PATCH 3/3] sanity: Add check for tar older than 1.28

On Thu, Nov 21, 2019 at 03:02:07PM +, Richard Purdie wrote: > Older versions break opkg-build when reproducible builds are enabled. > Rather than trying to be selective based on which features are enabled, > lets just make this a minimum version. >... > +if LooseVersion(version) <

Re: [OE-core] [PATCH 08/11] lrzsz: remove the recipe

On Thu, Nov 21, 2019 at 09:24:34AM +, Ross Burton wrote: >... > So, if zmodem is still a useful feature to have in core, then is anyone > willing to step up and either: > 1) maintain the recipe. I'd love someone who uses lrzsz to put a fork up on > github, integrate all of our patches, and

[OE-core] [meta-oe][PATCH] multimedia: janus-gateway: Added new recipe

Signed-off-by: Marek Belisko Signed-off-by: Jake Withecombe --- .../janus-gateway/files/janus-gateway.service | 14 +++ .../janus-gateway/janus-gateway_0.7.4.bb | 48 ++ 2 files changed, 62 insertions(+) create mode 100644

[OE-core] [PATCH] ghostscript: CVE-2019-14869

A flaw was found in all versions of ghostscript 9.x before 9.28, where the `.charkeys` procedure, where it did not properly secure its privileged calls, enabling scripts to bypass `-dSAFER` restrictions. An attacker could abuse this flaw by creating a specially crafted PostScript file that could

[OE-core] Disbanding SWAT team/process

It is with reluctance, after discussion with the TSC, that we've decided to disband the build failure SWAT process. The reason is simple, there were no longer enough people willing to participate in the process to make it viable. This process was there to try and offload some of the build

[OE-core] [PATCH 3/3] sanity: Add check for tar older than 1.28

Older versions break opkg-build when reproducible builds are enabled. Rather than trying to be selective based on which features are enabled, lets just make this a minimum version. Signed-off-by: Richard Purdie --- meta/classes/sanity.bbclass | 5 - 1 file changed, 4 insertions(+), 1

[OE-core] [PATCH 1/3] opkg: Add upstream fixes

Signed-off-by: Richard Purdie --- .../opkg/opkg/open_inner.patch| 150 .../opkg/opkg/opkg_archive.patch | 160 ++ meta/recipes-devtools/opkg/opkg_0.4.1.bb | 2 + 3 files changed, 312 insertions(+) create mode 100644

[OE-core] [PATCH 2/3] opkg-utils: Fix silent empty/broken opkg package creation

Signed-off-by: Richard Purdie --- .../opkg-utils/opkg-utils/pipefail.patch | 31 +++ .../opkg-utils/opkg-utils_0.4.1.bb| 1 + 2 files changed, 32 insertions(+) create mode 100644 meta/recipes-devtools/opkg-utils/opkg-utils/pipefail.patch diff --git

[OE-core] [PATCH] gstreamer1.0-plugins-bad: add PACKAGECONFIG option for zbar

As a recipe for zbar was added 2016-12-26, we can add an option in PACKAGECONFIG for it. Signed-off-by: Norbert Wesp --- .../gstreamer/gstreamer1.0-plugins-bad_1.16.1.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [OE-core] [PATCH v3 00/17] NPM refactoring

Hi, On Wed, 2019-11-20 at 22:36 -0800, Tim Orling wrote: > > > > On Nov 20, 2019, at 10:27 PM, Tim Orling > > wrote: > > > > > > > > > On Nov 20, 2019, at 1:33 AM, Jean-Marie LEMETAYER > > > wrote: > > > > > > The current NPM support have several issues: > > > - The current NPM fetcher

[OE-core] [PATCH] pulseaudio: 12.2 -> 13.0

Release notes: https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/13.0/ Dropped intltool-native from DEPENDS. The .desktop file translations don't need intltool any more, gettext is enough. Dropped upstreamed patches: 0001-alsa-Fix-inclusion-of-use-case.h.patch

Re: [OE-core] [PATCH 08/11] lrzsz: remove the recipe

On Thu, Nov 21, 2019 at 10:10:30AM +, Richard Purdie wrote: > On Thu, 2019-11-21 at 09:24 +, Ross Burton wrote: > > 2) the source is positively ancient and building it on modern linux is > > getting harder over time Just to put this in perspective, I tried fetching lrzsz-1.20.0.tar.gz

Re: [OE-core] How to backport openssl to Sumo

On Thu, 21 Nov 2019 at 13:39, Nicolas Dechesne wrote: > On Thu, Nov 21, 2019 at 2:15 PM Ryan Harkin > wrote: > > > > > > > > On Wed, 20 Nov 2019 at 23:53, Andre McCurdy wrote: > >> > >> On Wed, Nov 20, 2019 at 2:41 PM Ryan Harkin > wrote: > >> > On Wed, 20 Nov 2019 at 21:29, Ryan Harkin >

Re: [OE-core] How to backport openssl to Sumo

On Thu, Nov 21, 2019 at 2:15 PM Ryan Harkin wrote: > > > > On Wed, 20 Nov 2019 at 23:53, Andre McCurdy wrote: >> >> On Wed, Nov 20, 2019 at 2:41 PM Ryan Harkin wrote: >> > On Wed, 20 Nov 2019 at 21:29, Ryan Harkin wrote: >> >> >> >> I pulled the whole openssl dir from your repo, added the

Re: [OE-core] [PATCH v3 00/17] NPM refactoring

Hi Tim, On Nov 21, 2019, at 7:36 AM, Tim Orling timothy.t.orl...@linux.intel.com wrote: >> On Nov 20, 2019, at 10:27 PM, Tim Orling >> wrote: >>> On Nov 20, 2019, at 1:33 AM, Jean-Marie LEMETAYER >>> >> > wrote: >>> >>> The test steps are these

Re: [OE-core] How to backport openssl to Sumo

On Wed, 20 Nov 2019 at 23:53, Andre McCurdy wrote: > On Wed, Nov 20, 2019 at 2:41 PM Ryan Harkin > wrote: > > On Wed, 20 Nov 2019 at 21:29, Ryan Harkin > wrote: > >> > >> I pulled the whole openssl dir from your repo, added the layer.conf > changes to my layer.conf and rebuilt openssl and my

Re: [OE-core] [PATCH 1/2] devtool/standard.py: Allow recipe to disable menuconfig logic

> -Original Message- > From: Peter Kjellerstedt > Sent: Thursday, November 21, 2019 4:24 AM > To: Tom Hochstein ; > openembedded-core@lists.openembedded.org > Subject: RE: [OE-core] [PATCH 1/2] devtool/standard.py: Allow recipe to > disable menuconfig logic > > > -Original

[OE-core] ✗ patchtest: failure for "[meta-oe] openct: merge do_ins..." and 5 more

== Series Details == Series: "[meta-oe] openct: merge do_ins..." and 5 more Revision: 1 URL : https://patchwork.openembedded.org/series/21281/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

[OE-core] [meta-oe][PATCH 5/6] libp11: add support for native builds

This is needed as a dependency when using SoftHSM from the PKCS#11 OpenSSL engine for code singing. Signed-off-by: Jan Luebbe --- meta-oe/recipes-support/libp11/libp11_0.4.10.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb

[OE-core] [meta-oe][PATCH 4/6] opensc: add support for native builds

This is needed as a dependency when using SoftHSM from the PKCS#11 OpenSSL engine for code singing. Signed-off-by: Jan Luebbe --- meta-oe/recipes-support/opensc/opensc_0.19.0.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-oe/recipes-support/opensc/opensc_0.19.0.bb

[OE-core] [meta-oe][PATCH 3/6] opensc: use pcsc-lite instead of openct by default

OpenCT upstream maintenance seems to have stopped and OpenSC upstream uses pcsc-lite by default in their configure script. Add PACKAGECONFIGs for each and select pcsc by default. As the openct package depends on pcsc-lite by itself, this avoids an unnecessary package in the default case.

[OE-core] [meta-oe][PATCH 1/6] openct: merge do_install and do_install_append

There is no reason why both should be used in the same recipe. Merge them. Signed-off-by: Jan Luebbe --- meta-oe/recipes-support/openct/openct_0.6.20.bb | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/meta-oe/recipes-support/openct/openct_0.6.20.bb

[OE-core] [meta-oe][PATCH 2/6] pcsc-lite: add support for native builds

This is needed as a dependency when using SoftHSM from the PKCS#11 OpenSSL engine for code singing. Add a udev PACKAGECONFIG, as this is only useful on the target. Also don't RRECOMMEND ccid for the native variant. Signed-off-by: Jan Luebbe ---

[OE-core] [meta-oe][PATCH 6/6] softhsm: add recipe

This is useful for consolidation of code-signing interfaces when building an image with verified boot mechanisms or signed update artifacts. It can also be used on the target as a backend for software which uses the PKCS#11 API to access private key material. Signed-off-by: Jan Luebbe ---

Re: [OE-core] [PATCH] tiff: Refresh patch

On 21/11/2019 08:44, Zheng Ruoqin wrote: Refresh CVE-2019-7663.patch as it can't be applyed when using PATCHTOOL = "patch". FWIW this file is removed in current master-next. Ross -- ___ Openembedded-core mailing list

Re: [OE-core] [PATCH 1/2] devtool/standard.py: Allow recipe to disable menuconfig logic

> -Original Message- > From: openembedded-core-boun...@lists.openembedded.org boun...@lists.openembedded.org> On Behalf Of Tom Hochstein > Sent: den 20 november 2019 20:26 > To: openembedded-core@lists.openembedded.org > Subject: [OE-core] [PATCH 1/2] devtool/standard.py: Allow recipe to

Re: [OE-core] [PATCH 08/11] lrzsz: remove the recipe

On Thu, 2019-11-21 at 09:24 +, Ross Burton wrote: > On 20/11/2019 23:18, Adrian Bunk wrote: > > On Wed, Nov 20, 2019 at 11:56:38PM +0100, Alexander Kanavin wrote: > > > On Wed, 20 Nov 2019 at 23:32, Phil Blundell wrote: > > > > > > > However, I think the point still stands that the commit

Re: [OE-core] [PATCH 08/11] lrzsz: remove the recipe

On 20/11/2019 23:18, Adrian Bunk wrote: On Wed, Nov 20, 2019 at 11:56:38PM +0100, Alexander Kanavin wrote: On Wed, 20 Nov 2019 at 23:32, Phil Blundell wrote: However, I think the point still stands that the commit message needs to provide a better description of why the package is being

[OE-core] [PATCH] ltp: Remove acl and at runtime dependency

From: Joerg Vehlow Tests that use at and acl tool were removed in release 20190115. See ltp commit 0fc9b8624bea8acfdb408bf5ff4916b1453e3daa Signed-off-by: Joerg Vehlow --- meta/recipes-extended/ltp/ltp_20190517.bb | 2 -- 1 file changed, 2 deletions(-) diff --git

Re: [OE-core] How to backport openssl to Sumo

On Wed, Nov 20, 2019 at 03:53:14PM -0800, Andre McCurdy wrote: > But anyway, in all cases, the way to debug what's going on isn't to > try random recipe changes and then rebuild the final image. Instead > you should build your chosen version of openssl, look in the > packages-split directory to

Re: [OE-core] How to backport openssl to Sumo

On Thu, Nov 21, 2019 at 01:05:55AM +0200, Adrian Bunk wrote: > On Wed, Nov 20, 2019 at 09:39:51PM +, mikko.rap...@bmw.de wrote: > >... > > I could submit these too if someone wants to setup a communit maintenance > > branch for sumo. > > I would not consider this appropriate for a stable