[OE-core] SDK does not contain pkg-config files

I'm trying to get the SDK to work, but no success because the SDK apparently does not install any pkg-config file, resulting in autotools and cmake not being able to find any library. Built the SDK using "bitbake -c populate_sdk image" Install the resulting SDK, and source the shell script. Bu

Re: [OE-core] [PATCH v2 1/2] fortran-helloworld: add a very dumb Fortran Hello World for testing

On Tue, Jun 25, 2019 at 7:52 AM Ross Burton wrote: > > For future runtime testing something more complex is preferred but this is > sufficient to exercise the cross compiler. > > Signed-off-by: Ross Burton > --- > meta-selftest/recipes-test/fortran/files/hello.f95 | 5 + > .../recipes-test/

[OE-core] [PATCH] python: CVE-2019-9947 is same as CVE-2019-9740

See: https://bugs.python.org/issue30458 Signed-off-by: Anuj Mittal --- meta/recipes-devtools/python/python/CVE-2019-9740.patch | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/python/python/CVE-2019-9740.patch b/meta/recipes-devtools/python/python/CVE-2019-9740.patch in

[OE-core] [PATCH] python: fix CVE-2018-20852

Signed-off-by: Anuj Mittal --- meta/recipes-devtools/python/python.inc | 1 + .../python/python/CVE-2018-20852.patch| 123 ++ 2 files changed, 124 insertions(+) create mode 100644 meta/recipes-devtools/python/python/CVE-2018-20852.patch diff --git a/meta/recipes-

[OE-core] ✗ patchtest: failure for qemuboot-x86.inc: remove it and move content to corresponding conf

== Series Details == Series: qemuboot-x86.inc: remove it and move content to corresponding conf Revision: 1 URL : https://patchwork.openembedded.org/series/18978/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Seve

[OE-core] [PATCH] qemuboot-x86.inc: remove it and move content to corresponding conf

From: Changqing Li Configrations: MACHINE: qemux86-64 require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" Reproduce steps: bitbake lib32-core-image-minimal runqemu qemux86-64 nographic lib32-core-image-minimal Errors: qemu cannot bootup since: Bo

Re: [OE-core] [PATCHv3] mdadm:fix mdmonitor.service

On 07/31/2019 09:50 AM, Zang Ruochen wrote: -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

[OE-core] ✗ patchtest: failure for mdadm:fix mdmonitor.service

== Series Details == Series: mdadm:fix mdmonitor.service Revision: 1 URL : https://patchwork.openembedded.org/series/18977/ 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 pro

[OE-core] [PATCHv3] mdadm:fix mdmonitor.service

-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 proper

[OE-core] [PATCH 2/2] perl: add PACKAGECONFIG for db

perl-cross makes it easy to cleanly disable the use of Berkeley DB if desired, so add a PACKAGECONFIG for this. More of the dependencies (such as gdbm) can be controlled in the same way, but Berkeley DB is a prime contender: it's a large library which we have to ship an old release for due to lice

[OE-core] [PATCH 1/2] perl: fix whitespace

There was some tabs embedded in spaces, fix those. Signed-off-by: Ross Burton --- meta/recipes-devtools/perl/perl_5.30.0.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-devtools/perl/perl_5.30.0.bb b/meta/recipes-devtools/perl/perl_5.30.0.bb index e366429

Re: [OE-core] [PATCH] bind: Remove RECIPE_NO_UPDATE_REASON and follow the ESV releases

On 7/30/19 6:01 AM, Alexander Kanavin wrote: On Tue, 30 Jul 2019 at 11:21, akuster808 > wrote: So are you setting the package update policy to LTS only ?  Its a function over maintenance question. I don't understand why this package is being singled out

Re: [OE-core] OEDEM 2019

We are working with the Yocto Project on a two day Summit event. This should implement part of the ideas from the the last couple of developer meetings. Philip On 07/30/2019 12:58 PM, Ruslan Bilovol wrote: > Hi all, > > Is there any plan to hold an OpenEmbedded developer meting > in Lyon, France

[OE-core] OEDEM 2019

Hi all, Is there any plan to hold an OpenEmbedded developer meting in Lyon, France around this year's ELCE 2019 (October 28-30)? I see that OEDEM 2019 page isn't created yet and I didn't find any news in mailing lists yet: https://www.openembedded.org/wiki/OEDEM_2019 Thanks, Ruslan -- _

[OE-core] [PATCH] stress-ng: add a recipe that replaces the original stress

The original stress is no longer maintained and the homepage went down. This commit replaces it with a maintained re-implementation by Ubuntu. Stress-ng preserves command line option compatibility (for the options that are used in rt-tests), so adjustment is simply changing the name of the executa

