[OE-core] [PATCH] python3-psutil: fix-up -tests runtime dependencies

ot installed") ValueError: gcc is not installed along with other errors related to the missing tools and headers. Add the missing RDEPENDS for the -tests package such that simply adding the -tests package to an image will be all that is needed. Signed-off-by: Mark Asselstine --- .../

[OE-core] [PATCH] oeqa/selftest/bblogging: uncomment python stdout checks

Since bitbake commit 81a58647b2f4fc0a2589b2978fc9d81b2bfe6aec [bitbake: build: Make python output print to stdout when running with -v (verbose)] we no longer need to comment out the python stdout checks. Signed-off-by: Mark Asselstine --- meta/lib/oeqa/selftest/cases/bblogging.py | 18

Re: [OE-core] [PATCH 3/5] poky-meta: add go vendor class for offline builds

On 2022-05-06 02:59, Stefan Herbrechtsmeier wrote: From: Lukas Funke Signed-off-by: Lukas Funke Signed-off-by: Stefan Herbrechtsmeier --- meta/classes/go-vendor.bbclass | 68 ++ 1 file changed, 68 insertions(+) create mode 100644

Re: [OE-core] [PATCH 4/5] recipetool: add go recipe generator

On 2022-05-06 03:15, Alexander Kanavin wrote: This is a lot of code. Can you add some documentation for it, what it does and how it works? If someone would want to understand it, how would they go about it? Alex On Fri, 6 May 2022 at 09:00, Stefan Herbrechtsmeier wrote: From: Lukas Funke

Re: [OE-core] [PATCH 5/5] oe-selftest: add go recipe create selftest

On 2022-05-06 03:16, Alexander Kanavin wrote: Also here an explanation of what the test does would be useful. Please keep in mind: writing code is only half the job. You need to explain it to non-specialists too, we're already struggling with items which are understood by few people, or in

Re: [OE-core] [PATCH 1/5] recipetool-create: add ensure_native_cmd function

On 2022-05-11 15:45, Mark Asselstine wrote: On 2022-05-06 03:09, Alexander Kanavin wrote: I think the terminology is a bit confused here, instead of 'command' it should say 'recipe'. Also: """Check if the command is available in the recipes""" is not ever

Re: [OE-core] [PATCH 1/5] recipetool-create: add ensure_native_cmd function

On 2022-05-06 03:09, Alexander Kanavin wrote: I think the terminology is a bit confused here, instead of 'command' it should say 'recipe'. Also: """Check if the command is available in the recipes""" is not everything it does, it also builds the recipe. And please write a commit message that

Re: [OE-core][Patch v2 1/2] xinput-calibrator: avoid defunct process

On Tuesday, September 1, 2020 11:30:23 A.M. EDT Richard Purdie wrote: > On Fri, 2020-08-28 at 17:29 -0400, Mark Asselstine wrote: > > The xinput_calibrator_once.sh script produces output on stdout and > > stderr which the current 'Exec' doesn't consum

Re: [OE-core][Patch v2 1/2] xinput-calibrator: avoid defunct process

On Friday, August 28, 2020 5:29:19 P.M. EDT Mark Asselstine wrote: > The xinput_calibrator_once.sh script produces output on stdout and > stderr which the current 'Exec' doesn't consume. This results in a > [xinput_calibrator_once.sh] defunct process which will remain around > u

[OE-core][Patch v2 1/2] xinput-calibrator: avoid defunct process

and avoid the defunct process. Signed-off-by: Mark Asselstine --- V2: * no changes .../recipes-graphics/xinput-calibrator/xinput-calibrator_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/xinput-calibrator/xinput-calibrator_git.bb b/meta/recipes

[OE-core][Patch v2 2/2] xinput-calibrator: make _once run only once

file to avoid further attempts to perform calibration. If new HW is added the file can simply be removed to force a new calibration attempt. Signed-off-by: Mark Asselstine --- V2: * add Upstream-status to the patch ...r_pointercal.sh-allow-skipping-calib.patch | 34

[OE-core] [PATCH 1/2] xinput-calibrator: avoid defunct process

and avoid the defunct process. Signed-off-by: Mark Asselstine --- .../recipes-graphics/xinput-calibrator/xinput-calibrator_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/xinput-calibrator/xinput-calibrator_git.bb b/meta/recipes-graphics/xinput

[OE-core] [PATCH 2/2] xinput-calibrator: make _once run only once

file to avoid further attempts to perform calibration. If new HW is added the file can simply be removed to force a new calibration attempt. Signed-off-by: Mark Asselstine --- ...r_pointercal.sh-allow-skipping-calib.patch | 32 +++ .../xinput-calibrator_git.bb

