From: Lee Chee Yang
existing test case test_permissions use Wic command as standalone
tools to create wic image and check that wic image for permissions.
add extra steps to the test case to also check against image build
using bitbake do_image_wic.
Signed-off-by: Lee Chee Yang
---
meta/lib/oe
Le mer. 3 févr. 2021 à 21:56, Andrey Zhizhikin a
écrit :
> Hello Yann,
>
> > index 5fa99821c4..872592fdae 100644
> > --- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.12.bb
> > +++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.14.bb
> > @@ -18,14 +18,11 @@ PROVIDES = "virtual/libsdl2"
> >
> > SRC_UR
Adding a patch to remove an unecessary print statement
in test-codegen.py that cause the ptest-runner to fail.
Root cause is suspected to be in ptest-runner.
[YOCTO #14170]
Uptream-Status: Inappropriate [other]
this is a workaround.
Signed-off-by: Yi Fan Yu
---
...-removing-unecessary-print-s
Signed-off-by: Khem Raj
---
...-ISA-support-for-x86-64-level-marker.patch | 116 ++
meta/recipes-core/glibc/glibc_2.33.bb | 1 +
2 files changed, 117 insertions(+)
create mode 100644
meta/recipes-core/glibc/glibc/0031-x86-Require-full-ISA-support-for-x86-64-level-marke
Adding a patch to remove an unecessary print statement
in test-codegen.py that cause the ptest-runner to fail.
Root cause is suspected to be in ptest-runner.
[YOCTO #14170]
Uptream-Status: Inappropriate [other]
this is a workaround.
Signed-off-by: Yi Fan Yu
---
...-removing-unecessary-print-s
Enable Intel Control-flow Enforcement Technology (CET) instrumentation
support
helps with overcoming
/lib/libc.so.6: CPU ISA level is lower than required
Signed-off-by: Khem Raj
---
meta/recipes-core/glibc/glibc_2.33.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-core/gl
On Wed, 2021-02-03 at 11:56 -0800, Khem Raj wrote:
> Hi Richard
>
> I am seeing compile errors for pseudo, it could be glibc 2.33
> introduced and perhaps pseudo needs some forward porting ?
>
> https://errors.yoctoproject.org/Errors/Details/566884/
Looks very likely that we'll need to fix it to
Hello Yann,
On Mon, Feb 1, 2021 at 11:23 AM Yann Dirson wrote:
>
> From: Yann Dirson
>
> This version does not support tslib any more, as can be seen by the
> failed AUH run.
>
> Originally-by: Romain Roffé
> Signed-off-by: Yann Dirson
> ---
> .../libsdl2/directfb-renderfillrect-fix.patch | 3
I digged a bit: I think libsdl 1.x might still have it, but libsdl 2.x
definitely does not.
Alex
On Wed, 3 Feb 2021 at 20:47, Alexander Kanavin via lists.openembedded.org
wrote:
> It looks like tslib support was not in 2.0.12 version either, and probably
> was ripped out long time ago:
> http
Hi Richard
I am seeing compile errors for pseudo, it could be glibc 2.33
introduced and perhaps pseudo needs some forward porting ?
https://errors.yoctoproject.org/Errors/Details/566884/
On Fri, Jan 29, 2021 at 2:24 AM Richard Purdie
wrote:
>
> Pulls in:
> pseudo_client: Ensure renames update
It looks like tslib support was not in 2.0.12 version either, and probably
was ripped out long time ago:
http://hg.libsdl.org/SDL/rev/a708852dbd5c
Alex
On Wed, 3 Feb 2021 at 18:05, Alexander Kanavin via lists.openembedded.org
wrote:
> Certainly not in oe-core please. This looks like a problem y
Drop backported patches
Signed-off-by: Khem Raj
Signed-off-by: Richard Purdie
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
...2.32.bb => cross-localedef-native_2.33.bb} | 0
meta/recipes-core/glibc/glibc-common.inc | 2 +-
...bc-locale_2.32.bb => glibc-locale_2.33.bb} |
License file diff:
+ Files: doc/sphinxext/numpydoc/*
+ License: BSD-2-Clause
+ For details, see doc/sphinxext/LICENSE.txt
+
+ Name: scipy-sphinx-theme
+ Files: doc/scipy-sphinx-theme/*
+ License: BSD-3-Clause AND PSF-2.0 AND Apache-2.0
+ For details, see doc/scipy-sphinx-theme/LICENSE.txt
Sig
Signed-off-by: Oleksandr Kravchuk
---
meta/recipes-devtools/python/python-smmap.inc | 2 +-
.../python/{python3-smmap_3.0.4.bb => python3-smmap_4.0.0.bb} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-smmap_3.0.4.bb =>
python
Certainly not in oe-core please. This looks like a problem you need to take
upstream, and until then do any downgrades via private layer.
Alex
On Wed, 3 Feb 2021 at 14:54, Yann Dirson
wrote:
> Le lun. 1 févr. 2021 à 20:11, Mark Jonas a écrit :
>
>> Hi,
>>
>> tslib support is often relevant for
On Wed, Feb 3, 2021 at 6:24 AM Sourabh Banerjee wrote:
>
> On 2021-02-03 21:50, Sourabh Banerjee wrote:
> > Sanity checker reports following error for the PATH variable,
> > when bitbake -e command is run in an extensible SDK workspace.
> >PATH contains '.', './' or '' (empty element), which
On Wed, Feb 3, 2021 at 5:53 AM Mikko Rapeli wrote:
>
> On Wed, Feb 03, 2021 at 04:38:58AM -1000, Steve Sakoman wrote:
> > On Wed, Feb 3, 2021 at 12:02 AM Mikko Rapeli wrote:
> > >
> > > Hi,
> > >
> > > On Wed, Feb 03, 2021 at 08:42:57AM +, Anatol Belski wrote:
> > > > The naming convention ne
On 2021-02-03 21:50, Sourabh Banerjee wrote:
Sanity checker reports following error for the PATH variable,
when bitbake -e command is run in an extensible SDK workspace.
PATH contains '.', './' or '' (empty element), which will break the
build
In case of extensible SDK, PATH variable is fo
Sanity checker reports following error for the PATH variable,
when bitbake -e command is run in an extensible SDK workspace.
PATH contains '.', './' or '' (empty element), which will break the build
In case of extensible SDK, PATH variable is formed with two consecutive ':'
as bb.utils.which(d
On Wed, Feb 03, 2021 at 04:38:58AM -1000, Steve Sakoman wrote:
> On Wed, Feb 3, 2021 at 12:02 AM Mikko Rapeli wrote:
> >
> > Hi,
> >
> > On Wed, Feb 03, 2021 at 08:42:57AM +, Anatol Belski wrote:
> > > The naming convention needs to be help so the CVE is recognized as
> > > fixed by the toolin
On Wed, 2021-02-03 at 07:21 -0800, Khem Raj wrote:
> On Wed, Feb 3, 2021 at 2:30 AM Richard Purdie
> wrote:
> >
> > On Mon, 2021-02-01 at 10:39 -0800, Khem Raj wrote:
> > > Drop backported patches
> > >
> > > Signed-off-by: Khem Raj
> > > ---
> >
> > Patches fail to apply, e.g.:
> >
> > https
rngd daemon may spam the console when using an older version
than 6.11.
Backport patches from https://github.com/nhorman/rng-tools/pull/99/commits
Signed-off-by: Julien Massot
---
...-O_NONBLOCK-setting-for-entropy-pipe.patch | 26 +
...ialize-AES-key-before-setting-the-en.patch | 3
On Wed, Feb 3, 2021 at 2:30 AM Richard Purdie
wrote:
>
> On Mon, 2021-02-01 at 10:39 -0800, Khem Raj wrote:
> > Drop backported patches
> >
> > Signed-off-by: Khem Raj
> > ---
>
> Patches fail to apply, e.g.:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/1911
>
> (but bas
Hi,
On 2/3/2021 3:38 PM, Steve Sakoman wrote:
On Wed, Feb 3, 2021 at 12:02 AM Mikko Rapeli wrote:
Hi,
On Wed, Feb 03, 2021 at 08:42:57AM +, Anatol Belski wrote:
The naming convention needs to be help so the CVE is recognized as
fixed by the tooling.
Yocto CVE checker does detect CVE pat
On Wed, Feb 3, 2021 at 9:39 AM Richard Purdie
wrote:
>
> On Tue, 2021-02-02 at 22:24 -0500, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > Integrating the following commit(s) to linux-yocto/5.10:
> >
> > cdca78778415 objtool: Fix seg fault with Clang non-section symbols
> >
Hi,
On 2/3/2021 11:02 AM, Mikko Rapeli wrote:
Hi,
On Wed, Feb 03, 2021 at 08:42:57AM +, Anatol Belski wrote:
The naming convention needs to be help so the CVE is recognized as
fixed by the tooling.
Yocto CVE checker does detect CVE patches also from patch comments so
this change is not ne
On Tue, Feb 2, 2021 at 8:09 AM saloni wrote:
>
> Whitelisted below CVEs as their status is disputed
> and ignored and not affecting the Ubuntu and Debian
> environments. Hence, marked them whitelisted.
I'm not sure why you are referencing Ubuntu and Debian environments.
We care about whether it i
On Wed, 2021-02-03 at 00:18 +, Richard Purdie via
lists.openembedded.org wrote:
> On Tue, 2021-02-02 at 02:57 +, Mittal, Anuj wrote:
> > I see the same failure locally even when using the autobuilder
> > configuration so it's probably not related to multilib.
> >
> > I guess it's happening
On Tue, 2021-02-02 at 22:24 -0500, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Integrating the following commit(s) to linux-yocto/5.10:
>
> cdca78778415 objtool: Fix seg fault with Clang non-section symbols
> d3287798bd88 x86/entry: Emit a symbol for register restoring thu
On Wed, Feb 3, 2021 at 12:02 AM Mikko Rapeli wrote:
>
> Hi,
>
> On Wed, Feb 03, 2021 at 08:42:57AM +, Anatol Belski wrote:
> > The naming convention needs to be help so the CVE is recognized as
> > fixed by the tooling.
>
> Yocto CVE checker does detect CVE patches also from patch comments so
In an earlier commit, libprocps was split into a separate package leaving
no shlibs in the main package. A bug was seen where igt-gpu-tools wouldn't
build correctly in some cases as it thought the librbary was still in the
main package, throwing qa errors as a result.
The issue was due to an extra
With the IGNOREWITHLINUXSYSCALLNOTE variable set to "1" in local.conf, it
removes the "WITH Linux syscall note" string attached to the license value for
sources before comparism.
This is to get more recipe LICENSES to match with those of the sources and
reduce the number of warnings outputed.
S
Added text to distinguish licenses from sources and those from recipes when
warnings are outputed.
Signed-off-by: Ida Delphine
---
meta/classes/package.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index
The recipe LICENSE strings are split into their individual license and the
canonicalised to easy enable matching with licenses of sources.
License strings with "or-later" are replaced with "+" before comparism.
The warnings showup if and only if licenses in the sources don't match LICENSE
value o
Le lun. 1 févr. 2021 à 20:11, Mark Jonas a écrit :
> Hi,
>
> tslib support is often relevant for embedded projects with simple
> (resistive) touch screens. Would it make sense to keep the 2.0.12
> recipe and offer both in parallel?
>
What do others think ?
We could use a libsdl2.inc with the c
From: Luca Boccassi
Signed-off-by: Luca Boccassi
---
.../systemd/{systemd-boot_247.2.bb => systemd-boot_247.3.bb}| 0
.../systemd/{systemd-conf_247.2.bb => systemd-conf_247.3.bb}| 0
meta/recipes-core/systemd/systemd.inc | 2 +-
.../recipes-core/systemd/{system
On Mon, 2021-02-01 at 10:39 -0800, Khem Raj wrote:
> Drop backported patches
>
> Signed-off-by: Khem Raj
> ---
Patches fail to apply, e.g.:
https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/1911
(but basically everything failed)
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Link
Hi,
On Wed, Feb 03, 2021 at 08:42:57AM +, Anatol Belski wrote:
> The naming convention needs to be help so the CVE is recognized as
> fixed by the tooling.
Yocto CVE checker does detect CVE patches also from patch comments so
this change is not needed for that. This is sufficient:
poky$ git
2021. 01. 14. 16:40 keltezéssel, Kamel Bouhara írta:
On Thu, Jan 14, 2021 at 03:25:50PM +0100, Jean-Marie Lemetayer wrote:
Hi Kamel,
Hi Jean-Marie,
Thanks for your work. I should have fixed this a long time ago but I
didn't have the time :(
Well its never too late !
There is actually a
The naming convention needs to be help so the CVE is recognized as
fixed by the tooling.
Signed-off-by: Anatol Belski
---
...ion-to-avoid-GOptionEntry-lis.patch => CVE-2020-35457.patch} | 0
meta/recipes-core/glib-2.0/glib-2.0_2.62.6.bb | 2 +-
2 files changed, 1 insertion(+),
the multiconfig files are required at ${SDK_OUTPUT}/${SDKPATH}
for the populate_sdk_ext to pass. Without the multiconfig files
following command runs into error:
$ bitbake -c populate_sdk_ext mc::${image} mc:${conf1}:${image}
ERROR: bitbake failed:
ERROR: ParseError at ${/path}/poky/build/${tmp
41 matches
Mail list logo
