This reverts commit feb8893e0f52c7ab2d5efd456901a2bb91839d44.
---
meta/recipes-support/libical/libical_3.0.14.bb | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta/recipes-support/libical/libical_3.0.14.bb
b/meta/recipes-support/libical/libical_3.0.14.bb
index af8bc59dae3..58baf3f32f7
This is causing some install failures in meta-openembedded see
last five recipes in this batch
https://errors.yoctoproject.org/Errors/Details/651080/
https://errors.yoctoproject.org/Errors/Details/651082/
https://errors.yoctoproject.org/Errors/Details/651083/
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
ea948a0983d riscv32: drop MAXPHYSMEM_128GB
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb | 2 +-
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
915a747ac7f3 Linux 5.10.103
78706b051a8a memblock: use kfree() to release kmalloced memblock regions
4185b788d3ad gpio: tegra186: Fix chip_data type confusion
From: Bruce Ashfield
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
8993e6067f26 Linux 5.15.26
3c805fce07c9 ice: fix concurrent reset and removal of VFs
26bc7197f9d3 ice: Fix race conditions between virtchnl handling and VF ndo
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/5.15:
871f23ad3627 Revert "ARM: defconfig: Enable ax88796c driver for Exynos
boards"
ffad0783dd5b ARM: config: multi v7: Regenerate defconifg
5c1e1a1ff2d3 ARM: config: multi v7: Add renamed symbols
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/5.10:
253c752ed120 pstore/ftrace: Add and use ftrace_test_recursion_trylock_safe
356e8a12bd66 pstore/ftrace: Add recursion protection to the ftrace callback
334706a1e873 ftrace: Add
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
3969aba589d6 Linux 5.10.101
cb86e511e78e iommu: Fix potential use-after-free during probe
f6b5d51976fc perf: Fix list corruption in perf_cgroup_switch()
From: Bruce Ashfield
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
a0ebea480bb3 Linux 5.15.24
65ab30f6a695 iommu: Fix potential use-after-free during probe
7969fe91c983 perf: Fix list corruption in perf_cgroup_switch()
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
7a012dfacdc features/zram: remove CONFIG_ZRAM_DEF_COMP
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_5.10.bb | 2 +-
From: Bruce Ashfield
Richard,
Here's the next round of -stable and configuration updates for 5.10 and
5.15.
Nothing significant here, I've been soaking them for a while, hopefully
the AB agrees with my "it's green" assesment!
Cheers,
Bruce
The following changes since commit
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto:
commit e1b976ee4fb5af517cf01a9f2dd4a32f560ca894
Author: Bruce Ashfield
Date: Tue Feb 15 23:27:31 2022 -0500
riscv64: drop MAXPHYSMEM_128GB
The MAXPHYSMEM config options have been removed
On 2022-03-04 16:10, Khem Raj wrote:
On Fri, Mar 4, 2022 at 12:56 PM Otavio Salvador
wrote:
Em sex., 4 de mar. de 2022 às 15:04, Alexander Kanavin
escreveu:
Rust is a low-risk item from feature freeze perspective, so I already
queued a patch. If a-full is ok with it, there's no reason not
Where a recipe has depends on native docs tools, in most cases
we don't need recipes that depend on that recipe to also install
these things into the sysroot. We can rely on recipes wanting these
tools to have direct dependencies instead.
This massively reduced dependency creep in simple recipes
The only thing which needs perlcross-native will depend upon it directly
so we can optimise this out everywhere else for small space/speed gains.
Signed-off-by: Richard Purdie
---
meta/conf/layer.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/conf/layer.conf
On Fri, 2022-03-04 at 18:20 +, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org
> > On Behalf Of Carlos Rafael Giani
> > via lists.openembedded.org
> > Sent: den 4 mars 2022 08:55
> > To: openembedded-core@lists.openembedded.org
> >
On Fri, Mar 4, 2022 at 3:14 PM Khem Raj wrote:
>
> On Fri, Mar 4, 2022 at 11:20 AM Konrad Weihmann wrote:
> >
> > If it's about meta-python why can't be placed there? I don't follow the
> > argument that some edge case stuff outside of core requires the project to
> > have additional (as of
On 4 Mar 2022 21:14, Khem Raj wrote:On Fri, Mar 4, 2022 at 11:20 AM Konrad Weihmann wrote:
>
> If it's about meta-python why can't be placed there? I don't follow the argument that some edge case stuff outside of core requires the project to have additional (as of now not time limited)
On Fri, Mar 4, 2022 at 12:56 PM Otavio Salvador
wrote:
>
>
>
> Em sex., 4 de mar. de 2022 às 15:04, Alexander Kanavin
> escreveu:
>>
>> Rust is a low-risk item from feature freeze perspective, so I already
>> queued a patch. If a-full is ok with it, there's no reason not to
>> merge it in my
Em sex., 4 de mar. de 2022 às 15:04, Alexander Kanavin <
alex.kana...@gmail.com> escreveu:
> Rust is a low-risk item from feature freeze perspective, so I already
> queued a patch. If a-full is ok with it, there's no reason not to
> merge it in my opinion.
>
I agree; it makes sense to upgrade it
On Fri, Mar 4, 2022 at 11:20 AM Konrad Weihmann wrote:
>
> If it's about meta-python why can't be placed there? I don't follow the
> argument that some edge case stuff outside of core requires the project to
> have additional (as of now not time limited) maintenance effort - if there
> would
If it's about meta-python why can't be placed there? I don't follow the argument that some edge case stuff outside of core requires the project to have additional (as of now not time limited) maintenance effort - if there would be a clear plan to remove that before kirkstone release I might agree,
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Ross Burton
> Sent: den 4 mars 2022 18:14
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 2/3] setuptools3.bbclass: clean up
>
> There's been a lot
On Fri, Mar 4, 2022 at 10:01 AM Otavio Salvador
wrote:
>
>
>
> Em sex., 4 de mar. de 2022 às 13:56, Khem Raj escreveu:
>>
>> There are recipes in meta-oe and meta-python which would need this
>> and both layer only list core as sole dependency, if we put it in either of
>> these layers, then one
> -Original Message-
> From: openembedded-core@lists.openembedded.org
> On Behalf Of Carlos Rafael Giani
> via lists.openembedded.org
> Sent: den 4 mars 2022 08:55
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH] libsdl2: Add libunwind-native to the
>
Rust is a low-risk item from feature freeze perspective, so I already
queued a patch. If a-full is ok with it, there's no reason not to
merge it in my opinion.
Alex
On Fri, 4 Mar 2022 at 18:45, Randy MacLeod wrote:
>
>
> FYI: 1.59 release notes:
>
Em sex., 4 de mar. de 2022 às 13:56, Khem Raj escreveu:
> There are recipes in meta-oe and meta-python which would need this
> and both layer only list core as sole dependency, if we put it in either of
> these layers, then one will depend on other which is not nice, so I rather
> would prefer
FYI: 1.59 release notes:
https://blog.rust-lang.org/2022/02/24/Rust-1.59.0.html
While there are interesting features in 1.59, such as the inline
assembly support,
we are in feature freeze so I expect we'll stick with 1.58.1 .
It probably also makes sense to skip 1.59 and wait for 1.60 in
inherit setuptools_build_meta
v4.11.2
369: Fixed bug where EntryPoint.extras was returning match objects and not the
extras strings.
v4.11.1
367: In Distribution.requires for egg-info, if requires.txt is empty, return an
empty list.
v4.11.0
bpo-46246: Added __slots__ to EntryPoints.
v4.10.2
setuptools3 pulls this in, so there's no need to explicitly inherit it.
Signed-off-by: Ross Burton
---
meta/recipes-support/bmap-tools/bmap-tools_git.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-support/bmap-tools/bmap-tools_git.bb
There's been a lot of work in this class lately, so a little spring
cleaning is needed.
Create wheels verbosely to help debug problems.
Remove unused SETUPTOOLS_INSTALL_ARGS, these can't be passed to
bdist_wheel.
Remove duplicate manipulation of files in bindir as pip_install_wheel
does the
The asciidoc-py3 repository has been renamed to asciidoc-py.
Signed-off-by: Ross Burton
---
meta/recipes-extended/asciidoc/asciidoc_10.1.3.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-extended/asciidoc/asciidoc_10.1.3.bb
There's been a lot of work in this class lately, so a little spring
cleaning is needed.
Remove redundant creation of PYTHON_SITEPACKAGES_DIR, pip will do that.
Remove redundant export of PYPA_WHEEL.
Simplyify recompile code using "realpath --relative-to".
Signed-off-by: Ross Burton
---
The net result of this series is that for a recipe like run-postinsts (allarch)
with api-documentation enabled, for the do_package task, the recipe-sysroot-
native no longer needs to contain:
e2fsprogs-native
gperf-native
gtk-doc-native
libcap-ng-native
libpcre2-native
libxml2-native
On Fri, Mar 4, 2022 at 6:06 AM Konrad Weihmann wrote:
>
>
>
> On 04.03.22 14:13, Ross Burton wrote:
> > On Fri, 4 Mar 2022 at 12:44, Konrad Weihmann wrote:
> >> For me that would be a candidate to be added to meta-python, or are
> >> there any core recipes that currently break because of the new
Only libuuid is needed by python so reduce the dependency and hence
reduce the amount pulled into the syroot for the native case in particular.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/python/python3_3.10.2.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Currently, libarchive-native pulls e2fsprogs and all it's dependencies into
the sysroot. Since only headers are needed at buildtime and there is no
runtime dependency, we can avoid this and shrink the native sysroots.
Signed-off-by: Richard Purdie
---
meta/conf/layer.conf | 2 ++
1 file
Where a recipe has depends on native docs tools, in most cases
we don't need recipes that depend on that recipe to also install
these things into the sysroot. We can rely on recipes wanting these
tools to have direct dependencies instead.
This massively reduced dependency creep in simple recipes
On Fri, Mar 4, 2022 at 2:13 AM Lee Chee Yang
wrote:
> Error while do_compile
>
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/3190/steps/11/logs/stdio
>
>
I just have missed committing a local change.
>
>
> > -Original Message-
> > From:
From: Michael Halstead
Add support for glibc 2.35.
Signed-off-by: Michael Halstead
Signed-off-by: Richard Purdie
(cherry picked from commit 347b8c87fb4e2c398644f900728cf6e22ba4516d)
Signed-off-by: Steve Sakoman
---
meta/conf/distro/include/yocto-uninative.inc | 10 +-
1 file
From: Richard Purdie
uninative works via hashes and doesn't need the version in the tarball name but
it does make things easier to inspect in DL_DIR. There were reasons such as
ease of publication of the build tarballs but we can handle those differently
now and the signature issues from the
From: Nathan Rossi
The linux kernel will by default use pkg-config to get ncurses(w) paths,
falling back to absolute path checks otherwise. If the build host does
not have ncurses installed this will fail as pkg-config will not search
the native sysroot for ncurses.
To more all kernel/kconfig
From: Jose Quaresma
When the BUILDHISTORY_RESET is enabled we need to move the
content from BUILDHISTORY_DIR to BUILDHISTORY_OLD_DIR but
when we start a clean build in the first run we don't have the
BUILDHISTORY_DIR so the move of files will fail.
| ERROR: Command execution failed: Traceback
From: Richard Purdie
Running the ptest package in an image alone highlighted missing module
dependencies. Add them to fix those errors.
Signed-off-by: Richard Purdie
(cherry picked from commit 3859f49db2d694c7b63fdbe25be0018afba5c738)
Signed-off-by: Steve Sakoman
---
From: Marek Vasut
Without this dependency, generating the bootchart may fail with:
"
ModuleNotFoundError: No module named 'random'
"
(cherry picked from commit 487e9f16a00f895159b79f1865fe8b626b47ddc2)
Signed-off-by: Marek Vasut
Cc: Mingli Yu
Cc: Richard Purdie
Signed-off-by: Steve Sakoman
From: wangmy
Signed-off-by: Wang Mingyu
Signed-off-by: Richard Purdie
(cherry picked from commit e5c06ddfd3c0db0d0762c0241c019f59ad310e53)
Signed-off-by: Steve Sakoman
---
...ireless-regdb_2021.08.28.bb => wireless-regdb_2022.02.18.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Ross Burton
Now that all of the functions in cve-check open the database read-only,
we can remove this lockfile.
This means cve-check can run in parallal again, improving runtimes
massively.
This reverts commit d55fbf4779483d2cfd71df78d0f733b599fef739.
Signed-off-by: Ross Burton
From: Ross Burton
All of the function in cve-check should open the database read-only, as
the only writer is the fetch task in cve-update-db. However,
get_cve_info() was failing to do this, which might be causing locking
issues with sqlite.
Signed-off-by: Ross Burton
Signed-off-by: Richard
From: Ross Burton
Three CVEs were meant to be ignored via CVE_WHITELIST, but that wasn't
the correct variable name.
The CPEs for those CVEs mean that they don't get picked up in our report,
so just remove the assignment.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
(cherry picked
In Expat (aka libexpat) before 2.4.5, there is an integer overflow
in storeRawNames.
Backport patch from:
https://github.com/libexpat/libexpat/pull/559/commits/eb0362808b4f9f1e2345a0cf203b8cc196d776d9
CVE: CVE-2022-25315
Signed-off-by: Steve Sakoman
---
.../expat/expat/CVE-2022-25315.patch
In Expat (aka libexpat) before 2.4.5, there is an integer overflow in
copyString.
Backport patch from:
https://github.com/libexpat/libexpat/pull/560/commits/efcb347440ade24b9f1054671e6bd05e60b4cafd
CVE: CVE-2022-25314
Signed-off-by: Steve Sakoman
---
.../expat/expat/CVE-2022-25314.patch
In Expat (aka libexpat) before 2.4.5, an attacker can trigger stack
exhaustion in build_model via a large nesting depth in the DTD element.
Backport patch from:
https://github.com/libexpat/libexpat/pull/558/commits/9b4ce651b26557f16103c3a366c91934ecd439ab
Also add patch which fixes a regression
xmlparse.c in Expat (aka libexpat) before 2.4.5 allows
attackers to insert namespace-separator characters into
namespace URIs.
Backport patches from:
https://github.com/libexpat/libexpat/pull/561/commits
CVE: CVE-2022-25236
Signed-off-by: Steve Sakoman
---
.../expat/expat/CVE-2022-25236.patch
xmltok_impl.c in Expat (aka libexpat) before 2.4.5 lacks certain
validation of encoding, such as checks for whether a UTF-8 character
is valid in a certain context.
Backport patches from:
https://github.com/libexpat/libexpat/pull/562/commits
CVE: CVE-2022-25235
Signed-off-by: Steve Sakoman
---
From: Minjae Kim
crypto/elliptic: fix IsOnCurve for big.Int values that are not valid coordinates
Some big.Int values that are not valid field elements (negative or overflowing)
might cause Curve.IsOnCurve to incorrectly return true. Operating on those
values
may cause a panic or an invalid
From: Minjae Kim
math/big: prevent large memory consumption in Rat.SetString
An attacker can cause unbounded memory growth in a program using
(*Rat).SetString
due to an unhandled overflow.
Upstream-Status: Backport [https://go.dev/issue/50699]
CVE: CVE-2022-23772
Signed-off-by:Minjae Kim
From: Virendra Thakur
Add patch to fix CVE-2021-36976
CVE-2021-36976 fix are provided by below mentioned pull request.
1) https://github.com/libarchive/libarchive/pull/1491
2) https://github.com/libarchive/libarchive/pull/1492
3) https://github.com/libarchive/libarchive/pull/1493
Please review this set of patches for dunfell and have comments back by end
of day Tuesday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3314
with the exception of a known autobuilder intermittent issue on qemumips64:
On 04.03.22 14:13, Ross Burton wrote:
On Fri, 4 Mar 2022 at 12:44, Konrad Weihmann wrote:
For me that would be a candidate to be added to meta-python, or are
there any core recipes that currently break because of the new behavior?
This is restoring existing behaviour, so I believe it
On Fri, 4 Mar 2022 at 12:44, Konrad Weihmann wrote:
> For me that would be a candidate to be added to meta-python, or are
> there any core recipes that currently break because of the new behavior?
This is restoring existing behaviour, so I believe it should be in
core. There's going to be
For me that would be a candidate to be added to meta-python, or are
there any core recipes that currently break because of the new behavior?
Furthermore the variables names are the same, so if people accidentally
(or due to complex injection trees/classes/distro settings/whatever have
new
Following a good discussion with PyPA upstream[1] the migration of the
setuptools3.bbclass to use bdist_wheel+pip turns out to be more complex
than thought.
Essentially, we're midway through a lot of changes: the future of Python
packaging is wheels and pip, but those by design are not as
Error while do_compile
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/3190/steps/11/logs/stdio
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Tim Orling
> Sent: Friday, March 4, 2022 4:44 AM
> To:
Hi Daniel,
thanks for the explanation. To be honest, when I was dealing with the
layer structure, I didn't take a case about the layer outside of "work"
directory.
Basically it's the same as mine, but respect the external layers
outside of work, right? So, your proposal makes sense to me.
Hello Andrej,
On Thu, 2022-03-03 at 06:35 +, Andrej Valek wrote:
> Hi Daniel,
>
> Could you please give here the examples how the layer structure looks
> before and after change? I want to see how transformation looks like.
With a directory-structure like
/
├── repo
│ └── layers
│
Richard Purdie escreveu no dia quinta,
3/03/2022 à(s) 23:15:
> On Thu, 2022-03-03 at 15:05 -0800, Khem Raj wrote:
> > On Thu, Mar 3, 2022 at 2:53 PM Richard Purdie
> > wrote:
> > >
> > > On Mon, 2022-02-28 at 20:13 -0800, Khem Raj wrote:
> > > > This ensures that right sysroot is used during
66 matches
Mail list logo