Re: [OE-core] [PATCH][V2] sdkext: use simpler kernel module for devtool test

On Friday, September 6, 2019 6:56:26 A.M. EDT richard.pur...@linuxfoundation.org wrote: > On Thu, 2019-09-05 at 17:10 -0700, Michael Halstead wrote: > > On 9/5/19 2:27 PM, richard.pur...@linuxfoundation.org wrote: > > > On Thu, 2019-09-05 at 13:54 -0400, Mark Asselstine wrot

Re: [OE-core] [PATCH][V2] sdkext: use simpler kernel module for devtool test

On Thursday, August 22, 2019 11:56:16 A.M. EDT Mark Asselstine wrote: > The current devtool test for the building of an out-of-tree kernel > module uses something which requires several "high order" kconfigs to > be set. This results in the test failing, not for expected re

[OE-core] [PATCH][V2] sdkext: use simpler kernel module for devtool test

pler hello-world kernel module example will only require that CONFIG_MODULE is enabled, thus avoiding a false positive. Signed-off-by: Mark Asselstine --- **V2** - also updated the CROPS manual test json file (I have no idea how to run this so untested but this is a straight substition) - c

Re: [OE-core] [PATCH] sdkext: use simpler kernel module for devtool test

On Wednesday, August 21, 2019 4:57:40 P.M. EDT Richard Purdie wrote: > On Tue, 2019-08-20 at 13:52 -0400, Mark Asselstine wrote: > > The current devtool test for the building of an out-of-tree kernel > > module uses something which requires several "high order" kconfigs to

[OE-core] [PATCH] sdkext: use simpler kernel module for devtool test

pler hello-world kernel module example will only require that CONFIG_MODULE is enabled, thus avoiding a false positive. Signed-off-by: Mark Asselstine --- Richard, it is unclear if I need to match this change in meta/lib/oeqa/manual/crops.json. Please let me know and I send a V2 which does this. I

[OE-core] [PATCH] xfconf: fix 'Failed to get connection to xfconfd' during do_rootfs

upstream this appears to be an issue for xfconf and has an upstream update https://git.xfce.org/xfce/xfconf/commit?id=6f11cc65a2213f424728b5a0d25b1b63c19e773e Drawing from this change we can go ahead and use PACKAGECONFIG to emulate it. Signed-off-by: Mark Asselstine --- Guys, This is still broken

[OE-core] [v4][PATCH 1/2] go.bbclass: Export more GO* environment variables

polluting the build scripts with unnecessary exports, such as run.do_compile, we attempt to only export variables when they apply to a specific arch. Signed-off-by: Mark Asselstine --- V2 * Avoid potential undefined situations V3 * Add more exports to cover the basics * Tested on all qemu* variants

[OE-core] [v4][PATCH 2/2] goarch.bbclass: use MACHINEOVERRIDES and simplify go_map_arm()

of MACHINEOVERRIDES already consolidates the values of TUNE_FEATURES into something more consistent we can use the overrides mechanism to set GOARM, leaving just a little bit of logic in go_map_arm() to trigger off the arch (basically target vs host) for the setting of GOARM. Signed-off-by: Mark Asselstine --- V2

Re: [OE-core] [v3][PATCH 2/2] goarch.bbclass: use MACHINEOVERRIDES and simplify go_map_arm()

On Monday, March 18, 2019 12:40:28 PM EDT Martin Jansa wrote: > On Mon, Mar 18, 2019 at 11:21:53AM -0400, Mark Asselstine wrote: > > Per https://github.com/golang/go/wiki/GoArm we need to set GOARM when > > cross building for ARMv5, ARMv6 and ARMv7. The current approach of > >

[OE-core] [v3][PATCH 1/2] go.bbclass: Export more GO* environment variables

polluting the build scripts with unnecessary exports, such as run.do_compile, we attempt to only export variables when they apply to a specific arch. Signed-off-by: Mark Asselstine --- V2 * Avoid potential undefined situations V3 * Add more exports to cover the basics * Tested on all qemu* variants

[OE-core] [v3][PATCH 2/2] goarch.bbclass: use MACHINEOVERRIDES and simplify go_map_arm()

of MACHINEOVERRIDES already consolidates the values of TUNE_FEATURES into something more consistent we can use the overrides mechanism to set GOARM, leaving just a little bit of logic in go_map_arm() to trigger off the arch (basically target vs host) for the setting of GOARM. Signed-off-by: Mark Asselstine --- V2

Re: [OE-core] [v2][PATCH 2/2] goarch.bbclass: set TARGET_GOARM as '7' for valid cortexa* targets

