From: Chris Laplante
When building librsvg-native from meta-lts-mixins, we need to be able to
pass extra pkgconfig paths.
See
https://lists.yoctoproject.org/g/yocto-patches/topic/meta_lts_mixins_scarthgap_rust/110997188
Alexander Kanavin (1):
pkg-config-native: pick additional search paths
wrapper, instead of resetting it,
is not an option as that can lead to contamination with the cross values).
(From OE-Core rev: 2bc050146d47b14d890a1b0db2b55f9057a08b65)
Signed-off-by: Alexander Kanavin
Signed-off-by: Mathieu Dubois-Briand
Signed-off-by: Richard Purdie
Signed-off-by: Chris Laplante
Hi Alex,
> On Mon, 3 Feb 2025 at 23:19, Chris Laplante via lists.openembedded.org
> wrote:
> > Would this be the kind of thing that is best ported to
> > bitbake-diffsigs, maybe as some kind of recursive mode? (Just asking
> > out of curiosity - I don't yet have a s
Hi Richard,
> I've never liked that script and personally, I've always wanted to make
> bitbake's
> owm signature "diff" as helpful as we can. There are ton of different things
> that conspire against us in doing that and whilst we've improved, it still
> isn't
> ideal.
>
> I'd note that the sc
Hi all,
We are on Scarthgap, and I am seeing an issue with sstate-diff-machines.sh
wherein the script claims to see task signature differences, but then doesn't
report any. For example, I get:
ERROR: base-files different signature for task do_package_write_rpm.sigdata
between my-machine-1 and
From: Chris Laplante
Signed-off-by: Chris Laplante
---
scripts/lib/devtool/standard.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index 305536f6f0..ca89c8e882 100644
--- a/scripts/lib/devtool/standard.py
From: Chris Laplante
Signed-off-by: Chris Laplante
---
scripts/lib/devtool/standard.py | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index ca89c8e882..20c94616b2 100644
--- a/scripts/lib/devtool
From: Chris Laplante
The 'devtool' cases make a copy of 'poky', but before this patch, that
only included modifications to the 'meta/' subdirectory.
It's very frustrating to make changes to scripts/ and have them be
silently ignored by oe-selftest.
Signed-of
From: Chris Laplante
Signed-off-by: Chris Laplante
---
scripts/lib/devtool/standard.py | 41 ++---
scripts/lib/devtool/upgrade.py | 1 +
2 files changed, 24 insertions(+), 18 deletions(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool
From: Chris Laplante
The goal is to make this more Pythonic, as it was a little cryptic the
first time I looked at it.
Signed-off-by: Chris Laplante
---
scripts/lib/devtool/standard.py | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/scripts/lib/devtool
From: Chris Laplante
v1: initial
v2: shorten commit message to appease patchtest
Chris Laplante (5):
devtool: standard: cleanup imports; stop relying on transitive bb
imports
devtool: standard: fix typo in variable
devtool: standard: fix unbound variable usage
devtool: standard
From: Chris Laplante
Signed-off-by: Chris Laplante
---
scripts/lib/devtool/standard.py | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index ca89c8e882..20c94616b2 100644
--- a/scripts/lib/devtool
From: Chris Laplante
It's very frustrating to make changes to scripts/ and have them be
silently ignored by oe-selftest.
Signed-off-by: Chris Laplante
---
meta/lib/oeqa/selftest/cases/devtool.py | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/sel
From: Chris Laplante
The goal is to make this more Pythonic, as it was a little cryptic the
first time I looked at it.
Signed-off-by: Chris Laplante
---
scripts/lib/devtool/standard.py | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/scripts/lib/devtool
From: Chris Laplante
Signed-off-by: Chris Laplante
---
scripts/lib/devtool/standard.py | 41 ++---
scripts/lib/devtool/upgrade.py | 1 +
2 files changed, 24 insertions(+), 18 deletions(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool
From: Chris Laplante
Signed-off-by: Chris Laplante
---
scripts/lib/devtool/standard.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index 305536f6f0..ca89c8e882 100644
--- a/scripts/lib/devtool/standard.py
From: Chris Laplante
This should fix
https://valkyrie.yoctoproject.org/#/builders/80/builds/725/steps/13/logs/stdio
Signed-off-by: Chris Laplante
---
scripts/devtool | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/devtool b/scripts/devtool
index ebd3e4c11b
>
> On Sun, 12 Jan 2025 at 15:55, Chris Laplante via lists.openembedded.org
> wrote:
> > This patchset removes global variables from the 'devtool' script. It
> > also changes `Context` to be a dataclass.
>
> Thanks, these changes look really
Hi Mathieu,
> Hi Chris,
>
> I believe this series is breaking some builds on the autobuilder. We got the
> following error:
>
> devtool: error: argument : invalid choice: 'sdk-install' (choose
> from create-workspace, add, modify, extract, sync, rename, update-recipe,
> status, reset, finish, ed
From: Chris Laplante
Signed-off-by: Chris Laplante
---
scripts/devtool | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts/devtool b/scripts/devtool
index acc4e0e982..d7a5903c9f 100755
--- a/scripts/devtool
+++ b/scripts/devtool
@@ -15,7 +15,6 @@ import re
From: Chris Laplante
Signed-off-by: Chris Laplante
---
scripts/devtool | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts/devtool b/scripts/devtool
index 1994d4b507..ebd3e4c11b 100755
--- a/scripts/devtool
+++ b/scripts/devtool
@@ -95,7 +95,7 @@ def
From: Chris Laplante
'read_workspace' can now access it via the 'context' that's passed in
Signed-off-by: Chris Laplante
---
scripts/devtool | 20
1 file changed, 8 insertions(+), 12 deletions(-)
diff --git a/scripts/devtool b/scripts/devtool
ind
From: Chris Laplante
This patchset removes global variables from the 'devtool' script. It
also changes `Context` to be a dataclass.
All devtool self-tests pass, tested via: oe-selftest -r devtool
Chris Laplante (7):
devtool: un-globalize the 'basepath' variable
d
From: Chris Laplante
It never had to be a global anyway
Signed-off-by: Chris Laplante
---
scripts/devtool | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/scripts/devtool b/scripts/devtool
index d96d25a51a..b43a958497 100755
--- a/scripts/devtool
+++ b/scripts/devtool
From: Chris Laplante
1. Bad None comparison
2. Reliance on transitive includes in bb
3. Unbound 'ret' variable
Signed-off-by: Chris Laplante
---
scripts/devtool | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/scripts/devtool b/scripts/devtool
index
From: Chris Laplante
Please excuse the usage of 'typing' slipping in here - it's just how
dataclasses work :/.
Signed-off-by: Chris Laplante
---
scripts/devtool | 32 +++-
1 file changed, 19 insertions(+), 13 deletions(-)
diff --git a/scripts/de
From: Chris Laplante
Signed-off-by: Chris Laplante
---
scripts/devtool | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/scripts/devtool b/scripts/devtool
index 60ea3e8298..acc4e0e982 100755
--- a/scripts/devtool
+++ b/scripts/devtool
@@ -13,10 +13,8
Hi Richard,
> > Internally, my experience has been that users do not notice the
> > 'devtool' branch has been checked out. They go to push their changes
> > and end up creating a bizarre 'devtool' branch on the remote, which
> > obviously doesn’t get picked up by our build.
> >
> > In the case of
Hi Richard, Alex,
> > > Even if we take DEVTOOL_PREFER_BRANCH out of the equation, I think
> > > that's also true for a recipe that just uses SRCREV = "${AUTOREV}".
> >
> > I was also wondering if this new variable is really needed. Perhaps
> > devtool should just do the logical thing automaticall
> Hi Alex,
>
> > Will devtool finish and devtool reset do the right thing as well when
> > this is used?
> >
> > Alex
> >
> > On Fri 1. Nov 2024 at 20.38, Chris Laplante via
> > https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fli
Hi Alex,
> Will devtool finish and devtool reset do the right thing as well when this is
> used?
>
> Alex
>
> On Fri 1. Nov 2024 at 20.38, Chris Laplante via
> http://lists.ope/
> nembedded.org%2F&data=05%7C02%7Cchris.laplante%40agilent.com%7C8f50
&g
From: Chris Laplante
Provide a per-recipe opt-out for devtool's default behavior of using the
'devtool'
branch. This is primarily intended for company-internal recipes (e.g. on private
layers) that use floating upstream SRCREV. It is assumed that such recipes do
not care about
Hi Richard, Peter,
> > You might want to leave the test since there are ways you could set
> > this which will make it hard to disable :(
> >
> > A simple example would be:
> >
> > SANITY_TESTES_DISTROS:poky = "x y z"
> >
> > which is why this wasn't automated.
> >
> > Cheers,
> >
> > Richard
>
>
From: Chris Laplante
It always has to be done, so just do it.
[YOCTO #11933]
Signed-off-by: Chris Laplante
---
meta/lib/oeqa/selftest/context.py | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/meta/lib/oeqa/selftest/context.py
b/meta/lib/oeqa/selftest/context.py
Hi Khem,
> opengl in OE context is usually not the same as desktop GL, it means the
> distro
> needs OpenGL supported from the platform.
> It is then accentuated by other things like egl glesv2, glx etc. I think we
> could
> make it a bit better but this is something that sits in the middle of d
Hi all,
Just want to check my understanding on something. It seems to me that the
Weston having:
REQUIRED_DISTRO_FEATURES = "wayland opengl
${@oe.utils.conditional('VIRTUAL-RUNTIME_init_manager', 'systemd', 'pam', '',
d)}"
...is overly restrictive because 'opengl' implies desktop OpenGL, wher
Hi Alexandre,
> The series causes:
>
> 2023-10-17 23:07:15,509 - oe-selftest - INFO -
> devtool.DevtoolUpgradeTests.test_devtool_modify_kernel_overrides
> (subunit.RemotedTestCase)
> 2023-10-17 23:07:15,675 - oe-selftest - INFO - ... FAIL
> Stderr:
> 2023-10-17 22:28:35,773 - oe-selftest - INFO
> Hello,
>
> The series causes:
>
> 2023-10-17 23:07:15,509 - oe-selftest - INFO -
> devtool.DevtoolUpgradeTests.test_devtool_modify_kernel_overrides
> (subunit.RemotedTestCase)
> 2023-10-17 23:07:15,675 - oe-selftest - INFO - ... FAIL
> Stderr:
> 2023-10-17 22:28:35,773 - oe-selftest - INFO - A
Hi Bruce,
> > Is setting up MACHINE too invasive? Or do we come up with a way of only
> setting up override branches for overrides that are valid for the given
> local.conf? I lean towards the latter approach for simplicity.
> >
>
> I admit to not using devtool, and not following much of what has
> Ugh, actually this needs more work. If a recipe sets KBUILD_DEFCONFIG based
> on MACHINE overrides, then the no-override case will explode when we call
> 'kernel_pre_patch(localdata)'. Since in that case, KBUILD_DEFCONFIG will be
> unset.
Actually, this approach is problematic in general because
> From: Chris Laplante
>
> Fixes a couple of different issues that all conspired to break 'devtool
> modify' for
> many use cases with kernel-yocto recipes.
>
> To explain, we need to consider the basic flow of how 'devtool modify'
> w
From: Chris Laplante
This relatively exhaustive test is designed to exercise the 'devtool
modify' workflow for kernel recipes, with a focus on SRC_URI override
branches.
Signed-off-by: Chris Laplante
---
meta/lib/oeqa/selftest/cases/devtool.py | 132
1 fi
From: Chris Laplante
Call _check_src_repo to confirm that the 'devtool' branch is setup as we
expect. This would have caught the basic case of the bug (i.e. where
override branches are not involved).
Signed-off-by: Chris Laplante
---
meta/lib/oeqa/selftest/cases/devtool.py | 1
From: Chris Laplante
Fixes a couple of different issues that all conspired to break 'devtool
modify' for many use cases with kernel-yocto recipes.
To explain, we need to consider the basic flow of how 'devtool modify'
works for a recipe using
> FYI I also sent a patch to fix this issue the day just before you :) You can
> find it
> here:
> https://lists.op/
> enembedded.org%2Fg%2Fopenembedded-
> core%2Fmessage%2F188767&data=05%7C01%7Cchris.laplante%40agilent.com
> %7C34ce8f731f6f4590172108dbc89c6739%7Ca9c0bc098b46420693512ba12fb
> 4a5c
Hi Alexandre,
>
> Thank you for your patches!
>
> Could you remember changing your git config for your next submission:
> https://docs.yo/
> ctoproject.org%2Fnext%2Fcontributor-guide%2Fsubmit-
> changes.html%23fixing-your-from-
> identity&data=05%7C01%7Cchris.laplante%40agilent.com%7Cd8e4bf9a3b674
tinfoil.prepare will fail. But because tinfoil.shutdown
doesn't get called, the thread spawned by bb.server.process.BBUIEventQueue
spins forever and recipetool never exits, hanging the test.
Signed-off-by: Chris Laplante
---
scripts/recipetool | 16 +---
1 file changed, 5 insertions(+
The tests will fail anyway (since you will have two 'workspacelayer'
layers), so might as well make it fail faster and be clear.
Signed-off-by: Chris Laplante
---
meta/lib/oeqa/selftest/cases/devtool.py | 36 ++---
1 file changed, 33 insertions(+), 3 deletions(-)
Hi Richard,
Thanks for accepting my patch from a few days ago :). Just wanted to check if
you would like me to send more Python 3.12 compatibility patches. If there are
bigger fish to fry I will hold off, otherwise I'm happy to help with making
everything compatible.
P.S. I ask because I didn'
'imp' was deprecated in Python 3.4 and removed in 3.12. The
piece of importlib we use has been around since 3.3.
Signed-off-by: Chris Laplante
---
scripts/lib/recipetool/create_buildsys_python.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/scripts/lib/
> On Thu, 14 Sept 2023 at 21:54, Richard Purdie
> wrote:
> > The tools are already supposed to support doing this with local file
> > sstate sources, they just do a bad job at getting the diffs right. One
> > intent of this work item was to try and understand why they don't work
> > and address th
> The bitbake-layers command is needed only to generate the layer config file
> (in json format) out of an already existing yocto setup. It does not perform
> the actual layer fetch/setup from the json. That's the feature I like the most
> in my proposal: none of the other tools bootstrap the confi
Hi Alex,
> do you think any of these pieces could be moved to 'official yocto',
> specifically as bitbake-layers subcommands? I read through the README, and
> it seems that things like 'status' and 'run' would fit very well there.
I would agree that 'status' and 'run' would be useful additions, t
Hi all,
Today I'm excited to publish a tool I've been developing internally for about a
year now. It is called 'yb', and you can think of it like a cross between kas,
Google's repo, and myrepos (mr).
Project page: https://github.com/Agilent/yb
Download it here: https://github.com/Agilent/yb/rel
We're using honister. We have a recipe that generates a device tree using
devicetree.bbclass. It doesn't do anything special:
SRC_URI = file://system-top.dts
DT_INCLUDE:append = " ${THISDIR}/files"
COMPATIBLE_MACHINE:zynq = "zynq"
inherit devicetree
It's unclear to me how this i
We're using honister. We have a recipe that generates a device tree using
devicetree.bbclass. It doesn't do anything special:
SRC_URI = file://system-top.dts
DT_INCLUDE:append = " ${THISDIR}/files"
COMPATIBLE_MACHINE:zynq = "zynq"
inherit devicetree
It's unclear to me how this i
Hello,
We're using honister. We have a recipe that generates a device tree using
devicetree.bbclass. It doesn't do anything special:
SRC_URI = file://system-top.dts
DT_INCLUDE:append = " ${THISDIR}/files"
COMPATIBLE_MACHINE:zynq = "zynq"
inherit devicetree
It's unclear to me ho
Hi all,
We are using Yocto Zeus (yes, I know...) and I'm trying to track down some
reproducibility issues. My go-to tool is bitbake-diffsigs, but ever since we
started using multiconfig, the tool is pretty much useless with results like
this:
(where mc-one and mc-two are multiconfigs)
NOTE:
Hi Anuj,
> Thanks, this is the right way to request a backport. But since this is a
> bitbake
> change, should have been sent to the bitbake list. I had picked this though so
> no need to re-send.
Ah right. Thank you!
Chris
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this g
Hello,
> If the client process never sends cooker data, the server timeout will be 0.0,
> not None. This will prevent the server from exiting, as it is waiting for a
> new
> client. In particular, the client will disconnect with a bad "INHERIT" line,
> such
> as:
>
> INHERIT += "this-class-
From: Joshua Watt
From: Chris Laplante
If the client process never sends cooker data, the server timeout will
be 0.0, not None. This will prevent the server from exiting, as it is
waiting for a new client. In particular, the client will disconnect with
a bad "INHERIT" lin
Hello all,
Can someone please clarify expected behavior of 'devtool modify virtual/kernel'
when the kernel recipe has an additional SRC_URI entry for the kernel-metadata
repository? For example, the 2021.1 linux-xlnx recipe in the meta-xilinx-bsp
layer (part of meta-xilkinx) uses the following:
> > But it would happen even without multiconfig, if there is overlap in
> > the node modules that two recipes try to fetch. For some reason the
> > npmsw fetcher (or the proxy fetcher it is using, see
> > bitbake/lib/bb/fetch2/npmsw.py around lines 168-181) are not guarding
> > against two recipes
Hi Richard,
> >
> > +do_fetch[lockfiles] += "${DL_DIR}/npm2_fetch.lock"
> > +
> > def npm_global_configs(d):
> > """Get the npm global configuration"""
> > configs = []
>
> If its just multilib, you could put a ${BPN} in the lock name? or is it
> conflicting
> general recipes?
multic
From: Chris Laplante
The npmsw fetcher doesn't play nice with multiconfig for some reason.
Concurrent do_fetch tasks for npm recipes can try to download modules at
the same time to ${DL_DIR}/npm2, resulting in races and failed
downloads.
Signed-off-by: Chris Laplante
---
meta/cl
From: Chris Laplante
I didn't have time to dig into the npmsw fetcher to understand exactly
why the conflicts happen, but this fixes things in the meantime.
Chris Laplante (1):
classes/npm: utilize lockfile in do_fetch to avoid multiconfig
problems
meta/classes/npm.bbclass | 2
The previous message was fairly useless without diving into the bbclass.
Signed-off-by: Chris Laplante
---
meta/classes/systemd.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/systemd.bbclass b/meta/classes/systemd.bbclass
index 9ec465c759..db5d109545
From: Chris Laplante
This is useful for people using Microsoft Exchange / Office 360, which
butchers patches causing author identity to be lost.
Signed-off-by: Chris Laplante
---
contrib/git-hooks/sendemail-validate.sample | 78 +
1 file changed, 78 insertions(+)
create
From: Chris Laplante
This is because the test expects to find "do_package_write_rpm" in the
bitbake output.
Signed-off-by: Chris Laplante
---
meta/lib/oeqa/selftest/cases/bbtests.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/lib/oeqa/selftest/cases/bbtests.py
b/met
> > Is this patch something that should be backported to zeus and friends?
>
> Its fixing a very rare problem that I only ran into whilst doing "interesting"
> things most people don't probably do.
>
> If people were running into those issues I'd backport but for master it was
> more a correctnes
Hi Richard,
> Most recipe-sysroot dependencies are handled by these prefuncs. "configure"
> is special with a decidated task, prepare_recipe_sysroot which runs
> beforehand.
>
> do_prepare_recipe_sysroot does not have to be run before/after
> fetch/unpack/patch, they're independent tasks. If fetc
Default behavior is not changed. To suppress patched CVEs, set:
CVE_CHECK_REPORT_PATCHED = ""
Signed-off-by: Chris Laplante
---
meta/classes/cve-check.bbclass | 38 --
1 file changed, 22 insertions(+), 16 deletions(-)
diff --git a/meta/c
The addition of this variable also makes it possible to change the
output suffix of the check files, e.g. in local.conf:
CVE_CHECK_MANIFEST_append = ".txt"
CVE_CHECK_RECIPE_FILE_append = ".txt"
Signed-off-by: Chris Laplante
---
meta/classes/cve-check.bbclass | 8 ---
Signed-off-by: Chris Laplante
---
meta/conf/bitbake.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index a318d1ca58..e6338b0c75 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -701,7 +701,7
Signed-off-by: Chris Laplante
---
meta/recipes-core/meta/cve-update-db-native.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-core/meta/cve-update-db-native.bb
b/meta/recipes-core/meta/cve-update-db-native.bb
index e4e2451bfd..c2f713312f 100644
--- a/meta
Signed-off-by: Chris Laplante
---
meta/recipes-core/meta/cve-update-db-native.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-core/meta/cve-update-db-native.bb
b/meta/recipes-core/meta/cve-update-db-native.bb
index 242fbc2f30..cf2b251e21 100644
--- a/meta/recipes-core/meta
It was always questionable to do this in an anonymous function, but now
with multiconfig it is a critical mistake and leads to more strange
"Exception: sqlite3.OperationalError: disk I/O error" errors.
Signed-off-by: Chris Laplante
---
meta/recipes-core/meta/cve-update-db-nati
)
0101:
0102:cve_f.close()
*** 0103:conn.commit()
0104:conn.close()
0105:}
0106:
0107:def initialize_db(c):
Exception: sqlite3.OperationalError: disk I/O error
Use a lockfile to ensure multiple tasks don't step over each ot
Signed-off-by: Chris Laplante
---
.../recipes-core/meta/cve-update-db-native.bb | 90 ++-
1 file changed, 47 insertions(+), 43 deletions(-)
diff --git a/meta/recipes-core/meta/cve-update-db-native.bb
b/meta/recipes-core/meta/cve-update-db-native.bb
index 32d6dbdffc..2221825bf8
---
meta/recipes-core/meta/cve-update-db-native.bb | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/meta/recipes-core/meta/cve-update-db-native.bb
b/meta/recipes-core/meta/cve-update-db-native.bb
index d22b66f6c7..328f6ab364 100644
--- a/meta/recipes-core/meta/cve-update-db
For example, if you just run 'bitbake cve-update-db-native' in a clean
build system, |cve_tmp_file| won't exist yet.
Signed-off-by: Chris Laplante
---
meta/classes/cve-check.bbclass | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/meta/classes/cv
v1: initial
v2: use lockfile in cve-update-db-native as suggested by Ross Burton
Chris Laplante (4):
cve-update-db-native: add progress handler
cve-check/cve-update-db-native: use lockfile to fix usage under
multiconfig
cve-update-db-native: use context manager for cve_f
cve-check
> > But the databases will be identical so that's basically a waste of
> > time. How about adding a lock file so the second task waits for the
> > first to complete, and then does nothing as the database is up to date?
>
> That's a good point. I also considered just making it a bb.event.BuildStar
> On Wed, 9 Sep 2020 at 18:35, Chris Laplante via lists.openembedded.org
> wrote:
> >
> > Previously CVE_CHECK_DB_FILE / CVE_CHECK_DB_DIR was the same
> across
> > multiconfigs which led to a race condition wherein multiple
> > cve-update-db-native:do_populate_cv
Signed-off-by: Chris Laplante
---
.../recipes-core/meta/cve-update-db-native.bb | 90 ++-
1 file changed, 47 insertions(+), 43 deletions(-)
diff --git a/meta/recipes-core/meta/cve-update-db-native.bb
b/meta/recipes-core/meta/cve-update-db-native.bb
index 32d6dbdffc..2221825bf8
of
separation.
Signed-off-by: Chris Laplante
---
meta/classes/cve-check.bbclass | 2 +-
meta/recipes-core/meta/cve-update-db-native.bb | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 0889e
---
meta/recipes-core/meta/cve-update-db-native.bb | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/meta/recipes-core/meta/cve-update-db-native.bb
b/meta/recipes-core/meta/cve-update-db-native.bb
index 57368caf73..f8f13af97c 100644
--- a/meta/recipes-core/meta/cve-update-db
For example, if you just run 'bitbake cve-update-db-native' in a clean
build system, |cve_tmp_file| won't exist yet.
Signed-off-by: Chris Laplante
---
meta/classes/cve-check.bbclass | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/meta/classes/cv
Hi Richard,
> This looks interesting. Could we add something to the manual about how to
> use it and maybe a test for it as well please?
Halfway through writing the tests, and I realized
LOG_COLORIZER_SUPPRESS_COLORIZED_OUTPUT doesn’t quite work. I wrote a test
recipe with a do_compile that pu
Hi Richard,
> You can run these tests individually with "oe-selftest -r imagefeatures" to
> run
> that file or "oe-selftest -r imagefeatures.ImageFeatures.test_bmap" as an
> example of a specific test.
I'm developing the tests for log colorizer and I had a question about
oe-selftest. Is there a
Hi Richard,
> This looks interesting. Could we add something to the manual about how to
> use it and maybe a test for it as well please?
>
> I did write something similar in a different context recently which applies
> here near enough as well:
>
> """
> By documentation, I mean that kernel-fiti
..4271957e28
--- /dev/null
+++ b/meta/classes/log-colorizer.bbclass
@@ -0,0 +1,49 @@
+# Copyright (C) 2020 Agilent Technologies, Inc.
+# Author: Chris Laplante
+#
+# Released under the MIT license (see COPYING.MIT)
+
+LOG_COLORIZER_SUPPRESS_COLORIZED_OUTPUT
Signed-off-by: Chris Laplante
---
meta/classes/base.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index 4c681cc870..5a969b207a 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -12,7 +12,7
This progress handler intercepts log output, stripping any ANSII color
escape codes. Then the stripped output is fed to the underlying progress
handler which will render the progress bar as usual.
Signed-off-by: Chris Laplante
---
meta/lib/oe/log_colorizer.py | 86
f the task itself, not any prefuncs or postfuncs. This is
because the color filtering is implemented using progress handlers,
which don't see prefunc or postfunc output.
Chris Laplante (3):
lib/oe/log_colorizer.py: add LogColorizerProxyProgressHandler
base.bbclass: make oe.log_colorizer
Hi David,
> > "Does anyone know what the intended audience is for the Developer Day
> presentations?"
>
> The official description for the intended audience can be found here:
> https://www.yoctoproject.org/yocto-project-dev-day-virtual-north-america-
> 2020/
>
> We will be covering a lot of top
> > Does anyone know what the intended audience is for the Developer Day
> presentations? E.g. would someone who uses bitbake day-to-day but perhaps
> doesn't edit recipes benefit?
> >
>
> I would say look at the schedule and see if there are talks of interest to
> you.
I did, but the schedule s
> * Next week is ELC which is taking place virtually this year and Yocto Project
> has a presence there. There is also a virtual Yocto Project Developer Day:
> https://events.linuxfoundation.org/yocto-dev-day-north-america/
Does anyone know what the intended audience is for the Developer Day
pres
> "contains" has special magic where it caches the specific value presence
> rather than the whole string. I'd therefore recommend using the contains
> functions where at all possible for that reason.
So then regarding my other points, it is correctly handled by the signature
code? If so, why doe
> > So, is changing DISTRO_FEATURES but not changing the build directory
> > expected to work?
>
> Should work but has bugs.
>
> There were some fixed around the thud/zeus timeframe.
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13702
>
> is a recently reported one that has patches in m
1 - 100 of 120 matches
Mail list logo