[OE-core] [PATCH 8/8] bzip2: fix upstream version check

As it is now working, we do not need an exception from the check anymore. Signed-off-by: Alexander Kanavin --- meta/recipes-extended/bzip2/bzip2_1.0.8.bb | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/recipes-extended/bzip2/bzip2_1.0.8.bb b/meta/recipes-extended/bzip2/bzip2_1.0.8.bb in

[OE-core] [PATCH 7/8] webkitgtk: upgrade 2.24.2 -> 2.24.3

Signed-off-by: Alexander Kanavin --- meta/recipes-sato/webkit/webkitgtk/snprintf.patch | 15 --- .../{webkitgtk_2.24.2.bb => webkitgtk_2.24.3.bb} | 5 ++--- 2 files changed, 2 insertions(+), 18 deletions(-) delete mode 100644 meta/recipes-sato/webkit/webkitgtk/snprintf.patch renam

[OE-core] [PATCH 6/8] createrepo-c: upgrade 0.14.2 -> 0.14.3

Signed-off-by: Alexander Kanavin --- .../{createrepo-c_0.14.2.bb => createrepo-c_0.14.3.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/createrepo-c/{createrepo-c_0.14.2.bb => createrepo-c_0.14.3.bb} (95%) diff --git a/meta/recipes-devtools/creat

[OE-core] [PATCH 5/8] libwebp: upgrade 1.0.2 -> 1.0.3

Signed-off-by: Alexander Kanavin --- .../webp/{libwebp_1.0.2.bb => libwebp_1.0.3.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-multimedia/webp/{libwebp_1.0.2.bb => libwebp_1.0.3.bb} (93%) diff --git a/meta/recipes-multimedia/webp/libwebp_1.0.2.

[OE-core] [PATCH 4/8] libmodulemd: update to 2.6.0

Signed-off-by: Alexander Kanavin --- ...n.build-do-not-generate-gir-or-gtkdo.patch | 26 +++ .../libmodulemd/libmodulemd_git.bb| 4 +-- 2 files changed, 17 insertions(+), 13 deletions(-) diff --git a/meta/recipes-devtools/libmodulemd/libmodulemd/0002-modulemd-v1-mes

[OE-core] [PATCH 3/8] btrfs-tools: update 5.1.1 -> 5.2.1

Signed-off-by: Alexander Kanavin --- .../btrfs-tools/{btrfs-tools_5.1.1.bb => btrfs-tools_5.2.1.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_5.1.1.bb => btrfs-tools_5.2.1.bb} (97%) diff --git a/meta/recipes-devtools/btrfs-tool

[OE-core] [PATCH 1/8] meson: update 0.50.1 -> 0.51.1

Drop backports. Rebase other patches. Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/meson/meson.inc | 6 +- .../0001-Make-CPU-family-warnings-fatal.patch | 10 +- ...etect-windows-also-if-the-system-str.patch | 14 +- ...onment.py-check-environment-for-vari.patch | 20

[OE-core] [PATCH 2/8] meson.bbclass: do not pass native compiler/linker flags via command line

With 0.51.0 version these command line options override what is in the cross file (e.g. the cross-flags). I could not determine what is the scenario when the native flags are needed (this would be building a native binary in the context of cross build). If we find such a scenario we would need to

[OE-core] Yocto Project Status WW31'19

Current Dev Position: YP 2.8 M3 Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019 SWAT Team Rotation: * SWAT lead is currently: Paul * SWAT team rotation: Paul -> Ross on Aug. 2, 2019 * SWAT team rotation: Ross -> Amanda on Aug. 9, 2019 *

[OE-core] LF Community Bridge Mentorship

Dear all, The Community Bridge platform was launched earlier this year by the Linux Foundation. It’s a set of services available to LF projects to help them build stronger ecosystems, and foster developers relationship within their respective communities. See [1] and [2]. The Yocto Project has joi

Re: [OE-core] [PATCH] sstate: Truncate PV in sstate filenames that are too long

On 7/30/19 8:49 AM, Mike Crowe wrote: > On Tuesday 30 July 2019 at 08:25:52 -0500, Mark Hatle wrote: >> On 7/30/19 6:01 AM, Mike Crowe wrote: >>> sstate filenames are generated by concatenating a variety of bits of >>> package metadata. Some of these parts could be long, which could cause >>> the f

[OE-core] [PATCH] kmscube: update to latest revision

Switch to gitlab URL, since previos location is now a mirror Signed-off-by: Zoltan Kuscsik --- ...bo_map-_unmap-and-use-it-or-avoid-it.patch | 25 ++- meta/recipes-graphics/kmscube/kmscube_git.bb | 4 +-- 2 files changed, 15 insertions(+), 14 deletions(-) diff --git a/meta/re

Re: [OE-core] [PATCH] sstate: Truncate PV in sstate filenames that are too long

On Tuesday 30 July 2019 at 08:25:52 -0500, Mark Hatle wrote: > On 7/30/19 6:01 AM, Mike Crowe wrote: > > sstate filenames are generated by concatenating a variety of bits of > > package metadata. Some of these parts could be long, which could cause > > the filename to be longer than the 255 charact

[OE-core] ✗ patchtest: failure for Enforce Shared State Signing when optionsset

== Series Details == Series: Enforce Shared State Signing when optionsset Revision: 1 URL : https://patchwork.openembedded.org/series/18968/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been ex

Re: [OE-core] [PATCH] sstate: Truncate PV in sstate filenames that are too long

On 7/30/19 6:01 AM, Mike Crowe wrote: > sstate filenames are generated by concatenating a variety of bits of > package metadata. Some of these parts could be long, which could cause > the filename to be longer than the 255 character maximum for ext4. > > So, let's try to detect this situation and

[OE-core] [PATCH v2 3/3] classes/sstate: regenerate sstate when signing enabled

This change ensures that the task signatures changes, and therefore sstate tasks are rerun, when signing is enabled. This has the positive outcome that if signing is enabled new signed shared state objects will be produced, rather than just signing shared state objects for tasks where no work has b

[OE-core] [PATCH v2 1/3] sstate: fix log message

Referring to the sstate object as a staging package is an artefact of the code's origins. Switch to referring to an "Sstate package" in order to be more accurate and consistent with the rest of the file. Signed-off-by: Joshua Lock --- meta/classes/sstate.bbclass | 2 +- 1 file changed, 1 inserti

[OE-core] [PATCH v2 2/3] classes/sstate: don't use unsigned sstate when verification enabled

When signature verification of shared state objects is enabled (SSTATE_VERIFY_SIG) use of an unsigned object, even though it produces a warning, seems unexpected. Instead skip unsigned objects and force the non-accelerated task to be run. Signed-off-by: Joshua Lock --- meta/classes/sstate.bbclas

[OE-core] [PATCH v2 0/3] Enforce Shared State Signing when optionsset

There are 2 surprising behaviours in the current shared state signing implementation which this pull request addresses: 1) when signature verification is enabled a failure to verify doesn't prevent the shared state object from being used. A warning is printed and the unsigned shared state obj

Re: [OE-core] [PATCH] glib-networking: Support building with USE_NLS=no

On 30/07/2019 14:03, Mike Crowe wrote: On Tuesday 30 July 2019 at 12:15:36 +0100, Ross Burton wrote: On 30/07/2019 12:00, Mike Crowe wrote: As reported in http://lists.openembedded.org/pipermail/openembedded-core/2019-February/279344.html , glib-networking no longer configures successfully if U

Re: [OE-core] [PATCH] bind: Remove RECIPE_NO_UPDATE_REASON and follow the ESV releases

On Tue, 30 Jul 2019 at 11:21, akuster808 wrote: > So are you setting the package update policy to LTS only ? Its a > function over maintenance question. > > I don't understand why this package is being singled out. I think it > should be an OE architecture discussion > I am not sure why are yo

[OE-core] [thud][PATCH 2/2] python3: fix CVE-2019-9740

CVE-2019-9947 is same as CVE-2019-9740 and mark it as such. See: https://bugs.python.org/issue30458 Signed-off-by: Anuj Mittal --- .../python/python3/CVE-2019-9740.patch| 155 ++ meta/recipes-devtools/python/python3_3.5.6.bb | 1 + 2 files changed, 156 insertions(+) c

[OE-core] [thud][PATCH 1/2] patch: fix CVE-2019-13636

Signed-off-by: Anuj Mittal --- .../patch/patch/CVE-2019-13636.patch | 113 ++ meta/recipes-devtools/patch/patch_2.7.6.bb| 1 + 2 files changed, 114 insertions(+) create mode 100644 meta/recipes-devtools/patch/patch/CVE-2019-13636.patch diff --git a/meta/recipes-de

[OE-core] [warrior][PATCH 2/2] python3: fix CVE-2019-9740

CVE-2019-9947 is same as CVE-2019-9740 and mark it as such. See: https://bugs.python.org/issue30458 Signed-off-by: Anuj Mittal --- .../python/python3/CVE-2019-9740.patch| 151 ++ meta/recipes-devtools/python/python3_3.7.2.bb | 1 + 2 files changed, 152 insertions(+) c

[OE-core] [PATCH] sstate: Truncate PV in sstate filenames that are too long

sstate filenames are generated by concatenating a variety of bits of package metadata. Some of these parts could be long, which could cause the filename to be longer than the 255 character maximum for ext4. So, let's try to detect this situation and truncate the PV part of the filename so that it

[OE-core] [PATCH] glib-networking: Support building with USE_NLS=no

As reported in http://lists.openembedded.org/pipermail/openembedded-core/2019-February/279344.html , glib-networking no longer configures successfully if USE_NLS="no": | po/meson.build:1:5: ERROR: Can not do gettext because xgettext is not installed. In the current absence of anything better, i

[OE-core] [warrior][PATCH 1/2] patch: fix CVE-2019-13636

Signed-off-by: Anuj Mittal --- .../patch/patch/CVE-2019-13636.patch | 113 ++ meta/recipes-devtools/patch/patch_2.7.6.bb| 1 + 2 files changed, 114 insertions(+) create mode 100644 meta/recipes-devtools/patch/patch/CVE-2019-13636.patch diff --git a/meta/recipes-de

Re: [OE-core] [RFC PATCH 3/3] classes/sstate: regenerate sstate when signing enabled

> On 27 Jul 2019, at 11:12, Richard Purdie > wrote: > > On Fri, 2019-07-26 at 11:26 +, Joshua Lock via Openembedded-core > wrote: >> This change ensures that the task signatures changes, and therefore >> sstate tasks are rerun, when signing is enabled. This has the >> positive outcome that

[OE-core] [PATCH] patch: fix CVE-2019-13636

Signed-off-by: Anuj Mittal --- .../patch/patch/CVE-2019-13636.patch | 113 ++ meta/recipes-devtools/patch/patch_2.7.6.bb| 1 + 2 files changed, 114 insertions(+) create mode 100644 meta/recipes-devtools/patch/patch/CVE-2019-13636.patch diff --git a/meta/recipes-de

Re: [OE-core] [PATCH] bind: Remove RECIPE_NO_UPDATE_REASON and follow the ESV releases

On Tue, Jul 30, 2019 at 02:20:40AM -0700, akuster808 wrote: > > > On 7/29/19 3:00 AM, Adrian Bunk wrote: > > Signed-off-by: Adrian Bunk > > --- > > meta/recipes-connectivity/bind/bind_9.11.5-P4.bb | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/meta/recipes-co

Re: [OE-core] [PATCH] bind: Remove RECIPE_NO_UPDATE_REASON and follow the ESV releases

On 7/29/19 3:00 AM, Adrian Bunk wrote: > Signed-off-by: Adrian Bunk > --- > meta/recipes-connectivity/bind/bind_9.11.5-P4.bb | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/meta/recipes-connectivity/bind/bind_9.11.5-P4.bb > b/meta/recipes-connectivity/bind/bind_9.1

Re: [OE-core] [meta-oe][PATCH v2] fwts: Update to 19.06.00

ping? On Tue, Jul 23, 2019 at 10:04 PM Ricardo Ribalda Delgado wrote: > > Update to latest release. > > Since version 18.08.00, libbsd is a dependency: > https://wiki.ubuntu.com/FirmwareTestSuite/ReleaseNotes/18.08.00 > > Signed-off-by: Ricardo Ribalda Delgado > --- > .../fwts/0001-Remove-Werro

Re: [OE-core] [PATCH] inetutils: Fix abort on invalid files

ping? On Fri, Jul 19, 2019 at 8:12 AM Ricardo Ribalda Delgado wrote: > > Hi Khem > > Indeed is due to that, but infortunately it is part of arpa/tftp.h . > So the propossed solutionI believe that it is simpler. > > https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html > > Also is what I have been s

[OE-core] ✗ patchtest: failure for qemu: fix patch authorship

== Series Details == Series: qemu: fix patch authorship Revision: 1 URL : https://patchwork.openembedded.org/series/18959/ 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 prop

Re: [OE-core] [PATCH v2] qemu: add a patch fixing the native build on newer kernels

pon., 29 lip 2019 o 09:17 Bartosz Golaszewski napisał(a): > > 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 >

[OE-core] [PATCH] qemu: fix patch authorship

From: Bartosz Golaszewski I accidentally changed the patch author when backporting this from upstream qemu. This commit restores the original author. Signed-off-by: Bartosz Golaszewski --- ...4-linux-user-fix-to-handle-variably-sized-SIOCGSTAMP-w.patch | 2 +- 1 file changed, 1 insertion(+), 1