On Friday, March 15, 2019 9:28:16 AM EDT Mark Asselstine wrote: > On Thursday, March 14, 2019 7:44:36 PM EDT Andre McCurdy wrote: > > On Thu, Mar 14, 2019 at 1:05 PM Mark Asselstine > > > > wrote: > > > Per https://github.com/golang/go/wiki/GoArm we need to

Re: [OE-core] [v2][PATCH 2/2] goarch.bbclass: set TARGET_GOARM as '7' for valid cortexa* targets

On Thursday, March 14, 2019 7:44:36 PM EDT Andre McCurdy wrote: > On Thu, Mar 14, 2019 at 1:05 PM Mark Asselstine > > wrote: > > Per https://github.com/golang/go/wiki/GoArm we need to set GOARM when > > building for ARMv5, ARMv6 and ARMv7. The current code in go_map_arm()

Re: [OE-core] [v2][PATCH 1/2] go.bbclass: Export GOARM

On Friday, March 15, 2019 12:39:26 AM EDT Khem Raj wrote: > On Thu, Mar 14, 2019 at 1:05 PM Mark Asselstine > > wrote: > > When building GO packages for ARM (v5, v6, v7) it is expected that the > > GOARM env variable is set during the build. Not having GOARM exported

Re: [OE-core] [PATCH 2/2] goarch.bbclass: set TARGET_GOARM as '7' for cortexa7

On Friday, March 15, 2019 1:42:55 AM EDT Khem Raj wrote: > On Wed, Mar 13, 2019 at 1:04 PM Mark Asselstine > > wrote: > > On Wednesday, March 13, 2019 3:56:10 PM EDT Andre McCurdy wrote: > > > On Wed, Mar 13, 2019 at 10:57 AM Mark Asselstine > > > > > >

[OE-core] [v2][PATCH 1/2] go.bbclass: Export GOARM

are building for 'arm' and only when recipes requiring/inheriting go.bbclass are be used to build for the target. Signed-off-by: Mark Asselstine --- V2 * Avoid potential undefined situations meta/classes/go.bbclass | 4 1 file changed, 4 insertions(+) diff --git a/meta/classes/go.bbclass b

[OE-core] [v2][PATCH 2/2] goarch.bbclass: set TARGET_GOARM as '7' for valid cortexa* targets

Cortex-A5 through Cortex-A17 as ARMv7 variants (ie. GOARM='7'). The Cortex-R and Cortex-M variants are also captured even though there are no tunings for these currently (lack MMU support so not supported). Signed-off-by: Mark Asselstine --- V2 * Cover all ARMv7 Cortex* variants meta/classes

Re: [OE-core] [PATCH 1/2] go.bbclass: Export GOARM

n 20 minutes or so and we'll see how it stands up. MarkA > > On Thu, Mar 14, 2019 at 11:32 AM Mark Asselstine < > > mark.asselst...@windriver.com> wrote: > > On Wednesday, March 13, 2019 3:40:18 PM EDT Christopher Larson wrote: > > > How would bitbake respond t

Re: [OE-core] [PATCH 1/2] go.bbclass: Export GOARM

ue is set to the empty > string for others? Unfortunately no. It is a parsing error. I am working on alternatives and will hopefully have something out shortly. MarkA > > On Wed, Mar 13, 2019 at 10:57 AM Mark Asselstine < > > mark.asselst...@windriver.com> wrote: > > When buil

Re: [OE-core] [PATCH 1/2] go.bbclass: Export GOARM

13, 2019 at 10:57 AM Mark Asselstine < > > mark.asselst...@windriver.com> wrote: > > When building GO packages for ARM (v5, v6, v7) it is expected that the > > GOARM env variable is set during the build. Not having GOARM exported > > will result in GO binaries whic

Re: [OE-core] [PATCH 2/2] goarch.bbclass: set TARGET_GOARM as '7' for cortexa7

On Wednesday, March 13, 2019 3:56:10 PM EDT Andre McCurdy wrote: > On Wed, Mar 13, 2019 at 10:57 AM Mark Asselstine > > wrote: > > The cortexa7 tunings use 'cortexa7' in their tunings and do not > > include 'arm7' so we need to look for both when setting TARGET_GOARM. >

[OE-core] [PATCH 1/2] go.bbclass: Export GOARM

are building for 'arm' and only when recipes requiring/inheriting go.bbclass are be used to build for the target. Signed-off-by: Mark Asselstine --- Richard, MarkH and I were debating this one some. He was suggesting I add 'GOARM ?= ""' so as not to leave things undefined for non-arm t

[OE-core] [PATCH 2/2] goarch.bbclass: set TARGET_GOARM as '7' for cortexa7

