I couldn't find any evidence of it actually being
required at build or run time.
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/python/python3-pytest-runner_6.0.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-pytest
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/python/python3-babel_2.13.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-babel_2.13.1.bb
b/meta/recipes-devtools/python/python3-babel_2.13.1.bb
index 6908d813265
As allowed by https://github.com/PyO3/setuptools-rust/pull/336
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/python/python3-setuptools-rust_1.8.1.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-setuptools-rust_1.8.1.bb
b/meta/recipes
Date: Tue Mar 7 12:54:33 2017 -0600
gpgme: Fix issue building for the target
which wasn't prompted by any consumer requiring python,
but rather to correct build errors in absence of specific
configuration passed in.
Signed-off-by: Alexander Kanavin
---
meta/recipes-support/gpgme
g-i still uses distutils in various places, and upstream MRs and tickets
aren't getting a lot of traction. As distutils is gone from the core
library in python 3.12, rely on setuptools copy.
Signed-off-by: Alexander Kanavin
---
.../gobject-introspection/gobject-introspection_1.78.1.bb | 3
Upstream has made the needed fixes (not easy to backport), but
hasn't released a new version with them. Distutils has been
removed from the core python library in 3.12.0.
Signed-off-by: Alexander Kanavin
---
meta/recipes-support/libcap-ng/libcap-ng-python_0.8.3.bb | 3 ++-
1 file changed, 2
As of
https://github.com/rpm-software-management/dnf/commit/8806b2ee99a322c7201239a1cf14d191c87e152a
dnf is using librepo's crypto.
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/dnf/dnf_4.18.1.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-devtools/dnf
On Thu, 14 Dec 2023 at 15:39, Richard Purdie
wrote:
> I not entirely happy about this since start_worker() executes processes
> and isn't trivial. The code is careful enough to tear them down too at
> exit but it is all a bit of a waste of time.
>
> I had wondered if we can create
be completely broken or completely working, and we would
have no idea. I lean towards 'completely broken' but I'll reinstate
the patch.
Alex
On Thu, 14 Dec 2023 at 14:49, Alexander Kanavin via
lists.openembedded.org
wrote:
>
> FWIW in the upcoming python 3.12 update I have removed the pgo
FWIW in the upcoming python 3.12 update I have removed the pgo patch
(0001-Makefile.pre-use-qemu-wrapper-when-gathering-profile.patch) with
the rationale that "pgo support has been rewritten upstream and needs
to be reenabled and tested separately". I simply don't have bandwidth
to make it work,
Signed-off-by: Alexander Kanavin
---
bitbake/lib/bb/runqueue.py | 4
1 file changed, 4 insertions(+)
diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
index 2d2b28b3c99..bb75e81c557 100644
--- a/bitbake/lib/bb/runqueue.py
+++ b/bitbake/lib/bb/runqueue.py
@@ -1751,7
In particular having 'time' explicitly used as a sorting key should make it
more clear how the entries are being sorted.
Signed-off-by: Alexander Kanavin
---
bitbake/bin/bitbake-diffsigs | 11 +++
bitbake/lib/bb/runqueue.py | 10 +-
2 files changed, 12 insertions(+), 9
h
of those tasks (six or seven times) - this is an expensive operation
taking several minutes, and it's best to do it only once per test.
[YOCTO #15289]
Signed-off-by: Alexander Kanavin
---
.../perlcross_%.bbappend} | 0
meta/lib/oeqa/selftest/cases/sstatetests
'
and the actual local stamp will be discarded. This change ensures
the scenario does not happen.
It also makes use of the reworked find_siginfo(), particularly the 'sstate'
entry in returned results.
Signed-off-by: Alexander Kanavin
---
bitbake/lib/bb/runqueue.py | 3 +++
1 file changed, 3 insertions
prioritize local stamps when looking up most
recent task signatures.
Signed-off-by: Alexander Kanavin
---
meta/lib/oe/buildhistory_analysis.py| 2 +-
meta/lib/oe/sstatesig.py| 31 +
meta/lib/oeqa/selftest/cases/sstatetests.py | 10 +++
3 files
be useful to
determine whether the missing cdn objects were never created or
erroneously cleaned up, or if they were created but didn't propagate
to cdn.
[YOCTO #15303]
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 99 ++---
1 file changed, 67
basic and
affects tasks coming ahead of gnu-config-native:do_compile.
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/gnu-config/gnu-config_git.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/gnu-config/gnu-config_git.bb
b/meta/recipes
in a
different function later, and recursively comparing that to the current
signature,
which is unreliable on real world caches. For the sake of fixing the test
failures
I'd like to not delay the patchset any further for now.
[YOCTO #15289]
Signed-off-by: Alexander Kanavin
---
bitbake/lib/bb
printdiff needs setscene dependencies and they're available only
through that object. Previously it was instantianted just after
running printdiff, this moves the initilization to just prior.
Signed-off-by: Alexander Kanavin
---
bitbake/lib/bb/runqueue.py | 10 +-
1 file changed, 5
On Thu, 14 Dec 2023 at 13:30, Richard Purdie
wrote:
> I think it would have a huge impact on the throughput of patches :( An
> hour or two before the majority of the tests even start.
Then the only remaining idea I have is adding more hardware. So that
there's enough of it to rarely if ever have
On Thu, 14 Dec 2023 at 13:11, Richard Purdie
wrote:
> I've wondered about this. The "prebuild" ends up quite slow as it would
> involve rust for example and when I last tried this, it ended up being
> a pain and just increased overall testing times even of the overall
> load on the AB might have
On Thu, 14 Dec 2023 at 10:50, Richard Purdie
wrote:
> Once a given build has run through the system, things do run much
> faster but this is basically the performance issue I've been mentioning
> in the weekly status reports. Even the above packageconfig change in
> this patch would actually
On Thu, 14 Dec 2023 at 10:44, Robert Yang via lists.openembedded.org
wrote:
> >> +Upstream-Status: Pending
> >
> > Can you upstream this please?
>
> Submitted: https://marc.info/?l=linux-nfs=170254661824522=2
Thanks, please resubmit this patch with updated Upstream-Status.
Alex
On Wed, 13 Dec 2023 at 09:57, Yoann Congal wrote:
>
> The bluetooth support adds a bluez5 dependency (and,recursively, a lot
> of other stuff). Disable it by default to avoid having to build all of
> this when it is not needed.
>
> This decrease the number of tasks run for a core-image-minimal
; === short test summary info
>
> FAIL tests/test_skeleton_codestyle.py::BaseTests::test_skeleton_codestyle
> 1 failed, 174 passed in 7.08s
> =
>
> Thanks,
> __
On Wed, 13 Dec 2023 at 22:07, Peter Marko via lists.openembedded.org
wrote:
> +From f32056f825b926b5820d43478d11e92eee1ec91f Mon Sep 17 00:00:00 2001
> +From: Peter Marko
> +Date: Wed, 13 Dec 2023 21:18:14 +0100
> +Subject: [PATCH] meson: get version as parameter instead of querying git
> +
>
I see that run-ptest consists of a single pytest command; does that
command return a zero exit code even it fails?
Alex
On Wed, 13 Dec 2023 at 17:38, Alexander Kanavin wrote:
>
> Why isn't the ptest failure reported by the autobuilder? Shouldn't we
> first fix the ptest so that th
Why isn't the ptest failure reported by the autobuilder? Shouldn't we
first fix the ptest so that the failure is reported correctly, if it
starts occurring again?
Alex
On Wed, 13 Dec 2023 at 11:21, Yu, Mingli wrote:
>
> From: Mingli Yu
>
> Fix the below ptest failure:
> self =
> def
On Wed, 13 Dec 2023 at 09:30, Changqing Li
wrote:
> +From 1b7d547453fc57806ef86f64c86706530a23e62e Mon Sep 17 00:00:00 2001
> +From: Changqing Li
> +Date: Wed, 13 Dec 2023 11:53:18 +0800
> +Subject: [PATCH] Makefile.in: set outdir for tic
> +
> +tic is from ncurses-native, and set TERMINFO as
>
On Mon, 11 Dec 2023 at 10:09, Alex Kiernan wrote:
> In a single project there are (potentially) multiple Cargo.toml, but
> just one Cargo.lock. If there's multiple Cargo.lock files in a repo,
> that implies multiple projects which I don't think we've any way of
> building from a single recipe.
I have to say, I struggle to see this as an improvement, and I want
to object to it.
Why set the path manually, if the code to find where Cargo.lock is
just works, and handles the situations where upstreams move it around
in source trees?
Also, is the assumption that there's only one Cargo.lock
Perhaps you can publish the final version somewhere like github so we
can easily refer to it, should someone express interest in it?
Alex
On Fri, 8 Dec 2023 at 17:56, Alex Stewart wrote:
>
> Hopefully, the reply-to has worked here.
>
> This patchset was originally submitted by Charlie Johnston
On Fri, 8 Dec 2023 at 13:22, Richard Purdie
wrote:
> Crazy question - for the CDN tests, why don't we try just setting a
> dummy SSTATE_DIR, then "bitbake -n" and check the "State
> Summary:" line in the output?
It would be good to know what is missing though, not just how many?
Alex
On Fri, 8 Dec 2023 at 11:13, Changqing Li
wrote:
> dnf has a bug, refer [1], it cause 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
. This is reflected in
fixing up the selftests.
[YOCTO #15289]
Signed-off-by: Alexander Kanavin
---
bitbake/lib/bb/runqueue.py| 27 +-
.../perlcross_%.bbappend} | 0
meta/lib/oeqa/selftest/cases/sstatetests.py | 51 +++
3 files changed, 43
This is already done for local stamps just above, and will allow enabling
the full selftest that compares gcc-source signatures via printdiff
(that is, both local stamp and sstate variants).
Signed-off-by: Alexander Kanavin
---
meta/lib/oe/sstatesig.py | 3 +++
1 file changed, 3 insertions
).
The CDN check will be performed via a separate 'printmissing'
function, which would be written specifically for the purpose,
and so until then disable the test as it would only persistently fail.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 4 ++--
1 file
If the tests fail, these contain useful artefacts, and so should
be kept. If the test succeeds the whole build-st/ is deleted.
Also, give them unique names, as otherwise the tests would
step on each other.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 22
basic and
affects tasks coming ahead of gnu-config-native:do_compile.
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/gnu-config/gnu-config_git.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/gnu-config/gnu-config_git.bb
b/meta/recipes
Assert*() functions from python unittest would join the multiline output with
\n, making it
almost unreadable.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta/lib/oeqa/selftest
On Thu, 7 Dec 2023 at 13:45, Eilís 'pidge' Ní Fhlannagáin
wrote:
> -USERADDSETSCENEDEPS:class-target =
> "${MLPREFIX}base-passwd:do_populate_sysroot_setscene
> pseudo-native:do_populate_sysroot_setscene
> shadow-native:do_populate_sysroot_setscene
>
On Wed, 6 Dec 2023 at 20:46, Peter Kjellerstedt
wrote:
> Will changing that to:
>
> In addition to updating the sha256sum and removing the md5sum, update
> all other existing checksums. If the only existing checksum is md5sum, then
> replace it with the default expected checksums (currently only
I mean, what possible reason there could be to keep them? None as far
as I can see.
Alex
On Wed, 6 Dec 2023 at 20:25, Alexander Kanavin wrote:
>
> We've been relying on this to actually remove md5sums on version
> updates, so please do not regress that.
>
> Alex
>
> On Wed
We've been relying on this to actually remove md5sums on version
updates, so please do not regress that.
Alex
On Wed, 6 Dec 2023 at 20:22, Peter Kjellerstedt
wrote:
>
> Rather than only updating the sha256sum and removing the md5sum, update
> all existing checksums. If the only existing
On Wed, 6 Dec 2023 at 12:51, Andrey Zhizhikin wrote:
> > Unfortunately I have to say no to this. The problem is that this will
> > update to latest revisions on all the layers, which I believe is not
> > what people would want, as everything including poky etc. will be
> > shifting
Unfortunately I have to say no to this. The problem is that this will
update to latest revisions on all the layers, which I believe is not
what people would want, as everything including poky etc. will be
shifting uncontrollably.
Conceptually, I would not want oe-setup-layers to suffer from
On Wed, 6 Dec 2023 at 03:39, Changqing Li
wrote:
> The review comments that led to the revert are still valid, and this
> message does not address them. The concern was that the removal via
> rootfs postprocess is too late. If dnf leaves lock files around, they
> should be removed just after the
On Tue, 5 Dec 2023 at 10:44, Johannes Pointner wrote:
> Thanks, I understand that, but ldconfig-native seemed very special to me, so
> I tried to take an example from the existing patches.
>
> So the next step would be a v2 with a better explanation and obviously a
> fixed sendemail.from?
> Or
mickledore is already end of life I think?
Alex
On Mon, 4 Dec 2023 at 20:36, Joe Slater via lists.openembedded.org
wrote:
>
> From: Joe Slater
>
> De-fuzz existing patches.
> Do not update PACKAGECONFIG to match master.
>
> Signed-off-by: Joe Slater
> ---
>
On Tue, 5 Dec 2023 at 06:46, Changqing Li
wrote:
> So I add this patch
> https://git.openembedded.org/openembedded-core/commit/?id=406a72a9a47c2735b7e18cefc682b1df00d5a9aa
> to remove the lock file in rootfs.
>
> Since for dnf-native, it will not have reboot process, so it is better
> to
Then it's probably best to write a recipe, so that the code can be
hosted externally and maintained independently of oe-core?
Alex
On Mon, 4 Dec 2023 at 15:46, Andrey Popov wrote:
>
> Hello, Alex!
>
> I have doubts that the entire isoparser class set could be inlined, that
> would occupy
How big is the script? Can it be 'inlined' into the class as a set of functions?
Alex
On Mon, 4 Dec 2023 at 14:33, Andrey Popov wrote:
>
> Hello, Alexandre!
>
> Thank you for the feedback.
> I think I can eliminate the xorriso/libisoburn dependency by replacing it
> with a python script that
On Thu, 30 Nov 2023 at 17:16, Andrey Popov wrote:
> - # EFI only
> - if [ "${PCBIOS}" != "1" ] && [ "${EFI}" = "1" ] ; then
> - # Work around bug in isohybrid where it requires isolinux.bin
> - # In the boot catalog, even though it is not used
> -
On Mon, 4 Dec 2023 at 13:48, Lukas Funke
wrote:
> You're probably right. A little context is always helpful.
>
> From the top: the proposed change is setting the commit-hash in
> exported patches to all-zero.
>
> When devtool is updating the recipes using 'devtool update-recipe
> ' it figures
On Mon, 4 Dec 2023 at 11:48, Lukas Funke
wrote:
> Unfortunately, the patch indeed causes the tests to fail. The
> problamatic lines are in the 'lib\devtool\standard.py':
>
> if len(firstlineitems) > 1 and len(firstlineitems[1]) == 40:
> if not firstlineitems[1] in changed_revs:
>
Generally if you mark something as inappropriate, it's best to write
an extended description of why in the patch. The barrier to adding
patches that we can never upstream is high.
Alex
On Mon, 4 Dec 2023 at 07:53, Johannes Pointner wrote:
>
> Hello,
>
> On Sat, Dec 2, 2023 at 4:13 PM Alexandre
Is this a different patchtest issue to the one that was fixed?
Alex
On Sun, 3 Dec 2023 at 17:33, Patchtest
wrote:
>
> Thank you for your submission. Patchtest identified one
> or more issues with the patch. Please see the log below for
> more information:
>
> ---
> Tests failed for the patch,
Thanks for this one, I hope we can finally get that vte update in :)
Alex
On Sat, 2 Dec 2023 at 01:09, Khem Raj wrote:
>
> Signed-off-by: Khem Raj
> ---
> v2: Change 'if' to 'elif' to make it part of if else block
>
> meta/classes-recipe/rust-common.bbclass | 2 ++
> 1 file changed, 2
Please see my latest comment in the bug, I don't think recipe_qa is to
blame, and it's not going to solve the issue.
Also, we do plan to actually register the outcome of recipe_qa into
sstate, that's why there's a placeholder for it
Alex
On Fri, 1 Dec 2023 at 16:19, Joshua Watt wrote:
>
>
On Fri, 1 Dec 2023 at 12:49, Richard Purdie
wrote:
> This looks like it removes WORKDIR, not CFLAGS so it doesn't quite
> match the commit message?
>
> I think it might be wise to put a comment in the code here saying
> exactly what its doing so we can know in future too.
Yes, it drops WORKDIR
Hello Julien,
thanks again for making devtool better. I don't think there are any
particularly strong opinions about the finer points; at this point you
know the code better than anyone else, and so I trust you make the
right calls :)
Alex
On Thu, 30 Nov 2023 at 23:02, Julien Stephan wrote:
>
On Wed, 29 Nov 2023 at 10:36, Marco Felsch wrote:
> > I don't like removing WERROR unconditionally which decreases quality checks.
> > Can we do it only in case ICECC is used?
> > Something like "${@'-DDISABLE_WERROR=ON' if bb.data.inherits_class(icecc,
> > d) else ''}"
>
> Good point, but IMHO
On Tue, 28 Nov 2023 at 11:31, Zoltan Boszormenyi wrote:
> The warning only occurs if os.fork() is called when
> there are already Python threads.
>
> I guess the general performance uplift in Python 3.12
> can trigger a pre-existing issue in bitbake more easily.
>
> It is entirely possible that
On Tue, 28 Nov 2023 at 15:32, Sverdlin, Alexander
wrote:
> > So once someone sends an update to 2023, they should also backport
> > the patch that introduces the new make target, and use that target.
> > And if there's an update to an even newer version, then the new target
> > can be used
On Tue, 28 Nov 2023 at 14:50, Sverdlin, Alexander
wrote:
> > In general, || in shell scripts should be avoided because it ignores
> > the reason for the failure (ignoring some fails may be ok, ignoring
> > all fails is not ok, as it will cause silent regressions).
>
> 2023 will be problematic
On Tue, 28 Nov 2023 at 14:20, A. Sverdlin
wrote:
> Versions starting from 20230919 require rdfind; at some point new make
> target was introduced with commit 4124f8f928d5 ("Make rdfind optional").
> The commit is not yet included even in 2023, thus make even the
> new make target optional.
>
But what was the excessive line that caused patchtest to not say
anything useful? Can patchtest trim it or otherwise do better?
Alex
On Tue, 28 Nov 2023 at 11:48, Viswanath Kraleti
wrote:
>
> I figured it by running patchtest. S-o-B trailer missing in .patch. I am
> updating it.
>
> On
On Tue, 28 Nov 2023 at 11:00, Richard Purdie
wrote:
> I'm not sure that is entirely true/fair. The way bitbake has executed
> processes and handled threads was very carefully written deliberately
> to avoid some of these kinds of issues so it wasn't "pure luck". What I
> don't know is what
How about using --ignore-duplicates?
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/copy-firmware.sh?id=4124f8f928d51a1437e2fd2636b20d540edc2836
Adding a new recipe means someone has to keep it working and updated
(which means adding a maintainers.inc entry),
On Mon, 27 Nov 2023 at 11:59, Richard Purdie
wrote:
> FWIW I'm still leaning towards static linking for this. The setscence
> dependencies are playing with fire and we *really* don't want to do
> this :(
Was there some half-done branch with that approach? I could pick that
up once I get
Fedora 39 isn't yet supported or tested, so it's almost certainly
you've hit a python 3.12 compatibility issue. If you can look into,
that would be very appreciated.
Alex
On Mon, 27 Nov 2023 at 10:52, Zoltan Boszormenyi wrote:
>
> Hi,
>
> I am not sure what's the actual problem here.
>
> FWIW,
Better shortlog:
default-providers.inc: add PREFERRED_PROVIDER variables for llvm
Alex
On Mon, 27 Nov 2023 at 11:20, Patchtest
wrote:
>
> Thank you for your submission. Patchtest identified one
> or more issues with the patch. Please see the log below for
> more information:
>
> ---
> Testing
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/repo/repo/0001-python3-shebang.patch | 2 +-
meta/recipes-devtools/repo/{repo_2.37.bb => repo_2.39.bb} | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/repo/{repo_2.37.bb => repo_2.39.b
Signed-off-by: Alexander Kanavin
---
...0001-Makefile-Allow-for-CC-and-AR-to-be-overridden.patch | 6 +++---
meta/recipes-rt/rt-tests/rt-tests.inc | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git
a/meta/recipes-rt/rt-tests/files/0001-Makefile-Allow
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/meson/{meson_1.2.2.bb => meson_1.3.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/meson/{meson_1.2.2.bb => meson_1.3.0.bb} (98%)
diff --git a/meta/recipes-devtools/meson/meson_1.2.2.bb
Convert to meson.
Signed-off-by: Alexander Kanavin
---
...ktop-file-utils_0.26.bb => desktop-file-utils_0.27.bb} | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
rename meta/recipes-devtools/desktop-file-utils/{desktop-file-utils_0.26.bb =>
desktop-file-utils_0.27.bb} (76%)
--disable-lfs-alias removed upstream.
Signed-off-by: Alexander Kanavin
---
.../mpg123/{mpg123_1.31.3.bb => mpg123_1.32.3.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename meta/recipes-multimedia/mpg123/{mpg123_1.31.3.bb => mpg123_1.32.3.bb}
(95%)
diff
Switch to gitsm:// to fetch https://github.com/p11-glue/pkcs11-json.git
as a submodule (otherwise meson will try to do that in do_configure).
Signed-off-by: Alexander Kanavin
---
.../p11-kit/files/strerror-1.patch| 76 ---
.../p11-kit/files/strerror-2.patch
Latest meson expects it there and fails if it can't find it; meanwhile
we patch glib to put it into libexecdir for reasons of avoiding incorrect
debian package renaming in multilib scenarios.
Signed-off-by: Alexander Kanavin
---
meta/recipes-core/glib-2.0/glib.inc | 5 +
1 file changed, 5
License-Update: formatting
https://github.com/unicode-org/icu/commit/248b1c2a13fc7fc346e9e9419c4794df8a590ad9
Signed-off-by: Alexander Kanavin
---
meta/recipes-support/icu/{icu_73-2.bb => icu_74-1.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-support/
Add bash-completion support for xkbcli.
Signed-off-by: Alexander Kanavin
---
.../xorg-lib/{libxkbcommon_1.5.0.bb => libxkbcommon_1.6.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-graphics/xorg-lib/{libxkbcommon_1.5.0.bb =>
libxkbcommon_1.6.0.b
venus (virtual vulkan support) is no longer experimental.
Signed-off-by: Alexander Kanavin
---
...1-meson.build-use-python3-directly-for-python.patch | 10 +-
...{virglrenderer_0.10.4.bb => virglrenderer_1.0.0.bb} | 8
2 files changed, 9 insertions(+), 9 deletions(-)
ren
Signed-off-by: Alexander Kanavin
---
.../epiphany/{epiphany_44.6.bb => epiphany_45.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-gnome/epiphany/{epiphany_44.6.bb => epiphany_45.1.bb} (94%)
diff --git a/meta/recipes-gnome/epiphany/epiphany_4
Drop check-GST_GL_HAVE_PLATFORM_GLX.patch as upstream removed the code.
Signed-off-by: Alexander Kanavin
---
...44e17d258106617b0e6d783d073b188a2548.patch | 15 +
.../check-GST_GL_HAVE_PLATFORM_GLX.patch | 33 ---
...ebkitgtk_2.40.5.bb => webkitgtk_2.42.2.bb} |
Signed-off-by: Alexander Kanavin
---
.../cmake/{cmake-native_3.27.5.bb => cmake-native_3.27.7.bb}| 0
meta/recipes-devtools/cmake/cmake.inc | 2 +-
.../recipes-devtools/cmake/{cmake_3.27.5.bb => cmake_3.27.7.bb} | 0
3 files changed, 1 insertion(+), 1 de
Signed-off-by: Alexander Kanavin
---
...rofs-utils_1.6.bb => erofs-utils_1.7.1.bb} | 10 +-
...-don-t-allocate-read-too-large-exten.patch | 126 --
...-block-insane-long-paths-when-extrac.patch | 80 ---
3 files changed, 4 insertions(+), 212 deletions(-)
rename m
Drop CFLAGS (containing host paths) from installed pkg-config file.
Signed-off-by: Alexander Kanavin
---
.../usbutils/{usbutils_015.bb => usbutils_017.bb} | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
rename meta/recipes-bsp/usbutils/{usbutils_015.bb => usbutils_
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/python/python3-pyproject-hooks_1.0.0.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-pyproject-hooks_1.0.0.bb
b/meta/recipes-devtools/python/python3-pyproject-hooks_1.0.0.bb
index
ded.
A similar fix is added to musl in order to define non-standard
__BEGIN_DECLS/__END_DECLS.
Signed-off-by: Alexander Kanavin
---
...01-Disable-use-of-syslog-for-sysroot.patch | 52 ---
.../0001-Fix-can-not-print-full-login.patch | 41
.../files/0001-Overh
the reason no longer applies, sstate and sysroot handling
has changed massively since early 2013, testing on a-full revealed
no issues, and avoiding incorrect fall-through to host libraries
is better than pulling unneeded dependencies.
Signed-off-by: Alexander Kanavin
---
meta/classes-global
Latest shadow-native links with additional libraries;
I was unable to find a way to resolve those in setscene context
where tasks do not contain such dependencies.
Signed-off-by: Alexander Kanavin
---
meta/classes/useradd.bbclass | 8 +++-
1 file changed, 7 insertions(+), 1 deletion
Thank you, the patch is fine now. The next step is that if there are
integration issues on the autobuilder, you will get links to them and
the expectation is that they are resolved by you, and the adjusted
patch is resubmitted.
Alex
On Mon, 27 Nov 2023 at 05:02, qi...@fujitsu.com wrote:
>
>
On Fri, 24 Nov 2023 at 18:05, Khem Raj wrote:
>> > > Split the packages so that the GTK3 binaries are in separate packages to
>> > > the GTK4 binaries.
>> >
>> > Hmm interesting I wonder if it Will avoid adding the dependencies for dbg
>> > and dev packages
>>
>> It won’t, you’ll need to
On Thu, 23 Nov 2023 at 22:07, Marek Vasut wrote:
> The lzop is called in oe-core and I was under the impression that
> oe-core shouldn't depend on anything except bitbake . So either this
> stuff should be moved to meta-oe too (which would be unfortunate growth
> of dependencies) or the lzop
gt; create mode 100644 meta/recipes-support/lzop/lzop/acinclude.m4
> create mode 100644 meta/recipes-support/lzop/lzop_1.04.bb
>
> diff --git a/meta/conf/distro/include/maintainers.inc
> b/meta/conf/distro/include/maintainers.inc
> index 35f8a72fa4..e95ab59d0d 100
Thanks for working on this. I'm a little worried about the central
patch as it's large and changes things all over the place, but if
oe-selftest passes, there's no reason to not merge it. If AUH breaks,
we'll deal with it :)
Alex
On Wed, 22 Nov 2023 at 12:08, Julien Stephan wrote:
>
> This
I suppose you can check, on master:
- whether dropping the CVE fix addresses the problem
- whether updating to recent patchlevel addresses the problem
- bisect changes in the patchlevel down to what is needed to fix the
CVE and not regress
Given that you have a basic build, tweaking ncurses and
On Wed, 22 Nov 2023 at 10:30, Alexander Kanavin wrote:
> Thanks, now I understand what happened. This feature was actually
> never backported to kirkstone (and won't be because of LTS policy - no
> new features), but documentation was (mistakenly) updated to state
> that it
On Wed, 22 Nov 2023 at 13:23, Adrian Freihofer
wrote:
> But I also have to say that recent documentation points out that the
> rootfs.tar must be extracted into the extracted rootfs-dbg which is a
> working solution. The issue which I have is with the SDK which tries to
> avoid building the tars
On Wed, 22 Nov 2023 at 13:10, Alberto Merciai wrote:
> > Alberto, can you check that this works as expected on master or any
> > more recent release where my commit is present, and the file is set
> > correctly?
> Let me understand if we are both at the same page.
> That feture will be not
401 - 500 of 9901 matches
Mail list logo
