Upstream does not want the pam tests to be skipped
Signed-off-by: Markus Volk
---
.../libsecret/0001-meson-add-option-to-disable-pam-tests.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/recipes-gnome/libsecret/libsecret/0001-meson-add-option-to-disable-pam-tests
Hi Khem,
On 1/10/25 02:35, Khem Raj wrote:
I know this patch is applied but I still want to bring it to attention
Many packages in other layers depend on fmt. fmt's APIs are not or
not used in a very backward compatible way
some packages provide an option to use vendored version of fmt so in
ca
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-5.1.2.rc1.
We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
do you extract the reference from same version of llvm/clang branch
that is being used by given rust compiler version.
On Mon, Jan 13, 2025 at 4:08 AM Varatharajan, Deepesh via
lists.openembedded.org
wrote:
>
> From: Deepesh Varatharajan
>
> --
In case both UBOOT_SIGN_ENABLE and UBOOT_ENV are enabled and
kernel-fitimage.bbclass is in use to generate signed kernel
fitImage, there is a circular dependency between uboot-sign
and kernel-fitimage bbclasses . The loop looks like this:
kernel-fitimage.bbclass:
- do_populate_sysroot depends on d
From: Hiago De Franco
The error described does not occur in all cases where libxkbcommon is
used. As example, a Qt application that depends on libxkbcommon might
not require any locales to be installed.
Add it to RRECOMMENDS, as libxkbcommon does not seen to have any hard
dependency on libx11-co
The ide-sdk command bootstraps the SDK from the bitbake environment
before the IDE configuration is generated. In the case of the eSDK
installer, the bootstrapping is performed during the installation of
the eSDK installer. Running the ide-sdk plugin from an eSDK installer
based setup would require
These imports are not needed.
Signed-off-by: Adrian Freihofer
---
scripts/lib/devtool/build_sdk.py | 7 ---
1 file changed, 7 deletions(-)
diff --git a/scripts/lib/devtool/build_sdk.py b/scripts/lib/devtool/build_sdk.py
index 1cd4831d2b8..990303982c1 100644
--- a/scripts/lib/devtool/build_s
On Mon, Jan 13, 2025 at 04:45:38PM +, Ross Burton wrote:
> On 12 Dec 2024, at 21:34, Hiago De Franco via lists.openembedded.org
> wrote:
> >
> > From: Hiago De Franco
> >
> > The error described does not occur in all cases where libxkbcommon is
> > used. As example, a Qt application that d
From: Hiago De Franco
Linux kernel commit 48bff1053c17 ("random: opportunistically initialize
on /dev/urandom reads") introduced a change where /dev/urandom blocks if
the random pool is insufficiently initialized during hardware boot. This
behavior causes /dev/urandom reads to hang for approximat
Hello Christos!
I agree with Randy, this is a good start :)
Le 13/01/2025 à 21:44, Christos Gavros via lists.openembedded.org a écrit :
> Some users have reported issues which were caused because they were missing
> the right libstdc++-version-dev in their system.
> A new function with the name
Hi Steve
Would it be possible to cherry-pick also these poky commits:
a3c51794144 oe-selftest: devtool ide-sdk use modify debug-build
92a4abac54a devtool: ide-sdk recommend DEBUG_BUILD
71acb3b781d devtool: ide-sdk sort cmake preset
1f7eb26c947 devtool: modify support debug-builds
respectively th
On 2025-01-13 3:44 p.m., Christos Gavros via lists.openembedded.org wrote:
Some users have reported issues which were caused because they were missing the
right libstdc++-version-dev in their system.
A new function with the name 'check_cpp_toolchain' was added in sanity.bbclass
in order to ver
W dniu 12.01.2025 o 16:34, Alex Kiernan pisze:
On Sun, Jan 12, 2025 at 2:40 PM Artur Kowalski via
lists.openembedded.org
wrote:
The flag is similar to --user flag as it causes systemctl to operate on
user units, but it performs operations globally for all users. This is
required to for user pr
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/meta-oe-Sanity-test-for-cpp-toolchain.patch
FAIL: test bugzilla entry format: Bugzilla issue ID is not correctly fo
From: Changqing Li
By default, create-log-dirs is enabled in systemd, and a link
/var/log/README will be created, point to {{DOC_DIR}}/README.logs, but,
for oe, there are two problems here, firstly, DOC_DIR is packaged in
another package systemd-doc, so /var/log/README is a dead link when
system
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/scarthgap-12-15-linux-yocto-6.6-update-to-v6.6.69.patch
FAIL: test commit message user tags: Mbox includes one or m
From: Robert Yang
Fixed race issues for parallel build:
groff: error: couldn't exec soelim: Permission
And:
groff: error: couldn't exec grn: Permission denied
Signed-off-by: Robert Yang
(cherry picked from commit b9ee7ea9ab05a1887c863dc9fccc65cb9e6850df)
Signed-off-by: Steve Sakoman
---
...t
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
22a054ea1f08 Linux 6.6.64
f3b82bb26f5b posix-timers: Target group sigqueue to current task only if
not exiting
8a799149ab45 drm/amd/pm: update current_socclk and cu
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
18916a684a8b Linux 6.6.58
fd6e2af79a94 ALSA: hda/conexant - Use cached pin control for Node 0x1d on
HP EliteOne 1000 G2
9698088ac770 nilfs2: propagate directory rea
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
1/1 [
Author: Ross Burton
Email: ross.bur...@arm.com
Subject: bsp/genericarm64: disable ARM64_SME
Date: Thu, 21 Nov 2024 15:53:35 +
From upstream:
arm64: Kconfig: Make SME depend on BROKE
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
a66cdcdc9e44 Linux 6.6.66
35163f642d91 i3c: master: svc: fix possible assignment of the same address
to two devices
43bbc5f8586e i3c: master: Remove i3c_dev_disable
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
d4576c567009 Linux 6.6.56
1e0f696469d6 Revert "perf callchain: Fix stitch LBR memory leaks"
9b15f68c4127 Linux 6.6.55
e334ae4a0cd5 perf python: Allow checking fo
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
bf3af7e92bda Linux 6.6.59
7d9868180bd1 xfrm: validate new SA's prefixlen using SA family when
sel.family is unset
7a26cb660775 task_work: make TWA_NMI_CURRENT handl
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
a30cd70ab75a Linux 6.6.69
ee18012c8015 block: avoid to reuse `hctx` not removed from cpuhp callback
list
937fcde0e971 ALSA: hda/realtek: Fix spelling mistake "Firel
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
bff3e13adb72 Linux 6.6.63
62aec1e92599 mm/damon/core: copy nr_accesses when splitting region
6cba27abb669 mm/damon/core: handle zero schemes apply interval
b0fb9
From: Hiago De Franco
With Linux kernel v6.6, due to commit 59b047bc9808 ("Bluetooth:
MGMT/SMP: Fix address type when using SMP over BREDR/LE"), an error
might occur when trying to automatically repair a bluetooth device, as
the key might store using a wrong/invalid address type. This happens
onl
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
c1036e4f14d0 Linux 6.6.62
9da3636a4880 9p: fix slab cache name creation for real
fc4951c3e335 mm/thp: fix deferred split unqueue naming and locking
eb6b6d3e1f1e
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
9b5aad3a7498c Linux 6.6.60
cc082e50375a2 fs/ntfs3: Sequential field availability check in
mi_enum_attr()
10c20d79d59ca drm/amd/display: Add null checks for 'stream'
From: Mark Hatle
The custom do_fetch routine is ignoring BB_NO_NETWORK, add a check for this
as the correct behavior for the user is to set:
CVE_DB_UPDATE_INTERVAL = "-1"
If CVE_DB_UPDATE_INTERNAL is set to -1, check that a DB file exists, if not
we need to error so the user can deal with this
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
1/1 [
Author: Mikko Rapeli
Email: mikko.rap...@linaro.org
Subject: genericarm64.cfg: enable CONFIG_DMA_CMA
Date: Thu, 24 Oct 2024 08:49:29 +0300
It's needed for graphics on AMD KV260.
Cc: Bill Mi
Please review this set of changes for scarthgap and have comments back by
end of day Wednesday, January 15
Passed a-full on autobuilder:
https://valkyrie.yoctoproject.org/#/builders/29/builds/802
The following changes since commit c3e0666dd2624c20c5f32657846d6f044046205b:
sanity.bbclass: skip
Some users have reported issues which were caused because they were missing the
right libstdc++-version-dev in their system.
A new function with the name 'check_cpp_toolchain' was added in sanity.bbclass
in order to verify that the host system can compile and link successfully a
'hello world' c
On 1/13/25 12:10 PM, Adrian Freihofer wrote:
Hi Marek
Hi,
The issue is known and already discussed here:
https://lists.yoctoproject.org/g/yocto/message/64428. It probably hits many
users and a fix would be more than welcome.
Indeed.
A more general discussion about issues related to the
ke
On Mon, Jan 13, 2025 at 10:51 AM wrote:
>
> From: Igor Opaniuk
>
> create_image_spdx() implementation assumes that image is indeed a file.
> If image recipe deploys a directory (for example, which contains an
> hierarchy of flash artifacts, that is used by SoC vendor-specific
> flashing tool) whi
From: Igor Opaniuk
create_image_spdx() implementation assumes that image is indeed a file.
If image recipe deploys a directory (for example, which contains an
hierarchy of flash artifacts, that is used by SoC vendor-specific
flashing tool) which follows ${IMAGE_NAME}.${IMAGE_TYPE} naming scheme,
Hello,
Thank you for this work. Could you explain your use case, why do you
include all the entries in the image's SPDX?
I'm asking, because that SPDX file will be out of date quite rapidly,
probably in 24h. Without updating it with the new data, it can be even
misleading. How do you address this
From: Chris Laplante
This should fix
https://valkyrie.yoctoproject.org/#/builders/80/builds/725/steps/13/logs/stdio
Signed-off-by: Chris Laplante
---
scripts/devtool | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/devtool b/scripts/devtool
index ebd3e4c11b..39cebec
On 12 Dec 2024, at 21:34, Hiago De Franco via lists.openembedded.org
wrote:
>
> From: Hiago De Franco
>
> The error described does not occur in all cases where libxkbcommon is
> used. As example, a Qt application that depends on libxkbcommon might
> not require any locales to be installed.
Th
Hello Joshua,
On Mon, Jan 13, 2025 at 3:58 PM Joshua Watt wrote:
>
> On Mon, Jan 13, 2025 at 5:34 AM Igor Opaniuk via
> lists.openembedded.org
> wrote:
> >
> > From: Igor Opaniuk
> >
> > create_image_spdx() implementation assumes that image is indeed a file.
> > If image recipe deploys a direct
On Mon, 13 Jan 2025 at 15:08, Deepesh Varatharajan
wrote:
> Testing patch
> /home/patchtest/share/mboxes/V3-1-3-rust-target-config-Update-the-data-layout-for-x86-ppc-riscv64-aarch64-and-loongaarch64-targets..patch,
> the following test failed:
>
> FAIL: Test for shortlog length: The commit messa
What is happening with the 5.0.6 release?
Walt Miner
AGL Community Manager
The Linux Foundation
Visit us at:
www.automotivegradelinux.org
lists.automotivelinux.org
www.linuxfoundation.org
On Tue, Jan 7, 2025 at 10:49 AM Stephen Jolley via lists.yoctoproject.org <
sjolley.yp.pm=gmail@lists
On Mon, Jan 13, 2025 at 5:34 AM Igor Opaniuk via
lists.openembedded.org
wrote:
>
> From: Igor Opaniuk
>
> create_image_spdx() implementation assumes that image is indeed a file.
> If image recipe deploys a directory (for example, which contains an
> hierarchy of flash artifacts, that is used by S
>
> On Sun, 12 Jan 2025 at 15:55, Chris Laplante via lists.openembedded.org
> wrote:
> > This patchset removes global variables from the 'devtool' script. It
> > also changes `Context` to be a dataclass.
>
> Thanks, these changes look really nice.
My pleasure :)
Thanks,
Chris
-=-=-=-=-=-=-=-
Hi Mathieu,
> Hi Chris,
>
> I believe this series is breaking some builds on the autobuilder. We got the
> following error:
>
> devtool: error: argument : invalid choice: 'sdk-install' (choose
> from create-workspace, add, modify, extract, sync, rename, update-recipe,
> status, reset, finish, ed
On Mon Jan 13, 2025 at 12:16 AM CET, Markus Volk wrote:
> Signed-off-by: Markus Volk
> ---
> .../libsecret/0001-meson-add-option-to-disable-pam-tests.patch | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
> a/meta/recipes-gnome/libsecret/libsecret/0001-meson-add-option-to-
On Sun Jan 12, 2025 at 3:53 PM CET, Chris Laplante via lists.openembedded.org
wrote:
> From: Chris Laplante
>
> This patchset removes global variables from the 'devtool' script. It
> also changes `Context` to be a dataclass.
>
> All devtool self-tests pass, tested via: oe-selftest -r devtool
>
>
On 13/01/2025 12:23, Alexander Kanavin wrote:
> [Some people who received this message don't often get email from
> alex.kana...@gmail.com. Learn why this is important at
> https://aka.ms/LearnAboutSenderIdentification ]
>
> This email is not from Hexagon’s Office 365 instance. Please be careful
We want to ensure ARM nativesdk signatures match those for the 32 and 64 bit
x86 versions. Add a test to ensure this is the case.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 26 ++---
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git
On 13-01-2025 19:21, 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.
Hello,
when you send new patchset revisions, it helps to explain what changed
betwe
Hi Mathieu,
On 1/8/25 8:39 AM, Mathieu Othacehe via lists.openembedded.org wrote:
[You don't often get email from othacehe=gnu@lists.openembedded.org. Learn
why this is important at https://aka.ms/LearnAboutSenderIdentification ]
On ARMv7, the .ARM.extab and .ARM.exidx unwinding sections a
On Mon, 2025-01-13 at 14:45 +0100, Quentin Schulz wrote:
> Cc docs
>
> On 1/6/25 5:09 PM, Richard Purdie via lists.openembedded.org wrote:
> > If a recipe has something like:
> >
> > RPROVIDES:${PN}-xxx = "yyy"
> >
> > then the current code will turn this into:
> >
> > RPROVIDES:${BPN}-native-x
Hello,
when you send new patchset revisions, it helps to explain what changed
between revisions, especially when no feedback was given to the
previous revisions.
You can do this with cover letters, or by including a changelog in
commit messages under --- separator (so the changelog won't be
inclu
From: Deepesh Varatharajan
https://blog.rust-lang.org/2024/09/05/Rust-1.81.0.html
Drop the following backported patches which is addressed
with rust v1.81.0 upgrade.
0001-cargo-do-not-write-host-information-into-compilation.patch
https://github.com/rust-lang/cargo/commit/2db0bab16139d094f689587
Cc docs
On 1/6/25 5:09 PM, Richard Purdie via lists.openembedded.org wrote:
If a recipe has something like:
RPROVIDES:${PN}-xxx = "yyy"
then the current code will turn this into:
RPROVIDES:${BPN}-native-xxx = "yyy-native"
which can lead to errors. Add in some handling for this special case i
From: Deepesh Varatharajan
-
error: data-layout for target `x86-linux`,
`e-m:e-p:32:32-f64:32:64-f80:32-n8:16:32-S128`,
differs from LLVM target's `i686-unknown-linux-gnu` default layout,
`e-m:e-p:32:32-p270:
From: Deepesh Varatharajan
During the Rust build process, multiple copies of libstd-*.so are generated, as
Rust copies the required files from the stage2 build artifacts to the target
image directory. When these build binaries are copied to the image, Yocto's
do_package step encounters an error.
On Mon, 13 Jan 2025 at 14:07, POPESCU Catalin
wrote:
> I don't really know how to reproduce this error (which I don't see on my
> setup).
Have you run the testsdk task specifically?
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#209719):
ht
Hi Derek,
On 1/10/25 4:59 PM, Derek Straka via lists.openembedded.org wrote:
The complexity of overriding files from the bbclass made the behavior at
times hard to follow and predict. This change replaces the default file with a
heredoc equivalent that creates a default file if the user does not
From: Igor Opaniuk
create_image_spdx() implementation assumes that image is indeed a file.
If image recipe deploys a directory (for example, which contains an
hierarchy of flash artifacts, that is used by SoC vendor-specific
flashing tool) which follows ${IMAGE_NAME}.${IMAGE_TYPE} naming scheme,
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/V3-1-3-rust-target-config-Update-the-data-layout-for-x86-ppc-riscv64-aarch64-and-loongaarch64-targets..patch
FAIL:
From: Deepesh Varatharajan
-
error: data-layout for target `x86-linux`,
`e-m:e-p:32:32-f64:32:64-f80:32-n8:16:32-S128`,
differs from LLVM target's `i686-unknown-linux-gnu` default layout,
`e-m:e-p:32:32-p270:
From: Deepesh Varatharajan
https://blog.rust-lang.org/2024/09/05/Rust-1.81.0.html
Drop the following backported patches which is addressed
with rust v1.81.0 upgrade.
0001-cargo-do-not-write-host-information-into-compilation.patch
https://github.com/rust-lang/cargo/commit/2db0bab16139d094f689587
From: Deepesh Varatharajan
During the Rust build process, multiple copies of libstd-*.so are generated, as
Rust copies the
required files from the stage2 build artifacts to the target image directory.
When these build
binaries are copied to the image, Yocto's do_package step encounters an error
On Sun, 12 Jan 2025 at 15:55, Chris Laplante via
lists.openembedded.org
wrote:
> This patchset removes global variables from the 'devtool' script. It
> also changes `Context` to be a dataclass.
Thanks, these changes look really nice.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages
On Mon, 13 Jan 2025 at 12:16, POPESCU Catalin via
lists.openembedded.org
wrote:
> The error doesn't look like to be related to my patch.
> > rm: cannot remove
> > 'TOPDIR/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0/testimage-sdk/sysroots/core2-64-poky-linux/etc/bluetooth/input.conf':
> > Pe
systemd v256 introduces `mountfsd` and `nsresourced` as meson options,
make them PACKAGECONFIG so recipes could enable or disable the feature
by selecting PACKAGECONFIGs.
Signed-off-by: Lei YU
---
meta/recipes-core/systemd/systemd_257.1.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/me
Hi Steve,
The error doesn't look like to be related to my patch.
BR,
On 12/01/2025 15:23, Steve Sakoman wrote:
> [You don't often get email from st...@sakoman.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> This email is not from Hexagon’s Office 365 i
Hi Marek
The issue is known and already discussed here:
https://lists.yoctoproject.org/g/yocto/message/64428. It probably hits many
users and a fix would be more than welcome.
A more general discussion about issues related to the
kernel-fitimage.bbclass is here:
https://bugzilla.yoctoproject.org/
What this means is that changes to meta-poky/ should be sent to poky@
mailing list, changes to meta/ should be sent to openembedded-core@
Alex
On Mon, 13 Jan 2025 at 10:33, Patchtest via lists.openembedded.org
wrote:
>
> Thank you for your submission. Patchtest identified one
> or more issues wi
Can this patch be split up to make review easier? Particularly,
separate adding new functions into their own commits, with
justification for each, and introduce usage of those functions in
separate commits as well if possible, again with justification for
each.
Alex
On Sun, 12 Jan 2025 at 15:40,
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/poky-scarthgap-poky-sanity.bbclass-Remove-True-option-to-getVar-calls.patch
FAIL: test target mailing list: Series
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/poky-kirkstone-poky-Remove-True-option-to-getVar-calls.patch
FAIL: test target mailing list: Series sent to the wro
getVar() now defaults to expanding by default, thus remove the True
option from getVar() calls with a regex search and replace.
Signed-off-by: Akash Hadke
---
meta-poky/classes/poky-sanity.bbclass| 6 +++---
meta/classes/rust-bin.bbclass| 12 ++--
From: akash hadke
getVar() now defaults to expanding by default, thus remove the True
option from getVar() calls with a regex search and replace.
Signed-off-by: Akash Hadke
---
meta-poky/classes/poky-sanity.bbclass | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-
75 matches
Mail list logo
