Re: [PATCH] [OE-core] [PATCHv2] systemtap: upgrade 4.3 -> 4.4

Hi Zangrc, this patch is now in master-next https://patchwork.openembedded.org/series/27030/ but autobuilder detected a compilation error in the upgraded version https://autobuilder.yoctoproject.org/typhoon/#/builders/61/builds/2736/steps/13/logs/stdio Can you please take a look? (seems

Re: [OE-core] [PATCH 4/4] gnupg: use native version for signing, rather than one provided by host

Great that you figure out a solution. So I belive we need to revert this commit: commit 043d9ac0ae441e9a7e2ea8934bfc595a03ef9a52 Author: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Date: Mon Sep 25 13:52:59 2017 -0700 sign_rpm.bbclass: force rpm serial s

[OE-core] [PATCH v3] parallel-oe-selftest.sh: runs oe-selftest in parallel

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Run in parallel the (oe)selftests using GNU/Parallel: for each test defined, a job will be launched and at any time at maximum of jobs will be executing (defaults to 4). 1. Run all modules parallel-oe-selftest.sh

Re: [OE-core] [PATCH v2 2/2] parallel-oe-selftest.sh: runs oe-selftest in parallel

On Mon, 18 Dec 2017 12:26:32 -0800 Andre McCurdy <armccu...@gmail.com> wrote: > On Mon, Dec 18, 2017 at 9:43 AM, > <leonardo.sandoval.gonza...@linux.intel.com> wrote: > > From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> > > > > P

[OE-core] [PATCH v2 2/2] parallel-oe-selftest.sh: runs oe-selftest in parallel

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Parallelize oe-selftest execution using GNU/Parallel: for each test defined, a job will be launched and at any time at maximun of jobs will be executing (defaults to 4). 1. Run all modules parallel-oe-selftest.sh

[OE-core] [PATCH v2 1/2] scripts/oe-selftest: isolate oe-selftest execution

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The main idea is to isolate the oe-selftest execution so neither the current build directory, configuration nor environment is use when executing the selftests. The approach uses 'oe-selftest' as a wrapper scripts with on

