Re: [OE-core] [PATCH v4] python3{,-native}: update to 3.7.0

FWIW, the dnf upgrade appears to be trivial (I did not rebase python3 3.7.0 patches, but it probably won’t change much): http://git.openembedded.org/openembedded-core-contrib/commit/?h=timo/python37=94d4bba43097ec22f120f4327e5d13a52c1724fd NOTE: I used a hammer and overwrote Alex Kanavin’s

[OE-core] [sumo] [PATCH v2 2/2] libcroco: CVE-2017-7961

* CVE-2017-7961 The cr_tknzr_parse_rgb function in cr-tknzr.c in libcroco has an "outside the range of representable values of type long" undefined behavior issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a

[OE-core] [sumo] [PATCH v2 1/2] libice: CVE-2017-2626

* CVE-2017-2626 It was discovered that libICE before 1.0.9-8 used a weak entropy to generate keys. A local attacker could potentially use this flaw for session hijacking using the information available from the process list. Affects libice < 1.0.9-8 CVE: CVE-2017-2626 Ref:

[OE-core] [PATCH] [PATCH] adwaita-icon-theme:upgrade to 3.30.0

Upgrade adwaita-icon-theme from 3.28.0 to 3.30.0 Signed-off-by: Hong Liu --- .../{adwaita-icon-theme_3.28.0.bb => adwaita-icon-theme_3.30.0.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-gnome/gnome/{adwaita-icon-theme_3.28.0.bb =>

Re: [OE-core] [sumo] [PATCH v1 2/2] libcroco: CVE-2017-7961

On 09/25/2018 10:18 AM, Sinan Kaya wrote: > * CVE-2017-7961 > The cr_tknzr_parse_rgb function in cr-tknzr.c in libcroco has an > "outside the range of representable values of type long" undefined > behavior issue, which might allow remote attackers to cause a denial > of service (application

Re: [OE-core] [sumo] [PATCH v1 1/2] libice: CVE-2017-2626

On 09/25/2018 10:18 AM, Sinan Kaya wrote: > * CVE-2017-2626 > It was discovered that libICE before 1.0.9-8 used a weak entropy to > generate keys. A local attacker could potentially use this flaw for > session hijacking using the information available from the process list. > > Affects libice <

[OE-core] [PATCH] boost: build context and coroutine for arm

When cross-compiling for arm architecture, bjam fails to properly detect the abi, which causes a failed conditional to omit the assembly code that supports the platform. Signed-off-by: Vernon Mauery --- meta/recipes-support/boost/boost.inc | 4 1 file changed, 4 insertions(+) diff --git

Re: [OE-core] [PATCH RFC] insane.bbclass: add buildpaths_cmake and buildpaths_pkgconfig checks

On Tue, Sep 25, 2018 at 07:29:22PM +0100, richard.pur...@linuxfoundation.org wrote: > On Tue, 2018-09-25 at 17:11 +, mikko.rap...@bmw.de wrote: > > On Tue, Sep 25, 2018 at 04:19:39PM +0100, richard.purdie@linuxfoundat > > ion.org wrote: > > > On Tue, 2018-09-25 at 11:21 +,

Re: [OE-core] [PATCH RFC] insane.bbclass: add buildpaths_cmake and buildpaths_pkgconfig checks

On Tue, 2018-09-25 at 17:11 +, mikko.rap...@bmw.de wrote: > On Tue, Sep 25, 2018 at 04:19:39PM +0100, richard.purdie@linuxfoundat > ion.org wrote: > > On Tue, 2018-09-25 at 11:21 +, mikko.rap...@bmw.de wrote: > > > On Tue, Sep 25, 2018 at 12:08:24PM +0100, Richard Purdie wrote: > > > > I

[OE-core] [sumo] [PATCH v1 2/2] libcroco: CVE-2017-7961

* CVE-2017-7961 The cr_tknzr_parse_rgb function in cr-tknzr.c in libcroco has an "outside the range of representable values of type long" undefined behavior issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a

[OE-core] [sumo] [PATCH v1 1/2] libice: CVE-2017-2626

* CVE-2017-2626 It was discovered that libICE before 1.0.9-8 used a weak entropy to generate keys. A local attacker could potentially use this flaw for session hijacking using the information available from the process list. Affects libice < 1.0.9-8 CVE: CVE-2017-2626 Ref:

Re: [OE-core] [PATCH RFC] insane.bbclass: add buildpaths_cmake and buildpaths_pkgconfig checks

On Tue, Sep 25, 2018 at 04:19:39PM +0100, richard.pur...@linuxfoundation.org wrote: > On Tue, 2018-09-25 at 11:21 +, mikko.rap...@bmw.de wrote: > > On Tue, Sep 25, 2018 at 12:08:24PM +0100, Richard Purdie wrote: > > > I suspect we need to talk to cmake upstream about fixing this > > >

Re: [OE-core] [PATCH] openssh: resolve install conflict with openssh-sftp-server-dev

On Mon, 2018-09-24 at 15:26 +0200, Urs Fässler wrote: > On Wed, 2018-09-19 at 09:01 -0700, Richard Purdie wrote: > > On Wed, 2018-09-19 at 17:11 +0200, Andreas Oberritter wrote: > > > On Wed, 19 Sep 2018 08:41:35 +0200 > > > Urs Fässler wrote: > > > > > > > Image generation fails with the

Re: [OE-core] python-sqlite3 packaging

Hey Jeroen, On 9/24/2018 12:22 PM, Jeroen Hofstee wrote: Hello, Not sure where to report this, so trying here. It seems the /usr/lib/python2.7/sqlite3 ends up in the python-misc and not in python-sqlite3. This causes statements like: import sqlite3 To error with ImportError: No module named

[OE-core] error : QA Issue: libpqxx.pc failed sanity test (tmpdir) in path

hi, i would like to build libpqxx (https://github.com/jtv/libpqxx ) for my karo target(TX6S-8035). i use karo BSP ( https://github.com/karo-electronics/meta-karo

[OE-core] ✗ patchtest: failure for meson: respect target/native flag distinction in G-I and gtk-doc

== Series Details == Series: meson: respect target/native flag distinction in G-I and gtk-doc Revision: 1 URL : https://patchwork.openembedded.org/series/14228/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response.

Re: [OE-core] SDK and out of tree modules

On Tue, 2018-09-25 at 16:51 +0200, Andrej Valek wrote: > I have seen, that You have been supporting someone with the similar > problem. > So, I would like to ask you as question about current status of > failing task for kernel-devsrc recipe. I have found similar thread > about the same issue, but

Re: [OE-core] [PATCH RFC] insane.bbclass: add buildpaths_cmake and buildpaths_pkgconfig checks

On Tue, 2018-09-25 at 11:21 +, mikko.rap...@bmw.de wrote: > On Tue, Sep 25, 2018 at 12:08:24PM +0100, Richard Purdie wrote: > > I suspect we need to talk to cmake upstream about fixing this > > properly > > but adding something in the class may be an option until a better > > upstream solution

[OE-core] [PATCH V2] meson: respect target/native flag distinction in G-I and gtk-doc

Remove the previous attempt at this from 0001-gtkdoc-fix-issues-that-arise-when-cross-compiling.patch as it wasn't quite right, and the rest of the patch is adding the currently not upstreamable runner option. Add two new patches to fix both gobject-introspection and gtk-doc using native flags

[OE-core] Yocto Project Status WW39’18

Current Dev Position: YP 2.6 M4. Next Deadline: YP 2.6 M4 Build Target is Oct. 1, 2018 SWAT Team Rotation: · SWAT lead is currently: Chen · SWAT team rotation: Chen -> Armin on Sept. 28, 2018 · SWAT team rotation: Armin -> Paul on Oct. 5, 2018 ·

Re: [OE-core] [PATCH v4] python3{,-native}: update to 3.7.0

Hello Jens, It literally seems that you didn't even read the email, I am not asking whether or not it builds correctly for you, it clearly says that the fact that something builds correctly, doesn't necessarily means it runs properly, and it also says thanks because it contains some of the

[OE-core] SDK and out of tree modules

Hi all, I have seen, that You have been supporting someone with the similar problem. So, I would like to ask you as question about current status of failing task for kernel-devsrc recipe. I have found similar thread about the same issue, but without final solution

[OE-core] [master][sumo][PATCH] rootfs.py: Install -src packages when PACKAGE_DEBUG_SPLIT_STYLE is "debug-with-srcpkg"

When the source packages are created, they need to be included in the debug image created when IMAGE_GEN_DEBUGFS = "1" for it to be usable for debugging. [YOCTO #12930] Signed-off-by: Joshua Watt --- meta/lib/oe/rootfs.py | 4 1 file changed, 4 insertions(+) diff --git

[OE-core] [PATCH] linux-yocto/4.14: fix beaglebone configuration warnings

Backporting the following fixes from 4.18 to 4.14 to remove beaglebone configuration warnings: 1fb0b0379fb5 beaglebone: Clean up the cfg file 4176e7ded8e1 beaglebone: Drop the needless unsetting of the kernel options 65c209da574d beaglebone: Drop the obsolete kernel options Signed-off-by:

Re: [OE-core] [PATCH] openssh: resolve install conflict with openssh-sftp-server-dev

On Tue, 2018-09-25 at 15:05 +0200, Urs Fässler wrote: > On Mon, 2018-09-24 at 15:26 +0200, Urs Fässler wrote: > > On Wed, 2018-09-19 at 09:01 -0700, Richard Purdie wrote: > > > On Wed, 2018-09-19 at 17:11 +0200, Andreas Oberritter wrote: > > > > On Wed, 19 Sep 2018 08:41:35 +0200 > > > > Urs

[OE-core] [PATCH V2] siteinfo: generalise siteinfo

Add a function siteinfo_data_for_machine to look up the data for any arch/os pair, not just HOST_ARCH-HOST_OS. Signed-off-by: Ross Burton --- meta/classes/siteinfo.bbclass | 17 + 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/meta/classes/siteinfo.bbclass

[OE-core] [PATCH 6/6] meson: make native-specific patches native-specific

These two patches are only relevant for builds inside OpenEmbedded, so make them native-specific. Signed-off-by: Ross Burton --- meta/recipes-devtools/meson/meson.inc | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/meta/recipes-devtools/meson/meson.inc

[OE-core] [PATCH 4/6] meson: stop Meson using target CFLAGS in native builds

With the goal of autoconf-compatibility Meson respects $CFLAGS et al in builds. In cross-compiled build the cross file is the one true source of flags and the environment isn't used, but in a native build the environment will still be respected. As this can lead to target flags being used in the

[OE-core] [PATCH 5/6] meson: respect target/native flag distinction in G-I and gtk-doc

Remove the previous attempt at this from 0001-gtkdoc-fix-issues-that-arise-when-cross-compiling.patch as it wasn't quite right, and the rest of the patch is adding the currently not upstreamable runner option. Add two new patches to fix both gobject-introspection and gtk-doc using native flags

[OE-core] [PATCH 2/6] meson: squash the architecture warning patches together

Instead of one patch to change a warning into an exception and another to change the message, squash the patches together as neither of the are acceptable upstream. Signed-off-by: Ross Burton --- meta/recipes-devtools/meson/meson.inc | 1 -

[OE-core] [PATCH 3/6] meson: pass correct endian in the cross file

Meson doesn't care for the value of the endian field, but packages may want to use it and Meson master now validates the value. Use siteinfo to obtain the endianism and write the correct value. Signed-off-by: Ross Burton --- meta/classes/meson.bbclass | 20 +--- 1 file changed,

[OE-core] [PATCH 1/6] siteinfo: generalise siteinfo

Signed-off-by: Ross Burton --- meta/classes/siteinfo.bbclass | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/meta/classes/siteinfo.bbclass b/meta/classes/siteinfo.bbclass index 4698e6e474d..e80835605fb 100644 --- a/meta/classes/siteinfo.bbclass +++

Re: [OE-core] [oe-commits] [openembedded-core] 02/45: fribidi: use Meson instead of autotools

Can you try again with poky-contrib:ross/meson? Pulling that thread turned out to be more complex than expected... Ross On Mon, 24 Sep 2018 at 21:18, Khem Raj wrote: > > Ross > > I am seeing some extra fails which could be related to your proposed changes > >

[OE-core] ✗ patchtest: failure for utils: lockfile: Fix infinite loop

== Series Details == Series: utils: lockfile: Fix infinite loop Revision: 1 URL : https://patchwork.openembedded.org/series/14218/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on

[OE-core] [PATCH v2] rootfs: always update the opkg index

The previous logic assumed that if $BUILD_IMAGES_FROM_FEEDS=1 then a complete set of ipk feeds from which to build the image is already present under $IPK_FEED_URIS at do_rootfs runtime. $IPK_FEED_URIS usually contains "file://${DEPLOY_DIR_IPK}" which renders the above assumption bad because some

[OE-core] [bitbake-devel][PATCH] utils: lockfile: Fix infinite loop

A nasty corner case leads to a hang when utils.lockfile is called from oe-core's package-manager:deploy_dir_lock (in turn called from rootfs:_create further up the call stack) with "name" owned by root and the user running bitbake has no write access. Because this code runs under pseudo, the UID

[OE-core] ARC: machine dictionary - ARCompact vs ARCv2

Hello, While upstreaming ARC bits in OE core I faced one interesting challenge. As of today we have 2 binary-incompatible 32-bit ISAs (Instruction Set Arch): 1. ARCompact (AKA ARCv1) and 2. ARCv2 In Binutils they have 2 separate machine numbers: EM_ARC_COMPACT=93 for ARCompact, see [1] and

Re: [OE-core] [PATCH RFC] insane.bbclass: add buildpaths_cmake and buildpaths_pkgconfig checks

On Tue, Sep 25, 2018 at 12:08:24PM +0100, Richard Purdie wrote: > On Tue, 2018-09-25 at 10:44 +, mikko.rap...@bmw.de wrote: > > On Tue, Sep 25, 2018 at 01:28:13PM +0300, Mikko Rapeli wrote: > > > And enable them by default as ERROR_QA. Reason is that > > > absolute build directory paths in

Re: [OE-core] [PATCH RFC] insane.bbclass: add buildpaths_cmake and buildpaths_pkgconfig checks

On Tue, 2018-09-25 at 10:44 +, mikko.rap...@bmw.de wrote: > On Tue, Sep 25, 2018 at 01:28:13PM +0300, Mikko Rapeli wrote: > > And enable them by default as ERROR_QA. Reason is that > > absolute build directory paths in CMake .cmake modules > > and in pkg-config .pc files cause recipe builds to

Re: [OE-core] [PATCH RFC] insane.bbclass: add buildpaths_cmake and buildpaths_pkgconfig checks

On Tue, Sep 25, 2018 at 01:28:13PM +0300, Mikko Rapeli wrote: > And enable them by default as ERROR_QA. Reason is that > absolute build directory paths in CMake .cmake modules > and in pkg-config .pc files cause recipe builds to escape > their recipe specific sysroots and triggers hard to debug >

[OE-core] [PATCH RFC] insane.bbclass: add buildpaths_cmake and buildpaths_pkgconfig checks

And enable them by default as ERROR_QA. Reason is that absolute build directory paths in CMake .cmake modules and in pkg-config .pc files cause recipe builds to escape their recipe specific sysroots and triggers hard to debug and timing sensitive build failures. It's better to fail early. A

Re: [OE-core] [PATCH] rootfs: always update the opkg index

On Tue, 25 Sep 2018, Ioan-Adrian Ratiu wrote: > On Mon, 24 Sep 2018, richard.pur...@linuxfoundation.org wrote: >> On Mon, 2018-09-24 at 18:00 +0300, Ioan-Adrian Ratiu wrote: >>> > With master, a copy of the feed is constructed under WORKDIR which >>> > is >>> > then indexed since other image

Re: [OE-core] [PATCH] rootfs: always update the opkg index

On Mon, 24 Sep 2018, richard.pur...@linuxfoundation.org wrote: > On Mon, 2018-09-24 at 18:00 +0300, Ioan-Adrian Ratiu wrote: >> > With master, a copy of the feed is constructed under WORKDIR which >> > is >> > then indexed since other image generation or package writes could >> > occur >> > and

Re: [OE-core] [PATCH 1/3] acl: Make it compatible with externalsrc

> -Original Message- > From: openembedded-core-boun...@lists.openembedded.org core-boun...@lists.openembedded.org> On Behalf Of Richard Purdie > Sent: den 25 september 2018 10:13 > To: Peter Kjellerstedt ; openembedded- > c...@lists.openembedded.org > Subject: Re: [OE-core] [PATCH 1/3]

Re: [OE-core] [PATCH 1/3] acl: Make it compatible with externalsrc

On Mon, 2018-09-24 at 21:03 +0200, Peter Kjellerstedt wrote: > Make the subdir fetch path for configure.ac relative. This avoids the > following error after having done `devtool modify acl`: > > ERROR: acl-2.2.52-r0 do_unpack: Unpack failure for URL: >

[OE-core] [PATCH 1/1] perl: fix race issues for MakeMaker

Fixed a race issue when compile libhtml-parser-perl and others who use MakeMaker: [snip] chmod 755 blib/arch/auto/HTML/Parser/Parser.so chmod 644 "Parser.bs" [snip] The rule INST_DYNAMIC removes '.bs' file which are generated by BOOTSTRAP, but the have no dependencies, so there is a race issue:

[OE-core] [PATCH 0/1] perl: fix race issues for MakeMaker

The following changes since commit e3f5ceec690379d64bd38330111a32f6c8fc6353: build-appliance-image: Update to master head revision (2018-09-24 12:31:28 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/perl

[OE-core] [PATCH V2 1/1] runqemu: fix handling of SIGTERM and the problem of line wrapping

The current handling of SIGTERM is incorrect as the process pid returned by Popen call with shell setting to True is actualy the shell instead of the qemu process. So use shlex to split cmd so that we can avoid using shell=True. This ensures the child process is the actual qemu process. Also, as

[OE-core] [PATCH V2 0/1] runqemu: fix handling of SIGTERM and the problem of line wrapping

Changes in V2: * Change to get rid of shell=True The following changes since commit c6edf2f8bc5778b267e3a7f4e8875d22f359fb8d: build-appliance-image: Update to master head revision (2018-09-24 12:31:33 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib