lzo was missing CVE_PRODUCT and related CVEs (at least CVE-2014-4607) were
not reported.
Signed-off-by: Marta Rybczynska
---
meta/recipes-support/lzo/lzo_2.10.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-support/lzo/lzo_2.10.bb
b/meta/recipes-support/lzo/lzo_2.10.bb
ind
6.14.8 - 2021-08-16
This patch ensures that registering a strategy for a subclass of a
parametrised generic type such as class Lines(Sequence[str]): will not
“leak” into unrelated strategies such as st.from_type(Sequence[int])
(issue #2951). Unfortunately this fix requires PEP 560, meaning Python
3
v4.6.4
Issue 334: Correct SimplePath protocol to match pathlib protocol
for __truediv__.
References:
https://github.com/python/importlib_metadata/issues/334
Signed-off-by: Tim Orling
---
...ib-metadata_4.6.3.bb => python3-importlib-metadata_4.6.4.bb} | 2 +-
1 file changed, 1 insertion(+),
Hi Khem Raj,
FYI, the patch is committed in hardknott branch,
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=hardknott&id=9df882ce6835692774c649405fcb474ea0eacda4
Regards,
Vinay
On Mon, Aug 16, 2021 at 8:45 PM Khem Raj wrote:
>
> On Mon, Aug 16, 2021 at 1:59 AM Vinay Kumar wrote:
>
GCC has the ability to pass extensions to the march parameter, which
expand the funcationality of the march. For example
"-march=armv7ve+simd" adds SIMD to ARMv7. Currently, there is no way to
expand the march setting without modifying each instance, as you can't
guarantee the ordering when using
Add tune entries for all Arm Cortex-R processors currently supported in
GCC. Also, add the simd feature, which can be used in ARMv7a and
ARMv8a, but currently isn't.
Signed-off-by: Jon Mason
---
meta/conf/machine/include/arm/arch-armv7a.inc | 1 +
meta/conf/machine/include/arm/arch-armv7r.inc
On 2021-08-18 7:05 p.m., Sakib Sajal wrote:
Update glibc to head of release/2.34/master branch to
to include fixes, includes fix for CVE-2021-38604:
Changelog:
glibc.git$ git log --oneline ae37d06c7d127817ba43850f0f898b793d42aea7...
7c987a5ccb (HEAD, origin/release/2.34/master) librt: add test (
Update glibc to head of release/2.34/master branch to
to include fixes, includes fix for CVE-2021-38604:
Changelog:
glibc.git$ git log --oneline ae37d06c7d127817ba43850f0f898b793d42aea7...
7c987a5ccb (HEAD, origin/release/2.34/master) librt: add test (bug 28213)
7947430322 librt: fix NULL pointer
On 2021-08-16 12:14 p.m., Khem Raj wrote:
On Wed, Jul 14, 2021 at 6:42 AM Joshua Watt wrote:
Adds the command line compression tools which are needed by bitbake
Signed-off-by: Joshua Watt
---
meta/conf/bitbake.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/
On Wed, Aug 18, 2021 at 2:40 PM Sakib Sajal wrote:
>
> Hi Khem,
>
> I was going to apply the commit
>
> glibc is currently at ae37d06c7d127817ba43850f0f898b793d42aea7, 8
> commits behind origin/release/2.34/master as shown below.
>
> Those commits also contain the fix for CVE-2021-38604. Should I
Hi Khem,
I was going to apply the commit
glibc is currently at ae37d06c7d127817ba43850f0f898b793d42aea7, 8
commits behind origin/release/2.34/master as shown below.
Those commits also contain the fix for CVE-2021-38604. Should I go ahead
and update:
./glibc-version.inc:SRCREV_glibc ?=
"ae
- There are situration when the user have the 'patchdir' defined
as a parameter on SRC_URI. However he doesn't know with this,
the patch is applied relatively to the receipe source 'S'.
* On the next example, the patch is applied on ${WORKDIR}/contrib.
But if the user specifies a path on 'patchdir
On 8/19/2021 12:04 AM, Trevor Woerner wrote:
> root@rock-pi-e:~# zramctl
> NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
> /dev/zram2 lz4 975.6M4K 73B 12K 4 [SWAP]
> /dev/zram1 lz410M 400K 16.1K 240K 4 /run
> /de
On Wed 2021-08-18 @ 11:37:36 PM, Sinan Kaya wrote:
> On 8/18/2021 11:36 PM, Trevor Woerner wrote:
> > this is a WIP patch submitted for RFC
> > this patch only works, currently, with sysvinit
> > but I wanted to get feedback on the general approach before tackling systemd
>
> How about using/exten
On 8/18/2021 11:36 PM, Trevor Woerner wrote:
> this is a WIP patch submitted for RFC
> this patch only works, currently, with sysvinit
> but I wanted to get feedback on the general approach before tackling systemd
How about using/extending the zram package in meta-openembedded?
Would that be an op
The zram kernel module creates RAM-based block devices named /dev/zram
( = 0, 1, ...). Pages written to these disks are compressed and stored
in memory itself. These disks allow very fast I/O and compression provides
good amounts of memory savings. Some of the use cases include /tmp storage,
use as
Hi,
d.getVar("BB_NUMBER_THREADS") returns a string and it needs to be
converted to int.
-nproc = min(d.getVar("BB_NUMBER_THREADS"), len(tasklist))
+nproc = min(int(d.getVar("BB_NUMBER_THREADS")), len(tasklist))
fixed in V4
Richard Purdie escreveu no dia
quarta, 18/08/2021 à(s) 20:34:
>
> On We
- bitbake BB_NUMBER_THREADS uses cpu_count from oe utils that uses
the python os.sched_getaffinity and it is more acurrate.
grep -nH ^BB_NUMBER_THREADS meta/conf/bitbake.conf
meta/conf/bitbake.conf:806:BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
- multiprocessing.cpu_count() returns the num
We only has the progress bar when we have more than 100 objects.
So check for this and store the result to show the progress bar.
Signed-off-by: Jose Quaresma
---
meta/classes/sstate.bbclass | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/meta/classes/sstate.bbcl
On the first search we found some files on the local sstate cache.
The missing files are know as well when this step finish.
When we have sstate mirrors we don't need to iterate all files again
because we already know what's missing.
Signed-off-by: Jose Quaresma
---
meta/classes/sstate.bbclass |
We don't need extra python collections to count the found files
on the sstate cache and sstate mirrors.
The main found collections provides all the files that were found,
then we only need to count the files on sstate mirror
Signed-off-by: Jose Quaresma
---
meta/classes/sstate.bbclass | 13 +
The zram kernel module creates RAM-based block devices named /dev/zram
( = 0, 1, ...). Pages written to these disks are compressed and stored
in memory itself. These disks allow very fast I/O and compression provides
good amounts of memory savings. Some of the use cases include /tmp storage,
use as
On Wed, 2021-08-18 at 17:24 +0100, Jose Quaresma wrote:
> - bitbake BB_NUMBER_THREADS uses cpu_count from oe utils that uses
> the python os.sched_getaffinity and it is more acurrate.
>
> grep -nH ^BB_NUMBER_THREADS meta/conf/bitbake.conf
> meta/conf/bitbake.conf:806:BB_NUMBER_THREADS ?= "${@oe.
Currently, depends.dot includes per-file dependencies but not the packages
providing those files. This makes it hard to obtain all package
dependencies by just looking at depends.dot.
Parse the RPROVIDES and FILERPROVIDES fields from pkgdata to map each of
their values to the package providing the
On Wed, 2021-08-18 at 06:42 -0700, Khem Raj wrote:
>
>
> On Wed, Aug 18, 2021 at 12:00 AM Richard Purdie
> wrote:
> > On Tue, 2021-08-17 at 17:40 -0700, Khem Raj wrote:
> > > hmm I am seeing pseudo build failures on master-next on all arches see
> > > [1]. I wonder if this is related
> > >
>
The merge of libdl into libc in glibc 2.34 causes problems for pseudo. Add a fix
that works around this issue.
Signed-off-by: Richard Purdie
---
.../pseudo/files/glibc234.patch | 86 +++
meta/recipes-devtools/pseudo/pseudo_git.bb| 1 +
2 files changed, 87 inser
The elfutils ptests require debug symbols for the libc to be available, else
we see failures such as those on the autobuilder for the fast ptest image
on arm (the dbg symbols are pulled in by other recipes in other images).
Also fix various test skips/error messages due to missing gcc/ld and
devel
From: Ross Burton
Alongside GLIBC and UCLIBC, also relocate the musl loader.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/gcc/gcc-multilib-config.inc | 8
1 file changed, 8 insertions(+)
diff --git a/meta/recipes-devtools/gcc/gcc-multilib-config
Use the same dynamic link tweak for libdl as without this, we have issues
building/using pseudo in mixed glibc/libdl environments.
Signed-off-by: Richard Purdie
---
meta/recipes-core/glibc/glibc-package.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/glibc/glibc-package
In newer gcc versions the headers changed locations and our multiconfig
and nativesdk tweaks to loader paths wasn't working. The broke
buildtools-extended-tarball, particularly on arm. Update to fix this.
Ultimately we should dump the gcc specs and check for hardcoded paths.
This isn't possible qu
- bitbake BB_NUMBER_THREADS uses cpu_count from oe utils that uses
the python os.sched_getaffinity and it is more acurrate.
grep -nH ^BB_NUMBER_THREADS meta/conf/bitbake.conf
meta/conf/bitbake.conf:806:BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
- multiprocessing.cpu_count() returns the num
We only has the progress bar when we have more than 100 objects.
So check for this and store the result to show the progress bar.
Signed-off-by: Jose Quaresma
---
meta/classes/sstate.bbclass | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/meta/classes/sstate.bbcl
On the first search we found some files on the local sstate cache.
The missing files are know as well when this step finish.
When we have sstate mirrors we don't need to iterate all files again
because we already know what's missing.
Signed-off-by: Jose Quaresma
---
meta/classes/sstate.bbclass |
We don't need extra python collections to count the found files
on the sstate cache and sstate mirrors.
The main found collections provides all the files that were found,
then we only need to count the files on sstate mirror
Signed-off-by: Jose Quaresma
---
meta/classes/sstate.bbclass | 13 +
First of all, sorry for the inconvenience of this patch that adds many troubles.
I have concluded from the commit history that the lock is introduced
because of the progress bar and I don't know that the debug message
uses the events when it runs inside threads.
Basically I am wrong in my assumpt
Source: https://sourceware.org/git/glibc.git
Tracking -- https://sourceware.org/bugzilla/show_bug.cgi?id=28213
Backported upstream commits b805aebd42364fe696e417808a700fdb9800c9e8 and
4cc79c217744743077bf7a0ec5e0a4318f1e6641
to glibc-2.33 source.
Upstream-Status: Backport
[https://sourceware.or
Source: https://sourceware.org/git/glibc.git
Tracking -- https://sourceware.org/bugzilla/show_bug.cgi?id=28213
Backported upstream commits b805aebd42364fe696e417808a700fdb9800c9e8 and
4cc79c217744743077bf7a0ec5e0a4318f1e6641
to glibc-2.34 source.
Upstream-Status: Backport
[https://sourceware.or
Hello
On Wed, 2021-08-18 at 16:46 +0530, Purushottam Choudhary wrote:
> From: Glenn Strauss
> +Date: Wed, 23 Dec 2020 23:14:47 -0500
> +Subject: [PATCH] reuse large mem chunks (fix mem usage) (fixes #3033)
> +
> +(cherry picked from commit 7ba521ffb4959f6f74a609d5d4acafc29a038337)
> +
> +(thx fly
On Wed, Aug 18, 2021 at 10:49 AM Steve Sakoman wrote:
>
> Hi Bruce,
>
> On Wed, Aug 18, 2021 at 4:05 AM wrote:
> >
> > From: Bruce Ashfield
> >
> > Updating linux-yocto/5.4 to the latest korg -stable release that comprises
> > the following commits:
> >
> > b704883aa8dc Linux 5.4.141
> >
From: Dmitry Baryshkov
Add firmware packages for the recent Qualcomm SoCs:
- linux-firmware-qcom-adreno-a650, linux-firmware-qcom-adreno-a660,
containing firmware for Adreno A630 and A650 GPUs
- linux-firmware-qcom-sm8250-audio, linux-firmware-sm8250-compute,
containing firmware for aud
Hi Bruce,
On Wed, Aug 18, 2021 at 4:05 AM wrote:
>
> From: Bruce Ashfield
>
> Updating linux-yocto/5.4 to the latest korg -stable release that comprises
> the following commits:
>
> b704883aa8dc Linux 5.4.141
> 983d6a6b7e3c btrfs: don't flush from btrfs_delayed_inode_reserve_metadata
>
On Wed, Aug 18, 2021 at 12:41 AM Purushottam Choudhary
wrote:
>
> assimp CMake modules were adding non-existing paths to its CMake modules
> breaking builds for users of assimp. Remove the hardcoded paths with
> an upstream patch with small tweaks.
>
> Signed-off-by: Purushottam Choudhary
> ---
>
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
b704883aa8dc Linux 5.4.141
983d6a6b7e3c btrfs: don't flush from btrfs_delayed_inode_reserve_metadata
ea13f678a3fd btrfs: export and rename qgroup_reserve_meta
41
On Wed, Aug 18, 2021 at 12:00 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Tue, 2021-08-17 at 17:40 -0700, Khem Raj wrote:
> > hmm I am seeing pseudo build failures on master-next on all arches see
> > [1]. I wonder if this is related
> >
> > https://errors.yoctoproject.org
On Wed, 18 Aug 2021, Ross Burton wrote:
> No, yes. systemd_system_unitdir is newer so it's used less.
i'll put together a patch and see if it's just more churn than it's
worth.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154916):
http
Added 0001-core-reuse-large-mem-chunks-fix-mem-usage-fixes-3033.patch
to fix large memory usage for large file downloads
from dynamic backends reuse or release large memory chunks.
This issue is caused by a bug in the lighttpd 1.4.55 version and
has been fixed in lighttpd 1.4.58. Hence, it is not
assimp CMake modules were adding non-existing paths to its CMake modules
breaking builds for users of assimp. Remove the hardcoded paths with
an upstream patch with small tweaks.
Signed-off-by: Purushottam Choudhary
---
...-ASSIMP_LIB_INSTALL_DIR-to-search-library.patch | 68 --
...ove-shar
Currently in dunfell branch python3 version is 3.8.11.
so, python3_3.8.10.bb is not needed.
Hence, removed.
Signed-off-by: Purushottam Choudhary
---
meta/recipes-devtools/python/python3_3.8.10.bb | 363 -
1 file changed, 363 deletions(-)
delete mode 100644 meta/recipes-d
Looks like update-alternatives --install is not happening at all for any
packages during do_rootfs.
Thanks,
Devendra
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154912):
https://lists.openembedded.org/g/openembedded-core/message/154912
Mute Th
Verify that HTTPS connections work in both wget and Python, as this
depends on variables correctly pointing to the certificate chain.
Signed-off-by: Ross Burton
---
meta/lib/oeqa/sdk/buildtools-cases/https.py | 20
1 file changed, 20 insertions(+)
create mode 100644 meta/li
No, yes. systemd_system_unitdir is newer so it's used less.
Ross
On Wed, 18 Aug 2021 at 08:48, Robert P. J. Day wrote:
>
>
> i've (so far) run across a small number of OE recipes that use the
> identifier "${D}${systemd_unitdir}/system", which appears(?) to be
> equivalent to "${D}${systemd_s
Please merge these changes.
Thanks,
Anuj
The following changes since commit 49868162a1a1d088fbaabeffcc2debcbfc17b026:
nettle: update 3.7.2 -> 3.7.3 (2021-08-09 10:19:38 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/hardknott-ne
i've (so far) run across a small number of OE recipes that use the
identifier "${D}${systemd_unitdir}/system", which appears(?) to be
equivalent to "${D}${systemd_system_unitdir}". is there any potential
functional difference, or should this be standardized?
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links:
On Tue, 2021-08-17 at 17:40 -0700, Khem Raj wrote:
> hmm I am seeing pseudo build failures on master-next on all arches see
> [1]. I wonder if this is related
>
> https://errors.yoctoproject.org/Errors/Details/601473/
I think that would be an issue with my patch in master-next to try and fix
oth
54 matches
Mail list logo