Re: [OE-core] Yocto Project Status WW47’17

On 11/21/2017 07:09 PM, Richard Purdie wrote: On Mon, 2017-11-20 at 20:22 -0500, Randy MacLeod wrote: On 2017-11-20 10:36 AM, Jolley, Stephen K wrote: Current Dev Position: YP 2.5 Planning and M1 development Next Deadline: YP 2.5 M1 cut off of 12/4/17 SWAT team rotation: Juro -> Paul on

Re: [OE-core] backfill mechanism

> -Original Message- > From: openembedded-core-boun...@lists.openembedded.org > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > Slater, Joseph > Sent: Wednesday, November 22, 2017 03:11 > To: Andre McCurdy > Cc: openembedded-core@lists.openembedded.org > Subject:

Re: [OE-core] [PATCH 1/3] systemd: fix formatting IDE storage does not trigger "change" uevents

On 2017年11月21日 19:31, Burton, Ross wrote: On 21 November 2017 at 07:00, Hongxu Jia > wrote: 1. Tweak kernel-cache to remove CONFIG_IDE for all available bsp.     It require necessary test to prove it is safe to remove it.   

[OE-core] [PATCH v3 1/2] runqemu: Allow the user to override the Kernel option

Update the runqemu script to allow the user to specify a Kernel to boot when calling runqemu. Signed-off-by: Alistair Francis Cc: Ben Levinsky --- scripts/runqemu | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

Re: [OE-core] [PATCH] glibc: malloc: Add missing arena lock in malloc_info