[OE-core] [PATCH v2] core/loader.py: fix regex to include all available test cases

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Some test cases (eSDK.oeSDK*, runtime_test/*) does not match with current regex, fix it accept all. [YOCTO #12385] Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> --- meta/lib/oeqa/co

Re: [OE-core] ✗ patchtest: failure for "libxslt: use HTTP instead of F..." and 1 more

On Wed, 6 Dec 2017 16:03:13 + "Burton, Ross" <ross.bur...@intel.com> wrote: > On 6 December 2017 at 16:00, Leonardo Sandoval < > leonardo.sandoval.gonza...@linux.intel.com> wrote: > > > On Wed, 06 Dec 2017 15:02:57 - > > Patchwork &

Re: [OE-core] ✗ patchtest: failure for "libxslt: use HTTP instead of F..." and 1 more

On Wed, 06 Dec 2017 15:02:57 - Patchwork wrote: > == Series Details == > > Series: "libxslt: use HTTP instead of F..." and 1 more > Revision: 1 > URL : https://patchwork.openembedded.org/series/10099/ > State : failure > > == Summary == > > > Thank

Re: [OE-core] [PATCH] core/loader.py: fix regex to include all available test cases

On Wed, 6 Dec 2017 11:50:58 + Joshua Lock <joshua.g.l...@linux.intel.com> wrote: > On 05/12/17 15:51, leonardo.sandoval.gonza...@linux.intel.com wrote: > > From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> > > > > Some test cases (

[OE-core] [PATCH] core/loader.py: fix regex to include all available test cases

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Some test cases (i.e. eSDK.oeSDKExtSelfTest*) does not match with current regex, fix it to accept these (and previous ones). Without it, the following runtime exception is observed when executing eSDK selftest (oe-selft

Re: [OE-core] ✗ patchtest: failure for initramfs-framework installation improvements (rev4)

On Fri, 1 Dec 2017 23:07:48 +0100 Martin Jansa wrote: > Is it trying to apply whole series (including the 2 patches which were > already merged to master and actually introduced the issue I was trying to > fix)? > > Does it mean that I cannot send a fix into the e-mail

[OE-core] [PATCH] image-buildinfo.bbclass: include IMAGE related variables

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> These variables provide additional information (image related) targeted for QA image verification. Now, target /etc/build looks like: root@qemux86:~# cat /etc/build --- Build Configu

Re: [OE-core] [rocko][PATCH] weston: add patch to set pitch correctly for subsampled textures

On Sat, 25 Nov 2017 22:59:36 +0300 Andrey Konovalov <andrey.konova...@linaro.org> wrote: > On 24.11.2017 23:34, Leonardo Sandoval wrote: > > On Fri, 24 Nov 2017 22:58:20 +0300 > > Andrey Konovalov <andrey.konova...@linaro.org> wrote: > > > >> This exa

Re: [OE-core] ✗ patchtest: failure for linux-yocto: drop KCONF_BSP_AUDIT_LEVEL

On Mon, 27 Nov 2017 13:03:05 - Patchwork wrote: > == Series Details == > > Series: linux-yocto: drop KCONF_BSP_AUDIT_LEVEL > Revision: 1 > URL : https://patchwork.openembedded.org/series/9957/ > State : failure > > == Summary == > > > Thank you for

Re: [OE-core] [rocko][PATCH] weston: add patch to set pitch correctly for subsampled textures

On Fri, 24 Nov 2017 22:58:20 +0300 Andrey Konovalov wrote: > This exact patch also applies to pyro. > Should I send the separate "[OE-core][pyro][PATCH] weston: add patch to set > pitch correctly for subsampled textures" email, > or just asking to merge it into pyro

Re: [OE-core] ✗ patchtest: failure for weston: add patch to set pitch correctly for subsampled textures

On Fri, 24 Nov 2017 20:04:08 - Patchwork wrote: > == Series Details == > > Series: weston: add patch to set pitch correctly for subsampled textures > Revision: 1 > URL : https://patchwork.openembedded.org/series/9949/ > State : failure > > == Summary

Re: [OE-core] ✗ patchtest: failure for Add pypi.bbclass; python improvements

On Thu, 23 Nov 2017 12:48:32 -0700 Tim Orling wrote: > I stand corrected. When I try to apply the mbox file from patchwork it throws: > > error: patch fragment without header at line 147: @@ -172,6 +172,10 @@ > SUMMARY_${PN}-png

Re: [OE-core] ✗ patchtest: failure for systemd: fixs mips64 login issue

On Thu, 23 Nov 2017 18:37:54 - Patchwork wrote: > == Series Details == > > Series: systemd: fixs mips64 login issue > Revision: 1 > URL : https://patchwork.openembedded.org/series/9939/ > State : failure > > == Summary == > > > Thank you for

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] [yocto] [PATCH v4 1/3] image.bbclass: add prohibited-paths QA test

isn't it this class meta/classes/insane.bbclass for this type of checks? On Thu, 16 Nov 2017 15:05:56 + Martyn Welch wrote: > Sometimes we wish to ensure that files or directories are not installed > somewhere that may prove detrimental to the operation of the

Re: [OE-core] [PATCH 26/27] ffmpeg: update to 3.4

On Tue, 14 Nov 2017 11:41:16 -0800 Khem Raj wrote: > On Tue, Nov 14, 2017 at 6:57 AM, Alexander Kanavin > wrote: > > Schroedinger support has been dropped: > > https://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff/220b24c7c9 > > > >

Re: [OE-core] [PATCH 24/27] lighttpd: update to 1.4.48

On Tue, 14 Nov 2017 16:57:51 +0200 Alexander Kanavin wrote: > Refresh the pcre pkg-config patch. > > Signed-off-by: Alexander Kanavin > --- > ...fig-for-pcre-dependency-instead-of-config.patch | 48 > +-

Re: [OE-core] [PATCH v2 1/2] scripts/oe-selftest: oe-selftest-internal wrapper scripts that isolates execution

On Tue, 14 Nov 2017 17:09:28 +0100 Patrick Ohly <patrick.o...@intel.com> wrote: > On Tue, 2017-11-14 at 10:09 -0600, Leonardo Sandoval wrote: > > On Tue, 14 Nov 2017 09:24:30 +0100 > > Patrick Ohly <patrick.o...@intel.com> wrote: > > > &

Re: [OE-core] [PATCH v2 1/2] scripts/oe-selftest: oe-selftest-internal wrapper scripts that isolates execution

On Tue, 14 Nov 2017 09:24:30 +0100 Patrick Ohly <patrick.o...@intel.com> wrote: > On Mon, 2017-11-13 at 10:17 -0800, > leonardo.sandoval.gonza...@linux.intel.com wrote: > > From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> > > > > The mai

Re: [OE-core] ✗ patchtest: failure for connman: bump to version 1.35

On Tue, 14 Nov 2017 15:18:40 +0100 Daniel Mack wrote: > Ha, this exact same patch is already in master-next. > I must have missed that. > > Sorry for the noise! 'patchtest' checks only stable branches, and what I can see is that this patch is already on master (From OE-Core

[OE-core] [PATCH v2 1/2] scripts/oe-selftest: oe-selftest-internal wrapper scripts that isolates execution

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The main idea is to isolate the oe-selftest execution so neither the current build dir nor the configuration data is touch/polluted. This approach uses a wrapper script (which is the one presented on this commit) which c

[OE-core] [PATCH v2 2/2] parallel-oe-selftest.sh: runs oe-selftest in parallel

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Parallelize oe-selftest execution using GNU/Parallel: for each test defined, a job will be launched and at any time at maximun of jobs will be executing (defaults to 4). Extra parameters can be given to parallel cmd after

Re: [OE-core] [PATCH 1/1] scripts/oe-selftest: oe-selftest-internal wrapper scripts that isolates execution

items and send a v2. Leo > From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> > > The main idea is to isolate the oe-selftest execution so neither the current > build dir nor the configuration data is touch/polluted. This approach uses > a wrapper scr

Re: [OE-core] ✗ patchtest: failure for core package updates

On Fri, 03 Nov 2017 20:03:06 - Patchwork wrote: > == Series Details == > > Series: core package updates > Revision: 1 > URL : https://patchwork.openembedded.org/series/9623/ > State : failure > > == Summary == > > > Thank you for submitting this

Re: [OE-core] ✗ patchtest: failure for linux-firmware: Bump to bf04291 revision

On Sun, Oct 29, 2017 at 10:47 AM, Denys Dmytriyenko <de...@denix.org> wrote: On Thu, Oct 26, 2017 at 12:51:27PM -0500, Leonardo Sandoval wrote: I believe the patchtest complain is valid, some brief explanation should be given. FWIW, it was mentioned in the commit log: bf04291

[OE-core] [PATCH v2] qemu: upgrade to 2.10.1

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> All CVE patches and the glibc one removed because these are already integrated into 2.10.1. Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> --- v2: removed the glibc-2.25.pa

Re: [OE-core] [PATCH 0/1] scripts/oe-selftest: oe-selftest-internal wrapper scripts that isolates execution

encies will be fulfilled and executed correctly, right? the trade off is some extra work done on each oe-selftest due to dependencies but this wont hurt much in my opinion. Leo Cheers, Anibal On Thu, Oct 26, 2017 at 12:33 PM, <leonardo.sandoval.gonza...@linux.intel.com> wrote: From: Leona

Re: [OE-core] ✗ patchtest: failure for linux-firmware: Bump to bf04291 revision

I believe the patchtest complain is valid, some brief explanation should be given. But the way it is present need some improvement. We should not be listing all licenses, just the ones that change. Leo On Thu, Oct 26, 2017 at 11:32 AM, Patchwork

[OE-core] [PATCH 0/1] scripts/oe-selftest: oe-selftest-internal wrapper scripts that isolates execution

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The below is a profiling experiment, running oe-selftest -r (the proposed implementation, see patch description for more info): Procedure: With patch 1/1, multiple oe-selftest jobs can be launched in parallel. On

[OE-core] [PATCH 1/1] scripts/oe-selftest: oe-selftest-internal wrapper scripts that isolates execution

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The main idea is to isolate the oe-selftest execution so neither the current build dir nor the configuration data is touch/polluted. This approach uses a wrapper script (which is the one presented on this commit) which c

Re: [OE-core] [PATCH 1/2] qemu: upgrade to 2.10.1

Hi Patrick On Thu, Oct 26, 2017 at 4:33 AM, Patrick Ohly <patrick.o...@intel.com> wrote: On Thu, 2017-10-19 at 13:10 -0700, leonardo.sandoval.gonza...@linux.intel.com wrote: From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> All CVE patches rem

Re: [OE-core] ✗ patchtest: failure for git: CVE-2017-14867

* Issue LIC_FILES_CHKSUM changed on target git but there was no explanation as to why in the commit message [test_lic_files_chksum_modified_not_mentioned] Suggested fixProvide a reason for LIC_FILES_CHKSUM change in commit message Current checksum New checksum

Re: [OE-core] ✗ patchtest: failure for Restructure python2 and python3 packaging system (rev2)

gt; Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest > Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe > > -- > ___ > Openembedded-core mailing list > Openembedded-

[OE-core] [PATCH 2/2] texinfo: upgrade to 6.5

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Besides revision change, this version includes the project M4 macros path into EXTRA_AUTORECONF which avoid the following compilation issue: In file included from ../../../texinfo-6.5/gnulib/lib/mbrtowc.

[OE-core] [PATCH 1/2] qemu: upgrade to 2.10.1

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> All CVE patches removed because these are already integrated in 2.10.1. Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> --- .../qemu/qemu/CVE-2017-13672.patch

Re: [OE-core] [PATCH] kernel-fitimage: support ARM64 On arm64, the kernel image target is Image

_______ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v3 3/5] git.inc: remove sed statement removing SVN lines from .packlist

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The git-perltools package created with perl 5.26.1 does not contain the .packlist file thus there is no need to sed on this file. More general, the buildhistory-diff tool shows the following changes on the related p

[OE-core] [PATCH v3 4/5] libxml-namespacesupport-perl: upgrade to 1.12.9

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> --- .../perl/libxml-namespacesupport-perl_1.12.9.bb| 35 ++ .../perl/libxml-namespacesupport-perl_1.12.

[OE-core] [PATCH v3 1/5] perl-native: upgrade from 5.24.1 to 5.26.1

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Patch Name # Status at 5.26.1 file://Configure-multilib.patch# Already merged in 5.26.1, so removed it file://perl-configpm-switch.patch # Applies as it is file://native-nopacklist.patch # R

[OE-core] [PATCH v3 2/5] perl: upgrade to 5.26.1

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Highlights: * Patches rebased to 5.26.1 and just one removed * Several configs values taken from upstream script uconfig[64].sh were introduced in config.sh, avoiding pre-processor issues. * Several lib

Re: [OE-core] ✗ patchtest: failure for "README.qemu: qemuppc64 is not ..." and 1 more

; > # Randy MacLeod. WR Linux > > # Wind River an Intel Company > > -- > > ___ > > Openembedded-core mailing list > > Openembedded-core@lists.openembedded.org > > http://lists.openembedded.org/mailman/listinfo

Re: [OE-core] [PATCH] devtool: ensure temp directory is created

try: > tinfoil.logger.setLevel(logging.WARNING) > > -- > 2.13.6 > > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinf

Re: [OE-core] [PATCH] scripts/send-recipe-update-reminders: send recipe version update reminders by email

> > YP used to have a much more sophisticated system called Automated > Upgrade Helper for this, but it hasn't been heard from in several months > and so I quickly rolled my own cheap and cheery replacement. AUH is the system that send emails with upgrade statistics (basically the system tries

Re: [OE-core] [PATCH] scripts/send-recipe-update-reminders: send recipe version update reminders by email

On Tue, 17 Oct 2017 15:43:39 +0300 Alexander Kanavin wrote: I like the idea of a simpler script to do this job. Just one minor comment on the code: I would use non-zero exit values in case of errors and as a possible future enhancement, use a template (jinja2

[OE-core] [PATCH v2 5/5] ruby: upgrade to 2.4.2

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The CVE-2017-14064 patch is already at 2.4.2 as explained on project's commit, so removing from the recipe & repo. commit 83735ba29a0bfdaffa8e9c2a1dc025c3b0b63153 Author: hsbt <hsbt@b2dd03c8-39d4-4d8f-98ff

[OE-core] [PATCH v2 3/5] git.inc: remove sed statement removing SVN lines from .packlist

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The git-perltools package created with perl 5.26.1 does not contain the .packlist file thus there is no need to sed on this file. More general, the buildhistory-diff tool shows the following changes on the related p

[OE-core] [PATCH v2 1/5] perl-native: upgrade from 5.24.1 to 5.26.1

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Patch Name # Status at 5.26.1 file://Configure-multilib.patch# Already merged in 5.26.1, so removed it file://perl-configpm-switch.patch # Applies as it is file://native-nopacklist.patch # R

[OE-core] [PATCH v2 4/5] libxml-namespacesupport-perl: upgrade to 1.12.9

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> --- .../perl/libxml-namespacesupport-perl_1.12.9.bb| 35 ++ .../perl/libxml-namespacesupport-perl_1.12.

[OE-core] [PATCH v2 2/5] perl: upgrade to 5.26.1

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Highlights: * Patches rebased to 5.26.1 and just one removed * Several configs values taken from upstream script uconfig[64].sh were introduced in config.sh, avoiding pre-processor issues. * Several lib

Re: [OE-core] ✗ patchtest: failure for "README.qemu: qemuppc64 is not ..." and 1 more

octoproject.org/cgit/cgit.cgi/patchtest > > Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe > > > > > > > -- > # Randy MacLeod. WR Linux > # Wind River an Intel Company > -- > ___ > Opene

Re: [OE-core] [PATCH 2/4] perl: upgrade to 5.26.1

On Thu, 12 Oct 2017 15:11:04 -0400 Denys Dmytriyenko <de...@denix.org> wrote: > On Thu, Oct 12, 2017 at 11:35:21AM -0700, > leonardo.sandoval.gonza...@linux.intel.com wrote: > > From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> > > > >

[OE-core] [PATCH 4/4] ruby: upgrade to 2.4.2

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The CVE-2017-14064 patch is already at 2.4.2 as explained on project's commit, so removing from the recipe & repo. commit 83735ba29a0bfdaffa8e9c2a1dc025c3b0b63153 Author: hsbt <hsbt@b2dd03c8-39d4-4d8f-98ff

[OE-core] [PATCH 2/4] perl: upgrade to 5.26.1

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Highlights: * Patches rebased to 5.26.1 and just one removed * Several configs values taken from upstream script uconfig[64].sh were introduced in config.sh, avoiding pre-processor issues. * Several lib

[OE-core] [PATCH 1/4] perl-native: upgrade from 5.24.1 to 5.26.1

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Patch Name # Status at 5.26.1 file://Configure-multilib.patch# Already merged in 5.26.1, so removed it file://perl-configpm-switch.patch # Applies as it is file://native-nopacklist.patch # R

[OE-core] [PATCH 3/4] libxml-namespacesupport-perl: upgrade to 1.12.9

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> --- ...2.bb => libxml-namespacesupport-perl_1.12.9.bb} | 24 -- 1 file changed, 18 insertions(+), 6 deletions(

Re: [OE-core] Recipe versions and layer confusion

s at the Space Tech Expo Europe (Stand E-71) > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- Leonardo Sandoval <leonardo.sandoval.gonza...

[OE-core] [pyro][PATCH 1/2] selftest/cases/signing: ignore removal errors when cleaning temporary gpg directory

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The high-level method tempfile.TemporaryDirectory give us no way to ignore erros on removal thus use tempfile.mkdtemp instead. Ignoring possible issues on removal is neccesary because it contains gpg s

[OE-core] [pyro][PATCH 2/2] sign_rpm.bbclass: force rpm serial signing

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Newer versions of gpg (at least 2.1.5 and 2.2.1) have issues when signing occurs in parallel so (unfortunately) the signing must be done serially. Once the upstream problem is fixed, this patch must be reverted, otherw

[OE-core] [morty][PATCH 2/2] sign_rpm.bbclass: force rpm serial signing

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Newer versions of gpg (at least 2.1.5 and 2.2.1) have issues when signing occurs in parallel so (unfortunately) the signing must be done serially. Once the upstream problem is fixed, this patch must be reverted, otherw

[OE-core] [morty][PATCH 1/2] selftest/cases/signing: ignore removal errors when cleaning temporary gpg directory

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The high-level method tempfile.TemporaryDirectory give us no way to ignore erros on removal thus use tempfile.mkdtemp instead. Ignoring possible issues on removal is neccesary because it contains gpg s

[OE-core] [PATCH] qemurunner: print tail qemu log in case bootlog is empty

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> There are cases where the 'while loop' waiting for login prompt fails and the bootlog variable does not get populated, thus use the the new qemurunner member (self.msg) which stores all output coming from the qemu p

Re: [OE-core] ✗ patchtest: failure for Revamp the Go support (rev7)

Patchwork writes: > == Series Details == > > Series: Revamp the Go support (rev7) > Revision: 7 > URL : https://patchwork.openembedded.org/series/8697/ > State : failure > > == Summary == > > > Thank you for submitting this patch series to OpenEmbedded

[OE-core] [PATCH] selftest/cases/signing: ignore removal errors when cleaning temporary gpg directory

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> The high-level method tempfile.TemporaryDirectory give us no way to ignore erros on removal thus use tempfile.mkdtemp instead. Ignoring possible issues on removal is neccesary because it contains gpg s

[OE-core] [PATCH 1/2] package_deb, ipk: improve subprocess output on package manager command

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Redirecting stderr to stdout helps debugging issues, i.e instead of just getting the return code, get also the error log from the pkg manger This commit is in the way to figure out the root cause of [YOCTO #12012], wher

[OE-core] [PATCH 2/2] package_[deb|ipk]: improve multiprocess logic when creating deb/ipk packages

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Current implementation does not handle possible exceptions coming from child processes, the latter responsible for creating packages. With the aim to have more control, use pipes to communicate exceptions and stop p

[OE-core] [PATCH] waffle: fix REQUIRED_DISTRO_FEATURES and PACKAGECONFIG virtual/libgl dependencies

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Waffle's REQUIRED_DISTRO_FEATURES statement looks into DEPENDS and if virtual/libgl is present, it includes opengl as distro feature. However, in a multilib environment, recipes provides virtual/${MLPREFIX}libgl, thus

Re: [OE-core] [PATCH] waffle: prefix MLPREFIX on libgl dependency

leonardo.sandoval.gonza...@linux.intel.com writes: please ignore this patch. I will git-amend and provide a better explanation. > From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> > > Otherwise, on a multilib environment we get the following bitbake errors &

[OE-core] [PATCH] linux-yocto: add linux-yocto 4.12 bbappends

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> This allows the yocto-bsp script to pick the 4.12 kernel version when creating a custom BSP. [YOCTO #11995] Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> --- .../arm/recipes-kernel/

[OE-core] [PATCH] waffle: prefix MLPREFIX on libgl dependency

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Otherwise, on a multilib environment we get the following bitbake errors while building 'world' ERROR: Nothing PROVIDES 'virtual/lib32-libgl' (but virtual:multilib:lib32:/meta/recipes-graphics/waffle/waffle_1.

Re: [OE-core] [PATCH v2] (PRE)MIRRORS: add pattern for npm:// without slash

> npm://.*/.* http://sources.openembedded.org/ \n \ > +npm://.*http://sources.openembedded.org/ \n \ instead of adding a new npm regex, not sure if below one would the same job npm://.*(/.*)? -- ___ Openembedded-core mailing list

Re: [OE-core] [PATCH 4/7] json-glib: convert to meson build

> -inherit gnomebase gettext lib_package gobject-introspection gtk-doc manpages > +inherit gnomebase-meson lib_package gobject-introspection gtk-doc manpages gettext is dropped, does it mean that it was not needed? > > -PACKAGECONFIG[manpages] = "--enable-man >

Re: [OE-core] [PATCH 1/7] meson: add a recipe and class from meta-oe

> + > +inherit setuptools3 > + > +RDEPENDS_${PN} = "ninja python3-core python3-modules" > + if (python3) modules depends on core, I believe core can be dropped from RDEPENDS > +BBCLASSEXTEND = "native" > -- > 2.14.1 > -- ___ Openembedded-core

Re: [OE-core] ✗ patchtest: failure for do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev6)

