Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/elfutils-Fix-build-break-with-clang.patch
FAIL: test commit message presence: Please include a commit message on
Signed-off-by: Khem Raj
---
.../elfutils/elfutils_0.191.bb| 1 +
...01-debuginfod-Remove-unused-variable.patch | 34 +++
2 files changed, 35 insertions(+)
create mode 100644
meta/recipes-devtools/elfutils/files/0001-debuginfod-Remove-unused-variable.patch
diff
Hi,
On March 9, 2024 10:38:18 AM GMT+01:00, "Robert P. J. Day"
wrote:
>
> currently perusing countless recipes to choose really good
>pedagogical examples of "ptest" usage, and i began running across a
>number of recipes that (unrelated to ptest) included snippets toward
>the end of their
On Sat, Mar 9, 2024 at 12:58 PM wrote:
>
> From: Max Krummenacher
>
> Hello
>
> If one builds a kernel using AUTOREV invoking bitbake only works once.
> Any subsequent bitbake invocation fails parsing the meta data.
>
> Reproducable with:
> - latest poky, b5624ee564
> - Kernel with SRCREV =
This is final release after RC suffix is removed
Signed-off-by: Khem Raj
---
meta/recipes-devtools/llvm/llvm_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/llvm/llvm_git.bb
b/meta/recipes-devtools/llvm/llvm_git.bb
index
On Sat, Mar 9, 2024 at 5:29 AM Robert P. J. Day wrote:
>
>
> As ptest.bbclass defines the more intuitive ptest-related variable:
>
The ptest bbclass is in classes-recipe, while the distro feature is in
the global conf space.
They aren't really equivalent from that point of view.
The kernel
From: Max Krummenacher
Hello
If one builds a kernel using AUTOREV invoking bitbake only works once.
Any subsequent bitbake invocation fails parsing the meta data.
Reproducable with:
- latest poky, b5624ee564
- Kernel with SRCREV = "AUTOREV", e.g. in local.conf
I think (noreplace) flag only matters when the file has been manually
edited after rpm installation and its checksum diverges from what is
registered in rpm database. Which is not a common scenario in
embedded. If you manually edit the file on target, you might as well
manually resolve which
As ptest.bbclass defines the more intuitive ptest-related variable:
PTEST_ENABLED =
"${@bb.utils.contains('DISTRO_FEATURES', 'ptest', '1', '0', d)}"
modify a number of obvious recipe ptest checks to use that simpler
form.
Signed-off-by: Robert P. J. Day
---
i did a simple textual
currently perusing countless recipes to choose really good
pedagogical examples of "ptest" usage, and i began running across a
number of recipes that (unrelated to ptest) included snippets toward
the end of their recipe files that added content to FILES:${PN}.
here's an example from fwupd:
10 matches
Mail list logo