The cortexa7 tunings use 'cortexa7' in their tunings and do not include 'arm7' so we need to look for both when setting TARGET_GOARM. Signed-off-by: Mark Asselstine --- meta/classes/goarch.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/goarch.bbclass b

[OE-core] [PATCH] cpio: avoid conflict with tar-doc and rmt.8

but since the man pages are essentially the same we disambiguate the source of the man pages and make them both available should both cpio-doc and tar-doc are both installed. And as such we avoid the conflict. Signed-off-by: Mark Asselstine --- meta/recipes-extended/cpio/cpio_2.12.bb | 3 +++ 1 file

Re: [OE-core] [PATCH] man-pages: use alternatives to resolve crypt.3 conflict

On Wednesday, January 2, 2019 4:23:58 PM EST richard.pur...@linuxfoundation.org wrote: > On Wed, 2019-01-02 at 13:39 -0500, Mark Asselstine wrote: > > On Thursday, December 20, 2018 10:34:54 AM EST Mark Asselstine wrote: > > > From: mark asselstine > > > > > >

Re: [OE-core] [PATCH] man-pages: use alternatives to resolve crypt.3 conflict

On Thursday, December 20, 2018 10:34:54 AM EST Mark Asselstine wrote: > From: mark asselstine > > To fix: > > Error: Transaction check error: > file /usr/share/man/man3/crypt.3 conflicts between attempted installs > of libcrypt-doc-4.4.1-r0.core2_64 and man-p

[OE-core] [PATCH] man-pages: use alternatives to resolve crypt.3 conflict

