We were getting an endlessly-growing list of directories in
build/tmp/deploy/licenses/ of the form myimage-mymachine-20210629010203.
Use the normal sstate behaviour to clean them. Brings license_image in
line with the do_populate_lic behaviour in license.bbclass.
We must only clean the (new)
On 06/29/2021 03:47 AM, Alexander Kanavin wrote:
I just generally disagree with the idea that changing a = b to a=b, or
import a,b to import a\nimport b helps readability or reduces confusion.
Writing 'a =b' is acceptable, as it's not causing runtime problem.
However, keeping a consistent
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
Sorry, we will use devtool to upgrade later.
From: openembedded-core@lists.openembedded.org
On Behalf Of Alexander Kanavin
Sent: Monday, June 28, 2021 7:00 PM
To: Richard Purdie
Cc: Zang, Ruochen/臧 若尘 ; OE-core
Subject: Re: [OE-core] [PATCH] python3-pip: upgrade 21.1.2 -> 21.1.3
I have to
Hi Steve,
How about this patch? I already tested on qemux86-64.
https://lists.openembedded.org/g/openembedded-core/message/153284
Do I need more testing?
Thanks,
Minjae Kim.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#153401):
On Mon, 2021-06-28 at 14:01 +0100, Ross Burton wrote:
> Unless told otherwise, the util-linux test suite assumes that it is
> running in a build tree and looks for binaries to run.
>
> In ptest we're on the target, so it needs to run the system binaries
> instead.
>
> This reduces ~180 skipped
On Mon, Jun 28, 2021 at 2:21 PM Phil Blundell wrote:
> On Mon, Jun 28, 2021 at 02:10:39PM -0700, Khem Raj wrote:
> > well, if we can beat the compiler to not complain about using neon on a
> > non-neon system then yes, but changing float ABI to make compiler happy
> > seems a bit iffy, since
On Mon, Jun 28, 2021 at 02:10:39PM -0700, Khem Raj wrote:
> well, if we can beat the compiler to not complain about using neon on a
> non-neon system then yes, but changing float ABI to make compiler happy
> seems a bit iffy, since compiler will generate code expecting VFP and that
> could trip
n them. otherwise looking
> through tonne of issues you want to ignore is manual effort and can not
> be sustained.
>
> Persian Prince,
>
> I think it would be better if we have a selftest to run linter on AB
> to have this effort sustained in general.
We do have it r
On 6/28/21 12:52 PM, Phil Blundell wrote:
On Mon, Jun 28, 2021 at 12:42:55PM -0700, Khem Raj wrote:
On Mon, Jun 28, 2021 at 12:10 PM Phil Blundell wrote:
On Mon, Jun 28, 2021 at 11:46:08AM -0700, Khem Raj wrote:
I still hope that if we can add a proper neon detection patch to meson
they
On 6/28/21 12:47 PM, Alexander Kanavin wrote:
I just generally disagree with the idea that changing a = b to a=b, or
import a,b to import a\nimport b helps readability or reduces confusion.
I understand that this seems change for change's sake. Consistent coding
formatting goes long way in
On Mon, Jun 28, 2021 at 12:42:55PM -0700, Khem Raj wrote:
> On Mon, Jun 28, 2021 at 12:10 PM Phil Blundell wrote:
> >
> > On Mon, Jun 28, 2021 at 11:46:08AM -0700, Khem Raj wrote:
> > > I still hope that if we can add a proper neon detection patch to meson
> > > they would be ok to accept it.
> >
I just generally disagree with the idea that changing a = b to a=b, or
import a,b to import a\nimport b helps readability or reduces confusion.
I'm reading a lot of python code all the time, and never once have been
confused by inconsistent whitespace.
Can the linter fix anything else, which has
On Mon, Jun 28, 2021 at 12:10 PM Phil Blundell wrote:
>
> On Mon, Jun 28, 2021 at 11:46:08AM -0700, Khem Raj wrote:
> > I still hope that if we can add a proper neon detection patch to meson
> > they would be ok to accept it.
>
> Why doesn't the runtime detection work in the way that upstream
On Mon, Jun 28, 2021 at 12:25 PM Persian Prince wrote:
>
> When we can follow PEP8 we should as it's how developers could follow a
> common coding style and avoid creating different files.
>
> In "Safe PEP8" PRs some PEP8 codes carefully added so it won't change tabs to
> spaces but makes the
On Mon, Jun 28, 2021 at 11:46:08AM -0700, Khem Raj wrote:
> I still hope that if we can add a proper neon detection patch to meson
> they would be ok to accept it.
Why doesn't the runtime detection work in the way that upstream clearly
think it ought to?
p.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You
Signed-off-by: Jose Quaresma
---
.../glslang/{glslang_11.4.0.bb => glslang_11.5.0.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/glslang/{glslang_11.4.0.bb => glslang_11.5.0.bb}
(95%)
diff --git
Signed-off-by: Jose Quaresma
---
.../shaderc/{shaderc_2021.0.bb => shaderc_2021.1.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/shaderc/{shaderc_2021.0.bb => shaderc_2021.1.bb}
(95%)
diff --git
On 6/28/21 11:20 AM, Andrea Adami wrote:
On Mon, Jun 28, 2021 at 7:55 PM Khem Raj wrote:
Hi Andrea
On 6/28/21 3:01 AM, Andrea Adami wrote:
Hello,
during a core-image-sato build for armv4 I got one single build
failure with pulseaudio.
This happens after commit 80bbea0 pulseaudio: switch
On Mon, Jun 28, 2021 at 7:55 PM Khem Raj wrote:
>
> Hi Andrea
>
> On 6/28/21 3:01 AM, Andrea Adami wrote:
> > Hello,
> >
> > during a core-image-sato build for armv4 I got one single build
> > failure with pulseaudio.
> >
> > This happens after commit 80bbea0 pulseaudio: switch build system from
Hi Andrea
On 6/28/21 3:01 AM, Andrea Adami wrote:
Hello,
during a core-image-sato build for armv4 I got one single build
failure with pulseaudio.
This happens after commit 80bbea0 pulseaudio: switch build system from
Autotools to Meson. In the commit text it is evidenced:
"
With Meson
On 6/28/21 12:23 AM, Richard Purdie wrote:
Hi Khem,
I put the branch in for testing:
https://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/glibc-2.34
which resulted in:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2292
Mainly looks like an issue running
Since oe-core fa8950d0c the logic to turn a version into a directory name
doesn't work for versions which are too short.
Solve this by overriding gnome_verdir() to return the version as-is, as
that is what the directory is called.
Signed-off-by: Ross Burton
---
From: Tim Orling
Making ptest images based on core-image-minimal uncovered quite a
few missing depenendcies from various recipes, here they are.
(From OE-Core rev: 2cda6242f2f0f6f9c6bdef72bbb271eab7e5e1f5)
Signed-off-by: Alexander Kanavin
Signed-off-by: Richard Purdie
Backport to Python
From: Tim Orling
Release Date: May 3, 2021
This is the tenth and final regular maintenance release of Python 3.8
Note: The release you're looking at is Python 3.8.10, a bugfix release for the
legacy 3.8 series. Python 3.9 is now the latest feature release series of
Python 3.
FIXME:
From: Tim Orling
Release Date: April 2, 2021
Note: The release you're looking at is Python 3.8.9, a bugfix release for the
legacy 3.8 series. Python 3.9 is now the latest feature release series of
Python 3.
* Refresh test_local.py patch for upstream changes
* Add DEPENDS on autoconf-archive:
From: Tim Orling
Release Date: Dec. 21, 2020
Note: The release you're looking at is Python 3.8.7, a bugfix release for the
legacy 3.8 series. Python 3.9 is now the latest feature release series of
Python 3.
* Drop patch for CVE-2020-27619 fixed in 3.8.7
References:
From: Tim Orling
Backport configure.ac patches to fix
aclocal: error: too many loops
Adds build dependency on autoconf-archive
References:
https://bugzilla.redhat.com/show_bug.cgi?id=1826935
Signed-off-by: Tim Orling
Signed-off-by: Steve Sakoman
---
From: Tim Orling
Release Date: Feb. 19, 2021
Note: The release you're looking at is Python 3.8.8, a bugfix release for the
legacy 3.8 series. Python 3.9 is now the latest feature release series of
Python 3.
Notable changes in Python 3.8.8
Earlier Python versions allowed using both ; and & as
From: Tim Orling
Release Date: Sept. 24, 2020
Note: The release you're looking at is Python 3.8.6, a bugfix release for the
legacy 3.8 series. Python 3.9 is now the latest feature release series of
Python 3.
References:
https://www.python.org/downloads/release/python-386/
From: Tim Orling
Release Date: July 20, 2020
Note: The release you're looking at is Python 3.8.5, a bugfix release for the
legacy 3.8 series. Python 3.9 is now the latest feature release series of
Python 3.
Drop patches fixed in 3.8.5:
- CVE-2019-20907
- CVE-2019-26116
References:
From: Tim Orling
Release Date: July 13, 2020
Note: The release you're looking at is Python 3.8.4, a bugfix release for the
legacy 3.8 series. Python 3.9 is now the latest feature release series of
Python 3.
* Drop patch for CVE-2020-14422 fixed in 3.8.4
* Refresh CVE-2021-23336 patch
From: Jasper Orschulko
https://lists.x.org/archives/xorg-announce/2021-May/003088.html
XLookupColor() and other X libraries function lack proper validation
of the length of their string parameters. If those parameters can be
controlled by an external application (for instance a color name that
From: Jasper Orschulko
There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to
submit a crafted file to be processed by an application linked with libxml2
could trigger a use-after-free. The greatest impact from this flaw is to
confidentiality, integrity, and
From: Tim Orling
Release Date: May 13, 2020
Note: The release you're looking at is Python 3.8.3, a bugfix release for the
legacy 3.8 series. Python 3.9 is now the latest feature release series of
Python 3.
Notable changes in Python 3.8.3:
The constant values of future flags in the __future__
From: Jasper Orschulko
expat < 4.0 is vulnerable to billion laughs attacks (see
[https://github.com/libexpat/libexpat/issues/34]). This patch backports
the commits b1d039607d3d8a042bf0466bfcc1c0f104e353c8
and 60959f2b491876199879d97c8ed956eabb0c2e73 from upstream.
Additionally, the SRC_URI had
From: Michael Halstead
This upgrade builds unnative with gcc11 allowing it to work with newer distros
using gcc 11.
Signed-off-by: Michael Halstead
Signed-off-by: Richard Purdie
(cherry picked from commit a1c7b71c109ca68931d098f4149ab8284d56108e)
Signed-off-by: Steve Sakoman
---
Please review this next set of patches for dunfell and have comments back by
end of day Wednesday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2291
The following changes since commit ac8181d9b9ad8360f7dba03aba8b00f008c6ebb4:
Revert
When attempt_only flag is set to True all installation failures are
ignored. Disable attempt_only, that is the default in install function,
to raise error in install_complementary and to prevent do_populate_sdk
task to treat errors as warnings.
Signed-off-by: Fabio Berton
---
On Mon, Jun 28, 2021 at 3:03 PM Richard Purdie
wrote:
>
> On Mon, 2021-06-28 at 14:44 +0200, Andrea Adami wrote:
> > On Mon, Jun 28, 2021 at 2:36 PM Alexander Kanavin
> > wrote:
> > >
> > > What I am saying is, can you discuss this with upstream first please?
> >
> > Sorry, no, I'm not in the
On Mon, 2021-06-28 at 14:44 +0200, Andrea Adami wrote:
> On Mon, Jun 28, 2021 at 2:36 PM Alexander Kanavin
> wrote:
> >
> > What I am saying is, can you discuss this with upstream first please?
>
> Sorry, no, I'm not in the position to do that.
> Besides, I am dispatching my armv4/armv5te
Unless told otherwise, the util-linux test suite assumes that it is
running in a build tree and looks for binaries to run.
In ptest we're on the target, so it needs to run the system binaries
instead.
This reduces ~180 skipped test cases down to tens, and should fix weird
behaviour. There are
On Thu, 2021-06-24 at 21:48 -0700, Chuck Wolber wrote:
> All,
>
> Please accept my apologies in advance for the detailed submission. I think
> it is warranted in this case.
>
> There is something... "odd" about the GCC 10 compiler that is delivered with
> Hardknott. I am still chasing it down,
On Mon, Jun 28, 2021 at 2:36 PM Alexander Kanavin
wrote:
>
> What I am saying is, can you discuss this with upstream first please?
Sorry, no, I'm not in the position to do that.
Besides, I am dispatching my armv4/armv5te Zaurus hardware so I will
not be able to test anymore.
My point here is,
What I am saying is, can you discuss this with upstream first please?
Alex
On Mon, 28 Jun 2021 at 14:08, Andrea Adami wrote:
> On Mon, Jun 28, 2021 at 1:00 PM Alexander Kanavin
> wrote:
> >
> > Seems like an upstream problem rather than a Yocto one?
>
> Indeed,
>
> from
>
On Mon, Jun 28, 2021 at 1:00 PM Alexander Kanavin
wrote:
>
> Seems like an upstream problem rather than a Yocto one?
Indeed,
from
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/14.0/
"
One difference from Autotools is that the --disable-neon-opt option
for disabling NEON
Hello all,
This is the full report for yocto-3.1.9.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Sangeeta
> -Original Message-
> From:
I have to once again stress that you (zangrc) should learn the devtool
workflow as it handles this too.
Alex
On Mon, 28 Jun 2021 at 11:47, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Mon, 2021-06-28 at 16:15 +0800, zangrc wrote:
> > Signed-off-by: Zang Ruochen
> > ---
> >
Seems like an upstream problem rather than a Yocto one?
Alex
On Mon, 28 Jun 2021 at 12:02, Andrea Adami wrote:
> Hello,
>
> during a core-image-sato build for armv4 I got one single build
> failure with pulseaudio.
>
> This happens after commit 80bbea0 pulseaudio: switch build system from
>
Hello,
during a core-image-sato build for armv4 I got one single build
failure with pulseaudio.
This happens after commit 80bbea0 pulseaudio: switch build system from
Autotools to Meson. In the commit text it is evidenced:
"
With Meson there's no option for disabling Neon optimizations if the
On Mon, 2021-06-28 at 16:15 +0800, zangrc wrote:
> Signed-off-by: Zang Ruochen
> ---
> .../python/{python3-pip_21.1.2.bb => python3-pip_21.1.3.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-devtools/python/{python3-pip_21.1.2.bb =>
>
On Mon, 2021-06-28 at 11:17 +0200, Rasmus Villemoes wrote:
> On 25/06/2021 18.13, Richard Purdie wrote:
> > On Fri, 2021-06-25 at 17:45 +0200, Rasmus Villemoes wrote:
> > > On 25/06/2021 14.16, Richard Purdie wrote:
> > > > On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via
> > > >
On 25/06/2021 18.13, Richard Purdie wrote:
> On Fri, 2021-06-25 at 17:45 +0200, Rasmus Villemoes wrote:
>> On 25/06/2021 14.16, Richard Purdie wrote:
>>> On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via
>>> lists.openembedded.org wrote:
I noticed that if I have an image recipe that
From: Michael Ho
If a read-only sstate mirror is used in conjunction with hash equiv,
then OSError will be raised when an sstate-cache hit is achieved.
This is because sstate_task_postfunc will try to "touch" the symlinks
that point to the read-only sstate mirror when sstate_report_unihash
has
Signed-off-by: Zang Ruochen
---
.../python/{python3-pip_21.1.2.bb => python3-pip_21.1.3.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/python/{python3-pip_21.1.2.bb =>
python3-pip_21.1.3.bb} (83%)
diff --git
Hi Khem,
I put the branch in for testing:
https://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/glibc-2.34
which resulted in:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2292
Mainly looks like an issue running on target test builds not being
able to find
Right, but can you please write something more descriptive than "PEP8
double aggressive W291 ~ W293 and W391" ?
Also I'm not sure fiddling about with whitespace or whether imports all
need their own line really helps.
Alex
On Mon, 28 Jun 2021 at 08:16, Khem Raj wrote:
> On Sun, Jun 27, 2021
On Sun, Jun 27, 2021 at 11:13 PM Alexander Kanavin
wrote:
>
> Wait, what is this patchset all about?
>
its fixes for python linter (pylint) found issues.
> Alex
>
> On Mon, 28 Jun 2021 at 07:59, Khem Raj wrote:
>>
>> From: persianpros
>>
>> Signed-off-by: Khem Raj
>> ---
>>
Wait, what is this patchset all about?
Alex
On Mon, 28 Jun 2021 at 07:59, Khem Raj wrote:
> From: persianpros
>
> Signed-off-by: Khem Raj
> ---
> meta/lib/oe/package.py| 9 +++--
> meta/lib/oe/qa.py | 4 +++-
>
59 matches
Mail list logo