On Wed, 2017-08-23 at 13:04 +, Patchwork wrote: > == Series Details == > > Series: do_image: Implement IMAGE_ROOTFS_EXCLUDE_PATH feature. (rev6) > Revision: 6 > URL : https://patchwork.openembedded.org/series/6525/ > State : failure > > == Summary == > > > Thank you for submitting this

Re: [OE-core] ✗ patchtest: failure for staging: add missing import errno to staging_populate_sysroot_dir

On Wed, 2017-08-23 at 14:03 +, Marko, Peter wrote: > >* Issue Series does not apply on top of target branch > >[test_series_merge_on_head] > > Suggested fixRebase your series on top of targeted branch > > Targeted branch master (currently at b1e482ae20) > > Richie is

Re: [OE-core] [PATCH] meta: move some text from oe-setup-builddir to conf-notes.txt

On Mon, 2017-08-21 at 13:45 +0200, liu.min...@gmail.com wrote: > From: Ming Liu > > This allows the end users to be able to override the entire notes > showing on the shell console. For instance, Our company uses a > external conf-notes.txt, and we run

[OE-core] [PATCH v2 1/2] devtool/copy_buildsystem: adds meta-skeleton layer in the eSDK installation.

From: Juan M Cruz Alcaraz The eSDK installation requires the meta-skeleton layer. The build system might use the meta-skeleton recipes as layout to create custom recipes. An example is the recipetool script that uses the meta-skeleton kernel recipe when