From: mark asselstine To fix: Error: Transaction check error: file /usr/share/man/man3/crypt.3 conflicts between attempted installs of libcrypt-doc-4.4.1-r0.core2_64 and man-pages-4.16-r0.core2_64 This issue came about after commit 59be9254df9f [libxcrypt: Upgrade to 4.4.1 release

Re: [OE-core] [PATCH] meson.bbclass: Fix build issues with /tmp mounted with noexec

On Wednesday, October 10, 2018 4:32:56 PM EDT Nirbheek Chauhan wrote: > On Thu, Oct 11, 2018 at 1:50 AM Mark Asselstine > > wrote: > > Definitely a bug in that it doesn't propogate as an error. > > Note that compiler checks currently never raise an exception, and -1 &

Re: [OE-core] [PATCH] meson.bbclass: Fix build issues with /tmp mounted with noexec

On Wednesday, October 10, 2018 3:54:10 PM EDT Khem Raj wrote: > On Wed, Oct 10, 2018 at 12:36 PM Mark Asselstine > > wrote: > > Since commit d297f7ebf3f6 [fribidi: use Meson instead of autotools] > > build failures have been observed with this package. The immediate

[OE-core] [PATCH] meson.bbclass: Fix build issues with /tmp mounted with noexec

rectory and make use of TMPDIR to avoid this issue. Signed-off-by: Mark Asselstine --- meta/classes/meson.bbclass | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/classes/meson.bbclass b/meta/classes/meson.bbclass index ed08a40..7e63e12 100644 --- a/meta/classes/meson.bbclas

Re: [OE-core] [PATCH] recipe_links.bbclass: introduction

On Tuesday, May 29, 2018 3:22:54 PM EDT Khem Raj wrote: > On Mon, May 28, 2018 at 6:38 AM, Mark Asselstine > > wrote: > > This is a new class which can be used (for example via USER_CLASSES in > > local.conf) to make your build more development friendly. When > > incl

Re: [OE-core] [PATCH] recipe_links.bbclass: introduction

avin <alex.kana...@gmail.com>: > > 2018-05-28 16:38 GMT+03:00 Mark Asselstine <mark.asselst...@windriver.com>: > >> This is a new class which can be used (for example via USER_CLASSES in > >> local.conf) to make your build more development friendly. When > >

[OE-core] [PATCH] recipe_links.bbclass: introduction

-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/classes/recipe_links.bbclass | 79 +++ meta/conf/documentation.conf | 1 + 2 files changed, 80 insertions(+) create mode 100644 meta/classes/recipe_links.bbclass diff --git a/meta/c

Re: [OE-core] [PATCH 1/2] wayland: upgrade to 1.15.0

On Wednesday, May 9, 2018 12:16:30 PM EDT Burton, Ross wrote: > Good news: Denys beat you. I need to take long lunches more often. Thanks Denys for taking care of this. Mark > > Ross > > On 9 May 2018 at 17:09, Mark Asselstine <mark.asselst...@windriver.com> > > w

Re: [OE-core] [PATCH 1/2] wayland: upgrade to 1.15.0

On Wednesday, May 9, 2018 12:03:26 PM EDT Burton, Ross wrote: > On 9 May 2018 at 17:00, Mark Asselstine <mark.asselst...@windriver.com> > > wrote: > > I am also seeing build failures due to this conflict: > > > > ERROR: libglu-2_9.0.0-0 do_prepare_re

Re: [OE-core] [PATCH 1/2] wayland: upgrade to 1.15.0

On Tuesday, May 8, 2018 5:18:44 PM EDT Martin Jansa wrote: > On Tue, Apr 10, 2018 at 03:06:09PM -0400, Denys Dmytriyenko wrote: > > From: Denys Dmytriyenko > > > > Official announcement: > > https://lists.freedesktop.org/archives/wayland-devel/2018-April/037767.htm > > l > > > > |

Re: [OE-core] [PATCH] systemd: backport patch to fix build when gcrypt is enabled

On Wednesday, May 9, 2018 10:36:17 AM EDT Andrea Galbusera wrote: > Hi Mark! > > Il mer 9 mag 2018, 15:56 Mark Asselstine <mark.asselst...@windriver.com> ha > > scritto: > > On Wednesday, May 9, 2018 8:16:08 AM EDT Andrea Galbusera wrote: > > > When gcrypt

Re: [OE-core] [PATCH] systemd: backport patch to fix build when gcrypt is enabled

On Wednesday, May 9, 2018 8:16:08 AM EDT Andrea Galbusera wrote: > When gcrypt support is present in PACKAGECONFIG, build fails due to the bug > reported in [1]. Since this is already solved upstream, this commit > backports the corresponding patch. > > [1]

[OE-core] [PATCH] libcap: fix -native and usrmerge builds

l. When $root_prefix is "" this isn't noticed. By using $baselib we should not re-break the issue which commit 2c9c4a406a0f was fixing but we should avoid doubling down on the paths thus fixing the -native and usrmerge builds. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com&

Re: [OE-core] [PATCH v2 2/4] libcap: fix (base_)libdir usage

On Tuesday, May 8, 2018 2:26:47 PM EDT Mark Asselstine wrote: > On Tuesday, May 8, 2018 1:46:43 PM EDT Ricardo Salveti wrote: > > On Mon, Apr 16, 2018 at 10:00 AM, Koen Kooi <k...@dominion.thruhere.net> > > wrote: > > > The recipe wants to install libs into b

Re: [OE-core] [PATCH v2 2/4] libcap: fix (base_)libdir usage

On Tuesday, May 8, 2018 1:46:43 PM EDT Ricardo Salveti wrote: > On Mon, Apr 16, 2018 at 10:00 AM, Koen Kooi wrote: > > The recipe wants to install libs into base_libdir, but uses "basename > > $libdir" to derive that. That breaks in a multiarch setup. Use the proper >

Re: [OE-core] [PATCH 1/3] latencytop: remove recipe

On Tuesday, February 13, 2018 2:27:49 PM EST Randy MacLeod wrote: > On 2018-02-08 03:22 PM, Alexander Kanavin wrote: > > Last commit and release were in 2009; website is down; it's a dead > > project. > > Add MarkA who might care/know more about latencytop than I do. I believe Bruce had already

Re: [OE-core] [PATCH 1/2] gtk-doc: update to 1.27

On Friday, February 9, 2018 2:03:01 AM EST Alexander Kanavin wrote: > On 02/09/2018 12:13 AM, Mark Asselstine wrote: > > The use of libunique is non-consequential here. The issue is that the > > gtk-doc package has imports which are not going to be present via direct > > runt

Re: [OE-core] [PATCH 1/2] gtk-doc: update to 1.27

On Thursday, February 8, 2018 1:44:02 AM EST Alexander Kanavin wrote: > On 02/07/2018 11:34 PM, Mark Asselstine wrote: > > Alexander. When things move to python you can almost always bet on them > > requiring additional libraries and as such the lack of RDEPENDS here is a >

Re: [OE-core] [PATCH 1/2] gtk-doc: update to 1.27

he python-six recipe to oe-core or... I have added Derek to the CC as he is being a good sport and working hard on python recipes and might have thoughts on the best solution here. Mark Asselstine > ...r-out-if-perl-is-not-found-or-its-version.patch | 40 -- >

Re: [OE-core] [oe] [meta-python][PATCH] python-pyroute2: uprev to v0.4.21 (from 0.3.22)

On Monday, December 18, 2017 4:07:44 PM EST Derek Straka wrote: > I also need to look at the UPSTREAM_CHECK_URI for this recipe since it > isn't finding the latest version and telling me to update the package. Odd. Let me know how it goes. If it is easier for you to make the changes locally and

Re: [OE-core] [oe] [meta-python][PATCH] python-pyroute2: uprev to v0.4.21 (from 0.3.22)

I can respect this approach. I will put the RDEPENDS back and send out a V2. As for the overall approach being applied to all python recipes, my opinion still stands that this is such a small subset that we are devoting time better spent elsewhere to service the few. Mark > > -Derek > >

Re: [OE-core] [oe] [meta-python][PATCH] python-pyroute2: uprev to v0.4.21 (from 0.3.22)

On Mon, Dec 18, 2017 at 11:37 AM, Alexander Kanavin <alexander.kana...@linux.intel.com> wrote: > On 12/18/2017 06:15 PM, Mark Asselstine wrote: >> >> On Mon, Dec 18, 2017 at 10:36 AM, Christopher Larson <kerg...@gmail.com> >> wrote: >>> >>>

[OE-core] [PATCH 3/3] utils: qemurunner.py: cleanup grammar and ensure consistency

Minor grammar correction along with making the term 'login banner' consistent throughout to make searching logs easier. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/lib/oeqa/utils/qemurunner.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 2/3] utils: qemurunner.py: Log both 'failed to reach login banner" reasons

