From: Changqing Li
Error info:
ERROR: libpcre-8.44-r0 do_package_write_rpm: Failure expanding variable
SUMMARY_libpcrecpp, expression was ${SUMMARY} - C++ wrapper functions
which triggered exception RecursionError: maximum recursion depth
exceeded while calling a Python object
this error is hard
On Thu, 2020-08-27 at 17:12 -0500, Mark Hatle wrote:
> When the PR service is enabled a number of small changes may happen
> to variables. In the do_package step a call to package_get_auto_pr
> will end up setting PRAUTO and modifying PKGV (if AUTOINC is there).
>
> PRAUTO is then used by EXTENDP
While enabling systemd, there is QA issue:
...
|ERROR: sysstat-12.4.0-r0 do_package: QA Issue: sysstat: Files/directories
were installed but not shipped in any package:
| /lib/systemd/system-sleep
| /lib/systemd/system-sleep/sysstat.sleep
...
https://www.freedesktop.org/software/systemd/man/syst
When the PR service is enabled a number of small changes may happen
to variables. In the do_package step a call to package_get_auto_pr
will end up setting PRAUTO and modifying PKGV (if AUTOINC is there).
PRAUTO is then used by EXTENDPRAUTO, which is then used to generate
PKGR.
Since this behavio
...instead we call read_subpackage_metadata.
Calling package_get_auto_pr *should* result in the same PKGV AUTOINC
replacement. However, it will also end up changing PKGR differently
then do_package as the BB_TASKHASH used will be for the wrong task.
Generally this won't cause any real-world issu
v7:
Update packagedata_translate_pr_autoinc function to handle when there is no
pkgdata to process.
Exception: bb.process.ExecutionError: Execution of
'/mnt/b/yoe/master/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/libtool-cross/2.4.6-r0/temp/run.packagedata_translate_pr_autoinc.2499
Using this mechanism ensures that we have a single point to implement
the loading of the package and subpackage meta data. This also then
allows the buildhistory class to use the regular datastore vs it's
own custom arrays for processing history items.
Signed-off-by: Mark Hatle
---
meta/classes
On Thu, Aug 27, 2020 at 2:36 PM Alexander Kanavin
wrote:
>
> On Thu, 27 Aug 2020 at 23:31, Khem Raj wrote:
>>
>> On Thu, Aug 27, 2020 at 4:00 AM Alexander Kanavin
>> wrote:
>> >
>> > It is difficult and error-prone to ensure binutils gets
>> > installed into target images where this test may run
On Thu, 27 Aug 2020 at 23:31, Khem Raj wrote:
> On Thu, Aug 27, 2020 at 4:00 AM Alexander Kanavin
> wrote:
> >
> > It is difficult and error-prone to ensure binutils gets
> > installed into target images where this test may run;
> > on the other hand readelf is always present on the
> > host, as
On Thu, Aug 27, 2020 at 4:00 AM Alexander Kanavin
wrote:
>
> It is difficult and error-prone to ensure binutils gets
> installed into target images where this test may run;
> on the other hand readelf is always present on the
> host, as it is a part of HOSTTOOLS.
>
this would mean that we are rel
From: Bruce Ashfield
This is based on the patch from Zhaolong Zhang
[kernel-yocto: checksum indirect cfg and scc files]
While the recommended manner to share/reuse feature fragments is to
maintain them in a kernel-meta repository and track the changes via the
standard SRCREV fetcher mechanism,
On 8/26/20 1:13 AM, Jamaluddin, Khairul Rohaizzat wrote:
From: Khairul Rohaizzat Jamaluddin
Due to recent changes in bootimg-efi to include IMAGE_BOOT_FILES,
when both bootimg-partition and bootimg-efi occur in a single .wks
and IMAGE_BOOT_FILES are defined, files listed in IMAGE_BOOT_FILES
wil
v6:
Refactor do_packagedata to use existing copy routine, and then sed "inline" to
translate EXTENDPRAUTO and AUTOINC parts.
v5 (not sent to mailing list):
Refactor do_packagedata and create a custom copy routine. The routine also
uses sed to translate EXTENDPRAUTO and AUTOINC. This also intro
...instead we call read_subpackage_metadata.
Calling package_get_auto_pr *should* result in the same PKGV AUTOINC
replacement. However, it will also end up changing PKGR differently
then do_package as the BB_TASKHASH used will be for the wrong task.
Generally this won't cause any real-world issu
When the PR service is enabled a number of small changes may happen
to variables. In the do_package step a call to package_get_auto_pr
will end up setting PRAUTO and modifying PKGV (if AUTOINC is there).
PRAUTO is then used by EXTENDPRAUTO, which is then used to generate
PKGR.
Since this behavio
Using this mechanism ensures that we have a single point to implement
the loading of the package and subpackage meta data. This also then
allows the buildhistory class to use the regular datastore vs it's
own custom arrays for processing history items.
Signed-off-by: Mark Hatle
---
meta/classes
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
6576d69aac94 Linux 5.4.61
d316d52742c4 KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is
not set
e1818ffcca0e KVM: Pass MMU notifier range flags to kvm
From: Bruce Ashfield
Richard,
Here's the latest set of queued kernel changes.
Two are routine -stable updates, the other meta data change is the cherry pick
of a 5.4 change we had, that I somehow missed when creating the 5.8 config
branch. This will get rid of he intermittent reproducibility fa
From: Bruce Ashfield
A patch from 5.4 wasn't propagated to 5.8, and IKHEADERS was
renabled in our default builds.
This cases reproducibility issues when kernel modules are built.
We haven't tracked down the root cause yet, but for now, we still
don't want reproducibility failing on builds.
The
From: Bruce Ashfield
It was requested to add the ability to upgrade configuration warnings
to errors, so that they can't be missed in a build.
Add a flag KMETA_AUDIT_WERROR, that when set, triggers a bb.fatal at
the end of configuration checking if any warnings are found.
This is off by default
From: Bruce Ashfield
Updating linux-yocto/5.8 to the latest korg -stable release that comprises
the following commits:
47dcb7fcad1d Linux 5.8.4
920ebff48be3 Revert "drm/amd/display: Improve DisplayPort monitor interop"
d0a3a0136337 KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BL
From: Bruce Ashfield
This is based on the patch from Zhaolong Zhang
[kernel-yocto: checksum indirect cfg and scc files]
While the recommended manner to share/reuse feature fragments is to
maintain them in a kernel-meta repository and track the changes via the
standard SRCREV fetcher mechanism,
Hi Alex
On Thu, Aug 27, 2020 at 4:59 PM Alexander Kanavin
wrote:
>
> I am able to execute that exact same command without any errors. How can
this be reproduced?
Did you run it on Ubuntu 20.04 with Python 3.8?
» python3 --version
Python 3.8.2
» apt-cache policy python3.8
python3.8:
Install
From: Ross Burton
emit_pkgdata() creates symlinks for each of the RPROVIDES in
pkgdata/MACHINE/runtime-rprovides. However this string can contain
versions which results in directories called (=2.32), so pass the
RPROVIDES string through bb.utils.explode_deps() to strip the versions
out.
Helps m
On Thu, 27 Aug 2020 at 03:12, hongxu wrote:
>
> While enabling systemd, there is QA issue:
> ...
> |ERROR: sysstat-12.4.0-r0 do_package: QA Issue: sysstat: Files/directories
> were installed but not shipped in any package:
> | /lib/systemd/system-sleep
> | /lib/systemd/system-sleep/sysstat.sleep
I am able to execute that exact same command without any errors. How can
this be reproduced?
Note that we already had the same patch proposed earlier and it was
rejected, as the problem pops up in various different places and needs to
be understood and solved properly.
Alex
On Thu, 27 Aug 2020 a
On Ubuntu 20.04.1 LTS with Python 3.8.2 "devtool modify" fails with
Exception: ModuleNotFoundError: No module named '_sysconfigdata'
e.g.: devtool modify --no-same-dir --branch fit u-boot ~/ws/w/dtool/u-boot-fit
ERROR: Error executing a python function in exec_python_func() autogenerated:
The st
From: Ross Burton
emit_pkgdata() creates symlinks for each of the RPROVIDES in
pkgdata/MACHINE/runtime-rprovides. However this string can contain
versions which results in directories called (=2.32), so pass the
RPROVIDES string through bb.utils.explode_deps() to strip the versions
out.
Also us
On Thu, 2020-08-27 at 13:28 +0200, Adrian Freihofer wrote:
> python bindings are GPLv3+.
>
> Signed-off-by: Adrian Freihofer
> ---
> recipes-core/util-linux/util-linux_%.bbappend | 10 ++
> 1 file changed, 10 insertions(+)
> create mode 100644 recipes-core/util-linux/util-linux_%.bbappe
On Thu, 2020-08-27 at 13:25 +0200, Alexander Kanavin wrote:
> On Thu, 27 Aug 2020 at 13:06, Richard Purdie
> wrote:
> > Hmm. I think this test is only meant to trigger in a lib32-core-image-
> > sato where lib32-connman would be present and connman would not?
> >
> > The test name could certainl
It's not completely tested because we do not use meta-gplv2 layer.
But I guess it will solve the Problem of this build pipeline:
https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/2371
Adrian Freihofer (1):
util-linux: remove GPLv3 and pylibmount
recipes-core/util-linux/util-lin
python bindings are GPLv3+.
Signed-off-by: Adrian Freihofer
---
recipes-core/util-linux/util-linux_%.bbappend | 10 ++
1 file changed, 10 insertions(+)
create mode 100644 recipes-core/util-linux/util-linux_%.bbappend
diff --git a/recipes-core/util-linux/util-linux_%.bbappend
b/recipes
On Thu, 27 Aug 2020 at 13:06, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> Hmm. I think this test is only meant to trigger in a lib32-core-image-
> sato where lib32-connman would be present and connman would not?
>
> The test name could certainly be clearer as its not a generic co
On Wed, 2020-08-26 at 22:54 +0100, Richard Purdie via lists.openembedded.org
wrote:
> On Wed, 2020-08-26 at 18:13 +0200, Adrian Freihofer wrote:
> > Signed-off-by: Adrian Freihofer
> > ---
> > meta/recipes-core/util-linux/util-linux_2.36.bb | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletio
On Thu, 2020-08-27 at 12:59 +0200, Alexander Kanavin wrote:
> It was previously skipped as it was expecting plain connman
> to not be in the image, and for core-image-sato connman is always
> there.
>
> Signed-off-by: Alexander Kanavin
> ---
> meta/lib/oeqa/runtime/cases/multilib.py | 2 +-
> 1
It is difficult and error-prone to ensure binutils gets
installed into target images where this test may run;
on the other hand readelf is always present on the
host, as it is a part of HOSTTOOLS.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/runtime/cases/x32lib.py | 17 +++--
As specified in https://wiki.gnome.org/Projects/JsonGlib
Signed-off-by: Alexander Kanavin
---
meta/recipes-gnome/json-glib/json-glib_1.4.4.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-gnome/json-glib/json-glib_1.4.4.bb
b/meta/recipes-gnome/json-glib/json-g
It is difficult and error-prone to ensure binutils gets
installed into target images where this test may run;
on the other hand readelf is always present on the
host, as it is a part of HOSTTOOLS.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/runtime/cases/multilib.py | 9 ++---
1 file
The purpose and content of the group is not clear;
the only consumer (poky distro) is no longer using it.
Signed-off-by: Alexander Kanavin
---
.../packagegroup-core-device-devel.bb| 16
1 file changed, 16 deletions(-)
delete mode 100644
meta/recipes-devtools/packag
The recipe includes systemd.inc and so shares SRCREV with the main systemd.
Signed-off-by: Alexander Kanavin
---
.../systemd/{systemd-boot_246.1.bb => systemd-boot_246.2.bb} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta/recipes-core/systemd/{systemd-boot_246.1.bb =>
sys
It was previously skipped as it was expecting plain connman
to not be in the image, and for core-image-sato connman is always there.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/runtime/cases/multilib.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/runt
On Thu, 27 Aug 2020 at 09:48, zhou li wrote:
> I have a question here:
> building for a real machine (say, intel-corei7-64): MACHINE ?=
> intel-corei7-64
>
> While in connman-conf.bb:
> SRC_URI_append_qemuall = " file://wired.config \
> file://wired-setup \
>
Some platforms support kernel tracing, some support userspace tracing.
This change:
* Moves the knowledge/config to one place in an inc file
* Allows lttng-tools to build without lttng-modules
* Hence enables tools+ust for riscv64
* Has the packagegroup just depend on lttng-tools which will pull i
On 8/26/20 9:06 PM, Ross Burton wrote:
On Fri, 21 Aug 2020 at 09:07, Martin Jansa wrote:
We're using connman-conf to configure networking on various target machines -
not only on qemu*. If this is merged I'll just undo this in our layer - and
that's fine, but if there are more people using c
On Thu, 2020-08-27 at 09:21 +0100, Ross Burton wrote:
> On Thu, 27 Aug 2020 at 03:17, Khem Raj wrote:
> > > LTTng does not have a hard requirement on lttng-modules (on
> > > paper), when kernel modules
> > > (tracer) is not present kernel tracing is disabled and only
> > > userspace tracing is
> >
On Thu, 27 Aug 2020 at 03:17, Khem Raj wrote:
> > LTTng does not have a hard requirement on lttng-modules (on paper), when
> > kernel modules
> > (tracer) is not present kernel tracing is disabled and only userspace
> > tracing is
> > available.
> >
> > Was there any report that lttng-ust (users
46 matches
Mail list logo
