From: Kai Kang
This reverts commit 91264e5e0ab40b796e214edd84c72bc88b363778.
It adds meson options 'instrospection' to disable gobject introspection
files build. So no need to check distro feature 'gobject-introspection-data'
any longer.
Keep the spaces adjustment and comment removal.
Signed-o
From: Kai Kang
v2:
* revert distro feature check for 'gobject-introspection-data'
Build with/without config
DISTRO_FEATURES_remove = "gobject-introspection-data"
$ bitbake webkitgtk pinentry
Build successfully.
Kai Kang (2):
libsecret: add meson option introspection
Revert "webkitgtk, pi
From: Kai Kang
Add meson option 'introspection' for libsecret. For bsp which doesn't
support qemu usermode, it could disable gobject introspection build.
Then remove distro feature check for 'gobject-introspection-data' too.
Signed-off-by: Kai Kang
---
.../0001-meson-add-option-introspection.p
When we have rm_work enabled all image tasks are built every time. This has
been happening since at least warrior and is still happening as of master
today (8fc19639f47b959a141dae231395bbababa644e1).
Steps to reproduce:
bitbake core-image-minimal
bitbake core-image-minimal
echo 'INHERIT += "rm
Signed-off-by: Wang Mingyu
---
.../iso-codes/{iso-codes_4.4.bb => iso-codes_4.5.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/iso-codes/{iso-codes_4.4.bb => iso-codes_4.5.0.bb}
(92%)
diff --git a/meta/recipes-support/iso-codes/iso-codes_4.4.bb
refresh 0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch
remove 0001-revert-cease-dependence-on-range.patch
since it is included in 1.73.0
Signed-off-by: Wang Mingyu
---
...native_1.72.0.bb => bjam-native_1.73.0.bb} | 0
.../{boost-1.72.0.inc => boost-1.73.0.inc}| 4 +-
...h
Signed-off-by: Wang Mingyu
---
.../iproute2/{iproute2_5.5.0.bb => iproute2_5.6.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/iproute2/{iproute2_5.5.0.bb =>
iproute2_5.6.0.bb} (65%)
diff --git a/meta/recipes-connectivity/iproute2/iprout
Hello,
I am wondering, if it is possible to archive bitbake cache and send to another
server.
I tried to archive cache and tmp/cache directories and use them on another
server (configs and recipes/workspace name/user name and build server image
were same), but for some reason recipes are re-par
On Fri, 2020-05-22 at 04:59 -0700, krzysztof.tabor...@nokia.com wrote:
> I am wondering, if it is possible to archive bitbake cache and send
> to another server.
Only under very specific conditions. The paths and timestamps for the
metadata would all have to match perfectly. The cache is not desig
On Fri, May 22, 2020 at 05:04 AM, Richard Purdie wrote:
>
> Low. Its not designed to do that and you should never need to. Why
> can't it reparse?
I tried to reduce building time. I know, that it is not a big time, but
multiplying by build count it could bring some benefits.
Nevertheless thanks
Signed-off-by: Zheng Ruoqin
---
meta/recipes-devtools/ruby/{ruby_2.7.0.bb => ruby_2.7.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/ruby/{ruby_2.7.0.bb => ruby_2.7.1.bb} (95%)
diff --git a/meta/recipes-devtools/ruby/ruby_2.7.0.bb
b/meta/recipes-de
From: Adrian Bunk
This includes the fixes for CVE-2020-5260 and CVE-2020-11008.
Signed-off-by: Adrian Bunk
Signed-off-by: Armin Kuster
---
meta/recipes-devtools/git/git_2.20.1.bb | 11 ---
meta/recipes-devtools/git/git_2.20.4.bb | 11 +++
2 files changed, 11 insertions(+), 11
From: Jan Luebbe
This also fixes CVE-2020-1967.
Signed-off-by: Jan Luebbe
Signed-off-by: Anuj Mittal
Signed-off-by: Armin Kuster
---
.../openssl/{openssl_1.1.1f.bb => openssl_1.1.1g.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/openssl
From: Lee Chee Yang
CPE version could be '-' to mean no version info.
Current cve_check treat it as not valid and does not report these
CVE but some of these could be a valid vulnerabilities.
Since non-valid CVE can be whitelisted, so treat '-' as all version
and report all these CVE to capture
From: Adrian Bunk
LICENSE checksum changed due to 2019 -> 2020 update.
Signed-off-by: Adrian Bunk
Signed-off-by: Anuj Mittal
Signed-off-by: Armin Kuster
---
.../{python-native_2.7.17.bb => python-native_2.7.18.bb}| 0
meta/recipes-devtools/python/python.inc | 6 +++---
From: Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko
Signed-off-by: Richard Purdie
(cherry picked from commit 57fcf9b517fe95e871122946cb99fe7fa9fd2e26)
Signed-off-by: Armin Kuster
---
meta/recipes-connectivity/openssl/openssl_1.1.1d.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Richard Purdie
There was a build architecture leaking into the target ptest which
could vary depending upon host. Remove it as its cosmetic.
[YOCTO #13770]
(From OE-Core rev: 37db519eedb7eb5cd4f14d05f30f5d580aa7458d)
(From OE-Core rev: c31c676319812e6fc036741db2ab8e16eccff723)
Signed-of
From: Alexander Kanavin
This also un-breaks python3 ptest which got broken
with 1.1.1e update.
Signed-off-by: Alexander Kanavin
Signed-off-by: Richard Purdie
(cherry picked from commit b4ddf5b9d8cd769b7026663f93c8bc69b55d8cbf)
[AK: bugfix only update]
Signed-off-by: Armin Kuster
---
.../open
Please merge these changes into warrior
The following changes since commit ae341aed81be28232cc34daf4684bc0922f17699:
yocto-uninative.inc: version 2.8 updates glibc to 2.31 (2020-03-26 07:04:11
-0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-con
From: Adrian Bunk
Backported patch removed.
Signed-off-by: Adrian Bunk
Signed-off-by: Richard Purdie
(cherry picked from commit 710bc0f8544f54750c8fb7b8affa243932927a24)
[AK: bug fix only update]
Signed-off-by: Armin Kuster
---
.../openssl/openssl/CVE-2019-1551.patch | 758
We want the user metadata added on the packages but
if the index generator filters them they are useless
as they get to the index.
Allow user fields when populating the package index.
Signed-off-by: Paulo Neves
---
meta/lib/oe/package_manager.py | 2 +-
1 file changed, 1 insertion(+), 1 deletio
Up to now the user defined metadata was set recipe wide,
meaning all the packages generated in a recipe where the
variable was set would get the same metadata. That is not
always ideal and is counter to the per package control that
is usually available.
Keep support for package agnostic metadata b
Should there be a test for this functionality? Somewhere in oe-selftest
perhaps where various package manager features are tested?
Alex
On Fri, 22 May 2020 at 17:13, Paulo Neve wrote:
> Up to now the user defined metadata was set recipe wide,
> meaning all the packages generated in a recipe whe
Is ./meta/lib/oeqa/selftest/cases/package.py the right place?
If yes i can work on it. Note that this functionality is not used
anywhere in poky and is not documented at all. It just happened to
exist for a long time and be useful for my case.
On Fri, May 22, 2020 at 5:22 PM Alexander Kanavin
wro
Hi Mike,
On 5/22/20 10:13 AM, Mike Crowe via lists.openembedded.org wrote:
When we have rm_work enabled all image tasks are built every time. This has
been happening since at least warrior and is still happening as of master
today (8fc19639f47b959a141dae231395bbababa644e1).
Steps to reproduce:
On 5/21/20 7:22 PM, Otavio Salvador wrote:
When using Go Modules, the the current working directory MUST be at or
below the location of the 'go.mod' file when the go tool is used, and
there is no way to tell it to look elsewhere. It will automatically
look upwards for the file, but not downwar
Hi Paulo,
I actually have some patches in my "to send upstream list" to address the
documentation and some sstate-caching bugs with these variables so it's
fresh to me at the moment.
Correct me if I'm wrong but I think this is already available in the code
(applying metadata specific to a certain
Hello Michael,
The behavior you describe is indeed what i wanted. If you say this is
already working then my patches are redundant. Even so i am surprised
it is working. Is it done automatically by the getVar function?
def get_package_additional_metadata (pkg_type, d):
base_key = "PACKAGE_ADD
Signed-off-by: Khem Raj
---
meta/recipes-devtools/go/go-1.14.inc | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/go/go-1.14.inc
b/meta/recipes-devtools/go/go-1.14.inc
index c52593db6b..d729b65267 100644
--- a/meta/recipes-devtools/go/go-1.14.inc
+++
Hi Paulo,
Yes, this is handled by the bitbake data handlers automatically. You can
check this by trying the following:
python do_test() {
d.setVar("HELLO", "world!")
d.setVar("HELLO_space", "space!")
bb.warn("HELLO: %s" % d.getVar("HELLO", True))
d.setVar("OVERRIDES", "space")
On Fri, May 22, 2020 at 2:23 PM Khem Raj wrote:
...
> > +# Copyright 2020 (C) O.S. Systems Software LTDA.
> > +
>
> Do you also want to add license on top along with copyrights ?
It is same as OE-Core, if desired, I can make it explicit.
--
Otavio Salvador O.S. Syste
On Friday 22 May 2020 at 19:02:47 +0200, Jacob Kroon wrote:
> Hi Mike,
>
> On 5/22/20 10:13 AM, Mike Crowe via lists.openembedded.org wrote:
> > When we have rm_work enabled all image tasks are built every time. This has
> > been happening since at least warrior and is still happening as of master
The gtest and gmock packages provided by googletest are not added to the SDK by
default. I assume it is because the googletest main package is empty?
I added an RDEPENDS_${PN} from the dependent package to fix it. Is there a
better solution?
Tom
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all me
On Fri, May 22, 2020 at 5:48 PM Tom Hochstein wrote:
> The gtest and gmock packages provided by googletest are not added to the SDK
> by default. I assume it is because the googletest main package is empty?
>
> I added an RDEPENDS_${PN} from the dependent package to fix it. Is there a
> better s
As in other places in the file, skip layers that don't define a
collection when searching for a layer to resolve a dependency. Fixes
KeyError exceptions when attempting to access the layer collections
later
Signed-off-by: Joshua Watt
---
scripts/lib/checklayer/__init__.py | 3 +++
1 file changed
On Fri, May 22, 2020 at 2:29 PM Otavio Salvador
wrote:
>
> On Fri, May 22, 2020 at 5:48 PM Tom Hochstein wrote:
> > The gtest and gmock packages provided by googletest are not added to the
> > SDK by default. I assume it is because the googletest main package is empty?
Are you including googlet
Signed-off-by: Steve Sakoman
---
meta/lib/oeqa/core/utils/concurrencytest.py | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oeqa/core/utils/concurrencytest.py
b/meta/lib/oeqa/core/utils/concurrencytest.py
index fac59f765a..01c39830f9 100644
--- a/meta/lib
On Fri, May 22, 2020 at 03:33 PM, Andre McCurdy wrote:
>
> On Fri, May 22, 2020 at 2:29 PM Otavio Salvador
> wrote:
>
>> On Fri, May 22, 2020 at 5:48 PM Tom Hochstein
>> wrote:
>>
>>> The gtest and gmock packages provided by googletest are not added to the
>>> SDK by default. I assume it is b
On Fri, May 22, 2020 at 3:50 PM Tom Hochstein wrote:
> On Fri, May 22, 2020 at 03:33 PM, Andre McCurdy wrote:
> On Fri, May 22, 2020 at 5:48 PM Tom Hochstein wrote:
>
> The gtest and gmock packages provided by googletest are not added to the SDK
> by default. I assume it is because the googletes
Signed-off-by: Zheng Ruoqin
---
meta/recipes-devtools/strace/{strace_5.5.bb => strace_5.6.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/strace/{strace_5.5.bb => strace_5.6.bb} (92%)
diff --git a/meta/recipes-devtools/strace/strace_5.5.bb
b/meta/reci
Signed-off-by: Zheng Ruoqin
---
.../sysstat/{sysstat_12.2.1.bb => sysstat_12.2.2.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/sysstat/{sysstat_12.2.1.bb => sysstat_12.2.2.bb}
(54%)
diff --git a/meta/recipes-extended/sysstat/sysstat_12.2.1.
41 matches
Mail list logo
