meta-rust is generally seen as obsolete, is there a particular reason
you need to use it with oe-core master, instead of the standard rust
recipes?
Even then, this looks like it needs to be fixed in meta-rust, rather
than individual recipes. The error does not occur with official rust
toolchain,
When using meta-rust layer for rust below
do_package_qa error in librsvg is observed
Fix the below error:
ERROR: librsvg-2.52.10-r0 do_package_qa: QA Issue: File /usr/bin/rsvg-convert
in package rsvg doesn't have GNU_HASH (didn't pass LDFLAGS?) File
/usr/bin/rsvg-convert in package rsvg doesn't
When using meta-rust layer for rust below
do_package_qa error in librsvg is observed
Fix the below error:
ERROR: librsvg-2.52.10-r0 do_package_qa: QA Issue: File /usr/bin/rsvg-convert
in package rsvg doesn't have GNU_HASH (didn't pass LDFLAGS?) File
/usr/bin/rsvg-convert in package rsvg doesn't
When using meta-rust layer for rust below
do_package_qa error in librsvg is observed
Fix the below error:
ERROR: librsvg-2.52.10-r0 do_package_qa: QA Issue: File /usr/bin/rsvg-convert
in package rsvg doesn't have GNU_HASH (didn't pass LDFLAGS?) File
/usr/bin/rsvg-convert in package rsvg doesn't
When using meta-rust layer for rust below
do_package_qa error in librsvg is observed
Fix the below error:
ERROR: librsvg-2.52.10-r0 do_package_qa: QA Issue: File /usr/bin/rsvg-convert
in package rsvg doesn't have GNU_HASH (didn't pass LDFLAGS?) File
/usr/bin/rsvg-convert in package rsvg doesn't
From: Xiangyu Chen
The current tests will run both userspace and kernel testing. Some of use cases
only use lttng for one kind of tracing (e.g. userspace). If the lttng
modules(.ko files) is not present during the test,it would end up with lots of
failing.
Add a check in ptest script, if
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/v2-lttng-tools-lttng-tools-skip-lttng-kernel-related-test-if-lttng-kernel-modules-not-present.patch
FAIL: test
From: Xiangyu Chen
The current tests will run both userspace and kernel testing. Some of use cases
only use lttng for one kind of tracing (e.g. userspace). If the lttng
modules(.ko files) is not present during the test,it would end up with lots of
failing.
Add a check in ptest script, if
On 2/10/24 00:44, Richard Purdie wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Wed, 2024-01-31 at 11:40 +0800, Xiangyu Chen wrote:
From: Xiangyu Chen
The current
Ping
> -Original Message-
> From: openembedded-core@lists.openembedded.org
> On Behalf Of Khem Raj
> Sent: Monday, February 26, 2024 2:19 PM
> To: Lei, Maohui
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] glibc: Fix conflict error when enbale
From: Meenali Gupta
A flaw was found in Expat (libexpat). If XML_DTD is undefined at compile time,
a recursive XML Entity
Expansion condition can be triggered. This issue may lead to a condition where
data is expanded exponentially,
which will quickly consume system resources and cause a
This series is causing issues with adding and resizing partitions.
This reverts commit 5832eebee3c150a30bd489699ca693240d11beda.
---
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_5.15.bb| 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.15.bb |
This series is causing issues with adding and resizing partitions.
This reverts commit 4deed206f92fc207d18cdb4c8bc35ce1bf0fb0f6.
---
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_5.15.bb| 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.15.bb |
This series is causing issues with adding and resizing partitions.
This reverts commit 03794866c1333113c909ef88dc232bcc47a7c459.
---
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_5.15.bb| 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.15.bb |
This series is causing issues with adding and resizing partitions.
This reverts commit f4f1964a7a2922f3253484852b76602af5f31a89.
---
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_5.15.bb| 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.15.bb |
This series is causing issues with adding and resizing partitions.
This reverts commit ee4695138e36155c8e0b173f7952372693c0589a.
---
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_5.15.bb| 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.15.bb |
This series is causing issues with adding and resizing partitions.
This reverts commit 22b1db5362e18ee6c2a90049facc72c3554542dd.
---
.../linux/cve-exclusion_5.15.inc | 259 +++---
1 file changed, 36 insertions(+), 223 deletions(-)
diff --git
This series is causing issues with adding and resizing partitions.
This reverts commit c7c86d97f6a0e1d09eaca999ecec13656655f299.
---
.../linux/cve-exclusion_5.15.inc | 44 +++
1 file changed, 7 insertions(+), 37 deletions(-)
diff --git
This series is causing issues with adding and resizing partitions.
This reverts commit f1326d008a2a37b3860f25eb082efabdeba7cc32.
---
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_5.15.bb| 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.15.bb |
This series is causing issues with adding and resizing partitions.
This reverts commit b71eeab71911ab49a8e8b8d78560fdbd66f883e7.
---
.../linux/cve-exclusion_5.15.inc | 91 ++-
1 file changed, 6 insertions(+), 85 deletions(-)
diff --git
Unfortunately this series of linux-yocto version bumps has caused a
number of issues with adding and resizing partitions. The problem was
introduced in 5.15.132 and has not been fixed in any of the subsequent
version bumps.
Bruce and have decided to revert this series until we have an acceptable
Adding Kevin,
I'm not going to be able to debug this more for a week or so.
The alternate ways to fix it would be to try that ubuntu patch (fixed
for our tree), and / or see what else needs
to be cherry picked to -stable to fix util-linux. It is likely just a
return code difference to userspace
Hi Bruce,
This patch seems to fix the parted ptest problems, but now util-linux
ptest is failing :-(
Also seems to be partition resize related:
AssertionError: Failed ptests:
{'util-linux': ['fdisk:_gpt-resize']}
Steve
On Thu, Mar 7, 2024 at 9:34 AM Bruce Ashfield wrote:
>
> From: Bruce
As we're close to release, drop compatibility to nanbield, people
have had time to switch now.
Signed-off-by: Richard Purdie
---
meta/conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index 2418ee7d53b..62f86f361ad
Socket activation is prone to DoS (denial of service) because too many
connections will permanently deactivate sshd.socket [1]. Also, since
socket units do not allow setting Restart, accepting new connections can
fail due to, for example, OOM (out of memory) [2]. Therefore, it seems
more sensible
From: Bruce Ashfield
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
80efc6265290 Linux 5.15.150
da6cabc1981e r8169: use new PM macros
b7f3fac6d301 netfilter: nf_tables: can't schedule in nft_chain_validate
a4efc62cd1ed ext4:
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 25Feb24
Date: Sun, 25 Feb 2024 07:03:08 -0500
]
Signed-off-by: Bruce Ashfield
---
From: Bruce Ashfield
Signed-off-by: Bruce Ashfield
---
...partitions-if-GD_SUPPRESS_PART_SCAN-.patch | 43 +
...-support-partitions-without-scanning.patch | 87 +++
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 4 +
3 files changed, 134 insertions(+)
create mode
libosinfo fails due to this upgrade
https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/3691/steps/14/logs/stdio
On Wed, Mar 6, 2024 at 7:42 AM Alexander Kanavin wrote:
>
> License-Update: hash.c is rewritten and no longer carries a special copyright
> notice, but dict.c still
da9db878a15 systemd: fix dead link /var/log/README
add -Dcreate-log-dirs=false which means journal dir
will not be generated regardless of VOLATILE_LOG_DIR value
if a distro decided to set VOLATILE_LOG_DIR=no this
code path will be executes and the directory being operated
upon wont exist ending
The rename of bmap-tools to bmaptool creates an incompatibility that
will break package feeds. Restore package feed compatibility by adding
a bmap-tools runtime alias.
Acked-by: Otavio Salvador
Signed-off-by: Tom Hochstein
---
meta/recipes-support/bmaptool/bmaptool_git.bb | 4
1 file
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/kirkstone-3-4-selftest-skip-virgl-gtk-sdl-test-on-ubuntu-18.04.patch
FAIL: test commit message presence: Please
From: Hitendra Prajapati
Backport fixes for:
CVE-2023-45289 - Upstream-Status: Backport from
https://github.com/golang/go/commit/3a855208e3efed2e9d7c20ad023f1fa78afcc0be
CVE-2023-45290 - Upstream-Status: Backport from
https://github.com/golang/go/commit/041a47712e765e94f86d841c3110c840e76d8f82
Signed-off-by: Steve Sakoman
---
meta/lib/oeqa/selftest/cases/runtime_test.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py
b/meta/lib/oeqa/selftest/cases/runtime_test.py
index d06d480c2b..7dcdfd0ab2 100644
---
From: Fabio Estevam
Commit cc6c3e31526d ("u-boot: Move definitions to common locations") moved
UBOOT_INITIAL_ENV to uboot-config.bbclass, but it should be kept at u-boot.inc
because it encodes ${PN} in it, which should be set by the U-Boot recipe.
Currently, whatever inherits uboot-config
From: Chen Qi
The clear text password support has been dropped. So let's just
use a normal ecrypted one. The password remains to be 'user3'.
Signed-off-by: Chen Qi
Signed-off-by: Richard Purdie
(cherry picked from commit cd8232f9c58980d95180ad320b7b0bb0fcfd9ff5)
Signed-off-by: Fabio Berton
Please review this set of changes for kirkstone and have comments back by
end of day Monday, March 11
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6658
The following changes since commit d63af11e92094487d6e358f27283e5385937e7a8:
I retract this final patch of the series: there’s a few licenses which specify
that the text needs to be distributed alongside the firmware and not just in
“documentation or similar”.
The rest of the patches are good, however.
Ross
> On 7 Mar 2024, at 12:05, Ross Burton via
This is causing errors in do_install
| chown: cannot access
'/mnt/b/yoe/master/build/tmp/work/riscv64-yoe-linux/systemd/255.4/image/var/log/journal':
No such file or directory
On Wed, Mar 6, 2024 at 10:56 PM Changqing Li
wrote:
>
> From: Changqing Li
>
> There are 2 issues here:
> First, in
On Thu, Mar 7, 2024 at 4:48 PM Peter Kjellerstedt
wrote:
>
> We have a lot of recipes that use gdbus-codegen and are now facing this
> problem. To solve it, I have added a gdbus-codegen.bbclass that does:
>
> DEPENDS:append = " glib-2.0-native python3-packaging-native"
>
> inherit python3native
>
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Alexander Kanavin
> Sent: den 7 mars 2024 17:11
> To: Peter Kjellerstedt
> Cc: Khem Raj ; Martin Jansa ;
> openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core]
Is it? Why? There’s plenty of recipes in core that don’t do it. Package
managers resolvers are able to figure out that one package needs to be
replaced with another.
Alex
On Thu 7. Mar 2024 at 17.17, Otavio Salvador <
otavio.salva...@ossystems.com.br> wrote:
>
>
> Em qui., 7 de mar. de 2024 às
Em qui., 7 de mar. de 2024 às 13:14, Alexander Kanavin <
alex.kana...@gmail.com> escreveu:
> On Thu, 7 Mar 2024 at 14:43, Tom Hochstein wrote:
> > +# For compatibility with layers before scarthgap
> > +RPROVIDES:${PN} = "bmap-tools"
> > +RREPLACES:${PN} = "bmap-tools"
> > +RCONFLICTS:${PN} =
On Thu, 7 Mar 2024 at 14:43, Tom Hochstein wrote:
> +# For compatibility with layers before scarthgap
> +RPROVIDES:${PN} = "bmap-tools"
> +RREPLACES:${PN} = "bmap-tools"
> +RCONFLICTS:${PN} = "bmap-tools"
Only RREPLACES/RCONFLICTS please. Do not add the obsolete RPROVIDES.
Alex
On Thu, 7 Mar 2024 at 16:49, Peter Kjellerstedt
wrote:
> We have a lot of recipes that use gdbus-codegen and are now facing this
> problem. To solve it, I have added a gdbus-codegen.bbclass that does:
>
> DEPENDS:append = " glib-2.0-native python3-packaging-native"
>
> inherit python3native
>
>
On Wed, Mar 6, 2024 at 2:34 PM Richard Purdie
wrote:
>
> On Wed, 2024-03-06 at 10:52 -0800, Khem Raj wrote:
> > On Wed, Mar 6, 2024 at 8:23 AM Richard Purdie
> > wrote:
> > >
> > > From: Eilís 'pidge' Ní Fhlannagáin
> > >
> > > Excluding riscv64 due to mouse rather than a touchscreen which adds
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Khem Raj
> Sent: den 28 februari 2024 19:30
> To: Martin Jansa
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] glib-2.0: backport a switch from
On Thu, Mar 7, 2024 at 9:51 AM Steve Sakoman wrote:
>
> On Thu, Mar 7, 2024 at 4:34 AM Steve Sakoman via
> lists.openembedded.org
> wrote:
> >
> >
> >
> > On Thu, Mar 7, 2024, 4:29 AM Bruce Ashfield
> > wrote:
> >>
> >> On Thu, Mar 7, 2024 at 9:00 AM Steve Sakoman wrote:
> >> >
> >> > On Thu,
On Sat, Mar 2, 2024 at 1:23 PM Munehisa Kamata wrote:
>
> Hi Steve,
>
> Could you please cherry-pick the commit cd2072e5d953 ("kernel.bbclass: Set
> pkg-config variables for building modules") from the master for nanbield to
> avoid the unexpected rebuild at do_compile_kernelmodules()?
OK, will
On Sun, Mar 3, 2024 at 3:50 PM Vijay Anusuri wrote:
>
> Hi Steve,
>
> I've sent mail to cpe_diction...@nist.gov to update the information.
>
> Now it was updated in https://nvd.nist.gov/vuln/detail/CVE-2020-36773
Thanks!
Steve
> On Thu, Feb 8, 2024 at 8:40 PM Steve Sakoman wrote:
>>
>> On
On Thu, Mar 7, 2024 at 4:34 AM Steve Sakoman via
lists.openembedded.org
wrote:
>
>
>
> On Thu, Mar 7, 2024, 4:29 AM Bruce Ashfield wrote:
>>
>> On Thu, Mar 7, 2024 at 9:00 AM Steve Sakoman wrote:
>> >
>> > On Thu, Mar 7, 2024 at 3:46 AM Steve Sakoman via
>> > lists.openembedded.org
>> > wrote:
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Alexander Kanavin
> Sent: den 7 mars 2024 12:42
> To: qi.c...@windriver.com
> Cc: Li, Changqing ; Richard Purdie
> ; openembedded-
> c...@lists.openembedded.org
> Subject: Re:
The rename of bmap-tools to bmaptool creates an incompatibility that
will break package feeds. Restore compatibility by adding bmap-tools as
a runtime alias.
Acked-by: Otavio Salvador
Signed-off-by: Tom Hochstein
---
meta/recipes-support/bmaptool/bmaptool_git.bb | 5 +
1 file changed, 5
On Wed, 2024-03-06 at 14:34 -0800, Richard Purdie via
lists.openembedded.org wrote:
> On Wed, 2024-03-06 at 10:52 -0800, Khem Raj wrote:
> > On Wed, Mar 6, 2024 at 8:23 AM Richard Purdie
> > wrote:
> > >
> > > From: Eilís 'pidge' Ní Fhlannagáin
> > >
> > > Excluding riscv64 due to mouse rather
From: Ross Burton
The linux-firmware recipe goes to a lot of effort to attempt to package
the license texts into separate packages, and add dependencies so that
installing a piece of firmware will also ship the relevant license text.
However, licence.bbclass can already do this, because the
From: Ross Burton
The GPLv2 text is the standard text, so the -carl9170 package can just
set LICENSE=GPL-2.0-or-later and the custom license handling removed.
Confirmed in the source that the intended license is v2-or-later, not
v2-only as WHENCE says.
Signed-off-by: Ross Burton
---
From: Ross Burton
Signed-off-by: Ross Burton
---
meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
b/meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
From: Ross Burton
This can a non-trivial amount of disk space, but requires rdfind from
meta-oe. As duplicate pieces of firmware become links, this reduces the
size of individual packages and adds dependencies:
linux-firmware-adsp-sst: PKGSIZE changed from 6362678 to 560 (-12%)
On Thu, 7 Mar 2024 at 11:21, Chen Qi via lists.openembedded.org
wrote:
> You can see dnf's solution is:
> https://github.com/rpm-software-management/dnf/blob/master/etc/tmpfiles.d/dnf.conf
>
> I don't think dnf community will look into this issue. And I would expect it
> to be a complicated
Hi Alex,
You can see dnf's solution is:
https://github.com/rpm-software-management/dnf/blob/master/etc/tmpfiles.d/dnf.conf
I don't think dnf community will look into this issue. And I would expect it to
be a complicated one. Because dnf's own solution looks like more of a
workaround. At the
The GOPROXY is already correctly defined on the native sys root
and this can be checked using the bitbake devshell:
| $ go env GOPROXY
| https://proxy.golang.org,direct
The go_do_compile task calls the compiler directly so the
GOPROXY env is not seen because it's not defined in the shell.
On Thu, 7 Mar 2024 at 10:19, Changqing Li
wrote:
> ++for arg in args:
> ++if arg.startswith("--installroot="):
> ++root=arg.split("=")[1]
> ++if os.path.exists(os.path.join(root, "log_lock.pid")):
> ++
On Thu, 7 Mar 2024 at 10:19, Changqing Li
wrote:
> +Upstream-Status: Inappropriate [oe specific workaround]
You *just* said you will send this upstream as requested. Why is it
suddenly Inappropriate?
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply
From: Changqing Li
dnf has a bug, refer [1], it causes that log_lock.pid may not removed
after dnf exit. And for native dnf, since we change the lock file path
to /, it will never be removed, and make the rootfs not clean,refer
[2][3]. This patch is a workaround to fix above issue.
[1]
On 3/7/24 16:14, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
Thanks, the patch is ok, but you need to actually open a dnf pull
request with the
On 06/03/24 17:57, Richard Purdie wrote:
On Wed, 2024-03-06 at 08:37 -0800, Mauro wrote:
Before this commit, the .env file created in
tmp/sysroots//imgdata/.env was never cleaned,
but when the do_clean task is invoked on an image, the .env file
contains paths that are not valid anymore.
If
Thanks, this is fine.
Alex
On Thu, 7 Mar 2024 at 07:50, Changqing Li
wrote:
>
> From: Changqing Li
>
> For cross compile, TIC will be native tic in recipe-sysroot-native, and
> the terminfo path will be native path, the rxvt-unicode terminfo will be
> wrongly installed to native path.
>
>
Thanks, the patch is ok, but you need to actually open a dnf pull
request with the patch, and not just the ticket (also 'Submitted'
means that the patch was actually provided to upstream). It's okay if
upstream then rejects the patch. We'll at least try to convince them
:)
Alex
On Thu, 7 Mar
68 matches
Mail list logo