exhausted. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/lib/oeqa/utils/qemurunner.py | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/meta/lib/oeqa/utils/qemurunner.py b/meta/lib/oeqa/utils/qemurunner.py index 8296e98..dfcd63e 100644 ---

[OE-core] [PATCH 1/3] utils: qemurunner.py: Add wall clock to 'timeout' logging

in old logs also helps when debugging issues as we have a historic record as to what is a 'typical' time to complete an action. In addition to adding the wall clock times the time to 'login' is now printed making it consistent with the time to 'qemu pid'. Signed-off-by: Mark Asselstine

[OE-core] [PATCH 2/3] utils: qemurunner.py: Log both 'failed to reach login banner" reasons

exhausted. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/lib/oeqa/utils/qemurunner.py | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/meta/lib/oeqa/utils/qemurunner.py b/meta/lib/oeqa/utils/qemurunner.py index 2121a0d..f31c2ca 100644 ---

[OE-core] [PATCH 3/3] utils: qemurunner.py: cleanup grammar and ensure consistency

Minor grammar correction along with making the term 'login banner' consistent throughout to make searching logs easier. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/lib/oeqa/utils/qemurunner.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 1/3] utils: qemurunner.py: Add wall clock to 'timeout' logging

in old logs also helps when debugging issues as we have a historic record as to what is a 'typical' time to complete an action. In addition to adding the wall clock times the time to 'login' is now printed making it consistent with the time to 'qemu pid'. Signed-off-by: Mark Asselstine

Re: [OE-core] [IGNORE][PATCH] linux-yocto_4.12.bb: Use AUTOREV for qemu* BSPs

On Tuesday, October 24, 2017 5:21:35 PM EDT Bruce Ashfield wrote: > On Tue, Oct 24, 2017 at 5:17 PM, Mark Asselstine > > <mark.asselst...@windriver.com> wrote: > > The kernel we ship as part of product may have newer commits beyond > > any SRCREV captured in this r

[OE-core] [IGNORE][PATCH] linux-yocto_4.12.bb: Use AUTOREV for qemu* BSPs

to allow folks to set their own assignment it is most prudent to change these to AUTOREV here. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- Richard, Bruce, This is being sent only to conform with YP compliance and I don't expect or want this applied. No need to respond

[OE-core] [PATCH] gnome-themes-standard: drop .la file as unused

shared library file so instead of including this in the -dev pkg we simply drop it. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/recipes-gnome/gnome/gnome-themes-standard_3.22.3.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/recipes-gnome/gnome/gnome-

Re: [OE-core] [RFC] recipe_links.bbclass: introduction

On Friday, August 18, 2017 10:58:30 AM EDT Andre McCurdy wrote: > On Fri, Aug 18, 2017 at 8:44 AM, Mark Asselstine > > <mark.asselst...@windriver.com> wrote: > > This is a new class which can be used (for example via USER_CLASSES in > > local.conf) to make your buil

[OE-core] [RFC] recipe_links.bbclass: introduction

-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/classes/recipe_links.bbclass | 79 +++ meta/conf/documentation.conf | 1 + 2 files changed, 80 insertions(+) create mode 100644 meta/classes/recipe_links.bbclass diff --git a/meta/c

[OE-core] [PATCH v2] python: don't include -tests with modules

