On Wed, 2024-07-17 at 12:00 +0100, Jose Quaresma via lists.openembedded.org
wrote:
> This reverts commit d1ac9bb1bd2132cd121f0e80829302298d8a8a64.
>
> The variable TESTIMAGE_FAILED_QA_ARTIFACTS is not parsed as expected [1]
> and is making some noise on the testimage output log as can be seen bel
On Wed, 2024-07-17 at 11:20 +0200, Alexander Kanavin via
lists.openembedded.org wrote:
> You are welcome to send such a backport, but it has to preserve
> existing behaviour by default.
Given I found no users of it, I suspect if we wait a week or two and
hear no complaints, this one might be ok bu
On Tue, 2024-07-16 at 18:09 -0400, Denys Dmytriyenko via lists.openembedded.org
wrote:
> From: Denys Dmytriyenko
>
> Copy the same sed command to sanitize libtool script from target recipe
> to nativesdk one. Otherwise fails with buildpaths QA error:
>
> ERROR: nativesdk-libtool-2.5.0-r0 do_pac
On Tue, 2024-07-16 at 18:11 -0400, Denys Dmytriyenko via
lists.openembedded.org wrote:
> On Tue, Jul 16, 2024 at 08:12:25AM +0100, Richard Purdie wrote:
> > On Mon, 2024-07-15 at 21:36 -0400, Denys Dmytriyenko via
> > lists.openembedded.org wrote:
> > > It's not
On Tue, 2024-07-16 at 14:18 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Tue, 2024-07-16 at 00:00 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Mon, 2024-07-15 at 15:26 -0600, Joshua Watt wrote:
> > > On Mon, Jul 15, 2024 at 3:07 PM Richar
On Tue, 2024-07-16 at 00:00 +0100, Richard Purdie via lists.openembedded.org
wrote:
> On Mon, 2024-07-15 at 15:26 -0600, Joshua Watt wrote:
> > On Mon, Jul 15, 2024 at 3:07 PM Richard Purdie
> > wrote:
> > >
> > > On Mon, 2024-07-15 at 14:40 -0600, Joshua W
On Tue, 2024-07-16 at 10:00 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Tue, 2024-07-16 at 09:57 +0200, Alexander Kanavin via
> lists.openembedded.org wrote:
> > On Mon, 15 Jul 2024 at 21:07, Ryan Eatmon via
> > lists.openembedded.org
> > wrote:
> >
On Tue, 2024-07-16 at 10:29 +0100, Jose Quaresma via
lists.openembedded.org wrote:
> Still side effects of the XZ backdoor.
>
> Racional [1]:
>
> License incompatibility and library bloatedness were the reasons.
> Given recent events we're never going to take a dependency on
> libsystemd,
> thoug
On Tue, 2024-07-16 at 09:57 +0200, Alexander Kanavin via
lists.openembedded.org wrote:
> On Mon, 15 Jul 2024 at 21:07, Ryan Eatmon via lists.openembedded.org
> wrote:
> >
> > With the move to make more warnings into errors it is inevitable
> > that we
> > will need more hooks to skip the errors o
On Tue, 2024-07-16 at 09:48 +0200, Alexander Kanavin via
lists.openembedded.org wrote:
> On Mon, 15 Jul 2024 at 20:02, Jose Quaresma via
> lists.openembedded.org
> wrote:
> > +From: Jose Quaresma
> > +Date: Mon, 15 Jul 2024 18:43:08 +0100
> > +Subject: [PATCH] regress/test-exec: use the absolute
On Mon, 2024-07-15 at 21:36 -0400, Denys Dmytriyenko via
lists.openembedded.org wrote:
> It's not limited to "target", but also happens to e.g. nativesdk:
>
> ERROR: nativesdk-llvm-18.1.8-r0 do_package_qa: QA Issue: File
> /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-
> linux/usr/
On Tue, 2024-07-16 at 02:05 +0300, Dmitry Baryshkov via lists.openembedded.org
wrote:
> Fix following QA warnings / errors
>
> File /usr/bin/afuc-asm in package mesa-tools contains reference to TMPDIR
> [buildpaths]
> File /usr/bin/afuc-disasm in package mesa-tools contains reference to TMPDIR
On Mon, 2024-07-15 at 15:26 -0600, Joshua Watt wrote:
> On Mon, Jul 15, 2024 at 3:07 PM Richard Purdie
> wrote:
> >
> > On Mon, 2024-07-15 at 14:40 -0600, Joshua Watt wrote:
> > > On Sat, Jul 13, 2024 at 12:44 AM Richard Purdie
> > > wrote:
> > >
On Mon, 2024-07-15 at 14:40 -0600, Joshua Watt wrote:
> On Sat, Jul 13, 2024 at 12:44 AM Richard Purdie
> wrote:
> >
> > On Fri, 2024-07-12 at 09:58 -0600, Joshua Watt via
> > lists.openembedded.org wrote:
> > > This patch series add support for SPDX 3.0
On Mon, 2024-07-15 at 11:18 +, Ross Burton via
lists.openembedded.org wrote:
> On 15 Jul 2024, at 11:31, Mikko Rapeli
> wrote:
> > > + def test_cryptodev(self):
> > > + with tempfile.TemporaryDirectory(prefix="cryptodev",
> > > dir=self.tc.sdk_dir) as testdir:
> > > + git_
On Mon, 2024-07-15 at 11:37 +0100, Richard Purdie via lists.openembedded.org
wrote:
> On Mon, 2024-07-15 at 18:20 +0800, Kai wrote:
> > On 7/15/24 17:59, Martin Jansa wrote:
> > > Hi Kai,
> > >
> > > are you also seeing these buildpaths warnings from libgfort
There is a buildpaths QA error in the test recipe that somehow didn't show up
in earlier testing. Use a source directory and tweak the build command to
avoid embedding build paths in the generated binary.
Signed-off-by: Richard Purdie
---
meta-selftest/recipes-test/fortran/fortran-hellowor
On Mon, 2024-07-15 at 18:20 +0800, Kai wrote:
> On 7/15/24 17:59, Martin Jansa wrote:
> > Hi Kai,
> >
> > are you also seeing these buildpaths warnings from libgfortran?
> > These
> > will be fatal since ERROR_QA update from yesterday:
> > https://git.openembedded.org/openembedded-core/commit/?id=
These were used by external layers and were needed before we had better
unpack instrumenation and the recent unpack directory changes. Drop
them as obsolete.
Signed-off-by: Richard Purdie
---
meta/recipes-kernel/perf/perf.bb | 1 -
meta/recipes-support/icu/icu_75-1.bb | 1 -
2 files changed
On Fri, 2024-07-12 at 09:58 -0600, Joshua Watt via
lists.openembedded.org wrote:
> This patch series add support for SPDX 3.0 and sets it as the
> default.
> Currently it is not possible to have SPDX 2.2 and SPDX 3.0 enabled at
> the same time
>
> v2: Added tests and addressed feedback
> v3: Fixed
ne by spawning an openssl command, we don't need
dependencies on openssl for build. For runtime, we can assume
people would install openssl if they need/want this.
These changes put our default busybox configuration in a more secure
initial set of settings.
[YOCTO #14125]
Signed-off-by: Rich
build failures.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/meson/meson_1.4.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/meson/meson_1.4.0.bb
b/meta/recipes-devtools/meson/meson_1.4.0.bb
index 5db100ff1cd..a0c2ee633ae 100644
--- a/meta
hence allowing the build to succeed.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/locales.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/selftest/cases/locales.py
b/meta/lib/oeqa/selftest/cases/locales.py
index 4ca8ffb7aac..ac4888ef669
Recent changes to ERROR_QA meant that the build was failing in ways the test
wasn't expecting. Tweak the tests to ensure those failures don't impact the
test.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/incompatible_lic.py | 6 +++---
1 file changed, 3 insert
eliminate-unused-debug-types is a compiler default so we no longer
need to specify this. Drop the option. Also drop an obsolete comment
about another debug flag.
Signed-off-by: Richard Purdie
---
meta/conf/bitbake.conf | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a
: Richard Purdie
---
meta/conf/bitbake.conf | 15 ---
meta/conf/documentation.conf | 4 ++--
meta/recipes-core/ovmf/ovmf_git.bb | 2 +-
meta/recipes-kernel/perf/perf.bb | 7 +++
4 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/meta/conf
Allow the "-g" option in DEBUG_FLAGS to be controlled directly with
a specific DEBUG_LEVELFLAG variable.
We can then use this in the webkitgtk recipe for finer grained flag
control and it allows the flag to be unset easily.
Signed-off-by: Richard Purdie
---
meta/conf/bi
On Thu, 2024-07-11 at 19:05 +, Ross Burton wrote:
>
>
> > On 11 Jul 2024, at 17:54, Richard Purdie via lists.openembedded.org
> > wrote:
> >
> > -DEBUG_FLAGS ?= "-g -feliminate-unused-debug-types ${DEBUG_PREFIX_MAP}"
> > +DEBUG_LEVELFLAG
Allow the "-g" option in DEBUG_FLAGS to be controlled separately to the rest of
the flags with a new DEBUG_FLAGLEVEL variable. We can then use this in the
webkitgtk recipe for finer grained flag control and it allows the flag to be
unset easily.
Signed-off-by: Richard Purdie
---
On Thu, 2024-07-11 at 12:10 +, Ross Burton via lists.openembedded.org wrote:
> On 11 Jul 2024, at 10:30, Richard Purdie via lists.openembedded.org
> wrote:
> >
> > +DEBUG_FLAGS:remove:pn-llvm = "-g"
> > +DEBUG_FLAGS:remove:pn-qemu = "-g"
> &g
ff-by: Richard Purdie
---
meta/recipes-devtools/python/python3_3.12.4.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/python/python3_3.12.4.bb
b/meta/recipes-devtools/python/python3_3.12.4.bb
index 77bbfaa069e..743ba0b1f1f 100644
--- a/meta/recipes-devtools/python/python3_3
oes not require util-linux-col to succeed.
[1]
https://github.com/util-linux/util-linux/commit/8886d84e25a457702b45194d69a47313f76dc6bc
Signed-off-by: Chen Qi
Signed-off-by: Richard Purdie
---
meta/recipes-support/libssh2/libssh2_1.11.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-
ff-by: Richard Purdie
---
meta/conf/distro/include/yocto-space-optimize.inc | 1 +
meta/recipes-devtools/python/python3_3.12.4.bb| 1 +
2 files changed, 2 insertions(+)
diff --git a/meta/conf/distro/include/yocto-space-optimize.inc
b/meta/conf/distro/include/yocto-space-optimize.inc
index ffc121
On Wed, 2024-07-03 at 07:59 -0600, Joshua Watt via lists.openembedded.org wrote:
> Downstream tasks may want to know what image files were written so write
> out a manifest in do_image_complete. The format of the manifest is the
> same as the one in image.bbclass
>
> Signed-off-by: Joshua Watt
>
hat I'd recommend it.
Also note that the next version of Yocto Project Compatible will only be
available to layers which are not disabling some set of these errors.
Signed-off-by: Richard Purdie
---
meta/classes-global/insane.bbclass | 9 -
1 file changed, 4 insertions(+), 5 deleti
.
Signed-off-by: Richard Purdie
---
meta/conf/distro/include/yocto-space-optimize.inc | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 meta/conf/distro/include/yocto-space-optimize.inc
diff --git a/meta/conf/distro/include/yocto-space-optimize.inc
b/meta/conf/distro/include/yocto-space
We've been seeing increasing space problems on the autobuilder so we
need to track down "what changed?". A musl-qemux86-64 build (of oe-core
world) is using 240GB and I did a bit of searching to see where the
space was being used. In tmp:
4.0Kabi_version
79M buildstats
37M cache
28G
On Thu, 2024-07-11 at 01:12 -0700, Guðni Már Gilbert via lists.openembedded.org
wrote:
> I'm seeing a very weird bug in Bitbake and I'm not sure if it is just
> my environment. Sharing this in case anyone knows what is going on...
> I've isolated the issue to something between when do_install fini
On Wed, 2024-07-10 at 16:29 -0400, jermigra via lists.openembedded.org
wrote:
> I understand, it is true it doesn't really happen in real recipes. Is
> the new version of the class bad though? I cannot find a way to
> suppress the error from the recipe itself and wish not to edit the
> generated in
On Wed, 2024-07-10 at 08:03 -0600, Joshua Watt wrote:
> On Wed, Jul 10, 2024 at 6:18 AM Richard Purdie
> wrote:
> >
> > On Fri, 2024-07-05 at 08:17 +0100, Richard Purdie via
> > lists.openembedded.org wrote:
> > > > On Wed, 2024-0
On Fri, 2024-07-05 at 08:17 +0100, Richard Purdie via lists.openembedded.org
wrote:
> > On Wed, 2024-07-03 at 07:59 -0600, Joshua Watt via
> > lists.openembedded.org wrote:
> > > > This patch series add support for SPDX 3.0 and sets it as the
> > > > default.
On Thu, 2024-07-04 at 09:09 +0200, Adrian Freihofer via lists.openembedded.org
wrote:
> If the KERNEL_IMAGETYPES(S) contains fitImage, the kernel is always
> rebuilt when something changes in the initramfs, which happens
> frequently.
> This is even worse if the build runs from an empty TMPDIR. Th
On Wed, 2024-07-10 at 09:13 +, Guðni Már Gilbert via
lists.openembedded.org wrote:
> Changelog:
> * https://github.com/bluez/bluez/releases/tag/5.77
> * https://github.com/bluez/bluez/releases/tag/5.76
> * https://github.com/bluez/bluez/releases/tag/5.75
> * https://github.com/bluez/bluez/relea
On Thu, 2024-07-04 at 01:24 -0700, Chen Qi via lists.openembedded.org
wrote:
> From: Chen Qi
>
> License-Update:
> ===
> GPL-2.0 is changed to GPL-2.0-only in README.licensing.
>
> The following two patches are removed as they've been there in new
> release:
>
> 0001-login-utils-i
On Thu, 2024-07-04 at 01:24 -0700, Chen Qi via lists.openembedded.org wrote:
> From: Chen Qi
>
> The 'cgroupv2' PACKAGECONFIG is dropped as systemd now only supports
> cgroupv2.
>
> mime is now inherited because ${datadir}/mime/packages/io.systemd.xml
> is a mime type file.
>
> For musl specifi
On Tue, 2024-07-09 at 16:10 +0200, Alexandre Belloni via
lists.openembedded.org wrote:
> Hello,
>
> Can you submit one patch per recipe?
FWIW I tweaked the shortlog prefix in master-next to mesa/dnf: which
resolves this case.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messa
On Mon, 2024-07-08 at 15:56 -0700, Guðni Már Gilbert via
lists.openembedded.org wrote:
> Looks like BlueZ 5.77 is in the process of being released
> (https://github.com/bluez/bluez/commit/68864d1aa818aca00d67f7a4d60783
> 44483e9509). 👀
>
> I can look into upgrading to 5.77 instead of 5.76. It woul
On Tue, 2024-07-09 at 08:25 +0200, Stefan Mueller-Klieser via
lists.openembedded.org wrote:
> The location of files changed during unpackdir transition. Adapt dirs
> to fix custom icu data generation.
>
> Signed-off-by: Stefan Müller-Klieser
> ---
> meta/recipes-support/icu/icu_75-1.bb | 4 ++--
On Mon, 2024-07-08 at 23:10 +0200, Alexis Lothoré wrote:
> Hello Richard,
>
> On 7/7/24 10:10, Richard Purdie wrote:
> > On Fri, 2024-07-05 at 16:46 +0200, Alexis Lothoré via
> > lists.openembedded.org wrote:
> > > From: Alexis Lothoré
> > > + try:
>
On Mon, 2024-07-08 at 11:56 -0600, Gundlupet Raju, Sandeep wrote:
> Hi RP,
>
> We do see this issue in scarthgap, Can you get this patch backported
> to
> scarthgap branch?
>
> Thanks,
>
> Sandeep
>
> On 6/4/2024 2:06 AM, Enrico Jörns via lists.openembedded.org wrote:
> > Fixes:
> >
> > > pok
It does not always make sense to collect artifacts and data from the
target on failure, e.g. if testing firmware or if the target is not
running an SSH server.
Allow this by setting TESTIMAGE_FAILED_QA_ARTIFACTS to an empty
value.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/utils
On Sun, 2024-07-07 at 04:30 -0700, Guðni Már Gilbert via
lists.openembedded.org wrote:
> I sent a patch to fix the incompatible pointer type warning (from the
> musl logs):
> https://marc.info/?l=linux-bluetooth&m=172035149427086&w=2
>
> This casting is done in other places in the source so I don'
On Sun, 2024-07-07 at 05:55 -0700, Guðni Már Gilbert via
lists.openembedded.org wrote:
> On Sun, Jul 7, 2024 at 10:00 AM, Richard Purdie wrote:
> > Thanks for the patch, unfortunately this ran into issues in our CI.
> > One
> > interesting one is this:
> >
> >
On Wed, 2024-07-03 at 23:56 +, Guðni Már Gilbert via
lists.openembedded.org wrote:
> Changelog:
> * https://github.com/bluez/bluez/releases/tag/5.76
> * https://github.com/bluez/bluez/releases/tag/5.75
> * https://github.com/bluez/bluez/releases/tag/5.74
> * https://github.com/bluez/bluez/relea
On Fri, 2024-07-05 at 16:46 +0200, Alexis Lothoré via lists.openembedded.org
wrote:
> From: Alexis Lothoré
>
> Fixes [YOCTO 15536]
>
> The postactions retrieval actions currently rely on scp executed
> individually on any file or directory expanded from
> TESTIMAGE_FAILED_QA_ARTIFACTS. Unfortun
On Fri, 2024-07-05 at 11:39 +0200, Jörg Sommer via lists.openembedded.org wrote:
> From: Jörg Sommer
>
> The build of u-boot fails, if `UBOOT_MACHINE` (instead of `UBOOT_CONFIG`) is
> used. U-boot doe not like the setting of `O=$S` in the make call, which
> happen when `UBOOT_MACHINE` is used. Th
On Fri, 2024-07-05 at 11:41 +0200, Jörg Sommer wrote:
> Richard Purdie schrieb am Do 04. Jul, 20:38 (GMT):
> > On Thu, 2024-07-04 at 21:18 +0200, Jörg Sommer via
> > lists.openembedded.org wrote:
> > > From: Jörg Sommer
> > >
> > > The u-boot Makefil
and corrupt equivalence data now the underlying issue
was fixed.
Signed-off-by: Richard Purdie
---
meta/classes-global/package.bbclass | 2 +-
meta/conf/abi_version.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes-global/package.bbclass
b/meta
On Fri, 2024-07-05 at 07:18 +0200, Konrad Weihmann wrote:
>
>
> On 04.07.24 17:15, Richard Purdie wrote:
> > On Wed, 2024-07-03 at 04:47 +, Konrad Weihmann via
> > lists.openembedded.org wrote:
> > > if IMAGE_LINK_NAME is set empty to disable the symlinkin
On Wed, 2024-07-03 at 07:59 -0600, Joshua Watt via
lists.openembedded.org wrote:
> This patch series add support for SPDX 3.0 and sets it as the
> default.
> Currently it is not possible to have SPDX 2.2 and SPDX 3.0 enabled at
> the same time
>
> v2: Added tests and addressed feedback
> v3: Fixed
On Thu, 2024-07-04 at 13:46 +0100, Jose Quaresma via
lists.openembedded.org wrote:
> Release notes at https://www.openssh.com/txt/release-9.8
>
> Security
>
>
> This release contains fixes for two security problems, one critical
> and one minor.
>
> 1) Race condition in sshd(8)
>
> A c
On Thu, 2024-07-04 at 21:18 +0200, Jörg Sommer via
lists.openembedded.org wrote:
> From: Jörg Sommer
>
> The u-boot Makefile (even v2024.07) doesn't like it, when `O=…` is
> the same
> directory as the source directory and complains about a dirty source
> directory; see below. This happens when `
ons where they aren't. For now, to try and keep builds
working, work around the problem until we can better look into the problem.
It is likely recent taskhash imrovements have caused this to occur more
regularly.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/reprodu
On Wed, 2024-07-03 at 04:47 +, Konrad Weihmann via
lists.openembedded.org wrote:
> if IMAGE_LINK_NAME is set empty to disable the symlinking
> for image artifacts in deploy, testexport fails, as the path assembly
> is incorrect.
> In that case fallback to IMAGE_NAME
>
> Signed-off-by: Konrad W
Ensure we show the failing exit code in case of failures.
We're seeing autobuilder failures with -15 which is probably from slow
boot/init. Retry in these cases for now.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/runtime/cases/ssh.py | 6 --
1 file changed, 4 insertions(
On Thu, 2024-07-04 at 12:52 +0200, Alexander Kanavin wrote:
> On Wed, 3 Jul 2024 at 15:31, Richard Purdie
> wrote:
>
> > Sorry, I've got confused. Look at tinfoil.cooker_data.file_depends
>
> AttributeError: TinfoilRecipeCacheAdapter instance has no attribute
> &#x
On Wed, 2024-07-03 at 16:40 +0100, Jose Quaresma via lists.openembedded.org
wrote:
> Release notes at https://www.openssh.com/txt/release-9.8
Thanks for the upgrade, it does look important. Unfortunately it had a build
failure for musl:
https://valkyrie.yoctoproject.org/#/builders/3/builds/68
On Wed, 2024-07-03 at 14:28 +0200, Alexander Kanavin wrote:
> On Tue, 25 Jun 2024 at 13:54, Richard Purdie
> wrote:
>
> > I appreciate it calls this "inherits" but this is actually a list
> > of
> > any file included by the base recipe so any bbclass, .bb, o
On Tue, 2024-07-02 at 10:37 -0700, Sundeep KOKKONDA via
lists.openembedded.org wrote:
> On Tue, Jul 2, 2024 at 08:38 PM, Ross Burton wrote:
> > My builder is running oe-selftest -r rust on the incremental
> > upgrades to see what of those fail, but I’m not running
> > reproducible builds yet.
> >
Signed-off-by: Richard Purdie
---
.../qemu/{qemu-native_9.0.0.bb => qemu-native_9.0.1.bb} | 0
...{qemu-system-native_9.0.0.bb => qemu-system-native_9.0.1.bb} | 0
meta/recipes-devtools/qemu/qemu.inc | 2 +-
meta/recipes-devtools/qemu/{qemu_9.
On Tue, 2024-07-02 at 05:37 -0700, Sundeep KOKKONDA via
lists.openembedded.org wrote:
> Hello Richard,
>
> Thanks for test results. We will look into the failures reported.
> These failures are only in 1.78 (Is the testing done on 1.76 & 1.77)?
I only tested with all patches applied so 1.78.
I g
On Tue, 2024-06-25 at 20:30 +0200, Max Krummenacher via
lists.openembedded.org wrote:
> From: Max Krummenacher
>
> When a user of devicetree.bbclass overrides setting S, e.g. to
> git/overlays then having UNPACKDIR set to S results in that
> git repo unpacked inside UNPACKDIR. Thus the sources ar
On Mon, 2024-07-01 at 17:47 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Mon, 2024-07-01 at 02:26 -0700, Yash Shinde via
> lists.openembedded.org wrote:
> > From: Yash Shinde
> >
> > * Drop the following backported patches which are merged
>
On Mon, 2024-07-01 at 02:26 -0700, Yash Shinde via
lists.openembedded.org wrote:
> From: Yash Shinde
>
> * Drop the following backported patches which are merged
> with rust v1.78 upgrade.
>
> - 0001-Revert-Map-source-absolute-paths-to-OUT_DIR-as-relat.patch
> - repro-issue-fix-with-v175.patch
>
On Mon, 2024-07-01 at 02:56 -0700, Sundeep KOKKONDA via
lists.openembedded.org wrote:
> We intentionally dropped these packages from exclude list (informed
> to Richard earlier) to see the issue fixes with latest releases.
This kind of patch series should really have a cover letter explaining
that
On Thu, 2024-06-27 at 16:16 -0600, Joshua Watt via lists.openembedded.org wrote:
> Adds a script to read the released SPDX license JSON data, and uses it
> to update the common license files
>
> Joshua Watt (2):
> scripts/pull-spdx-licenses.py: Add script
> licenses: Update to SPDX license ver
On Thu, 2024-06-27 at 12:34 +, Ross Burton wrote:
> On 27 Jun 2024, at 13:02, Richard Purdie
> wrote:
> >
> > On Wed, 2024-06-26 at 10:41 +0100, Peter Hoyes via
> > lists.openembedded.org wrote:
> > > It does not always make sense to collect artifacts and da
On Thu, 2024-06-27 at 11:29 +0200, Alexandre Belloni via
lists.openembedded.org wrote:
> I believe this causes the following reproducibility failures:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4998/steps/13/logs/stdio
>
> https://autobuilder.yocto.io/pub/repro-fail/oe
On Wed, 2024-06-26 at 10:41 +0100, Peter Hoyes via lists.openembedded.org wrote:
> It does not always make sense to collect artifacts and data from the
> target on failure, e.g. if testing firmware or if the target is not
> running an SSH server.
>
> Introduce the variable TESTIMAGE_RUN_FAILURE_PO
On Mon, 2024-05-06 at 17:32 +0200, Marta Rybczynska via
lists.openembedded.org wrote:
> I'm not a copyright lawyer, but from what I understand public domain
> is not a licence. For a discussion
> see https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Publ
> ic_Domain_within_SPDX_Files
>
During testing we're finding some kernel oops messages and other key kernel
errors such as irq issues are not triggering our log parsing.
Add those keywords to the list of things to scan for, making such
failures much more visible.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/runtime/
On Wed, 2024-06-26 at 15:34 +0200, Quentin Schulz wrote:
> Hi Richard,
>
> On 6/26/24 3:20 PM, Richard Purdie via lists.openembedded.org wrote:
> > On Mon, 2024-06-24 at 00:32 +0300, Leon Anavi via lists.openembedded.org
> > wrote:
> > > Replace references of WOR
On Tue, 2024-06-25 at 19:15 +, Sreejith Ravi via
lists.openembedded.org wrote:
> Currently, the package_do_pkgconfig() only handles the "Requires" key
> field from the .pc file and ignores the "Requires.private" field
> while
> generating the dev dependency chain. This results in a broken
> dep
On Wed, 2024-06-26 at 13:41 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Wed, 2024-06-26 at 10:07 +0100, Sreejith Ravi wrote:
> > No, static libraries were not enabled. I am using only the -dev
> > IPK,
> > which has only the shared libraries. Wi
On Mon, 2024-06-24 at 00:32 +0300, Leon Anavi via lists.openembedded.org wrote:
> Replace references of WORKDIR with UNPACKDIR for U-Boot script
> and variable UBOOT_ENV_BINARY, for example for boot.scr.
>
> Signed-off-by: Leon Anavi
> ---
> meta/recipes-bsp/u-boot/u-boot.inc | 6 +++---
> 1 fil
On Wed, 2024-06-26 at 10:07 +0100, Sreejith Ravi wrote:
> No, static libraries were not enabled. I am using only the -dev IPK,
> which has only the shared libraries. With this change, it is
> successfully building. Also, if it links to the static library, it
> will fail as I am not installing the s
On Tue, 2024-06-25 at 19:15 +, Sreejith Ravi via lists.openembedded.org
wrote:
> Currently, the package_do_pkgconfig() only handles the "Requires" key
> field from the .pc file and ignores the "Requires.private" field while
> generating the dev dependency chain. This results in a broken depend
On Tue, 2024-06-25 at 17:08 +0200, Alexandre Belloni via
lists.openembedded.org wrote:
> Hello,
>
> I believe this is the cause of the following failures:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4986/steps/12/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon
On Mon, 2024-06-24 at 13:10 -0600, Joshua Watt via lists.openembedded.org wrote:
> +python spdx30_build_started_handler () {
> + import oe.spdx30
> + import oe.sbom30
> + import os
> + from pathlib import Path
> +
> + # Create a copy of the datastore. Set PN to "bitbake" so that SPDX
On Tue, 2024-06-25 at 14:41 +0200, Marta Rybczynska wrote:
> Applying ADP (we'll add support just after finishing the tests in
> progress now) requires modifying JSONs for each affected entry. The
> only ADP today is CISA and their entries have been merged in the
> cvelistV5 repo. For us becoming a
On Tue, 2024-06-25 at 13:34 +0200, Alexander Kanavin wrote:
> On Tue, 25 Jun 2024 at 13:06, Richard Purdie
> wrote:
>
> > I don't think we even need to list the recipes like this. When
> > devtool
> > upgrade runs, we get a list of files which change. We can then
On Tue, 2024-06-25 at 11:19 +0200, Alexander Kanavin wrote:
> On Mon, 24 Jun 2024 at 22:33, Richard Purdie
> wrote:
> > Whilst I understand the desire, I'm not sure this lives up to way
> > devtool works.
> >
> > By that I mean that devtool upgrade usually does
On Fri, 2024-06-21 at 12:34 +0200, Alexander Kanavin via
lists.openembedded.org wrote:
> From: Alexander Kanavin
>
> This is modeled on RECIPE_UPGRADE_EXTRA_TASKS with the difference
> being that the tasks run in 'devtool finish', and only when
> finishing an upgrade operation. This allows recipe
On Thu, 2024-06-13 at 21:55 +, Peter Kjellerstedt wrote:
> > -Original Message-
> > From:
> > openembedded-core@lists.openembedded.org
> > > > On Behalf Of Richard Purdie
> > Sent: den 13 juni 2024 10:40
> > To: changqing...@windriver.com;
&g
On Thu, 2024-06-13 at 19:51 +0800, Kai Kang via lists.openembedded.org
wrote:
> From: Kai Kang
>
> It fails to run both `gcc` and `gfortran` with errors:
>
> > root@qemux86-64:~# x86_64-poky-linux-gcc a.c
> > x86_64-poky-linux-gcc: fatal error: cannot execute 'as':
> > posix_spawnp: No such file
On Thu, 2024-06-13 at 09:58 -0700, Khem Raj via lists.openembedded.org
wrote:
> On Thu, Jun 13, 2024 at 4:53 AM Kai Kang via lists.openembedded.org
> wrote:
> >
> > From: Kai Kang
> >
> > g77/f77 has been removed from gcc 4.0.0 via commit:
> >
> > * b4117c30610 Makefile.def, [...]: Remove all
change. This
change will result in some flags appearing to some native/nativesdk variants
but that is probably what was originally expected anyway.
Signed-off-by: Richard Purdie
---
meta/classes-recipe/native.bbclass | 5 -
meta/classes-recipe/nativesdk.bbclass
On Thu, 2024-06-13 at 14:18 +0800, Changqing Li via lists.openembedded.org
wrote:
> From: Changqing Li
>
> * do_configure failed with gcc-14:
> error in build/config.log:
> conftest.c:56:3: error: return type defaults to 'int' [-Wimplicit-int]
> conftest.c:59:5: error: implicit declaration of fu
On Tue, 2024-06-04 at 08:50 +0200, Johannes Schneider wrote:
> systemd-sysext allows to overlay another image (or multiple) ontop of
> a "base-image" = the current rootfs, via the use of overlayfs; to add
> tools and features meant for development purposes.
>
> To quote the documentation on system
Where we're using DL_DIR in sdk archive to try and cache testing artefacts,
copy into the cache so that it gets populated and this doesn't have to be done
manually. Currently we're making a lot of repeat requests to github as this
wasn't being populated.
Signed-off-by: Richa
201 - 300 of 6871 matches
Mail list logo
