Re: [OE-core] [PATCH v2 1/6] bitbake.conf: new variable BUILD_REPRODUCIBLE_BINARIES

I think you can define them in bitbake.conf, but then export them only where needed. On Tue, May 2, 2017 at 2:35 AM, Bystricky, Juro wrote: > I see your point. The original idea was to keep all related variables in > one place. There is > one variable (

Re: [OE-core] [PATCH v2 1/6] bitbake.conf: new variable BUILD_REPRODUCIBLE_BINARIES

I see your point. The original idea was to keep all related variables in one place. There is one variable ( BUILD_REPRODUCIBLE_BINARIES ) that I think should be global, as it should be visible by all tasks (well, a lot of tasks). The rest can be moved to more appropriate places.

Re: [OE-core] [PATCH v2 5/6] busybox.inc: improve reproducibility

On Mon, May 1, 2017 at 1:59 PM, Juro Bystricky wrote: > For reproducible builds do not generate build timestamp as part of > the version string. Maybe just do that by default? > Signed-off-by: Juro Bystricky > --- >

Re: [OE-core] [PATCH 1/1] tcf-agent: add -USR2 to stop/kill initscript

Looks like this is addressing the same problem as Jan's patch from earlier today. I think the differences are: - kill vs start-stop-daemon - Jan removed the retry loop while this patch does not On 05/01/2017 02:59 PM, brian avery wrote: The current initscript was lacking a -USR2 signal in

Re: [OE-core] [PATCH v2 1/6] bitbake.conf: new variable BUILD_REPRODUCIBLE_BINARIES

On Mon, 2017-05-01 at 13:58 -0700, Juro Bystricky wrote: > Building reproducible binaries may remove certain intentional > randomness intended for increased security. Hence, it is reasonable > to expect there will be cases where this is not desirable. > The user can select his/her preferences via

Re: [OE-core] [PATCH] cmake.bbclass: use `cmake --build` to build & install

On Mon, May 1, 2017 at 12:42 PM, Cody P Schafer wrote: > Rather than presuming `make` is the generator, use cmake's generic > `cmake --build` feature (which knows to call the appropriate generator). > > Both DESTDIR and VERBOSE still behave as intended when used as > environment

[OE-core] [PATCH 1/1] tcf-agent: add -USR2 to stop/kill initscript

The current initscript was lacking a -USR2 signal in the stop section. This resulted in /etc/init.d/tcf-agent stop; taking roughly 10 seconds then failing to kill the tcf-agent process. This patch brings us in line with how upstream stops the agent. Fixes [YOCTO #10858] Signed-off-by: brian

[OE-core] [PATCH 0/1] tcf-agent: add -USR2 to stop/kill initscript

This fixes the tcf-agent init script so /etc/init.d/tcf-agent stop works. It adds a -USR2 to the kill command like upstream does. -brian The following changes since commit 381897c64069ea43d595380a3ae913bcc79cf7e1: build-appliance-image: Update to master head revision (2017-05-01 08:56:47

[OE-core] [PATCH v2 6/6] image.bbclass: support binary reproducibility

Added a new task "reproducible_final_image_task". If binary reproducibility is desired ($BUILD_REPRODUCIBLE_BINARIES" = "1"), then recursivley modify mtimes of all files to a reproducible vale. The value is obtained via REPRODUCIBLE_TIMESTAMP_ROOTFS. This task is executed as the very last step in

[OE-core] [PATCH v2 2/6] base.bbclass: initial support for binary reproducibility

Conditionally set some environment variables in order to achieve improved binary reproducibility. Providing BUILD_REPRODUCIBLE_BINARIES is set to "1", we set the following environment variables: export PYTHONHASHSEED=0 export PERL_HASH_SEED=0 export TZ="UTC" We also export and set

[OE-core] [PATCH v2 3/6] image-prelink.bbclass: support binary reproducibility

Conditionally support binary reproducibility in built images. If BUILD_REPRODUCIBLE_BINARIES = 1 then: 1. Do not randomize library addresses 2. Set/export PRELINK_TIMESTAMP to a reproducible value. If REPRODUCIBLE_TIMESTAMP_IMAGE_PRELINK is specified, then the value will be used. Otherwise

[OE-core] [PATCH v2 5/6] busybox.inc: improve reproducibility

For reproducible builds do not generate build timestamp as part of the version string. Signed-off-by: Juro Bystricky --- meta/recipes-core/busybox/busybox.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/recipes-core/busybox/busybox.inc

[OE-core] [PATCH v2 4/6] rootfs-postcommands.bbclass: support binary reproducibility

Conditionally support binary reproducibility of rootfs images. If BUILD_REPRODUCIBLE_BINARIES = 1 then: 1. set /etc/timestamp to a reproducible value 2. set /etc/version to a reproducible value The reproducible value is taken from the variable REPRODUCIBLE_TIMESTAMP_ROOTFS. If the variable is

[OE-core] [PATCH v2 0/6] Reproducible binaries

This patch set (V2) contains several patches aimed to achieve reproducible binaries. Building reproducible binaries may remove certain intentional randomness intended for increased security. Hence, it is reasonable to expect there will be cases where this is not desirable. The user can select

[OE-core] [PATCH v2 1/6] bitbake.conf: new variable BUILD_REPRODUCIBLE_BINARIES

Building reproducible binaries may remove certain intentional randomness intended for increased security. Hence, it is reasonable to expect there will be cases where this is not desirable. The user can select his/her preferences via the variable BUILD_REPRODUCIBLE_BINARIES. The variable defaults

[OE-core] [PATCH] cmake.bbclass: use `cmake --build` to build & install

Rather than presuming `make` is the generator, use cmake's generic `cmake --build` feature (which knows to call the appropriate generator). Both DESTDIR and VERBOSE still behave as intended when used as environment variables instead of make variable-arguments. This makes it more straight forward

Re: [OE-core] [oe] [Openembedded-architecture] OpenEmbedded 2017 General Meeting

On 05/01/2017 10:07 AM, Martin Jansa wrote: > On Mon, May 01, 2017 at 01:55:11PM +0100, Richard Purdie wrote: >> On Mon, 2017-05-01 at 13:59 +0200, Martin Jansa wrote: >>> I had to change the password on the login, but then it worked for me. >> >> I think someone promoted you to an admin which is

[OE-core] [PATCH] cmake: in SDK use OE env var to set default toolchain

Patch the location in cmake where the toolchain file is loaded to use the (new) OE_CMAKE_TOOLCHAIN_FILE variable to select a default toolchain if no toolchain has been specified. The cmake alias is removed. The alternatives: - shell alias fails when cmake is called indirectly (ex: a makefile

[OE-core] [PATCH 2/2] ptest-runner: Upgrade tto to 2.1+gitAUTOINC+78afe246fb

The new 2.1 version supports creating XML results specifying the -x option. The xml output format can be see here [1]. [1] https://wiki.yoctoproject.org/wiki/QA/xUnit_XML_Template Signed-off-by: Aníbal Limón --- .../ptest-runner/{ptest-runner_2.0.2.bb =>

[OE-core] [PATCH 1/2] libxml-sax-base-perl: upgrade to 1.09

Signed-off-by: Aníbal Limón --- .../{libxml-sax-base-perl_1.08.bb => libxml-sax-base-perl_1.09.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/perl/{libxml-sax-base-perl_1.08.bb => libxml-sax-base-perl_1.09.bb} (83%)

[OE-core] [PATCH] selftest/devtool: change write to append config in virtual_kernel_modify

When uses write it creates a full new configuration in selftest.inc causing to fail populate_sdk_ext linux-yocto because the signature of the sstate changes. [YOCTO #11300] Signed-off-by: Aníbal Limón --- meta/lib/oeqa/selftest/devtool.py | 2 +- 1 file changed, 1

Re: [OE-core] [PATCH] tcf-agent: Fix daemon termination

On 04/30/2017 08:28 AM, Jan Kiszka wrote: From: Jan Kiszka The upstream init script uses SIGUSR2 to terminate that daemon because SIGTERM is ignored. As the killproc function does not support specifying a signal, switch to start-stop-daemon. Drop the retry loop because

Re: [OE-core] [oe] [Openembedded-architecture] OpenEmbedded 2017 General Meeting

On Mon, May 01, 2017 at 01:55:11PM +0100, Richard Purdie wrote: > On Mon, 2017-05-01 at 13:59 +0200, Martin Jansa wrote: > > I had to change the password on the login, but then it worked for me. > > I think someone promoted you to an admin which is why its working for > you... Yes I was after:

Re: [OE-core] [Openembedded-architecture] [oe] OpenEmbedded 2017 General Meeting

On Mon, 2017-05-01 at 13:59 +0200, Martin Jansa wrote: > I had to change the password on the login, but then it worked for me. I think someone promoted you to an admin which is why its working for you... Cheers, Richard -- ___ Openembedded-core

Re: [OE-core] [Openembedded-architecture] [oe] OpenEmbedded 2017 General Meeting

On Mon, May 1, 2017 at 1:59 PM, Martin Jansa wrote: > I had to change the password on the login, but then it worked for me. > > I've added Andrea and Andrei to the list. > Thanks! > > On Mon, May 1, 2017 at 1:46 PM, Philip Balister > wrote: > >>

Re: [OE-core] [oe] [Openembedded-architecture] OpenEmbedded 2017 General Meeting

I can't edit the page. @Martin, Could you add me (Changhyeok Bae (chabe)) in there? Thanks Changhyeok 2017-05-01 21:02 GMT+09:00 Andrei Gherzan : > On Mon, May 1, 2017 at 12:59 PM, Martin Jansa > wrote: > > I had to change the password on the login,

Re: [OE-core] [Openembedded-architecture] [oe] OpenEmbedded 2017 General Meeting

On Mon, May 1, 2017 at 12:59 PM, Martin Jansa wrote: > I had to change the password on the login, but then it worked for me. > > I've added Andrea and Andrei to the list. Thanks Martin. -- Andrei Gherzan -- ___

Re: [OE-core] [Openembedded-architecture] [oe] OpenEmbedded 2017 General Meeting

I had to change the password on the login, but then it worked for me. I've added Andrea and Andrei to the list. On Mon, May 1, 2017 at 1:46 PM, Philip Balister wrote: > On 05/01/2017 07:42 AM, Richard Purdie wrote: > > On Mon, 2017-05-01 at 13:07 +0200, Nicolas Dechesne

Re: [OE-core] [Openembedded-architecture] [oe] OpenEmbedded 2017 General Meeting

On 05/01/2017 07:42 AM, Richard Purdie wrote: > On Mon, 2017-05-01 at 13:07 +0200, Nicolas Dechesne wrote: >> well, it's the same for me. In the 'view source' page, i can see >> this: >> >> == >> You do not have permission to edit this page, for the following >> reason: >> The action you have

Re: [OE-core] [oe] OpenEmbedded 2017 General Meeting

On Mon, 2017-05-01 at 13:07 +0200, Nicolas Dechesne wrote: > well, it's the same for me. In the 'view source' page, i can see > this: > > == > You do not have permission to edit this page, for the following > reason: > The action you have requested is limited to users in the group: >

Re: [OE-core] [oe] OpenEmbedded 2017 General Meeting

On Mon, May 1, 2017 at 12:40 PM, Richard Purdie wrote: > > On Mon, 2017-05-01 at 12:27 +0200, Andrea Galbusera wrote: > > > > > > On Mon, May 1, 2017 at 12:02 PM, Andrei Gherzan > > wrote: > > > On Wed, Apr 19, 2017 at 9:48 PM, Sean Hudson

Re: [OE-core] [oe] OpenEmbedded 2017 General Meeting

On Mon, 2017-05-01 at 12:27 +0200, Andrea Galbusera wrote: > > > On Mon, May 1, 2017 at 12:02 PM, Andrei Gherzan > wrote: > > On Wed, Apr 19, 2017 at 9:48 PM, Sean Hudson > m> wrote: > > > The board would like to hold a general meeting with all

Re: [OE-core] [oe] OpenEmbedded 2017 General Meeting

On Mon, May 1, 2017 at 12:02 PM, Andrei Gherzan wrote: > On Wed, Apr 19, 2017 at 9:48 PM, Sean Hudson > wrote: > > The board would like to hold a general meeting with all members. Under > > the new by-laws of the OpenEmbedded organization, we can meet

Re: [OE-core] [oe] OpenEmbedded 2017 General Meeting

On Wed, Apr 19, 2017 at 9:48 PM, Sean Hudson wrote: > The board would like to hold a general meeting with all members. Under > the new by-laws of the OpenEmbedded organization, we can meet > electronically. This will also fulfill the requirement for an annual, > general

Re: [OE-core] [PATCH 0/2] Handle the hossttools directory when restoring from the sstate cache

On Sat, 2017-04-29 at 18:07 +, Peter Kjellerstedt wrote: > > Richard Purdie > > Sent: den 29 april 2017 10:53 > > On Fri, 2017-04-28 at 17:01 +0200, Peter Kjellerstedt wrote: > > > > > > After the introduction of copying host tools to the build > > > directory > > > and cleaning out $PATH, we