modified accordingly, providing a generic mechanism to exclude modules from the 'all modules' package. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- *** v2 Updated the generator script missed in the v1 and pointed out by RP. meta/recipes-devtools/python/pyth

Re: [OE-core] [PATCH] python: don't include -tests with modules

On Thursday, July 27, 2017 10:39:07 PM EDT Richard Purdie wrote: > On Mon, 2017-07-24 at 12:10 -0400, Mark Asselstine wrote: > > Although 'test' is listed in the python module list > > (https://docs.python.org/3/py-modindex.html) it is meant only to be > > used 'internally

[OE-core] [PATCH] python: don't include -tests with modules

the above warnings. Additionally this module is one of the largest py modules going, by dropping this unneeded module from the 'modules' package we can reduce overall image size, something which is important for many embedded deployments. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.

[OE-core] [PATCH v2] python3: fix weakref spewing exceptions during interp finalization

quick search this was found to be a well reported issue upstream and had an appropriate fix which is backported here. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- v2: Add patch author SOB to embedded patch after failing Patchwork's patchtest. ...eakref-spewing-excep

[OE-core] [PATCH] python3: fix weakref spewing exceptions during interp finalization

quick search this was found to be a well reported issue upstream and had an appropriate fix which is backported here. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- ...eakref-spewing-exceptions-during-interp-f.patch | 55 ++ meta/recipes-devtools/pyth

[OE-core] [PATCH v2] attr: Fix build failure when image includes man-pages pkg

the conflicted files in favour of those in the man-pages package. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- v2: Fixed case in Upstream-Status meta/recipes-support/attr/attr_2.4.47.bb | 2 + ...ve-the-attr.5-man-page-moved-to-man-pages.patch

Re: [OE-core] [PATCH] attr: Fix build failure when image includes man-pages pkg

On Tuesday, June 13, 2017 9:13:28 PM EDT Burton, Ross wrote: > On 13 June 2017 at 19:46, Mark Asselstine <mark.asselst...@windriver.com> > > wrote: > > Yet the 'Upstream-status' is marked in the same way for both patches. So I > > am > > ingnoring this unless

Re: [OE-core] [PATCH] attr: Fix build failure when image includes man-pages pkg

On Tuesday, June 13, 2017 2:08:11 PM EDT Mark Asselstine wrote: > If you attempt to build an image with both attr(-doc) and man-pages > packages your rootfs might fail to assemble. The error will be > something like: > > Error: Transaction check error: > file /usr/share/ma

[OE-core] [PATCH] attr: Fix build failure when image includes man-pages pkg

the conflicted files in favour of those in the man-pages package. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/recipes-support/attr/attr_2.4.47.bb | 2 + ...ve-the-attr.5-man-page-moved-to-man-pages.patch | 240 .../files/Remove-the-section

Re: [OE-core] [meta-oe][resend][PATCH] sysstat: fixup pkg_postinst to allow SYSTEMD_AUTO_ENABLE to work

On Tuesday, May 9, 2017 4:51:37 PM EDT Mark Asselstine wrote: > The logic added to the pkg_postinst in commit 6bf82c26f953 has the > side effect of rendering SYSTEMD_AUTO_ENABLE ineffective. The systemd > service will not be configured as 'enabled' either offline(do_rootfs) > or durin

[OE-core] [meta-oe][resend][PATCH] sysstat: fixup pkg_postinst to allow SYSTEMD_AUTO_ENABLE to work

with systemd we can simply skip the pkg_postinst when not using sysvinit. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/recipes-extended/sysstat/sysstat.inc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/meta/recipes-extended/sysstat/sysstat.inc

Re: [OE-core] [oe] State of bitbake world, Failed tasks 2017-03-11

On Sat, Mar 11, 2017 at 1:02 PM, Martin Jansa wrote: > This time the results are very inconsistent across different MACHINEs > because they were using significantly different metadata. > > qemuarm is oldest 3 from 4 failures were causes by pending meta-oe > changes which

Re: [OE-core] [PATCH 1/3] go: Add recipes for golang compilers and tools

On Wednesday, February 8, 2017 9:17:48 AM EST Paul Eggleton wrote: > On Tuesday, 7 February 2017 9:44:46 AM NZDT Khem Raj wrote: > > On Tue, Feb 7, 2017 at 9:35 AM, Burton, Ross wrote: > > > On 7 February 2017 at 04:24, Khem Raj wrote: > > >> This is

[OE-core] [V2][PATCH] sysklogd: do more to properly work with systemd

and the expected logs are available. Unfortunately I was not able to find any work done on this upstream or in other distros so this is my best effort at making this work. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- ** V2 ** * update to not break sysvinit builds

Re: [OE-core] [PATCH] systemd: disable 'libdir' QA check

On Monday, December 12, 2016 9:17:14 PM EST Burton, Ross wrote: > On 12 December 2016 at 20:51, Mark Asselstine <mark.asselst...@windriver.com > > wrote: > > > > I think the discussion I pointed to in the commit log closes the door on > > any > > such chang

Re: [OE-core] [PATCH] systemd: disable 'libdir' QA check

On Monday, December 12, 2016 11:59:04 AM EST Khem Raj wrote: > > On Dec 12, 2016, at 11:36 AM, Mark Asselstine > > <mark.asselst...@windriver.com> wrote: > > > > When building systemd with multilib support enabled in your build you > > will get the following Q

[OE-core] [PATCH] systemd: disable 'libdir' QA check

contain any other libraries we can respect the upstream placement and skip this QA check for these packages. Unfortunately the QA mechanism doesn't allow us to specify individual files so this approach is the best we can do. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/r

[OE-core] [PATCH] sysklogd: do more to properly work with systemd

and the expected logs are available. Unfortunately I was not able to find any work done on this upstream or in other distros so this is my best effort at making this work. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/recipes-extended/sysklogd/files/klogd.service

[OE-core] [PATCH] sysstat: fixup pkg_postinst to allow SYSTEMD_AUTO_ENABLE to work

with systemd we can simply skip the pkg_postinst when not using sysvinit. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/recipes-extended/sysstat/sysstat.inc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/meta/recipes-extended/sysstat/sysstat.inc

[OE-core] [PATCH] systemd.bbclass: don't block on service restart

attempting to start or restart any service will result in the call get stuck on poll(). Since the run_postinsts.service does not monitor the outcome of the call to restart we can work around this by using '--no-block'. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> ---

Re: [OE-core] [PATCHv3 10/30] vte: Upgrade to 0.44.1

On Wednesday, June 22, 2016 9:18:10 PM EDT Burton, Ross wrote: > On 22 June 2016 at 19:24, Andreas Müller > > wrote: > > Could we move vte to meta-oe to avoid further world blacklisting? > > This was the agreement in the other thread - Mark was going to restore the

Re: [OE-core] [RFC][PATCH] vte: bring back old version to support xfce4-terminal

On June 17, 2016 20:43:06 Jussi Kukkonen wrote: > On 17 June 2016 at 16:33, Mark Asselstine <mark.asselst...@windriver.com> > > wrote: > > On June 16, 2016 18:10:09 Andre McCurdy wrote: > > > On Thu, Jun 16, 2016 at 2:47 PM, Burton, Ross <ross.bur...@intel.com>

Re: [OE-core] [RFC][PATCH] vte: bring back old version to support xfce4-terminal

On June 16, 2016 18:10:09 Andre McCurdy wrote: > On Thu, Jun 16, 2016 at 2:47 PM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 16 June 2016 at 21:49, Mark Asselstine <mark.asselst...@windriver.com> > > > > wrote: > >> While waiting to hear back

[OE-core] [RFC][PATCH] vte: bring back old version to support xfce4-terminal

'0.0' was selected to match the api version string used by the the upstream vte project. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- While waiting to hear back about my inquiry I did take some time to put together this patch that allows things that require the old

Re: [OE-core] [PATCHv3 10/30] vte: Upgrade to 0.44.1

On 14 June 2016 at 11:14, Jussi Kukkonen > wrote: > > * License change LGPL 2.0 -> LGPL 2.1+ > * vte-termcap is no more > * API break: current version seems to be parallel installable >with old one, but I did not opt

[OE-core] [PATCH 2/2] useradd_base.bbclass: prevent variable expansion in $opts

[useradd_base.bbclass: replace retry logic with flock]. Signed-off-by: Mark Asselstine <mark.asselst...@windriver.com> --- meta/classes/useradd_base.bbclass | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/meta/classes/useradd_base.bbclass b/meta/c

[OE-core] [PATCH 1/2] extrausers.bbclass: drop retry count for perform_user/group* calls

Commit 2ebf697b46c42cee8bfa6d2e6087397f8cce385c [useradd_base.bbclass: replace retry logic with flock] dropped the 3rd (retry) parameter for these functions. These are simply being ignored now but we should remove the retry count to avoid confusion. Signed-off-by: Mark Asselstine <mark.asse

[OE-core] [PATCH] openssl: add a vardeps for configure on libdir

whenever 'libdir' is modified. This will fix both target and -native builds per the usecases described above. If 'libdir' is unchanged things continue to function as they did before and a re-configure will not happen. Signed-off-by: Mark Asselstine mark.asselst...@windriver.com --- meta/recipes

  1   2   >