The following changes since commit bfce90b1260d07f01a8dc2998c9e63ca36d4ebbe:
npm: use npm_registry to cache package (2022-09-06 07:10:59 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
The following changes since commit c9a9d5a1f7fbe88422ccee542a89afbc4c5336e4:
vim: Upgrade 9.0.0242 -> 9.0.0341 (2022-09-07 04:40:43 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
This removes a call to an undocumented and now deprecated subcommand of
git submodule--helper and replaces it with a suppoorted one that gives an
equivalent list.
Signed-off-by: Jacob Creedon
---
meta/classes/externalsrc.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi,
I have faced a problem today that sstate-cache `${SSTATE_PKG}` generation will
silently fail on the file systems no supporting hard linking.
I've faced this problem on cloud-based Kubernetes cluster, where persistent
volume is mounted to Docker containers as shared sstate-cache location.
> -Original Message-
> From: Alexander Kanavin
> Sent: den 15 september 2022 10:20
> To: Peter Kjellerstedt
> Cc: ChenQi ; OE-core c...@lists.openembedded.org>; Alexander Kanavin
> Subject: Re: [OE-core] [PATCH 1/7] scripts/oe-setup-builddir: add a check
> that TEMPLATECONF is valid
>
Add packages for the new Qualcomm firmware released for Lenovo X13s
laptop.
The INSANE_SKIP:${PN} has to be provided to silent following warnings:
WARNING: File '/lib/firmware/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn' from
linux-firmware was already stripped, this will prevent future debugging!
From: Dmitry Baryshkov
License-Update: additional files
Signed-off-by: Dmitry Baryshkov
---
...{linux-firmware_20220708.bb => linux-firmware_20220913.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20220708.bb =>
On Thu, Sep 15, 2022 at 4:20 AM Sundeep KOKKONDA
wrote:
>
> Regression test are performed and below is test summary.
>
> Test summary after glibc updates:
> 204 FAIL
> 4341 PASS
> 41 UNSUPPORTED
> 12 XFAIL
> 6 XPASS
>
> Test summary before glibc updates:
> 200 FAIL
> 4343 PASS
> 41 UNSUPPORTED
>
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxslt* to *1.1.37* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libxslt-upgrade-1.1.35-1.1.37.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *numactl* to *2.0.15* has
Succeeded.
Next steps:
- apply the patch: git am 0001-numactl-upgrade-2.0.14-2.0.15.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *pinentry* to *1.2.1* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe pinentry failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *repo* to *2.29.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-repo-upgrade-2.29.1-2.29.2.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libpng* to *1.6.38* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libpng-upgrade-1.6.37-1.6.38.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *wayland-utils* to *1.1.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade wayland-utils -V 1.1.0
NOTE: Starting bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lttng-modules* to *2.13.5*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxft* to *2.3.6* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade libxft -V 2.3.6
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *flac* to *1.4.0* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade flac -V 1.4.0
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ffmpeg* to *5.1.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ffmpeg-upgrade-5.1-5.1.1.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *linux-firmware* to *20220913*
has Succeeded.
Next steps:
- apply the patch: git am
0001-linux-firmware-upgrade-20220708-20220913.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *virglrenderer* to *0.10.1*
has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe virglrenderer failed.
NOTE: Starting bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-headers* to
*1.3.224.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-vulkan-headers-upgrade-1.3.216.0-1.3.224.1.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-tools* to *1.3.224.1*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mesa* to *22.1.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-mesa-upgrade-22.1.6-22.1.7.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *spirv-headers* to *1.3.224.1*
has Succeeded.
Next steps:
- apply the patch: git am
0001-spirv-headers-upgrade-1.3.216.0-1.3.224.1.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *sqlite3* to *3.39.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-sqlite3-upgrade-3.39.2-3.39.3.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *diffoscope* to *221* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-220-221.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glslang* to *1.3.224.1* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe glslang failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *spirv-tools* to *1.3.224.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-spirv-tools-upgrade-1.3.216.0-1.3.224.1.patch
- check the changes to upstream patches
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libjitterentropy* to *3.4.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-libjitterentropy-upgrade-3.4.0-3.4.1.patch
- check the changes to upstream patches
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libsoup* to *3.2.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libsoup-upgrade-3.0.7-3.2.0.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *nghttp2* to *1.49.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-nghttp2-upgrade-1.48.0-1.49.0.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *grep* to *3.8* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe grep failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to
*2ce8856b7e20c28467f0b2f86429d3f54d7821a5* has Failed(other errors).
Detailed error information:
'MACHINE=qemux86 bitbake vulkan-samples' failed
WARNING: Host
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-loader* to *1.3.224.1*
has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade vulkan-loader -V 1.3.224.1 -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-poetry-core* to
*1.1.0* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-poetry-core -V 1.1.0
NOTE: Starting
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rsync* to *3.2.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-rsync-upgrade-3.2.5-3.2.6.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools* to
*65.3.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-setuptools-upgrade-65.0.2-65.3.0.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-psutil* to *5.9.2*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-psutil-upgrade-5.9.1-5.9.2.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *hdparm* to *9.65* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe hdparm failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3* to *3.10.7* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-python3-upgrade-3.10.6-3.10.7.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *tzdata* to *2022c* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-tzdata-upgrade-2022b-2022c.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-jsonschema* to
*4.16.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *shadow* to *4.12.3* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-shadow-upgrade-4.12.1-4.12.3.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *stress-ng* to *0.14.05* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe stress-ng failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rpm* to *4.17.1.1* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade rpm -V 4.17.1.1 -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gawk* to *5.2.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gawk failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hypothesis* to
*6.54.5* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.46.11-6.54.5.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-bcrypt* to *4.0.0*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libdrm* to *2.4.113* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libdrm-upgrade-2.4.112-2.4.113.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-numpy* to *1.23.3*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-numpy-upgrade-1.23.2-1.23.3.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-certifi* to
*2022.9.14* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-certifi-upgrade-2022.6.15-2022.9.14.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cryptography* to
*38.0.1* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe python3-cryptography failed.
NOTE: Starting bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-idna* to *3.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-idna-upgrade-3.3-3.4.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *meson* to *0.63.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-meson-upgrade-0.63.1-0.63.2.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hatchling* to *1.9.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-hatchling-upgrade-1.8.1-1.9.0.patch
- check the changes to upstream patches
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-dbus* to *1.3.2* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *jquery* to *3.6.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-jquery-upgrade-3.6.0-3.6.1.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libcomps* to *0.1.19* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libcomps-upgrade-0.1.18-0.1.19.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go* to *1.19.1* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe go failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to
*20403c5701973a4cbd7e0b4bbeb627fcd424a0f1* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gnu-config -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *git* to *2.37.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-git-upgrade-2.37.2-2.37.3.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-runtime* to *1.19.1* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe go-runtime failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cryptography-vectors*
to *38.0.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-cryptography-vectors-upgrade-37.0.4-38.0.1.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ninja* to *1.11.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ninja-upgrade-1.11.0-1.11.1.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *llvm* to *15.0.0* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade llvm -V 15.0.0 -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cmake* to *3.24.2* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.24.0-3.24.2.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dnf* to *4.14.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-dnf-upgrade-4.13.0-4.14.0.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ovmf* to *edk2-stable202208*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *btrfs-tools* to *5.19.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-btrfs-tools-upgrade-5.19-5.19.1.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *init-system-helpers* to
*1.65.* has Succeeded.
Next steps:
- apply the patch: git am 0001-init-system-helpers-upgrade-1.64-1.65.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ccache* to *4.6.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ccache-upgrade-4.6.2-4.6.3.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *autoconf-archive* to
*2022.09.03* has Succeeded.
Next steps:
- apply the patch: git am
0001-autoconf-archive-upgrade-2022.02.11-2022.09.03.patch
- check the changes to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *base-passwd* to *3.6.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe base-passwd failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ofono* to *2.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-ofono-upgrade-1.34-2.0.patch
- check the changes to upstream patches and summarize them in the
On Tue, Sep 13, 2022 at 8:04 PM Lee Chee Yang wrote:
>
> From: Chee Yang Lee
>
> backport fixes:
> CVE-2020-13754, backport patches as debian security tracker notes
> https://security-tracker.debian.org/tracker/CVE-2020-13754
>
> CVE-2021-3713
> CVE-2021-3748
> CVE-2021-3930
> CVE-2021-4206
>
Hi,
On Thu, 15 Sep 2022, at 13:50, Andrei Gherzan wrote:
> From: Andrei Gherzan
>
> Grub tries to force the compilation in softfp mode for some known target
> CPU. That is because it doesn't use floats or doubles and there are
> known limitations of using a configuration with hardfp. There are
From: Andrei Gherzan
Grub tries to force the compilation in softfp mode for some known target
CPU. That is because it doesn't use floats or doubles and there are
known limitations of using a configuration with hardfp. There are though
target CPUs that grub won't know how to configure failing
From: Andrei Gherzan
Grub tries to force the compilation in softfp mode for some known target
CPU. That is because it doesn't use floats or doubles and there are
known limitations of using a configuration with hardfp. There are though
target CPUs that grub won't know how to configure failing
On Wed, 2022-09-14 at 16:16 +0200, Marta Rybczynska wrote:
> The sources with a long README are available at
> https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/toolchain/tinfoilhat/-/tree/srctracker/srctracker
>
> What do you think of this work? Would it be of interest to integrate
>
FWIW: nodejs error when it fails to load openssl errors is also a bit
confusing and needs OPENSSL_MODULES export:
https://lists.openembedded.org/g/openembedded-devel/message/96799
On Thu, Sep 15, 2022 at 1:26 PM Mikko Rapeli
wrote:
> Hi,
>
> On Thu, 15 Sept 2022 at 14:18, Ross Burton wrote:
>
Hi,
On Thu, 15 Sept 2022 at 14:18, Ross Burton wrote:
>
> On 14 Sep 2022, at 09:09, Mikko Rapeli via lists.openembedded.org
> wrote:
> > Found the root cause. As suggested on #pyco too maybe native openssl
> > was mising legacy support.
> > It wasn't but loading the on purpose hidden openssl
Regression test are performed and below is test summary.
Test summary *after* glibc updates:
204 FAIL
4341 PASS
41 UNSUPPORTED
12 XFAIL
6 XPASS
Test summary *before* glibc updates:
200 FAIL
4343 PASS
41 UNSUPPORTED
12 XFAIL
6 XPASS
There are 4 tests added newly and 2 are removed with latest
libntirpc is not compatible with libtirpc. Some work would make it so,
but it is not a trivial change, i tried it :)
Not only the API is different, the pkgconfig presents itself as ntirpc
whereas most dependencies of litbtirpc specifically try to detect
libtirpc. A good summary of the
On 14 Sep 2022, at 09:09, Mikko Rapeli via lists.openembedded.org
wrote:
> Found the root cause. As suggested on #pyco too maybe native openssl
> was mising legacy support.
> It wasn't but loading the on purpose hidden openssl legacy.so was
> failing. It is located in
>
Below commits on glibc-2.35 development branch are updated.
f8ad66a4ca nscd: Fix netlink cache invalidation if epoll is used [BZ #29415]
9e960717e1 Apply asm redirections in wchar.h before first use
577c2fc7f3 elf: Call __libc_early_init for reused namespaces (bug 29528)
83f1d9851e NEWS: Add
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e3e5ae049371a27fd1737aba946fe26d06e029b5]
Signed-off-by: pgowda
---
.../binutils/binutils-2.38.inc| 1 +
.../binutils/0016-CVE-2022-38126.patch| 34 +++
On 28 Aug 2022, at 18:43, Paulo Neves via lists.openembedded.org
wrote:
>
> ntirpc is an actively maintained rpc implementation. We cannot completely
> remove libtirpc due to arising circular dependencies where ntirpc
> depends on libnsl2, which in turn depends on an RPC implementation.
Can
Signed-off-by: Alexander Kanavin
---
meta/recipes-core/initscripts/init-system-helpers_1.64.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/initscripts/init-system-helpers_1.64.bb
b/meta/recipes-core/initscripts/init-system-helpers_1.64.bb
index 22ddd6840f..663d60c6e0
On Thu, 15 Sept 2022 at 03:07, Peter Kjellerstedt
wrote:
> I know you have suggested this to me too as we use a similar setup to
> generate the bblayers.conf.sample file based on the layers that repo
> has checked out in our environment, and now I realized why this is not
> as simple as it seems.
From: Ruiqiang Hao
We supported neoversen2 base on armv8.5a in the past, add tune include
for armv9a and support neoversen2 base on armv9a.
Signed-off-by: Ruiqiang Hao
---
meta/conf/machine/include/arm/arch-armv9a.inc | 28 +++
.../include/arm/armv9a/tune-neoversen2.inc|
Hello Adrian,
Sorry for my late replies but i can only work on this effort
sporadically. I was not aware of the issue of runqemu and given that i
am progressing slowly i definitely will follow the breakdown you suggest.
It is taking me quite longer due to the fact that ntirpc is not
From: Teoh Jay Shen
Signed-off-by: Teoh Jay Shen
---
.../inetutils/inetutils/CVE-2022-39028.patch | 54 +++
.../inetutils/inetutils_2.2.bb| 1 +
2 files changed, 55 insertions(+)
create mode 100644
92 matches
Mail list logo
