Re: [OE-core] openssl: OpenSSL 1.1.x update

Hi Raymond, On Thu, 06 Oct 2016 02:11:59 Tan, Raymond wrote: > Greetings, I would like to know if there is any plan / schedule to upgrade > to openssl 1.1.0 into OE-core? I am not aware of any discussion about this (and my answer shouldn't be considered authoritative), however it does look like

[OE-core] [PATCH 0/1 V2] yocto-uninative: allow URL override

This changes the UNINATIVE_URL = to a UNINATIVE_URL ?= so we can override it in the local.conf file. This matches the form of the CHECKSUMS and is useful in the case that you have a special uninative or can't reach downloads.yoctoproject.org. -bavery p.s. The V2 is because my script cut the

[OE-core] [PATCH 1/1 V2] uninative: users can override download site

The default download site for the uninative tarball is http://downloads.yoctoproject.org/releases/uninative/. There are scenarios in which the user may need to force the download to be somewhere else. This patch allows the UNINATIVE_URL to be set in the local.conf. Signed-off-by: bavery

Re: [OE-core] [PATCH 22/22] cmake: Use bb.fatal() instead of raising FuncFailed

On Thu, Oct 6, 2016 at 12:15 AM, Richard Purdie wrote: > On Wed, 2016-10-05 at 22:26 +0200, Ulf Magnusson wrote: >> On Sat, Oct 1, 2016 at 4:47 AM, Ulf Magnusson >> wrote: >> > >> > This sets a good example and avoids unnecessarily

[OE-core] [PATCH 1/1] uninative: users can override download site

The default download site for the uninative tarball is http://downloads.yoctoproject.org/releases/uninative/. There are scenarios in which the user may need to force the download to be somewhere else. This patch allows the UNINATIVE_URL to be set in the local.conf. Signed-off-by: bavery

[OE-core] [PATCH 0/1] yocto-uninative: allow URL override

This changes the UNINATIVE_URL = to a UNINATIVE_URL ?= so we can override it in the local.conf file. This matches the form of the CHECKSUMS and is useful in the case that you have a special uninative or can't reach downloads.yoctoproject.org. -bavery The following changes since commit

[OE-core] openssl: OpenSSL 1.1.x update

Greetings, I would like to know if there is any plan / schedule to upgrade to openssl 1.1.0 into OE-core? Thanks! Raymond Tan -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

Re: [OE-core] openssl: OpenSSL 1.1.x update

On Wed, Oct 5, 2016 at 7:33 PM, Mark Hatle wrote: > On 10/5/16 9:11 PM, Tan, Raymond wrote: >> Greetings, I would like to know if there is any plan / schedule to upgrade >> to openssl 1.1.0 into OE-core? > > Currently 1.0.2 is the LTS version of OpenSSL. 1.1.0 is not

Re: [OE-core] [PATCH 22/22] cmake: Use bb.fatal() instead of raising FuncFailed

On Wed, 2016-10-05 at 22:26 +0200, Ulf Magnusson wrote: > On Sat, Oct 1, 2016 at 4:47 AM, Ulf Magnusson > wrote: > > > > This sets a good example and avoids unnecessarily contributing to > > perceived complexity and cargo culting. > > > > Motivating quote below: > > > > <

Re: [OE-core] [PATCH] pango: add libpcre to DEPENDS

Hi again On Fri, 09 Sep 2016, "Burton, Ross" wrote: > On 9 September 2016 at 10:32, Ioan-Adrian Ratiu wrote: > >> I cleared the build directory and sstate cache, started with a clean >> rebuild and I can't reproduce the error anymore. gen-all-unicode

Re: [OE-core] [PATCH] Revert "attr: Added ncurses to depends"

On 2016-10-04 05:41 AM, Ross Burton wrote: There doesn't appear to be any reason to keep this dependency on ncurses in attr, so remove it. This reverts commit 7c474dc3d65bb3f71b375d36d81959cb405be80a. Might be a a poky commit id? The right one is: commit

Re: [OE-core] openssl: OpenSSL 1.1.x update

On 10/5/16 9:11 PM, Tan, Raymond wrote: > Greetings, I would like to know if there is any plan / schedule to upgrade to > openssl 1.1.0 into OE-core? Currently 1.0.2 is the LTS version of OpenSSL. 1.1.0 is not scheduled to be LTS. For the upcoming release (soon), I would NOT expect 1.1.0 to

Re: [OE-core] [PATCH v2] scripts: add new script 'native'

On Tue, 04 Oct 2016 12:22:56 Randy MacLeod wrote: > On 2016-10-02 03:37 PM, Paul Eggleton wrote: > >> "native" might be a bit too generic... > >> > >> > >> could I suggest oe_native-run or bitbake-native ? > >> > >> > >> > >> something that says it's yocto-galaxy specific and can be > >> > >>

Re: [OE-core] [PATCH v2] scripts: add new script 'native'

On Thu, Oct 6, 2016 at 5:02 AM, Paul Eggleton wrote: > On Tue, 04 Oct 2016 12:22:56 Randy MacLeod wrote: >> On 2016-10-02 03:37 PM, Paul Eggleton wrote: >> >> "native" might be a bit too generic... >> >> >> >> > >> could I suggest oe_native-run or bitbake-native ?

Re: [OE-core] [PATCH V3] add function to check for git config user

On 10/03, Stephano Cetola wrote: > Chnages since V2: > moved functionality from sanity to utils > utilize existing name / email variables > > Stephano Cetola (1): > utils.bbclass: add function to check for git config user > > meta/classes/buildhistory.bbclass | 15 ++- >

[OE-core] [PATCH] scripts: Rename 'native' to 'oe-run-native'

Makes it a bit more descriptive and potentially more discoverable. Most people seemed to prefer an oe- prefix, so let's go with that. Signed-off-by: Ulf Magnusson --- scripts/{native => oe-run-native} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename

Re: [OE-core] [PATCH v2] scripts: add new script 'native'

On Thu, 06 Oct 2016 05:20:20 Ulf Magnusson wrote: > On Thu, Oct 6, 2016 at 5:02 AM, Paul Eggleton > > wrote: > > On Tue, 04 Oct 2016 12:22:56 Randy MacLeod wrote: > >> On 2016-10-02 03:37 PM, Paul Eggleton wrote: > >> >> "native" might be a bit too generic... > >>

[OE-core] [PATCH] pigz: Update SRC_URI

Upstream have released a new tarball and removed the old one. Revert to the Yocto Project source mirror instead, preserving the upstream version  check. Signed-off-by: Richard Purdie diff --git a/meta/recipes-extended/pigz/pigz_2.3.3.bb

Re: [OE-core] State of bitbake world 2016-10-04

> === qemuarm (1) === > * > meta-openembedded/meta-filesystems/recipes-support/physfs/physfs_git.bb:do_populate_lic ^ This one was fixed during run - correct? > > === qemux86 (2) === > * > meta-browser/recipes-browser/chromium/chromium_52.0.2743.76.bb:do_compile > * >

[OE-core] [PATCH v2] oeqa.buildperf: measure apparent size instead of real disk usage

This change aligns disk usage measurements of the eSDK test with the old build-perf-test.sh script. And thus, also makes the results between the old and the new script comparable. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/buildperf/base.py | 9

[OE-core] [PATCH] update-rc.d.bbclass: check that init script exists before running it

Check that the init script that is going to be called in the prerm() script really exists. There might be a packaging bug or the script might've been removed already earlier in prerm(). [YOCTO #10299] Signed-off-by: Markus Lehtonen ---

[OE-core] State of bitbake world 2016-10-04

== Number of issues - stats == {| class='wikitable' !|Date !!colspan='3'|Failed tasks !!colspan='6'|Failed depencencies!!|Signatures !!colspan='12'|QA !!Comment |- || ||qemuarm ||qemux86 ||qemux86_64

Re: [OE-core] [PATCH] pango: add libpcre to DEPENDS

On 5 October 2016 at 12:59, Ioan-Adrian Ratiu wrote: > I think libpcre_%.bbappend in meta-selinux is just missing the following > line: > > ln -sf ${relpath}/${realsofile} ${D}${libdir}/libpcre.so.1 > > after creating this symlink the build works without problems (previously

[OE-core] [fido][PATCH] gnupg: fix find-version for beta checking

From: Wenzong Fan find-version always assumes that gnupg is beta if autogen.sh is run out of git-repo. This doesn't work for users whom just take release tarball and re-run autoconf in their local build dir. This fixes runtime issue: $gpg --list-sigs gpg: NOTE:

[OE-core] [jethro][PATCH] gnupg: fix find-version for beta checking

From: Wenzong Fan find-version always assumes that gnupg is beta if autogen.sh is run out of git-repo. This doesn't work for users whom just take release tarball and re-run autoconf in their local build dir. This fixes runtime issue: $gpg --list-sigs gpg: NOTE:

Re: [OE-core] State of bitbake world 2016-10-04

On Wed, Oct 05, 2016 at 03:29:25PM +0200, Andreas Müller wrote: > > === qemuarm (1) === > > * > > meta-openembedded/meta-filesystems/recipes-support/physfs/physfs_git.bb:do_populate_lic > ^ This one was fixed during run - correct? > > > > === qemux86 (2) === > > * > >

[OE-core] [PATCH V4] devtool: modify command fails to ignore source files

With recent changes to recipeutils, the list of local files returned by get_recipe_local_files could possibly include source files. This only happens when the recipe contains a SRC_URI using subdir= to put files in the source tree. These files should be ignored when populating the list of local

[OE-core] [PATCH V4] devtool: modify command fails to ignore source

changed since V3: added a check for the case where $S = $WORKDIR fixes [YOCTO #10379] Stephano Cetola (1): devtool: modify command fails to ignore source files scripts/lib/devtool/standard.py | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) -- 2.10.0 --

Re: [OE-core] [bitbake-devel] Not building python socketmodule.c with openssl 1.0.2h

On 10/5/16 8:57 AM, Jeff Hatch wrote: > I am seeing an issue where we upgraded the openssl bitbake recipes to build > and > install openssl 1.0.2h in a higher layer than the base openembedded layer > which > was building openssl 1.0.1m. After this was done, the build of python 2.7.3 > stopped

[OE-core] [PATCHv2 2/4] package_manager.py: Allow multiple regexps in PACKAGE_EXCLUDE_COMPLEMENTARY

The PACKAGE_EXCLUDE_COMPLEMENTARY variable can currently only contain one regular expression. This makes it hard to add to it from different configuration files and recipes. Allowing it to contain multiple, whitespace separated regular expressions should be backwards compatible as it is assumed

[OE-core] [PATCH 2/2] package_manager.py: Allow multiple regexps in PACKAGE_EXCLUDE_COMPLEMENTARY

The PACKAGE_EXCLUDE_COMPLEMENTARY variable can currently only contain one regular expression. This makes it hard to add to it from different configuration files and recipes. Allowing it to contain multiple, whitespace separated regular expressions should be backwards compatible as it is assumed

[OE-core] [PATCH 1/2] package_manager.py: Allow a leading - in PACKAGE_EXCLUDE_COMPLEMENTARY

This allows a regular expression specified in PACKAGE_EXCLUDE_COMPLEMENTARY to have a leading dash. Without this, the dash was treated by oe-pkgdata-util as the beginning of a command line argument. E.g., if PACKAGE_EXCLUDE_COMPLEMENTARY = "-foo$", it resulted in an error like: ERROR: -1.0-r0

[OE-core] [PATCHv2 1/4] package_manager.py: Allow a leading - in PACKAGE_EXCLUDE_COMPLEMENTARY

This allows a regular expression specified in PACKAGE_EXCLUDE_COMPLEMENTARY to have a leading dash. Without this, the dash was treated by oe-pkgdata-util as the beginning of a command line argument. E.g., if PACKAGE_EXCLUDE_COMPLEMENTARY = "-foo$", it resulted in an error like: ERROR: -1.0-r0

[OE-core] [PATCHv2 3/4] image.bbclass: Make do_rootfs depend on PACKAGE_EXCLUDE_COMPLEMENTARY

Signed-off-by: Peter Kjellerstedt --- meta/classes/image.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass index 4d5a401..915500a 100644 --- a/meta/classes/image.bbclass +++

[OE-core] [PATCHv2 0/4] Fixes for PACKAGE_EXCLUDE_COMPLEMENTARY

The first patch fix a problem with PACKAGE_EXCLUDE_COMPLEMENTARY where it could not contain a regular expression that began with a dash, and the second makes it possible to specify multiple, whitespace separated regular expressions in PACKAGE_EXCLUDE_COMPLEMENTARY. PATCH v2: Added two more

[OE-core] [PATCHv2 4/4] populate_sdk_base.bbclass: Make do_populate_sdk depend on PACKAGE_EXCLUDE_COMPLEMENTARY

Signed-off-by: Peter Kjellerstedt --- meta/classes/populate_sdk_base.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/populate_sdk_base.bbclass b/meta/classes/populate_sdk_base.bbclass index a23775e..4462b52 100644 ---

Re: [OE-core] [PATCH] pango: add libpcre to DEPENDS

On Wed, 05 Oct 2016, "Burton, Ross" wrote: > On 5 October 2016 at 12:59, Ioan-Adrian Ratiu wrote: > >> I think libpcre_%.bbappend in meta-selinux is just missing the following >> line: >> >> ln -sf ${relpath}/${realsofile} ${D}${libdir}/libpcre.so.1 >>

Re: [OE-core] [PATCH] update-rc.d.bbclass: check that init script exists before running it

Hello Markus, On 05.10.2016 16:11, Markus Lehtonen wrote: > Check that the init script that is going to be called in the prerm() > script really exists. There might be a packaging bug or the script > might've been removed already earlier in prerm(). isn't it called prerm in the first place

[OE-core] [PATCH 0/2] Fixes for PACKAGE_EXCLUDE_COMPLEMENTARY

The first patch fix a problem with PACKAGE_EXCLUDE_COMPLEMENTARY where it could not contain a regular expression that began with a dash, and the second makes it possible to specify multiple, whitespace separated regular expressions in PACKAGE_EXCLUDE_COMPLEMENTARY. //Peter The following changes

[OE-core] [PATCHv2] icecc.bbclass: replace os.popen with subprocess.check_output

* otherwise there is a lot of warnings about missing close on file descriptor Signed-off-by: Martin Jansa --- meta/classes/icecc.bbclass | 14 ++ 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/meta/classes/icecc.bbclass

Re: [OE-core] [PATCH 22/22] cmake: Use bb.fatal() instead of raising FuncFailed

On Sat, Oct 1, 2016 at 4:47 AM, Ulf Magnusson wrote: > This sets a good example and avoids unnecessarily contributing to > perceived complexity and cargo culting. > > Motivating quote below: > > < kergoth> the *original* intent was for the function/task to error via >