On Tue, Nov 21, 2017 at 3:05 PM, Burton, Ross wrote: > What glibc release is this in? We've an upgrade patch pending that bumps it > to 77f921dac17c5fa99bd9e926d926c327982895f7. It's currently in the glibc master branch only (ie hasn't been backported to the 2.26 release

Re: [OE-core] [PATCH v2 2/2] runqemu: Allow the user to override the device tree option

On Tue, Nov 14, 2017 at 4:32 AM, Burton, Ross wrote: > Doesn't actually work if DEVICE_TREE is not set but QB_DTB is: > > Traceback (most recent call last): > File > "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/scripts/runqemu", > line 1277, in

[OE-core] [PATCH] bin_package: fail if ${S} doesn't actually contain anything

If the user is trying to use bin_package but the SRC_URI hasn't extracted anything into ${S}, which is easily done when writing a recipe by hand, instead of silently shippping an empty package abort the build. Signed-off-by: Ross Burton ---

Re: [OE-core] [PATCH] glibc: malloc: Add missing arena lock in malloc_info

What glibc release is this in? We've an upgrade patch pending that bumps it to 77f921dac17c5fa99bd9e926d926c327982895f7. Ross On 20 November 2017 at 07:44, Zhixiong Chi wrote: > There are the multiple process crashes seen while using malloc_info. > Obtain the size

Re: [OE-core] [PATCH v2 2/2] install*.sh: add short sleep after parted commands

Much better! Sau! On Tue, 2017-11-21 at 15:02 -0800, California Sullivan wrote: > I wasn't able to install to my Optane SSD due to the following error: > > Formatting /dev/nvme0n1p1 to vfat... > mkfs.fat 4.1 (2017-01-24) > mkfs.vfat: unable to open /dev/nvme0n1p1: No such file or directory >

[OE-core] [PATCH v2 2/2] install*.sh: add short sleep after parted commands

I wasn't able to install to my Optane SSD due to the following error: Formatting /dev/nvme0n1p1 to vfat... mkfs.fat 4.1 (2017-01-24) mkfs.vfat: unable to open /dev/nvme0n1p1: No such file or directory Target install-efi failed A couple lines later I see: [10.265401] nvme0n1: p1 p2 p3 Then

Re: [OE-core] [PATCH 2/2] install*.sh: add short sleep after parted commands

On Tue, 2017-11-21 at 13:47 -0800, California Sullivan wrote: > I wasn't able to install to my Optane SSD due to the following error: > > Formatting /dev/nvme0n1p1 to vfat... > mkfs.fat 4.1 (2017-01-24) > mkfs.vfat: unable to open /dev/nvme0n1p1: No such file or directory > Target install-efi

Re: [OE-core] [morty][PATCH v3 2/2] glibc: Fix CVE-2017-1000366

On Tue, Nov 21, 2017 at 12:01 PM, George McCollister wrote: > Add backported patches from the upstream release/2.24/master branch to > fix CVE-2017-1000366. Also add a backported patch that resolves SSE > related build problems introduced by these patches. > these

[OE-core] [PATCH 1/2] init-install: fix grub-install command

The grub_version variable was calling 'grub-install -v' (verbose) instead of 'grub-install -V' (version) causing unexpected failures. Fixes bug [YOCTO #12111]. Signed-off-by: California Sullivan --- meta/recipes-core/initrdscripts/files/init-install.sh | 2 +-

[OE-core] [PATCH 2/2] install*.sh: add short sleep after parted commands

I wasn't able to install to my Optane SSD due to the following error: Formatting /dev/nvme0n1p1 to vfat... mkfs.fat 4.1 (2017-01-24) mkfs.vfat: unable to open /dev/nvme0n1p1: No such file or directory Target install-efi failed A couple lines later I see: [10.265401] nvme0n1: p1 p2 p3 Then

Re: [OE-core] [PATCH] toolchain-scripts: Add PYTHONHOME in sdk env script

This fails all over the autobuilders: == ERROR: test_python_stdout (python.PythonTest) -- Traceback (most recent call last): File

[OE-core] ✗ patchtest: failure for Master package updates (rev2)

== Series Details == Series: Master package updates (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/9884/ 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

[OE-core] ✗ patchtest: failure for glibc: Fix CVE-2017-1000366

== Series Details == Series: glibc: Fix CVE-2017-1000366 Revision: 1 URL : https://patchwork.openembedded.org/series/9907/ 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

[OE-core] ✗ patchtest: failure for "[morty,v3] glibc: Fix CVE-2015..." and 1 more

== Series Details == Series: "[morty,v3] glibc: Fix CVE-2015..." and 1 more Revision: 1 URL : https://patchwork.openembedded.org/series/9906/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

Re: [OE-core] [yocto] Contribute meta-installer to yocto

Hello, On 11/21/2017 12:55 AM, Hongxu Jia wrote: > Hi all, > > Wind River has maintained meta-installer for several years, > and now we want to contribute it to yocto community. > > This layer provides an installation program based on > OE platform. The installation program is anaconda from >

[OE-core] [pyro][PATCH] glibc: Fix CVE-2017-1000366

Add backported patches from the upstream release/2.25/master branch to fix CVE-2017-1000366. Also add a backported patch that resolves SSE related build problems introduced by these patches. Signed-off-by: George McCollister ---

[OE-core] [morty][PATCH v3 1/2] glibc: Fix CVE-2015-5180

Add backported patch to fix CVE-2015-5180 from the upstream release/2.24/master branch. Signed-off-by: George McCollister --- Changes in v2: - Fix commit message Changes in v3: - None. Resending with other patch in the series.

[OE-core] [PATCH 4/5] libassuan: update to 2.4.4

From: Armin Kuster forward ported patch assuan-def.h checksum changed do to "SPDX formating" assuan.c checksum changes do to "SPDX formating" Signed-off-by: Armin Kuster --- .../libassuan-add-pkgconfig-support.patch | 77 +++---

[OE-core] [PATCH 5/5] curl: update to 7.56.1

From: Armin Kuster v2] - remove inherit curlbuild.h removed from sources includes: CVE-2017-1000257 removed patches for the following cve fixs: CVE-2017-1000254 CVE-2017-1000101 CVE-2017-1000100 CVE-2017-199 Signed-off-by: Armin Kuster ---

[OE-core] [morty][PATCH v3 2/2] glibc: Fix CVE-2017-1000366

Add backported patches from the upstream release/2.24/master branch to fix CVE-2017-1000366. Also add a backported patch that resolves SSE related build problems introduced by these patches. Signed-off-by: George McCollister --- Changes in v2: - Fix commit message

[OE-core] [PATCH 3/5] nss: update to 3.34

From: Armin Kuster for more info see: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.34_release_notes Signed-off-by: Armin Kuster --- meta/recipes-support/nss/{nss_3.33.bb => nss_3.34.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2

[OE-core] [PATCH 0/5][V2] Master package updates

I suspect curl may have conflicts if the changes in mut are applied. The gnutls changes built with meta-oe world. boot tested on a few arm machines. v2: remove dangling patch removed inherit added checksum changes The following changes since commit 33418ed064fe9cff5b4803f09135a81d9170c189:

[OE-core] [PATCH 1/5] gnutls: update to 3.6.1

zlib configure.ac support removed in 3.6.1 drop patch v2: actually remove patch Signed-off-by: Armin Kuster --- meta/recipes-support/gnutls/gnutls.inc | 3 +- .../gnutls/use-pkg-config-to-locate-zlib.patch | 75 --

[OE-core] [PATCH 2/5] nettle: update to 3.4 and cleanup

From: Armin Kuster merge .inc forward ported two patches to work with 3.4 for more info see: http://lists.gnu.org/archive/html/info-gnu/2017-11/msg7.html Signed-off-by: Armin Kuster --- ...d-target-to-only-build-tests-not-run-them.patch | 46

Re: [OE-core] ✗ patchtest: failure for "[v2] openssl10: Upgrade 1.0.2l..." and 3 more

On Mon, 20 Nov 2017 14:36:16 +0200 Alexander Kanavin wrote: > On 11/18/2017 11:03 AM, Stefan Agner wrote: > > >> * Patch[v2,1/4] openssl10: Upgrade 1.0.2l -> 1.0.2m > >> Issue Missing or incorrectly formatted CVE tag in > >> included

Re: [OE-core] ✗ patchtest: failure for lib/oe/terminal.py: use an absolute path to execute oe-gnome-terminal-phonehome (rev5)

On Mon, 20 Nov 2017 11:46:40 -0800 Andre McCurdy wrote: > On Mon, Nov 20, 2017 at 11:05 AM, Patchwork > wrote: > > == Series Details == > > > > Series: lib/oe/terminal.py: use an absolute path to execute > > oe-gnome-terminal-phonehome

Re: [OE-core] ✗ patchtest: failure for glibc_2.25: fix building for x86 with -Os (or -fno-omit-frame-pointer)

On Mon, 20 Nov 2017 20:02:56 - Patchwork wrote: > == Series Details == > > Series: glibc_2.25: fix building for x86 with -Os (or -fno-omit-frame-pointer) > Revision: 1 > URL : https://patchwork.openembedded.org/series/9881/ > State : failure > > ==

Re: [OE-core] backfill mechanism

The problem is that when backfilling is done, TUNE_FEATURES, etc, all have values associated with the base arch, not the current multilib. The "generic" solution, below, should work, although I would still use overrides when available. Beyond what actually works, if the special backfill

Re: [OE-core] [PATCH 4/5] libassuan: update to 2.4.4

On 11/21/2017 07:56 AM, Alexander Kanavin wrote: > On 11/21/2017 04:41 PM, Burton, Ross wrote: >> License checksum changes but no explanation. > > Should we introduce a standard tag for the explanation, similar to cve > tags? > > License-checksum-change: copyright years updated seems reasonable.

Re: [OE-core] [PATCH 4/5] libassuan: update to 2.4.4

On 11/21/2017 04:41 PM, Burton, Ross wrote: License checksum changes but no explanation. Should we introduce a standard tag for the explanation, similar to cve tags? License-checksum-change: copyright years updated and then have the robot do the check, while we can spend time on more

Re: [OE-core] Yocto Project Status WW47’17

On Tue, 2017-11-21 at 11:09 +, Richard Purdie wrote: > On Mon, 2017-11-20 at 20:22 -0500, Randy MacLeod wrote: > > On 2017-11-20 10:36 AM, Jolley, Stephen K wrote: > > > Current Dev Position: YP 2.5 Planning and M1 development > > > Next Deadline: YP 2.5 M1 cut off of 12/4/17 > > > > > >

[OE-core] [PATCH] image_types: Add debugging code to ext4 fs creation

We have seen a small number of issues with ROOTFS_SIZE not getting computed correctly, resulting in a failure in the mke2fs processing and populating the resulting new filesystem. This information should help us to reproduce [YOCTO #12304] Signed-off-by: Saul Wold ---

Re: [OE-core] [PATCH 4/5] libassuan: update to 2.4.4

License checksum changes but no explanation. Ross On 21 November 2017 at 00:07, Armin Kuster wrote: > From: Armin Kuster > > forward ported patch > > Signed-off-by: Armin Kuster > --- > .../libassuan-add-pkgconfig-support.patch

Re: [OE-core] [PATCH 5/5] curl: update to 7.56.1

As with the last time this upgrade was done, the multilib_header inherit can be removed now. Ross On 21 November 2017 at 00:07, Armin Kuster wrote: > From: Armin Kuster > > curlbuild.h removed from sources > > includes: > CVE-2017-1000257 > > removed

Re: [OE-core] [PATCH] verify-bashisms: use argparse, add verbose option

On Tue, 21 Nov 2017, Ross Burton wrote: > Signed-off-by: Ross Burton > --- > scripts/verify-bashisms | 15 +++ > 1 file changed, 11 insertions(+), 4 deletions(-) > > diff --git a/scripts/verify-bashisms b/scripts/verify-bashisms > index

[OE-core] ✗ patchtest: failure for "runqemu: Ensure we process all..." and 5 more

== Series Details == Series: "runqemu: Ensure we process all..." and 5 more Revision: 1 URL : https://patchwork.openembedded.org/series/9898/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

[OE-core] [PATCH] verify-bashisms: use argparse, add verbose option

Signed-off-by: Ross Burton --- scripts/verify-bashisms | 15 +++ 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/scripts/verify-bashisms b/scripts/verify-bashisms index dab64ef5019..a979bd29650 100755 --- a/scripts/verify-bashisms +++

[OE-core] [PATCH 4/6] runqemu: Improve relative path handling in qemuconf files

If a variable starts with "../", its likely its a path and we want to set it to an absolute path relative to the qemuconf file. This means we don't have to use bitbake as often to figure out variables. Signed-off-by: Richard Purdie --- scripts/runqemu | 2 ++

[OE-core] [PATCH 2/6] qemu: Add patch to avoid qemuppc boot hangs

qemuppc boots are occasionally hanging on the autobuilder. This adds a patch which fixes the issue in local testing. Its being discussed with upstream qemu. Signed-off-by: Richard Purdie --- meta/recipes-devtools/qemu/qemu/ppc_locking.patch | 105

[OE-core] [PATCH 5/6] qemuboot: Improve relative path handling

qemuconf files are currently written relative to TOPDIR. What makes more sense is to write paths relative to the location of the file. This makes moving them around and decoding the end paths in runqemu much easier. The effect of this should allow less use of bitbake to determine variables and

[OE-core] [PATCH 6/6] qemurunner: Simplify binary data handling

I have concerns that bad timing of the flow of data from the logger might corrupt the output due to the way binary strings are handled in qemurunner. This simplifies the code to do the same thing it did before but much more safely. Signed-off-by: Richard Purdie

[OE-core] [PATCH 3/6] classes/cross: Add addto_recipe_sysroot task to cross recipes

This is particularly useful if you want to use gdb-cross as there is no other good way to access it now with RSS. Signed-off-by: Richard Purdie --- meta/classes/cross.bbclass | 5 + 1 file changed, 5 insertions(+) diff --git a/meta/classes/cross.bbclass

[OE-core] [PATCH 1/6] runqemu: Ensure we process all tap devices

The regexp in the script misses some tap devices, e.g. we see output like: runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap25.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap26.lock failed: [Errno 11] Resource

Re: [OE-core] native CA cert bundles (was: Re: [PATCH 3/3] cve-check-tool: Use CA cert bundle in correct sysroot)

On Tue, Nov 21, 2017 at 10:21 AM, Patrick Ohly wrote: > On Tue, 2017-11-21 at 10:06 -0200, Otavio Salvador wrote: >> On Tue, Nov 21, 2017 at 6:04 AM, Patrick Ohly > > wrote: >> > On Thu, 2017-02-09 at 21:38 +0200, Jussi Kukkonen wrote: >> > There

Re: [OE-core] native CA cert bundles (was: Re: [PATCH 3/3] cve-check-tool: Use CA cert bundle in correct sysroot)

On Tue, 2017-11-21 at 10:06 -0200, Otavio Salvador wrote: > On Tue, Nov 21, 2017 at 6:04 AM, Patrick Ohly > wrote: > > On Thu, 2017-02-09 at 21:38 +0200, Jussi Kukkonen wrote: > > There is https://bugzilla.yoctoproject.org/show_bug.cgi?id=9883 > > open > > about some

Re: [OE-core] native CA cert bundles (was: Re: [PATCH 3/3] cve-check-tool: Use CA cert bundle in correct sysroot)

On Tue, Nov 21, 2017 at 6:04 AM, Patrick Ohly wrote: > On Thu, 2017-02-09 at 21:38 +0200, Jussi Kukkonen wrote: > There is https://bugzilla.yoctoproject.org/show_bug.cgi?id=9883 open > about some aspect of this, but it doesn't actually address the > underlying question

Re: [OE-core] [RFC][PATCH 0/5] Kernel artifacts naming changes

Hello Martin, On Mon, Nov 20, 2017 at 6:11 PM, Martin Jansa wrote: ... > This RFC doesn't implement it all, but it makes naming all the artifacts in > consistent way a bit easier. If there is an agreement that OE should support > the naming scenario described above, I'll

Re: [OE-core] [PATCH 1/3] systemd: fix formatting IDE storage does not trigger "change" uevents

On 21 November 2017 at 07:00, Hongxu Jia wrote: > 1. Tweak kernel-cache to remove CONFIG_IDE for all available bsp. > It require necessary test to prove it is safe to remove it. > If the test is OK, I will send patch to yocto mailing list. > I know you have

Re: [OE-core] Yocto Project Status WW47’17

On 21 November 2017 at 11:09, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > > > o Issues with 4.13.10 host kernels booting kvm x86 guests on > > > Tumbleweed (Suse) and Fedora 26 (attempting to see if 4.13.12 > > > helps) > > > > Robert, can you test Fedora 26. It would help to

Re: [OE-core] [PATCH 2/2] image.bbclass: improve reproducibility

Hi Ross, On Tue, Nov 21, 2017 at 10:59:49AM +, Burton, Ross wrote: >I think this is to blame for a slew of failures on the autobuilder: Sorry for that. Please revert it. >http://errors.yoctoproject.org/Errors/Latest/?filter=57ddf212e64207edfbd813d32ca3a15f6c1c8211=commit > >Such as: >

Re: [OE-core] Yocto Project Status WW47’17

On Mon, 2017-11-20 at 20:22 -0500, Randy MacLeod wrote: > On 2017-11-20 10:36 AM, Jolley, Stephen K wrote: > > Current Dev Position: YP 2.5 Planning and M1 development > > Next Deadline: YP 2.5 M1 cut off of 12/4/17 > >   > > SWAT team rotation: Juro -> Paul on Nov.17, 2017. > > SWAT team

Re: [OE-core] [PATCH 2/2] image.bbclass: improve reproducibility

I think this is to blame for a slew of failures on the autobuilder: http://errors.yoctoproject.org/Errors/Latest/?filter=57ddf212e64207edfbd813d32ca3a15f6c1c8211=commit Such as: NOTE: FAIL [0.616s]: test_df (df.DfTest) NOTE: --

[OE-core] [PATCH v7 00/15] support profile-optimized build for Python

Seventh version of the patchset making it possible to do profile-guided-optimization for Python 3. Changes since v6: - fixed a typo (Utream-Status -> Upstream-Status) in openssh patch - changes to python-3.5-manifest.inc now done properly by using scripts/contrib/python/generate-manifest-3.5.py

[OE-core] [PATCH] glibc/gcc/libgcc-initial: Reimplement "deltask do_build"

From: Mingli Yu Previously, "deltask do_build" can result in the dependency of do_build lost and can trigger a race condition error as below when do_rm_work is enabled. = NOTE: recipe glibc-initial-2.26-r0: task do_fetch:

Re: [OE-core] [PATCH] glibc/gcc/libgcc-initial: Reimplement "deltask do_build"

Please ignore this patch as the indentation is TAB, will send V2 to use four space as indentation. Thanks, Mingli On 2017年11月21日 16:00, mingli...@windriver.com wrote: From: Mingli Yu Previously, "deltask do_build" can result in the dependency of do_build lost and

[OE-core] [PATCH] glibc/gcc/libgcc-initial: Reimplement "deltask do_build"

From: Mingli Yu Previously, "deltask do_build" can result in the dependency of do_build lost and can trigger a race condition error as below when do_rm_work is enabled. = NOTE: recipe glibc-initial-2.26-r0: task do_fetch:

[OE-core] native CA cert bundles (was: Re: [PATCH 3/3] cve-check-tool: Use CA cert bundle in correct sysroot)

On Thu, 2017-02-09 at 21:38 +0200, Jussi Kukkonen wrote: > Native libcurl looks for CA certs in the wrong place by > default. > * Add patch that allows overriding the default CA certificate >   location. Patch is originally from meta-security-isafw. > * Use the new --cacert to set the correct CA