Thanks Tim for your help.
On 1/26/2023 1:40 PM, Tim Orling wrote:
On Wed, Jan 25, 2023 at 11:17 AM Gundlupet Raju, Sandeep
wrote:
Hello,
I'm upgrading python3-bqplot from honister to langdale in
meta-jupyter,
I've migrated the recipe version from 0.12.31 ->0.12.36 but I'm
On Thu, Jan 26, 2023 at 11:06 AM Fabio Estevam wrote:
>
> Hi Steve,
>
> Could you please backport poky commit 2ee1fdb8404d ("bitbake:
> fetch2/git: Prevent git fetcher from fetching gitlab repository
> metadata") to kirkstone?
>
> It fixes an issue when trying to fetch mesa.
OK, will do!
Steve
On Thu, Jan 26, 2023 at 5:10 PM Richard Purdie
wrote:
>
> With the 6.1 kernel we've seen reproducibility/determinism issues where the
> kernel
> seems to rebuild headers referencing the hostname or local user. kernel-devsrc
> building after the kernel seemed to trigger it in some cases.
>
>
With the 6.1 kernel we've seen reproducibility/determinism issues where the
kernel
seems to rebuild headers referencing the hostname or local user. kernel-devsrc
building after the kernel seemed to trigger it in some cases.
Moving the definitions to the bbclass used by all the kernel recipe code
On Thu, 2023-01-26 at 14:51 +0100, Tobias Hagelborn wrote:
> For the case of a global shared state cache and a local sstate cache
> with a mix of signed and un-signed entries, there is a case where
> a .sig is missing locally, but may exist in the global sstate cache.
>
> For this case, do not
From: Andrej Valek
- update to next (un)stable version 1.36.0
- refresh defconfig
- disable new applets (tree, tsort, seedrng)
- use hw-accel for sha1/256 sums when available
- remove and refresh already merged patches
Signed-off-by: Andrej Valek
Signed-off-by: Khem Raj
---
v2: Rebased
busybox 1.36 has an ongoing regression on musl/i386 [1] we see same on
glibc systems too.
therefore avoid the affected code by disabling sha256/sha1 sum accelaration
meanwhile
CONFIG_SHA256_HWACCEL and CONFIG_SHA1_HWACCEL are enabled by default
[1]
From: Armin Kuster
Signed-off-by: Armin Kuster
---
.../fix-jbd2-upper-bound-for-v5.10.163.patch | 52
...e-the-correct-print-format-v5.10.163.patch | 61 +++
.../lttng/lttng-modules_2.13.8.bb | 2 +
3 files changed, 115 insertions(+)
create mode
Signed-off-by: Khem Raj
---
meta/recipes-devtools/gdb/gdb.inc | 1 +
...sing-_Alignof-when-using-C11-or-newe.patch | 55 +++
2 files changed, 56 insertions(+)
create mode 100644
From: Marek Vasut
The bitbake git fetcher currently fetches 'refs/*:refs/*', i.e. every
single object in the remote repository. This works poorly with gitlab
and github, which use the remote git repository to track its metadata
like merge requests, CI pipelines and such.
Specifically, gitlab
Hi Steve,
Could you please backport poky commit 2ee1fdb8404d ("bitbake:
fetch2/git: Prevent git fetcher from fetching gitlab repository
metadata") to kirkstone?
It fixes an issue when trying to fetch mesa.
Thanks a lot,
Fabio Estevam
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages
On Wed, Jan 25, 2023 at 11:17 AM Gundlupet Raju, Sandeep <
sandeep.gundlupet-r...@amd.com> wrote:
> Hello,
>
> I'm upgrading python3-bqplot from honister to langdale in meta-jupyter,
> I've migrated the recipe version from 0.12.31 ->0.12.36 but I'm running
> into build missing dependencies
The patch that allows to do so has not been accepted upstream, and wasn't
correctly
working as it was running a native executable (gdk-pixbuf-query-loaders) with
target .so plugins.
On the other hand, out of 20+ (currently 23) tests only three require
running binaries at build time to produce
On Thu, 26 Jan 2023 at 15:54, Richard Purdie
wrote:
> Lets just patch it. I'd rather keep tests, the patch isn't going to be
> complicated or that difficult to maintain.
>
> We might even just be able to force a file into the right place at the
> end of do_install?
I checked. Out of 23 tests
On Thu, Jan 26, 2023 at 9:16 AM Richard Purdie
wrote:
>
> oe-selftest efibootpartition.GenericEFITest.test_boot_efi was failing for 6.1
> kernels with:
>
> | ERROR: _exec_cmd: export PATH=[...] mcopy -i [...]/rootfs_boot.1.vfat -s
> [...]/rootfs1/* ::/ returned '1' instead of 0
> | output: Disk
ssues are:
> > > > > > >
> > > > > > > a) two selftest failures:
> > > > > > >
> > > > > > > oe-selftest -r
> > > > > > > devtool.DevtoolUpgradeTests.test_devtool_virtual_kernel_mod
t; > > > > devtool.DevtoolUpgradeTests.test_devtool_virtual_kernel_modify
> > > > > > oe-selftest -r efibootpartition.GenericEFITest.test_boot_efi
> > > > > >
> > > > > > b) meta-a
a) two selftest failures:
> > > > >
> > > > > oe-selftest -r
> > > > > devtool.DevtoolUpgradeTests.test_devtool_virtual_kernel_modify
> > > > > oe-selftest -r efibootpartition.GenericEFITest.test_boot_efi
> > > > >
> > &
Signed-off-by: Khem Raj
---
...01-drd-tests-Include-missing-cstdint.patch | 34 +++
.../valgrind/valgrind_3.20.0.bb | 1 +
2 files changed, 35 insertions(+)
create mode 100644
meta/recipes-devtools/valgrind/valgrind/0001-drd-tests-Include-missing-cstdint.patch
t; > > >
> > > > oe-selftest -r
> > > > devtool.DevtoolUpgradeTests.test_devtool_virtual_kernel_modify
> > > > oe-selftest -r efibootpartition.GenericEFITest.test_boot_efi
> > > >
> > > > b) meta-arm issues
> > >
Call logger.info() in the log_message handler so that we get request
logging, and hopefully even error messages.
Create a child logger to be neat and compartmentalise the logging.
Add a __main__ entrypoint so this class can be exercised outside of oeqa.
Remove unused traceback import.
oe-selftest efibootpartition.GenericEFITest.test_boot_efi was failing for 6.1
kernels with:
| ERROR: _exec_cmd: export PATH=[...] mcopy -i [...]/rootfs_boot.1.vfat -s
[...]/rootfs1/* ::/ returned '1' instead of 0
| output: Disk full
I believe we hit a file boundary size and having "0" overhead
In recent kernel versions the string "Linux" moved to a header,
'include/linux/uts.h' instead of init/version.c. Allow the test
to work with both situations.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/devtool.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff
t.test_boot_efi
> > >
> > > b) meta-arm issues
> > >
> > > c) meta-virt issue (which you have a patch pending for in -next)
> > >
> >
> > Unfortunately, I have to add
> >
> > d) perf reproducibility issues:
> > https://autobu
t.test_boot_efi
> > >
> > > b) meta-arm issues
> > >
> > > c) meta-virt issue (which you have a patch pending for in -next)
> > >
> >
> > Unfortunately, I have to add
> >
> > d) perf reproducibility issues:
> > https://autobu
On Thu, 2023-01-26 at 11:31 -0500, Randy MacLeod wrote:
> On 2022-11-21 06:11, Tomasz Dziendzielski via lists.openembedded.org wrote:
>
>
>
>
> > From: Mikolaj Lasota
> >
> > Bash script used at the moment takes too much time to calculate obsolete
> > sstate cache files. Let's try to
I have to add
>
> d) perf reproducibility issues:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2294/steps/13/logs/stdio
Ahrrg.
http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230126-poma_o8v/packages/diff-html/
/lib/modules/6.1.5-yocto-standard/b
This is the final pull request for the kirkstone 4.0.7 release build next week.
Steve
On Tue, Jan 24, 2023 at 4:30 PM Steve Sakoman wrote:
>
> The following changes since commit 4760fac939a6204e3cb7dcd3699cd9a2508f9dee:
>
> devtool: process local files only for the main branch (2023-01-12
On 2022-11-21 06:11, Tomasz Dziendzielski via lists.openembedded.org wrote:
From: Mikolaj Lasota
Bash script used at the moment takes too much time to calculate obsolete
sstate cache files. Let's try to rewrite necessary logic in python and
store intermediate data in memory rather than
On 26/01/2023 12:39:02+, Richard Purdie wrote:
> On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > Richard,
> >
> > As promised, here are the commits to switch us over to 6.1 as the
> > default.
> >
> > I'll also send a series for poky to
From: Armin Kuster
Fixes building after updating to 5.10.163 kernel
Signed-off-by: Armin Kuster
---
.../fix-jbd2-upper-bound-for-v5.10.163.patch | 52 ++
...e-the-correct-print-format-v5.10.163.patch | 61 +++
...ix-jbd2-use-the-correct-print-format.patch | 153 ++
Master was recently updated to 2.13.8 and needs this fix. I intend on sending a
patch later today.
I am sending this now to help minimize dup effort if anyone is intending on
updating their 5.10 kernel to the latest version on these branches.
Armin Kuster (1):
lttng-modules: Fix for 5.10.163
On Thu, 2023-01-26 at 15:18 +0100, Alexander Kanavin wrote:
> On Thu, 26 Jan 2023 at 14:01, Richard Purdie
> wrote:
> > Ok, that helps explain it, thanks. Could generate these files using
> > gdk-pixbuf-native?
>
> gsk-pixbuf's meson files are written such that the files cannot be
> supplied
On Thu, 26 Jan 2023 at 13:07, Ravineet Singh wrote:
> I believe the patch cannot be
> upstreamed into gnutls since gnutls use automake and use 'make check' to
> verify the same locally.
> This patch enables running gnutls tests under ptest, hence it would tag the
> patch as:
> Upstream-Status:
On Thu, 26 Jan 2023 at 14:01, Richard Purdie
wrote:
> Ok, that helps explain it, thanks. Could generate these files using
> gdk-pixbuf-native?
gsk-pixbuf's meson files are written such that the files cannot be
supplied from elsewhere. We could patch it in, but upstream will
likely reject that:
From: Fabio Estevam
The patch to fix the tools-only_defconfig error has landed in
U-Boot upstream.
Update the Upstream-Status accordingly.
Signed-off-by: Fabio Estevam
---
...1-Revert-config-tools-only-add-VIDEO-to-build-bmp_logo.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
For the case of a global shared state cache and a local sstate cache
with a mix of signed and un-signed entries, there is a case where
a .sig is missing locally, but may exist in the global sstate cache.
For this case, do not just fail sstate fetch, but rather backfill
the .sig file from the
On Thu, 2023-01-26 at 13:58 +0100, Alexander Kanavin wrote:
> On Thu, 26 Jan 2023 at 13:52, Richard Purdie
> wrote:
> > I don't quite understand this. Does does mean the ptest was working on
> > x86 but not on arm and was silently failing?
>
> Generating data files needed for ptest was working
On Thu, 26 Jan 2023 at 13:52, Richard Purdie
wrote:
> I don't quite understand this. Does does mean the ptest was working on
> x86 but not on arm and was silently failing?
Generating data files needed for ptest was working as long as build
host could execute target binaries (build host
On Thu, 2023-01-26 at 09:37 +0100, Alexander Kanavin wrote:
> Moving to x86-64-v3 instructions revealed that the recipe was doing an
> entirely
> incorrect thing: running native gdk-pixbuf-query-loaders executable against
> the target set
> of loader .so binaries. This worked, but only by
The buildtools-tarball includes a native sysroot with .pc files, and
in the case of buildtools-extended-tarball a pkg-config binary too.
If we're using the host pkg-config then it doesn't know to search in the
native sysroot. If we're using our pkg-config then it searches in the
build-time
On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Richard,
>
> As promised, here are the commits to switch us over to 6.1 as the
> default.
>
> I'll also send a series for poky to bump things there as well.
>
> Also, if there are any significant
On Mon, 16 Jan 2023 at 14:30, Richard Purdie
wrote:
> There is also an implied challenge here of the different stages of
> "checkout the repos", "document those checkouts in bblayers.conf" and
> "here is a separate build directory". The layer config file is where
> information from the two are
On Thu, 2023-01-26 at 11:09 +0100, Louis Rannou wrote:
> On 26/01/2023 11:02, Richard Purdie wrote:
> > On Wed, 2023-01-25 at 09:31 +0100, Louis Rannou wrote:
> > > From: Louis Rannou
> > >
> > > [YOCTO #9070]
> > >
> > > Add a new selftest to validate the locales generation. This selftest
> >
On 26/01/2023 11:02, Richard Purdie wrote:
On Wed, 2023-01-25 at 09:31 +0100, Louis Rannou wrote:
From: Louis Rannou
[YOCTO #9070]
Add a new selftest to validate the locales generation. This selftest builds a
complete target with GLIBC_GENERATE_LOCALES, IMAGE_LINGUAS,
On Wed, 2023-01-25 at 09:31 +0100, Louis Rannou wrote:
> From: Louis Rannou
>
> [YOCTO #9070]
>
> Add a new selftest to validate the locales generation. This selftest builds a
> complete target with GLIBC_GENERATE_LOCALES, IMAGE_LINGUAS,
> ENABLE_BINARY_LOCALE_GENERATION set. The locales are
Signed-off-by: Alexander Kanavin
---
meta/recipes-graphics/vulkan/vulkan-samples_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
index c0ce393201..0a936a78e2 100644
Moving to x86-64-v3 instructions revealed that the recipe was doing an entirely
incorrect thing: running native gdk-pixbuf-query-loaders executable against the
target set
of loader .so binaries. This worked, but only by coincidence, and no longer
works on build hosts that do not support v3
My bad, will fix and resend the patch.
Thanks Alex!
/RAvineet
On Thu, Jan 26, 2023 at 09:18:06AM +0100, Alexander Kanavin wrote:
> On Thu, 26 Jan 2023 at 09:03, Ravineet Singh
> wrote:
> > > Also the newly added patch is missing Upstream-Status. Aren't you
> > > getting a build failure with
On Thu, 26 Jan 2023 at 09:03, Ravineet Singh wrote:
> > Also the newly added patch is missing Upstream-Status. Aren't you
> > getting a build failure with that?
> Sorry, I am new to openembedded/yocto hence I do not know where to find the
> build output/status. Could you point me to it?
I
On Wed, Jan 25, 2023 at 10:02:22PM +0100, Alexander Kanavin wrote:
> On Wed, 25 Jan 2023 at 15:20, Ravineet Singh
> wrote:
> >
> > On Wed, Jan 25, 2023 at 03:02:27PM +0100, Alexander Kanavin wrote:
> > > Thanks! Before this can be added I'd like to clarify two things:
> > > - is execution time
51 matches
Mail list logo
