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

> 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 downloads the dependency tree but n

[OE-core] [PATCH v2] wic: 'wic cp' to copy from image

From: Chee Yang Lee currently 'wic cp' only works for copy file from local storage to wic image. enhance 'wic cp' to copy file/directory from wic image to local storage. include selftest and 'wic help' updates. [YOCTO#12169] Signed-off-by: Chee Yang Lee --- meta/lib/oeqa/selftest/cases/wic.

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

> On Nov 20, 2019, at 1:33 AM, 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 n

[OE-core] [PATCH] wic: 'wic cp' to copy from image

From: Chee Yang Lee currently 'wic cp' only works for copy file from local storage to wic image. enhance 'wic cp' to copy file/directory from wic image to local storage. include selftest and 'wic help' updates. Signed-off-by: Chee Yang Lee --- meta/lib/oeqa/selftest/cases/wic.py | 17 +++

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

Refresh CVE-2019-7663.patch as it can't be applyed when using PATCHTOOL = "patch". Signed-off-by: Zheng Ruoqin --- .../libtiff/tiff/CVE-2019-7663.patch | 71 -- 1 file changed, 26 insertions(+), 45 deletions(-) diff --git a/meta/recipes-multimedia/libtiff/tiff

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

Refresh CVE-2019-7663.patch as it can't be applyed when using PATCHTOOL = "patch". Signed-off-by: Zheng Ruoqin --- .../libtiff/tiff/CVE-2019-7663.patch | 71 -- 1 file changed, 26 insertions(+), 45 deletions(-) diff --git a/meta/recipes-multimedia/libtiff/tiff

[OE-core] ✗ patchtest: failure for busybox:upgrade 1.31.0 -> 1.31.1

== Series Details == Series: busybox:upgrade 1.31.0 -> 1.31.1 Revision: 1 URL : https://patchwork.openembedded.org/series/21263/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on th

[OE-core] ✗ patchtest: failure for busybox:upgrade 1.31.0 -> 1.31.1 (rev2)

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

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

--- .../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 meta/recipes-devtools/cmake/{cmake-native_3.15.3.bb => cmake-native_3.15.5.bb} (1

[OE-core] [PATCH] busybox:upgrade 1.31.0 -> 1.31.1

--- meta/recipes-core/busybox/{busybox_1.31.0.bb => busybox_1.31.1.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-core/busybox/{busybox_1.31.0.bb => busybox_1.31.1.bb} (92%) diff --git a/meta/recipes-core/busybox/busybox_1.31.0.bb b/meta/recipes-core/busybox/b

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

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 image. >> >> Unfortunately, I still have no /usr/bin/openssl in m

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

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 removed. If you > > think it represe

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

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 branch. With such invasive changes it would no longer be reasonably safe for

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

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 removed. If you > think it represents an ongoing maintenance headache that's already bad and > only going to ge

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

On Wed, 20 Nov 2019 at 21:29, Ryan Harkin wrote: > > > On Wed, 20 Nov 2019 at 19:09, Mark Hatle > wrote: > >> >> >> On 11/20/19 1:06 PM, Ryan Harkin wrote: >> > >> > >> > On Wed, 20 Nov 2019 at 18:36, Mark Hatle < >> mark.ha...@kernel.crashing.org >> > > wr

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

On Wed, Nov 20, 2019 at 11:12:37PM +0100, Alexander Kanavin wrote: > The gettext problem is the immediate reason, but the broader reason is that > the code is not maintained, and we should try to avoid burdening the > project with unmaintained code. There's already 8 custom patches fixing > issues

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

On Wed, 20 Nov 2019 at 22:38, Phil Blundell wrote: > If this is the actual reason for removing lrszsz, the commit message should > say so. As it stands, this patch provides no meaningful justification for > why the package should be removed, it just contains a statement about the > last release

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

On Wed, Nov 20, 2019 at 09:00:28PM +0100, Alexander Kanavin wrote: > Do you want to maintain it? Protocols are not changing, but the software > that lrzsz depends on is changing. > > Your first task would be making it build with the latest version of > gettext, the branch containing that is here:

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

On Wed, Nov 20, 2019 at 06:18:05PM +, Ryan Harkin wrote: > I'm struggling with backporting OpenSSL to my Sumo build [1], so wondered > if anyone else had done something similar with success. I've done it by backporting following changes to poky (sorry for subject only): openssh: upgrade 7.6p1

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

On Wed, 20 Nov 2019 at 19:09, Mark Hatle wrote: > > > On 11/20/19 1:06 PM, Ryan Harkin wrote: > > > > > > On Wed, 20 Nov 2019 at 18:36, Mark Hatle > > wrote: > > > > > > > > On 11/20/19 12:18 PM, Ryan Harkin wrote: > > > Hi all, > > > > > >

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

On Wed, 20 Nov 2019 at 21:17, Adrian Bunk wrote: > > Do you want to maintain it? > > Did you already contact the maintainer whose name your patch removes > from maintainers.inc? > Most entries in oe-core's maintainers.inc do not carry any real responsibility or commitment; they're there mostly s

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

On Wed, Nov 20, 2019 at 09:00:28PM +0100, Alexander Kanavin wrote: > On Wed, 20 Nov 2019 at 20:49, Adrian Bunk wrote: > > > > Using serial lines for console work may have its uses, > > > but for transferring files please set up proper networking. > > >... > > > > I've had several recent embedded

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

On Wed, 20 Nov 2019 at 20:49, Adrian Bunk wrote: > > Using serial lines for console work may have its uses, > > but for transferring files please set up proper networking. > >... > > I've had several recent embedded experiences where this was impossible, > and lrzsz was extremely useful. > Do yo

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

On Wed, Nov 20, 2019 at 11:44 AM Ryan Harkin wrote: > > Hi Andre, > > On Wed, 20 Nov 2019 at 19:27, Andre McCurdy wrote: >> >> On Wed, Nov 20, 2019 at 11:09 AM Mark Hatle >> wrote: >> > On 11/20/19 1:06 PM, Ryan Harkin wrote: >> > > On Wed, 20 Nov 2019 at 18:36, Mark Hatle > > >

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

On Wed, Nov 20, 2019 at 02:44:52PM +0100, Alexander Kanavin wrote: > This is 2019; last release of lrzsz was in 1998. The protocols are not changing. > Using serial lines for console work may have its uses, > but for transferring files please set up proper networking. >... I've had several recen

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

Hi Andre, On Wed, 20 Nov 2019 at 19:27, Andre McCurdy wrote: > On Wed, Nov 20, 2019 at 11:09 AM Mark Hatle > wrote: > > On 11/20/19 1:06 PM, Ryan Harkin wrote: > > > On Wed, 20 Nov 2019 at 18:36, Mark Hatle < > mark.ha...@kernel.crashing.org > > > > wrote:

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

On Wed, Nov 20, 2019 at 11:09 AM Mark Hatle wrote: > On 11/20/19 1:06 PM, Ryan Harkin wrote: > > On Wed, 20 Nov 2019 at 18:36, Mark Hatle > > wrote: > > > > You know that 1.0.2 and 1.1 APIs are not compatible? So you will need > > to update > > eve

[OE-core] [PATCH 2/2] u-boot.inc: Fix devtool build u-boot for u-boot without menuconfig

For u-boot recipes without menuconfig support, running devtool results in a do_configure error: cp: cannot stat '/home/r60874/upstream/fsl-xwayland/tmp/work/imx8mmevk-fsl-linux/u-boot-imx/2018.03-r0/u-boot-imx-2018.03//.config': No such file or directory The problem arises because u-boot.inc su

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

u-boot.inc supports u-boot recipes with or without menuconfig [1]. However, running devtool on a u-boot recipe that does not support menuconfig results in an error: cp: cannot stat '/home/r60874/upstream/fsl-xwayland/tmp/work/imx8mmevk-fsl-linux/u-boot-imx/2018.03-r0/u-boot-imx-2018.03//.config':

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

On 11/20/19 1:06 PM, Ryan Harkin wrote: > > > On Wed, 20 Nov 2019 at 18:36, Mark Hatle > wrote: > > > > On 11/20/19 12:18 PM, Ryan Harkin wrote: > > Hi all, > > > > I'm struggling with backporting OpenSSL to my Sumo build [1], so > won

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

On Wed, 20 Nov 2019 at 18:36, Mark Hatle wrote: > > > On 11/20/19 12:18 PM, Ryan Harkin wrote: > > Hi all, > > > > I'm struggling with backporting OpenSSL to my Sumo build [1], so > wondered if > > anyone else had done something similar with success. > > > > I copied "meta/recipes-connectivity/op

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

On Wed, 20 Nov 2019 at 18:28, Ross Burton wrote: > On 20/11/2019 18:18, Ryan Harkin wrote: > > Now it builds fine. However, I no longer have /usr/bin/openssl in my > > disk image. > > $ oe-pkgdata-util find-path /usr/bin/openssl > openssl-bin: /usr/bin/openssl > > Did you try adding openssl-bin t

[OE-core] [PATCH 5/5] grub: don't autoreconf twice

do_configure() essentially calls autogen.sh to generate some sources and then autoreconf, but autogen.sh also calls autoreconf. Pass a magic variable so that autogen.sh doesn't autoreconf for us. Signed-off-by: Ross Burton --- meta/recipes-bsp/grub/grub2.inc | 5 +++-- 1 file changed, 3 inserti

[OE-core] [PATCH 1/5] packagegroup-core-sdk: remove intltool

Intltool is deprecated these days, as gettext can handle almost everything intltool could. Remove it from the SDK packagegroups, if it is needed then the user can add it explicitly. Signed-off-by: Ross Burton --- meta/recipes-core/packagegroups/packagegroup-core-sdk.bb | 1 - 1 file changed, 1

[OE-core] [PATCH 4/5] grub: inherit pkgconfig

Grub uses pkg-config but is only in the sysroot via dependencies. Be explicit and inherit pkgconfig directly. Signed-off-by: Ross Burton --- meta/recipes-bsp/grub/grub2.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-bsp/grub/grub2.inc b/meta/recipes-bsp/gru

[OE-core] [PATCH 3/5] parted: fix whitespace

Signed-off-by: Ross Burton --- meta/recipes-extended/parted/parted_3.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-extended/parted/parted_3.2.bb b/meta/recipes-extended/parted/parted_3.2.bb index 21a815345a9..fb5fa33a8ad 100644 --- a/meta/recipes-extended/

[OE-core] [PATCH 2/5] packagegroup-core-self-hosted: remove intltool

Very little software needs intltool to build, and we don't need it on the host to build Poky. Signed-off-by: Ross Burton --- meta/recipes-core/packagegroups/packagegroup-self-hosted.bb | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb

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

On 11/20/19 12:18 PM, Ryan Harkin wrote: > Hi all, > > I'm struggling with backporting OpenSSL to my Sumo build [1], so wondered if > anyone else had done something similar with success. > > I copied "meta/recipes-connectivity/openssl" from Poky master branch [2] into > my > own layer [3]. It

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

On 20/11/2019 18:18, Ryan Harkin wrote: Now it builds fine. However, I no longer have /usr/bin/openssl in my disk image. $ oe-pkgdata-util find-path /usr/bin/openssl openssl-bin: /usr/bin/openssl Did you try adding openssl-bin to your image explicitly? Ross --

Re: [OE-core] [PATCH] rpm: use libgcrypt instead of NSS for cryptography

On 20/11/2019 17:51, Mark Hatle wrote: Just as an ack.. Please get rid of NSS/NSPR ASAP, and move to libgcrypt. Long term it's a much much better solution. Absolutely. I saw nss fly past in a build and was surprised we still needed it. This is the last user in oe-core currently, but meta-o

[OE-core] How to backport openssl to Sumo

Hi all, I'm struggling with backporting OpenSSL to my Sumo build [1], so wondered if anyone else had done something similar with success. I copied "meta/recipes-connectivity/openssl" from Poky master branch [2] into my own layer [3]. It didn't pick up, so I discovered I needed to add a PREFERRED_

Re: [OE-core] [PATCH] rpm: use libgcrypt instead of NSS for cryptography

Just as an ack.. Please get rid of NSS/NSPR ASAP, and move to libgcrypt. Long term it's a much much better solution. --Mark On 11/20/19 10:19 AM, Ross Burton wrote: > RPM 4.15 by default will use libgcrypt instead of NSS for cryptography > functions, but as we didn't have libgcrypt in DEPENDS it

[OE-core] ✗ patchtest: failure for rpm: use libgcrypt instead of NSS for cryptography

== Series Details == Series: rpm: use libgcrypt instead of NSS for cryptography Revision: 1 URL : https://patchwork.openembedded.org/series/21254/ 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] How to add build date?

On 11/17/19 3:19 PM, Alexander Kanavin wrote: I'd write the date into the file at image creation, via ROOTFS_POSTPROCESS_COMMAND. Having it in a recipe means that you either force the recipe to not be a part of sstate cache, always rebuilding it and its dependencies (bad idea), or accept that

[OE-core] [PATCH] rpm: use libgcrypt instead of NSS for cryptography

RPM 4.15 by default will use libgcrypt instead of NSS for cryptography functions, but as we didn't have libgcrypt in DEPENDS it kept using NSS. As RPM is the sole user of NSS/NSPR in oe-core, moving to libgcrypt can make a noticable difference to build time. For example, building rpm (and packagi

Re: [OE-core] [PATCH] bitbake: prserv: fix ResourceWarning due to unclosed socket

Thanks, but it still starts and terminates PRServer immediately, right? With your fix, all my builds now start with: NOTE: Started PRServer with DBfile: /OE/build/oe-core/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 34335, PID: 9429 NOTE: Terminating PRServer... NOTE: Started PRServer with DBfile:

[OE-core] [PATCH v2] sdk: environment script doesn't set security options in CC and LDFLAGS variables

When building a SDK from a DISTRO with security flags enabled, options added to CC and LDFLAGS are not replicated in the SDK environment script. This could lead to some situations where an application compiled with the SDK and having some security weaknesses correctly runs on target but crashes onc

Re: [OE-core] [PATCH 01/13] python: update to 2.7.17

On Wed, Nov 20, 2019 at 04:06:44PM +0100, Alexander Kanavin wrote: > On Wed, 20 Nov 2019 at 14:50, Tom Rini wrote: > > > Well, the release is scheduled for January 6th. I'd really like to see > > more testing in no-python2 environment. I believe the Fedora folks have > > confirmed things are go

Re: [OE-core] [PATCH 01/13] python: update to 2.7.17

On Wed, 20 Nov 2019 at 14:50, Tom Rini wrote: > Well, the release is scheduled for January 6th. I'd really like to see > more testing in no-python2 environment. I believe the Fedora folks have > confirmed things are good now but it would be good to see OE do it too, > especially on master and n

[OE-core] ✗ patchtest: failure for SDK environment script doesn't set security options in CC and LDFLAGS variables

== Series Details == Series: SDK environment script doesn't set security options in CC and LDFLAGS variables Revision: 1 URL : https://patchwork.openembedded.org/series/21252/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated

[OE-core] [yocto] [PATCH] SDK environment script doesn't set security options in CC and LDFLAGS variables

When building a SDK from a DISTRO with security flags enabled, options added to CC and LDFLAGS are not replicated in the SDK environment script. This could lead to some situations where an application compiled with the SDK and having some security weaknesses correctly runs on target but crashes onc

Re: [OE-core] [PATCH 01/13] python: update to 2.7.17

On Wed, Nov 20, 2019 at 02:47:19PM +0100, Alexander Kanavin wrote: > On Wed, 20 Nov 2019 at 13:56, Tom Rini wrote: > > > I would _really_ like to see someone move master to using v2020.01-rc3 > > or so for U-Boot as that should not have any Python 2 dependencies left. > > rc3 means the final rel

Re: [OE-core] [PATCH 01/13] python: update to 2.7.17

On Wed, 20 Nov 2019 at 13:56, Tom Rini wrote: > I would _really_ like to see someone move master to using v2020.01-rc3 > or so for U-Boot as that should not have any Python 2 dependencies left. > rc3 means the final release is very soon, so we'll gladly update to that. Alex --

[OE-core] [PATCH 11/11] systemtap: update to 4.2

Signed-off-by: Alexander Kanavin --- meta/recipes-kernel/systemtap/systemtap_git.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-kernel/systemtap/systemtap_git.inc b/meta/recipes-kernel/systemtap/systemtap_git.inc index abb2b3743b4..116e83fe0ff 100644 ---

[OE-core] [PATCH 10/11] mc: backport a patch to fix builds with latest gettext

Signed-off-by: Alexander Kanavin --- ...29-configure.ac-drop-bundled-gettext.patch | 110 ++ meta/recipes-extended/mc/mc_4.8.23.bb | 1 + 2 files changed, 111 insertions(+) create mode 100644 meta/recipes-extended/mc/files/0001-Ticket-3629-configure.ac-drop-bundled-get

[OE-core] [PATCH 07/11] console-tools: remove the recipe

The last release of this was in 2002(!), kbd is the modern, supported alternative. Signed-off-by: Alexander Kanavin --- meta/conf/distro/include/maintainers.inc | 1 - .../0001-Cover-the-else-with-__GLIBC__.patch | 51 - ...ix-format-security-compilation-error.patch | 57 -

[OE-core] [PATCH 09/11] p11-kit: convert to meson

Signed-off-by: Alexander Kanavin --- .../p11-kit/p11-kit_0.23.18.1.bb | 26 +++ 1 file changed, 3 insertions(+), 23 deletions(-) diff --git a/meta/recipes-support/p11-kit/p11-kit_0.23.18.1.bb b/meta/recipes-support/p11-kit/p11-kit_0.23.18.1.bb index 9193a06ea80..dbf

[OE-core] [PATCH 02/11] man-pages: update to 5.03

Signed-off-by: Alexander Kanavin --- .../man-pages/{man-pages_5.01.bb => man-pages_5.03.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/man-pages/{man-pages_5.01.bb => man-pages_5.03.bb} (87%) diff --git a/meta/recipes-extended/man-pages/man-pa

[OE-core] [PATCH 06/11] e2fsprogs: fix build issues with the latest version of gettext

Signed-off-by: Alexander Kanavin --- ...-configure.ac-correct-AM_GNU_GETTEXT.patch | 26 ++ ...to-use-gettext-defines-that-no-longe.patch | 27 +++ ...-missing-check-for-permission-denied.patch | 7 ++--- .../e2fsprogs/e2fsprogs/quiet-debugfs.patch | 13 +++-

[OE-core] [PATCH 03/11] dummy-sdk-package.inc: do not include files into RREPLACES

rpm 4.15 no longer allows it, which makes sense. Signed-off-by: Alexander Kanavin --- meta/recipes-core/meta/dummy-sdk-package.inc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/recipes-core/meta/dummy-sdk-package.inc b/meta/recipes-core/meta/dummy-sdk-package.inc in

[OE-core] [PATCH 05/11] gettext: update to 0.20.1

License-Update: URLs changed from http to https Signed-off-by: Alexander Kanavin --- .../gettext-0.19.8.1/fix-CVE-2018-18751.patch | 141 .../gettext/gettext-0.19.8.1/parallel.patch | 23 - .../gettext-0.19.8.1/use-pkgconfig.patch | 321 .../add-with-bisonlocaledir.patch

[OE-core] [PATCH 01/11] man-pages: correct the SRC_URI

The homepage: https://www.kernel.org/doc/man-pages/download.html specifies that the latest tarballs are published one level up from where we currently take them. Signed-off-by: Alexander Kanavin --- meta/recipes-extended/man-pages/man-pages_5.01.bb | 2 +- 1 file changed, 1 insertion(+), 1 delet

Re: [OE-core] [PATCH] alsa-lib:upgrade 1.1.9 -> 1.2.1.1

Hi, I'm still around. Yes, the moved UCM conf files need to be packaged. (And no doubt the topology files too, although that's an area I understand less well). -- Tanu On Wed, 2019-11-20 at 13:10 +0100, Alexander Kanavin wrote: > If Tanu is still around, he should probably chime in. > > Alex >

Re: [OE-core] [PATCH 01/13] python: update to 2.7.17

On Mon, Nov 18, 2019 at 02:07:49PM +0100, Alexander Kanavin wrote: > Drop backports, rebase a couple of patches. > > This is the second last release of py 2.x; upstream support ends on > 1 January 2020, there will be one final 2.x afterwards. > > Note that the only thing that still needs python

[OE-core] [PATCH v5 2/2] image_types: add Zstandard conversion support

From: Stefan Agner Add Zstandard (or just Zstd) compression support. This allows to create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES. Signed-off-by: Stefan Agner --- meta/classes/image_types.bbclass | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/me

[OE-core] [PATCH v5 1/2] zstd: move recipe to oe-core from meta-oe

From: Stefan Agner Zstd is a very fast compression algorithm and has gained quite some popularity recently. An upcoming patch allows to compress rootfs using Zstd. Moving Zstd to oe-core allows this new conversion formats to be automatically tested by the oe-selftest imagefeatures.ImageFeatures.t

Re: [OE-core] [PATCH v4 2/2] image_types: add Zstandard conversion support

On 2019-11-20 11:49, Alex Kiernan wrote: > On Wed, Nov 20, 2019 at 9:13 AM Stefan Agner wrote: >> >> From: Stefan Agner >> >> Add Zstandard (or just Zstd) compression support. This allows to >> create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES. >> >> Signed-off-by: Stefan Agner >

Re: [OE-core] [PATCH] alsa-lib:upgrade 1.1.9 -> 1.2.1.1

If Tanu is still around, he should probably chime in. Alex On Wed, 20 Nov 2019 at 12:55, Mittal, Anuj wrote: > This version has moved ucm and topology conf files to separate > repositories. We should also probably fetch and package those. > > > https://github.com/alsa-project/alsa-lib/commit/1f

Re: [OE-core] [PATCH 01/13] python: update to 2.7.17

On 19/11/2019 16:30, Adrian Bunk wrote: You want meta-oe to have a LAYERDEPENDS on a new python2 layer that is not in meta-openembedded? Would that be a bad thing? Layers shouldn't care about where they are hosted. My ideal would be that meta-python2 exists with both the python2 recipes an

Re: [OE-core] [PATCH] alsa-lib:upgrade 1.1.9 -> 1.2.1.1

This version has moved ucm and topology conf files to separate repositories. We should also probably fetch and package those. https://github.com/alsa-project/alsa-lib/commit/1f37ba2a2b1c07c04de1c368cd4943f712cccfa5 https://github.com/alsa-project/alsa-lib/commit/cdc8aacbb57c82a81e3b398f2ede6440d4

Re: [OE-core] [PATCH] pseudo: Update checksum of the license file

On Wed, 2019-11-20 at 11:39 +, shohei.maruy...@cybertrust.co.jp wrote: > On Wed, 2019-11-20 at 12:23 +0100, Alexander Kanavin wrote: > > On Wed, 20 Nov 2019 at 07:26, wrote: > > > Recently pseudo.inc has been updated to latest master > > > (d50b9c511e17c6f582e > > > f39b61eaaa8d4555eabba), but

Re: [OE-core] [PATCH] pseudo: Update checksum of the license file

On Wed, 2019-11-20 at 12:23 +0100, Alexander Kanavin wrote: On Wed, 20 Nov 2019 at 07:26, mailto:shohei.maruy...@cybertrust.co.jp>> wrote: Recently pseudo.inc has been updated to latest master (d50b9c511e17c6f582e f39b61eaaa8d4555eabba), but checksum of the license file did not change. This commi

Re: [OE-core] [PATCH] pseudo: Update checksum of the license file

On Wed, 20 Nov 2019 at 07:26, wrote: > Recently pseudo.inc has been updated to latest master (d50b9c511e17c6f582e > f39b61eaaa8d4555eabba), but checksum of the license file did not change. > This commit updates the checksum to latest one. > I am not sure I can make sense of this. When the checks

Re: [OE-core] [PATCH] alsa-lib:upgrade 1.1.9 -> 1.2.1.1

On Wed, 20 Nov 2019 at 06:17, Zang Ruochen wrote: > +From f419276a716daf8d98846b3df50995e5ac030134 Mon Sep 17 00:00:00 2001 > +From: Zang Ruochen > +Date: Wed, 20 Nov 2019 11:24:17 +0800 > +Subject: [PATCH] Fix problem with libtool not found > + > +Upstream-Status: Inappropriate > Why inappropr

Re: [OE-core] [PATCH v4 2/2] image_types: add Zstandard conversion support

On Wed, Nov 20, 2019 at 9:13 AM Stefan Agner wrote: > > From: Stefan Agner > > Add Zstandard (or just Zstd) compression support. This allows to > create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES. > > Signed-off-by: Stefan Agner > --- > meta/classes/image_types.bbclass | 8 +

Re: [OE-core] [PATCH v4 2/2] image_types: add Zstandard conversion support

On Wed, Nov 20, 2019 at 10:32 AM Adrian Bunk wrote: > > On Wed, Nov 20, 2019 at 09:12:58AM +, Stefan Agner wrote: > >... > > --- a/meta/classes/image_types.bbclass > > +++ b/meta/classes/image_types.bbclass > > @@ -59,6 +59,8 @@ XZ_INTEGRITY_CHECK ?= "crc32" > > > > ZIP_COMPRESSION_LEVEL ?= "

Re: [OE-core] [PATCH v4 2/2] image_types: add Zstandard conversion support

On Wed, Nov 20, 2019 at 09:12:58AM +, Stefan Agner wrote: >... > --- a/meta/classes/image_types.bbclass > +++ b/meta/classes/image_types.bbclass > @@ -59,6 +59,8 @@ XZ_INTEGRITY_CHECK ?= "crc32" > > ZIP_COMPRESSION_LEVEL ?= "-9" > > +ZSTD_COMPRESSION_LEVEL ?= "-3" > + >... Why -3 and not

[OE-core] [PATCH v3 15/17] devtool/standard.py: npm: configure the NPM_CACHE_DIR to be persistent

When using devtool the ${WORKDIR} is not persistent as the creation workflow is using temporary directories and external workspace. For npm recipes the NPM_CACHE_DIR needs to be persistent to make the link between the first do_fetch, do_unpack tasks and the do_compile task. As the only persistent

[OE-core] [PATCH v3 17/17] oeqa/selftest/devtool: add npm recipe build test

This commit adds a devtool build test for npm recipe: - devtool.DevtoolAddTests.test_devtool_add_npm Signed-off-by: Jean-Marie LEMETAYER --- meta/lib/oeqa/selftest/cases/devtool.py | 20 1 file changed, 20 insertions(+) diff --git a/meta/lib/oeqa/selftest/cases/devtool.py

[OE-core] [PATCH v3 13/17] recipetool/create_npm.py: convert the shrinkwrap file

A local npm cache pre filled with the dependencies is used to be able to install the npm package without doing any unauthorized network access. When it is offline, the npm cache identify a package using its integrity metadata [1] but only the sha512 algorithm is used (this is the default cacache a

[OE-core] [PATCH v3 16/17] oeqa/selftest/recipetool: add npm recipe creation test

This commit adds a recipetool creation test for npm recipe: - recipetool.RecipetoolTests.test_recipetool_create_npm Signed-off-by: Jean-Marie LEMETAYER --- meta/lib/oeqa/selftest/cases/recipetool.py | 21 + 1 file changed, 21 insertions(+) diff --git a/meta/lib/oeqa/selfte

[OE-core] [PATCH v3 14/17] npm.bbclass: force to rebuild the prebuild addons

This commit forces to rebuild the prebuild addons which are using node-gyp-build. https://www.npmjs.com/package/node-gyp-build Signed-off-by: Jean-Marie LEMETAYER --- meta/classes/npm.bbclass | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/classes/npm.bbclass b/meta/classes/npm.bb

[OE-core] [PATCH v3 10/17] recipetool/create_npm.py: handle the licenses of the dependencies

As usual the 'LICENSE' and the 'LIC_FILES_CHKSUM' values reflects all the license files discovered in the source tree (including the dependencies). For npm recipes the 'LIC_FILES_CHKSUM' value contains also the status of the 'package.json' file of every packages as it contains license informations

[OE-core] [PATCH v3 12/17] npm.bbclass: use the local node headers

When building addons, the node headers are needed to be able to compile properly. Usually they are downloaded by npm but network access in the do_compile task are unauthorized. Hopefully the local node headers are available in the native sysroot so lets use them. Signed-off-by: Jean-Marie LEMETAYE

[OE-core] [PATCH v3 09/17] devtool/standard.py: npm: exclude the node_modules directory

If 'devtool add' was executed without the '--no-git' option a git repository have been initialized in the source directory in order to check if the sources stay unchanged after the 'devtool build' command. The 'devtool finish' command will fail if any modification is found. As the node_modules dir

[OE-core] [PATCH v3 07/17] recipetool/create.py: npm: replace the 'latest' keyword

The new npm fetcher allows the 'latest' keyword to be used to download the latest version on the registry. But the keyword must be replace as soon as the version is determined to have a stable generated recipe. Signed-off-by: Jean-Marie LEMETAYER --- scripts/lib/recipetool/create.py | 2 ++ 1 fi

[OE-core] [PATCH v3 11/17] npm.bbclass: restrict the build to be offline

After the do_fetch task, every other tasks must not access the network. In order to ensure this point every npm command must use the '--offline' argument. In addition, setting an invalid proxy is used as a safety. Signed-off-by: Jean-Marie LEMETAYER --- meta/classes/npm.bbclass | 4 +++- 1 file

[OE-core] [PATCH v3 08/17] npm.bbclass: split the do_compile task

The do_compile task must be split in order to fit the yocto workflow. The dependencies are fetched in the do_fetch task and cached in the do_unpack task. Signed-off-by: Jean-Marie LEMETAYER --- meta/classes/npm.bbclass | 19 +++ 1 file changed, 19 insertions(+) diff --git a/meta

[OE-core] [PATCH v3 06/17] recipetool/create.py: npm: remove the 'noverify' url parameter

This commit removes the 'noverify' parameter which was added to the url to fix warnings with the shrinkwrap / lockdown file generation. This is not needed anymore with the new npm fetcher. Signed-off-by: Jean-Marie LEMETAYER --- scripts/lib/recipetool/create.py | 2 -- 1 file changed, 2 deletion

[OE-core] [PATCH v3 02/17] npm.bbclass: refactor the npm class

Many issues were related to npm dependencies badly handled: package names, installation directories, ... In fact npm is using an install algorithm [1] which is hard to reproduce / anticipate. Moreover some npm packages use scopes [2] which adds more complexity. The simplest solution is to let npm

[OE-core] [PATCH v3 05/17] devtool/standard.py: npm: update the append file

When creating a recipe using devtool, a workspace is created to store the new recipe, the recipe source and some append files. These append files are used by devtool to build the recipe using externalsrc (to use the source which are in the workspace). They can also have some additional actions acco

[OE-core] [PATCH v3 01/17] devtool: npm: update command line options

This commit renames the '--fetch-dev' option into '--npm-dev' which is more easily understandable. It also adds the '--npm-registry' option to allow creating a npm recipe with a non default npm registry (e.g. if the SRC_URI is using git://). Signed-off-by: Jean-Marie LEMETAYER --- scripts/lib/d

[OE-core] [PATCH v3 04/17] lib/oe/package.py: remove unneeded npm_split_package_dirs function

The npm_split_package_dirs function was used by the recipetool when creating npm recipes. This is not the case anymore. Signed-off-by: Jean-Marie LEMETAYER --- meta/lib/oe/package.py | 33 - 1 file changed, 33 deletions(-) diff --git a/meta/lib/oe/package.py b/me

[OE-core] [PATCH v3 03/17] recipetool/create_npm.py: refactor the npm recipe creation handler

This commit refactors the npm recipe creation handler to use the new npm behavior. The process is kept as simple as possible and only generates the shrinkwrap file. To avoid naming issues the recipe name is now extracted from the npm package name and not directly mapped. Signed-off-by: Jean-Marie

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

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 names (uppercase, exotic characters, scoped packages) even if they are

[OE-core] [PATCH v4 1/2] zstd: move recipe to oe-core from meta-oe

From: Stefan Agner Zstd is a very fast compression algorithm and has gained quite some popularity recently. An upcoming patch allows to compress rootfs using Zstd. Moving Zstd to oe-core allows this new conversion formats to be automatically tested by the oe-selftest imagefeatures.ImageFeatures.t

[OE-core] [PATCH v4 2/2] image_types: add Zstandard conversion support

From: Stefan Agner Add Zstandard (or just Zstd) compression support. This allows to create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES. Signed-off-by: Stefan Agner --- meta/classes/image_types.bbclass | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/me

Re: [OE-core] [PATCH v3 1/2] zstd: move recipe to oe-core from meta-oe

On 2019-11-19 17:18, Alex Kiernan wrote: > On Mon, Nov 18, 2019 at 6:39 PM Stefan Agner wrote: >> >> [adding Alex, he maintained the recipe in meta-oe so far] >> >> On 2019-11-18 13:19, Richard Purdie wrote: >> > On Thu, 2019-11-14 at 15:47 +0100, Stefan Agner wrote: >> >> On 2019-11-08 10:14, Ste