From: Chen Qi
When enabling multilib for qemuarm64, populate_sdk would fail with
the following error:
Error: Transaction test error: file /usr/include/bits/indirect-return.h
conflicts between installs of lib32-libc6-dev-2.41 and libc6-dev-2.41+
The problem could be reproduced by adding the
On Sun, 2025-02-09 at 18:27 -0500, Bruce Ashfield wrote:
>
>
> On Sun, Feb 9, 2025 at 5:58 PM Adrian Freihofer
> wrote:
> > Hi Bruce
> >
> > Am Do., 30. Jan. 2025 um 15:48 Uhr schrieb Bruce Ashfield via
> > lists.openembedded.org
> > :
> > >
> > >
> > > On Thu, Jan 30, 2025 at 9:31 AM Steve S
Remove /bin/sh from bash RPROVIDES as this has a side-effect which
confuses rpm package manager when also busybox provides /bin/sh and
base-files depend on /bin/sh . The problem is broken down below.
First, bash depends on base-files and bash pkg_postinst must run
after base-files was installed, b
Sure Joshua,
I hope it won't be much extra work, as I have this patch already applied
and it is working for me without any issues.
BR
Piotr
pon., 10 lut 2025 o 18:51 Joshua Watt napisał(a):
>
> Piotr,
>
> I think with the provided example I can look into this. I suspect it
> will be a little mor
Additionally, changing the packaging does not affect what is added to
the sysroot.
//Peter
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Alexander Kanavin via
> lists.openembedded.org
> Sent: den 10 februari 2025 18:20
>
On 5 Feb 2025, at 14:34, Marta Rybczynska via lists.openembedded.org
wrote:
>
> This series is allowing choice of the NVD feed to use, you can
> configure them using the NVD_DB_VERSION variable in local.conf
>
> Available feeds:
> - NVD2 (default) - the current NVD API v2 feed
> - NVD1 - the ol
From: Khem Raj
* backporting, because it's also needed also for qemu-native builds
on hosts with glibc >= 2.41
Signed-off-by: Khem Raj
Signed-off-by: Richard Purdie
Signed-off-by: Martin Jansa
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
...ed_attr-Do-not-define-for-glibc-2.41
From: Peter Marko
ptest compile and install tasks do not have parallel build settings for
cmake. On powerful build machines this can cause overload situations
and oomkills.
Observed when building qtgrpc with ptest generally enabled in distro.
Having this in ptest class is suboptimal, but creatin
> To be clear, this change adds:
>
> ${@bb.utils.contains('DISTRO_FEATURES', 'minidebuginfo', 'xz', '', d)}
>
> to the default PACKAGECONFIG for gdb-cross. You can't tell that from
> the patch.
That's what I was referring to in the commit message with "This enables xz
for gdb-cross as side-effect.
From: Peter Marko
ptest compile and install tasks do not have parallel build settings for
cmake. On powerful build machines this can cause overload situations
and oomkills.
Observed when building qtgrpc with ptest generally enabled in distro.
Having this in ptest class is suboptimal, but creatin
From: Etienne Cordonnier
- Keep a single base-value of the PACKAGECONFIG variable in gdb-common.inc for
easier maintenance.
- Enable xz (needed by minidebuginfo) unconditionally in gdb-cross and
gdb-cross-canadian since those are typically not used in minimal systems, but
rather e.g. on an
From: Peter Marko
Upgrade to latest 1.22.x release [1]:
$ git --no-pager log --oneline go1.22.11..go1.22.12
5817e65094 (tag: go1.22.12) [release-branch.go1.22] go1.22.12
0cc45e7ca6 [release-branch.go1.22] crypto/internal/fips140/nistec: make
p256NegCond constant time on ppc64le
c3c6a50095 [rele
Piotr,
I think with the provided example I can look into this. I suspect it
will be a little more involved than adding MACHINE_ARCH
On Mon, Feb 10, 2025 at 9:58 AM Piotr Łobacz wrote:
>
> Actually this was just an issue with the path to the deps.json file.
> which was containing all the dependen
On Mon, Feb 10, 2025 at 8:21 AM Richard Purdie via
lists.openembedded.org
wrote:
>
> On Mon, 2025-02-10 at 16:49 +0100, Etienne Cordonnier via
> lists.openembedded.org wrote:
> > From: Etienne Cordonnier
> >
> > Duplicating the PACKAGECONFIG variable in gdb-cross and gdb-common makes
> > it easy
Actually this was just an issue with the path to the deps.json file.
which was containing all the dependencies and in case of different
machine
for packages like e.g. base-files this file was containing bad
dependency, meaning that if i'm building first machine A, than B,
the spdx files from A for
They're not actually copied. They're hard-linked from
sysroots-components/. This is a cheap operation and it doesn't waste
disk space.
Alex
On Mon, 10 Feb 2025 at 18:05, Oleksiy Obitotskyy via
lists.openembedded.org
wrote:
>
> Hi Alexander,
>
> By 'deploying whole systemd' I mean next:
>
> Every
On 2/10/25 9:14 AM, Mikko Rapeli via lists.openembedded.org wrote:
Hi,
On Mon, Feb 10, 2025 at 09:07:57AM +0100, Vyacheslav Yurkov via
lists.openembedded.org wrote:
On 08.02.2025 19:34, Richard Purdie wrote:
On Fri, 2025-02-07 at 08:10 +0100, Vyacheslav Yurkov via lists.openembedded.org
wr
Hi Alexander,
By 'deploying whole systemd' I mean next:
*
Every component copy and installs packages with libraries, utilities and config
files in component local sysroot, i.e. directory used to create final component
image:
*
libsystemd0_255.4
*
libsystemd-shared_255.4
*
syste
opkg accepts both - and _ in its options but use the help text
preferred format. From https://github.com/yoctoproject/poky/pull/14
from Philipp-Alexander Blum .
Signed-off-by: Richard Purdie
---
meta/classes-global/package_ipk.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
On Mon, 2025-02-10 at 16:49 +0100, Etienne Cordonnier via
lists.openembedded.org wrote:
> From: Etienne Cordonnier
>
> Duplicating the PACKAGECONFIG variable in gdb-cross and gdb-common makes
> it easy to forget updating one definition without updating the other.
> However at the moment there is
If networking fails, we can get useful informaiton over the serial connection.
Add
this fallback code so that any issues can be more easily debugged by showing the
host and target networking states.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/runtime/case.py | 16
met
Currently, the perf report charts use start_time which is when the build
is run. If running builds for commits in the past, this is inaccurate so
switch to using the recently added commit_time if the field is present.
Over time, the reports will switch to using the more accurate values.
Signed-off
Use the class available for bash compleition to simplify the recipe.
Signed-off-by: Richard Purdie
---
meta/recipes-gnome/libsecret/libsecret_0.21.6.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-gnome/libsecret/libsecret_0.21.6.bb
b/meta/recipes-gnome/lib
Hi,
I was hesitating a bit for this patch: typically when building gdb-cross
there is no space constraint on the host where gdb-cross runs (a desktop PC
/ laptop, etc), so we could keep the separated definition of PACKAGECONFIG,
and enable xz and minidebuginfod for gdb-cross per default and avoid
r
From: Etienne Cordonnier
Duplicating the PACKAGECONFIG variable in gdb-cross and gdb-common makes
it easy to forget updating one definition without updating the other.
However at the moment there is no need for two different definitions.
xz is also useful for gdb-cross when minidebuginfo is enab
On Mon, 2025-02-10 at 13:50 +0100, Piotr Łobacz via lists.openembedded.org
wrote:
> Currently SPDXDIR is pointing to `${WORKDIR}/spdx` which means that the by-id
> and by-namespace SPDX files are created without differentiation between
> machines.
> This means that for two machines using a common
Currently SPDXDIR is pointing to `${WORKDIR}/spdx` which means that the by-id
and by-namespace SPDX files are created without differentiation between
machines.
This means that for two machines using a common package architecture
(e.g. genericx86-64 and qqemux86-64), there would be overlapping file
Currently SPDXDIR is pointing to `${WORKDIR}/spdx` which means that the by-id
and by-namespace SPDX files are created without differentiation between
machines.
This means that for two machines using a common package architecture
(e.g. genericx86-64 and qqemux86-64), there would be overlapping file
From: Alexander Kanavin
Upstream no longer publishes tarballs. 1.8.0 release is git only.
Signed-off-by: Alexander Kanavin
---
meta/recipes-graphics/xorg-lib/libxkbcommon_1.7.0.bb | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/meta/recipes-graphics/xorg-lib/libxkbco
On Mon, 10 Feb 2025 at 13:01, Oleksiy Obitotskyy via
lists.openembedded.org
wrote:
> We have next situation:
> - a lot of software components that depend on packages and deploy all
> packages they depend on locally inside component.
> - some components directly depend on systemctl only (e.g. this
Hi,
We have next situation:
- a lot of software components that depend on packages and deploy all packages
they depend on locally inside component.
- some components directly depend on systemctl only (e.g. this binary used in
scripts), so for every component we have to deploy whole systemd local
On 6 Feb 2025, at 14:49, Oleksiy Obitotskyy via lists.openembedded.org
wrote:
> Move systemctl into separate subpackage to minimize
> dependencies from core systemd package.
In what situation would you have systemd or systemctl without the other?
Cheers,
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You
2025. 02. 10. 10:03 keltezéssel, Alexander Kanavin írta:
On Sat, 8 Feb 2025 at 08:24, Zoltán Böszörményi wrote:
+Assume that the policies are good as they are committed.
+The CI for fedora-crypto-policies ensures this.
+
+Upstream-Status: Inappropriate [Yocto specific]
The patch as it is is in
Point to the crypto policy file so RPM signing may work.
Signed-off-by: Zoltán Böszörményi
---
meta/recipes-devtools/rpm/rpm_4.20.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/rpm/rpm_4.20.0.bb
b/meta/recipes-devtools/rpm/rpm_4.20.0.bb
index 6c995ff50c..d296c20d
This ships a crypto policy file for rpm-sequoia.
Signed-off-by: Zoltán Böszörményi
---
meta/conf/distro/include/maintainers.inc | 1 +
...1-Make-xsltproc-settable-as-XSLTPROC.patch | 43
...002-Don-t-use-hardcoded-python3-path.patch | 41 +++
...policy-validation-when-
Point to the crypto policy file so dnf can work with signed packages.
Signed-off-by: Zoltán Böszörményi
---
meta/recipes-devtools/dnf/dnf_4.22.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/dnf/dnf_4.22.0.bb
b/meta/recipes-devtools/dnf/dnf_4.22.0.bb
index f9d6ea1
With all the pieces in place, the self test can be re-enabled.
Signed-off-by: Zoltán Böszörményi
---
meta/lib/oeqa/selftest/cases/signing.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/selftest/cases/signing.py
b/meta/lib/oeqa/selftest/cases/signing.py
in
rpm 4.20 removed the built-in code to handle signed packages
and uses rpm-sequoia as a more feature complete library.
Runtime-depend on rpm-sequoia-crypto-policy.
Signed-off-by: Zoltán Böszörményi
---
meta/conf/distro/include/maintainers.inc | 1 +
.../rpm-sequoia/rpm-sequoia-crates.inc
From: Julian Haller
In case BB_FETCH_PREMIRRORONLY is set, the fetcher.download() function
sets BB_NO_NETWORK = "1" after downloading the first file. This alters
the precondition for the second and third loop run, disallowing network
access entirely. As a consequence, the .siginfo and .sig files
From: Mingli Yu
After below commit introduced, the do_install_ptest function is defined
concentratedly in ptest-python-pytest.bbclass.
8d84d9e19b python3-*: Update recipes with pytest ptests to use the new
ptest-python-pytest class
Use append for do_install_ptest to avoid the do_install_ptest l
On Sat, 8 Feb 2025 at 08:24, Zoltán Böszörményi wrote:
> +Assume that the policies are good as they are committed.
> +The CI for fedora-crypto-policies ensures this.
> +
> +Upstream-Status: Inappropriate [Yocto specific]
The patch as it is is indeed not suitable, but perhaps you can open a
ticket
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/psplash.c-fix-crash-from-length-becoming-negative.patch
FAIL: test mbox format: Series has malformed diff lines. Cr
I do apologise - I have the wrong mailing list. I need
https://lists.yoctoproject.org/g/yocto - will submit there.
Chris Moore
Embedded Software Engineer
@ cmo...@hanoverdisplays.com
T +44 1273 477528
www.hanoverdisplays.comHanover Displays Ltd. Southerham House, Southerham Lane,
L
Fixes [Yocto #14806]
If there is an error in read(), it returns -1 but this is just added to
length without checking first. This can lead to a runaway negative
value
for length which eventually crashes when memchr() is called with the
negative value.
The fix is to check the return from read() fir
Hi,
On Mon, Feb 10, 2025 at 09:07:57AM +0100, Vyacheslav Yurkov via
lists.openembedded.org wrote:
> On 08.02.2025 19:34, Richard Purdie wrote:
> > On Fri, 2025-02-07 at 08:10 +0100, Vyacheslav Yurkov via
> > lists.openembedded.org wrote:
> > > From: Vyacheslav Yurkov
> > >
> > > Instead of the
On 08.02.2025 19:34, Richard Purdie wrote:
On Fri, 2025-02-07 at 08:10 +0100, Vyacheslav Yurkov via lists.openembedded.org
wrote:
From: Vyacheslav Yurkov
Instead of the python re-implementation build the actual systemctl from
the systemd source tree. The python script was used when systemd di
46 matches
Mail list logo