[OE-core] [PATCH v2 2/2] build-appliance-image: include proxy on pip3 installation

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Otherwise, we get timeouts, leading to errors: pip._vendor.requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded with url: /pypi/pip/json (

Re: [OE-core] bussybox: updating to new version

On Fri, 2017-08-18 at 12:16 +0200, Andrej Valek wrote: > Hello everyone, > > I would like to ask you a question about busybox upgrading. > > Is there any reason, why we are still using the version 1.24.1? > I think that, the latest version 1.27.2 has a lot of fixes and it less > vulnerable then

Re: [OE-core] [PATCH] gpg_sign: perform rpm signing serially

depends on the number of subpackages the recipe > produces. Selftest uses one of the smallest recipes , i.e. "ed", so you won't > see any difference. But with hundreds of subpackages you get different > figures. >- Markus > > On 17/08/2017, 17.52, "Leonardo Sandoval

Re: [OE-core] [PATCH v3 02/11] image-prelink.bbclass: support binary reproducibility

On Wed, 2017-08-09 at 10:48 -0700, Juro Bystricky wrote: > 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

Re: [OE-core] [PATCH v3 08/11] python2.7: improve reproducibility

On Wed, 2017-08-09 at 10:48 -0700, Juro Bystricky wrote: > The compiled .pyc files contain time stamp corresponding to the compile time. > This prevents binary reproducibility. This patch allows to achieve binary > reproducibility by overriding the build time stamp by the value > exported via

[OE-core] [PATCH] report-error: provide distro identifier string in case of uninative build

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Besides providing the NATIVELSBSTRING, include distro info when creating the (json) error report. This information provides better info than the standard 'universal*' string for uninative builds. [YOCTO #11824] Sign

[OE-core] [PATCH] sign_rpm: Allow pkg signing by chunks through RPM_GPG_SIGN_CHUNK

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Commit d58b1d196 moved from chunk to serial signing, but neither of both approaches allowed the user to select the chunks size. This patch allows the user to select a chunk size through RPM_GPG_SIGN_CHUNK defa

Re: [OE-core] [PATCH] gpg_sign: perform rpm signing serially

s Andre suggested in another email. > - Markus > > > > On 16/08/2017, 19.00, "Leonardo Sandoval" > <leonardo.sandoval.gonza...@linux.intel.com> wrote: > > On Wed, 2017-08-16 at 15:28 +0300, Markus Lehtonen wrote: > > I agree. I don't see reason

Re: [OE-core] [PATCH] gpg_sign: perform rpm signing serially

> --Mark > > On 8/15/17 4:40 PM, leonardo.sandoval.gonza...@linux.intel.com wrote: > > From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> > > > > gpg signing in file batches (which was default to 100) is a memory > expe

[OE-core] [PATCH] gpg_sign: perform rpm signing serially

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> gpg signing in file batches (which was default to 100) is a memory expensive computation, causing trouble in some host machines (even on production AB as seen on the bugzilla ID). Also, in terms of performance, there is n

[OE-core] [PATCH 2/2] build-appliance-image: include proxy on pip3 installation

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Otherwise, we get timeouts, leading to errors: pip._vendor.requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded with url: /pypi/pip/json (

[OE-core] [PATCH 1/2] packagegroup-self-hosted: include missing (pod2man scp ssh) RPEDENDS packages

From: Leonardo Sandoval <leonardo.sandoval.gonza...@linux.intel.com> Otherwise, the following bitbake error is observed root@qemux86-64:~/openembedded-core/build# bitbake -e NOTE: Starting bitbake server... ERROR: Unable to start bitbake server ERROR: Last 10 lines of serv

Re: [OE-core] [PATCH] insane: add qa check for lowercase recipe name

On Mon, 2017-08-14 at 19:23 -0700, Yeoh Ee Peng wrote: > Since we disabled uppercase characters in overrides a few releases ago, > uppercase characters in recipe names (and for that matter, distro and > machine names) cannot be supported due to their reliance upon overrides > including the name. >

Re: [OE-core] master-next

On Mon, 2017-08-14 at 19:24 +, Slater, Joseph wrote: > Is there something “different” about this branch? this branch is the what at some point will be landed to master, pretty dynamic and only created/used by key maintainers (RP, Ross) and consumed by the auto-builder. > I find that if I

Re: [OE-core] [PATCH v2] libx11: Add patch to fix hanging issue in _XReply

On Mon, 2017-08-14 at 11:00 +0300, Jose Alarcon wrote: > Assume event queue is empty if another thread is blocking waiting for event. > > If one thread was blocking waiting for an event and another thread sent a > reply to the X server, both threads got blocked until an event was > received. > >

Re: [OE-core] ✗ patchtest: failure for libx11: Add patch to fix hanging issue in _XReply

On Mon, 2017-08-14 at 07:01 +, Patchwork wrote: > == Series Details == > > Series: libx11: Add patch to fix hanging issue in _XReply > Revision: 1 > URL : https://patchwork.openembedded.org/series/8209/ > State : failure > > == Summary == > > > Thank you for submitting this patch series

  1   2   3   4   5   >