From: Saul Wold
FIXES [YOCTO #12342]
When testing a Multilib image, the package manifest list contains
the fully qualified package name which includes the Multilib Prefix.
This patch adds the MLPREFIX to the package names that are passed
into the @OEHasPackage() decorator to ensure the set
From: Richard Purdie
The tests were not cleaning up after themselves and making assumptions about
memory resident bitbake being stopped by the scripts.
Add cleanup logic to ensure the tests don't break other things and
clean up created files.
Signed-off-by: Richard Purdie
(cherry picked from
From: Richard Purdie
It is possible we could crash holding a lock whilst parsing in this code.
Switch to use utils.fileslocked() in the with expression to avoid this.
This may be causing some of our strange intermittent failures in PRServ
tests.
Signed-off-by: Richard Purdie
(cherry picked
From: Joshua Watt
The vardepsexclude was subtly wrong in that it referenced STATE_MANMACH
when the actual variable name is SSTATE_MANMACH.
Signed-off-by: Joshua Watt
Signed-off-by: Richard Purdie
(cherry picked from commit ec5054396f7fafea2a071d2695ae111fc585d6e6)
Signed-off-by: Steve Sakoman
From: Robert Berger
added --clamp-mtime --mtime to the tar command
see:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15148
Signed-off-by: Robert Berger
Signed-off-by: Richard Purdie
(cherry picked from commit 2ef7c63871ab4fb62a9cea45a23a78bf9d541e4a)
Signed-off-by: Steve Sakoman
---
From: Soumya Sambu
Serial tty is hung after reset command -
$echo "test " >> /dev/ttyS0
test
$stty -a < /dev/ttyS0
speed 115200 baud; rows 34; columns 153; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 =
; swtch = ;
start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
From: Clay Chang
Use oe.utils.get_bb_number_threads to get max_process
Signed-off-by: Clay Chang
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit f0056dca0a44c374f1f0c5fccbf66ae88e0b1850)
Signed-off-by: Steve Sakoman
---
From: Richard Purdie
These two tests seem to fail semi-regularly so just stop running them.
Signed-off-by: Richard Purdie
(cherry picked from commit 1bfa564f1aa8b865f6c3ae3501e6d5f6cc0542eb)
Signed-off-by: Steve Sakoman
---
meta/recipes-support/curl/curl/disable-tests | 6 ++
1 file
From: Peter Marko
Since switch from Makefile to meson based build,
the version is no longer hardcoded but queried from git tag.
This works only if git history is available.
When shallow tarballs are used, tag is not available.
Example error for trusted-firmware-a from meta-arm:
dtc version too
From: Mingli Yu
Fix the below ptest failure:
self =
def test_skeleton_codestyle(self):
"""
This test shouldn't run in proliferated repositories.
"""
setup_cfg = configparser.ConfigParser()
setup_cfg.read("setup.cfg")
> if setup_cfg["metadata"]["name"] != "skeleton":
From: Robert Yang
Update Upstream-Status for
0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch.
Signed-off-by: Robert Yang
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 7189d1ea5c066b9ffc52103160bb34945fd779d7)
Signed-off-by: Steve
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 15Jan24
Date: Mon, 15 Jan 2024 12:48:45 -0500
]
Signed-off-by: Bruce Ashfield
From: Bruce Ashfield
Updating linux-yocto/6.1 to the latest korg -stable release that comprises
the following commits:
fec3b1451d5f Linux 6.1.73
f9ee31dc7fcd cifs: fix flushing folio regression for 6.1 backport
0f22c8a6efe6 ipv6: remove max_size check inline with ipv4
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
1/1 [
Author: Xiangyu Chen
Email: xiangyu.c...@windriver.com
Subject: feature/security: add configs to harden protection
Date: Tue, 16 Jan 2024 18:22:31 +0800
Add some configs to harden protection:
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 27Dec23
Date: Wed, 27 Dec 2023 19:47:13 -0500
]
Signed-off-by: Bruce Ashfield
From: Bruce Ashfield
Updating linux-yocto/6.1 to the latest korg -stable release that comprises
the following commits:
7c58bfa711cb Linux 6.1.72
2dbe25ae06e6 Revert "interconnect: qcom: sm8250: Enable sync_state"
f73a374c1969 smb3: Replace smb2pdu 1-element arrays with flex-arrays
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 27Dec23
Date: Wed, 27 Dec 2023 19:47:13 -0500
]
Signed-off-by: Bruce Ashfield
From: Bruce Ashfield
Updating linux-yocto/6.1 to the latest korg -stable release that comprises
the following commits:
a507f147e6f0 Linux 6.1.70
a413b88cdb69 loop: deprecate autoloading callback loop_probe()
75c27bdb2144 wifi: nl80211: fix deadlock in nl80211_set_cqm_rssi (6.6.x)
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
4aa6747d9352 Linux 6.1.69
325556d46bfd r8152: fix the autosuspend doesn't work
4c2ad8e39c62 r8152: remove rtl_vendor_mode function
1d82735f4bae r8152: avoid to change cfg for
From: Wang Mingyu
Changelog:
=
-The library version numbers have been bumped up for the Kea 2.4.1 stable
release.
-Fixed interface redetection which had stopped working since Kea 2.3.6.
-Fixed a race condition in free lease queue allocator
fix-multilib-conflict.patch
From: Markus Volk
=
Version 1.4.2
=
- Really fix build with libappstream 1.0
=
Version 1.4.1
=
- Fix build with MSVC
- Fix build with libappstream 1.0
- AdwCarousel
- Fix carousel scroll behavior with page reordering
- AdwComboRow
- Fix
From: Wang Mingyu
Changelog:
-Fix some coverity issues exposed in encode
-Fixed VPP coverity issues
Signed-off-by: Wang Mingyu
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 2bd1443d047ba56196b2eaa7d59b3c39c9c0f49b)
Signed-off-by: Steve
From: Wang Mingyu
Changelog:
=
* Eliminate 'atomic_thread_fence is unsupported with tsan' gcc-11 warning
* Eliminate 'comparing signed/unsigned values' lcc warning in add_chunk_as
* Fix 'undefined reference to AO_pt_lock' if configure is using clang-16
* Fix 'undefined reference to
Please review this set of changes for nanbield and have comments back by
end of day Tuesday, January 30
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6501
with the exception of a known autobuilder intermittent error on qemumips-tc:
Current include logic goes into generic arm v8/v9 architecture tunes and
adds corresponding -march option after synthesizing it from various tune
fragments, this is fine for a machine which is using armv8/armv9 based
tunes but cortex tunes are intentionally using -mcpu option based on
selected
The pid file can disappear when qemu is shutting down leading to a
file not found race before it is read.
Tweak the code to handle this and fix a rare but annoying race error
case.
[YOCTO #15036]
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/utils/qemurunner.py | 8 ++--
1 file changed,
Khem Raj escreveu (sexta, 26/01/2024 à(s) 17:58):
> On Fri, Jan 26, 2024 at 8:24 AM Jose Quaresma
> wrote:
> >
> >
> >
> > Alexander Kanavin escreveu (sexta, 26/01/2024
> à(s) 16:10):
> >>
> >> Hello Jose,
> >>
> >> there was a 1.21 update earlier, what happened to that?
> >
> >
> > Hi Alex,
>
On Fri, 2024-01-26 at 20:41 +, Ross Burton wrote:
> Hi,
>
> A somewhat recurring theme about this time in the release cycle is
> people asking what version of a recipe will be in the next release,
> especially more now because the next release is a LTS.
>
> So to avoid the relevant people
Hi,
A somewhat recurring theme about this time in the release cycle is people
asking what version of a recipe will be in the next release, especially more
now because the next release is a LTS.
So to avoid the relevant people repeating themselves, I’ve created a wiki page:
Adds bitbake variable to set additional mount flags for the /var/lib
overlayfs or bind mount when using a read-only root filesystem. This
can be used to set additional options like "-o nodev".
Signed-off-by: Colin McAllister
---
.../initscripts/initscripts-1.0/read-only-rootfs-hook.sh | 4
On Fri, Jan 26, 2024 at 4:46 AM Robert P. J. Day wrote:
>
>
> i've been trying to put together a really basic example of a recipe
> using "externalsrc" that refers to some local source, and cannot get
> it to work. so here's what i'm trying.
>
> as a demo, i selected a random simple OE recipe
I'll have a look at this early next week!
Bruce
On Fri, Jan 26, 2024 at 11:45 AM Alexandre Belloni
wrote:
>
> Hello Bruce,
>
> I'm not sur this has been reported yet, we are seeing those warnings for
> beaglebone:
>
>
On Fri, Jan 26, 2024 at 8:24 AM Jose Quaresma wrote:
>
>
>
> Alexander Kanavin escreveu (sexta, 26/01/2024 à(s)
> 16:10):
>>
>> Hello Jose,
>>
>> there was a 1.21 update earlier, what happened to that?
>
>
> Hi Alex,
>
> I know and I've already done some work on this but unfortunately there are
On Fri, 2024-01-26 at 16:18 +0200, Mikko Rapeli wrote:
> Hi,
>
> On Fri, Jan 26, 2024 at 02:04:18PM +, Joakim Tjernlund via
> lists.openembedded.org wrote:
> > On Fri, 2024-01-26 at 14:33 +0100, Alexander Kanavin via
> > lists.openembedded.org wrote:
> > > On Fri, 26 Jan 2024 at 14:21,
I like the idea of this patch (hardcoding behaviour is bad), but I think it
could be generalised some more.
> On 6 Dec 2023, at 16:03, Jonathan GUILLOT via lists.openembedded.org
> wrote:
> -localedir = os.path.join(dvar + datadir, 'locale')
> +localedirs = [os.path.join(dvar +
On Fri, 2024-01-19 at 14:19 +0800, Jamin Lin via lists.openembedded.org
wrote:
> Currently, u-boot FIT image only support to load u-boot image.
> To support optee-os and trusted-firmware-a, update ITS file generation
> scripts, so users are able to use u-boot FIT image to load
> u-boot, optee-os
Hello Bruce,
I'm not sur this has been reported yet, we are seeing those warnings for
beaglebone:
https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/8541/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/7446/steps/12/logs/stdio
On
Alexander Kanavin escreveu (sexta, 26/01/2024 à(s)
16:10):
> Hello Jose,
>
> there was a 1.21 update earlier, what happened to that?
>
Hi Alex,
I know and I've already done some work on this but unfortunately there are
runtime problems.
From: Ross Burton
Signed-off-by: Ross Burton
---
meta/conf/sanity.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/sanity.conf b/meta/conf/sanity.conf
index 435455d9fb4..c3e6c5179c6 100644
--- a/meta/conf/sanity.conf
+++ b/meta/conf/sanity.conf
@@ -3,7 +3,7 @@
Hello Jose,
there was a 1.21 update earlier, what happened to that?
Alex
On Fri, 26 Jan 2024 at 17:06, Jose Quaresma wrote:
>
> Upgrade to latest 1.20.x release [1]:
>
> $ git log --oneline go1.20.12..go1.20.13
> a95136a88c (tag: go1.20.13) [release-branch.go1.20] go1.20.13
> 5c38c04957
Upgrade to latest 1.20.x release [1]:
$ git log --oneline go1.20.12..go1.20.13
a95136a88c (tag: go1.20.13) [release-branch.go1.20] go1.20.13
5c38c04957 [release-branch.go1.20] crypto/tls: align FIPS-only mode with
BoringSSL policy
9e4abed39b [release-branch.go1.20] crypto/internal/boring:
They're forbidden in selftests as a whole, for other reasons. You can
probably find the reasons out via git blame.
Alex
On Fri, 26 Jan 2024 at 16:14, Joakim Tjernlund
wrote:
>
> On Fri, 2024-01-26 at 15:55 +0100, Alexander Kanavin wrote:
> > On Fri, 26 Jan 2024 at 15:52, Joakim Tjernlund
> >
On Fri, 2024-01-26 at 15:55 +0100, Alexander Kanavin wrote:
> On Fri, 26 Jan 2024 at 15:52, Joakim Tjernlund
> wrote:
> > A thought just occurred to me, these vars(SANITY_TESTED_DISTROS,
> > buildhistory etc.),
> > do they need to be off in the original machine when building up the SSTATE ?
> >
On Fri, 2024-01-26 at 16:00 +0100, Alexander Kanavin wrote:
> On Fri, 26 Jan 2024 at 15:54, Richard Purdie
> wrote:
>
> > > +def test_devtool_modify_git_no_extract(self):
> > > +# Check preconditions
> > > +testrecipe = 'psplash'
> > > +src_uri = get_bb_var('SRC_URI',
On Fri, 26 Jan 2024 at 15:54, Richard Purdie
wrote:
> > +def test_devtool_modify_git_no_extract(self):
> > +# Check preconditions
> > +testrecipe = 'psplash'
> > +src_uri = get_bb_var('SRC_URI', testrecipe)
> > +self.assertIn('git://', src_uri, 'This test
On Fri, 26 Jan 2024 at 15:52, Joakim Tjernlund
wrote:
> A thought just occurred to me, these vars(SANITY_TESTED_DISTROS, buildhistory
> etc.),
> do they need to be off in the original machine when building up the SSTATE ?
> I figured they just needed to be off for the repro build(in -st dir)
On Mon, 2024-01-22 at 13:29 +0800, Chen Qi via lists.openembedded.org
wrote:
> From: Chen Qi
>
> Add a test case to ensure the following error does not happen again for
> 'devtool modify -n'.
>
> Traceback (most recent call last):
> File "/buildarea2/chenqi/poky/scripts/devtool", line 349, in
On Fri, 2024-01-26 at 14:33 +0100, Alexander Kanavin via lists.openembedded.org
wrote:
> On Fri, 26 Jan 2024 at 14:21, Joakim Tjernlund
> wrote:
> > I will try workaround these somehow but will not go so far as creating a
> > new MACHINE just to
> > run these tests.
>
> Why would you need a
Hello,
This causes oe-selftest failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/6342/steps/15/logs/stdio
2024-01-25 02:21:53,130 - oe-selftest - INFO - RESULTS -
runqemu.RunqemuTests.test_boot_machine_slirp_qcow2: ERROR (1028.13s)
2024-01-25 02:21:53,131 -
On Fri, 26 Jan 2024 at 15:11, Richard Purdie
wrote:
>
> On Fri, 2024-01-26 at 14:34 +0100, Alexander Kanavin wrote:
> > Discovery of the test file was happening in a class initializer.
> > That block of code cannot fail (it's not a test), and so it
> > falls through to completion even if the
From: Khem Raj
Backport a patch to fix
| ../git/util.cxx:1766:56: error: 'std::pointer_to_unary_function<_Arg,
_Result> std::ptr_fun(_Result (*)(_Arg)) [with _Arg = int; _Result = int]' is
deprecated: use 'std::function' instea
d [-Werror=deprecated-declarations]
| 1766 |
From: virendra thakur
In the case of a zero length string being returned by fgets(), the condition
checking for a trailing new line would perform a bad memory access outside
of `buf`. This might happen when line with a leading null byte is read.
Avoid this case by checking that the string has a
From: Vijay Anusuri
Fix below CVE's
CVE-2023-6816
CVE-2024-0229
CVE-2024-21885
CVE-2024-21886
CVE-2024-0408
CVE-2024-0409
Signed-off-by: Vijay Anusuri
Signed-off-by: Steve Sakoman
---
.../xserver-xorg/CVE-2023-6816.patch | 55 +
.../xserver-xorg/CVE-2024-0229-1.patch|
From: Vijay Anusuri
Upstream-Status: Backport from
https://github.com/linux-pam/linux-pam/commit/031bb5a5d0d950253b68138b498dc93be69a64cb
Signed-off-by: Vijay Anusuri
Signed-off-by: Steve Sakoman
---
.../pam/libpam/CVE-2024-22365.patch | 59 +++
From: Vijay Anusuri
CVE-2024-0553
A vulnerability was found in GnuTLS. The response times to malformed
ciphertexts in RSA-PSK ClientKeyExchange differ from response times of
ciphertexts with correct PKCS#1 v1.5 padding. This issue may allow a remote
attacker to perform a timing side-channel
From: Vijay Anusuri
Upstream-Status: Backport [import from ubuntu
https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/gnutls28/3.6.13-2ubuntu1.9/gnutls28_3.6.13-2ubuntu1.9.debian.tar.xz
Upstream-Commit:
https://gitlab.com/gnutls/gnutls/-/commit/29d6298d0b04cfff970b993915db71ba3f580b6d]
From: Vijay Anusuri
Backport https://sqlite.org/src/info/0e4e7a05c4204b47
Signed-off-by: Vijay Anusuri
Signed-off-by: Steve Sakoman
---
.../sqlite/files/CVE-2023-7104.patch | 46 +++
meta/recipes-support/sqlite/sqlite3_3.31.1.bb | 1 +
2 files changed, 47
From: Ranjitsinh Rathod
OS command injection might occur if a user name or host name has shell
metacharacters, and this name is referenced by an expansion token in
certain situations. For example, an untrusted Git repository can have a
submodule with shell metacharacters in a user name or host
Please review this set of changes for dunfell and have comments back by
end of day Tuesday, January 30
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6495
The following changes since commit 82e67bd9c77f0c5cbb652ca91071b9e57bdcfb33:
Hi,
On Fri, Jan 26, 2024 at 02:04:18PM +, Joakim Tjernlund via
lists.openembedded.org wrote:
> On Fri, 2024-01-26 at 14:33 +0100, Alexander Kanavin via
> lists.openembedded.org wrote:
> > On Fri, 26 Jan 2024 at 14:21, Joakim Tjernlund
> > wrote:
> > > I will try workaround these somehow
On Fri, 2024-01-26 at 14:34 +0100, Alexander Kanavin wrote:
> Discovery of the test file was happening in a class initializer.
> That block of code cannot fail (it's not a test), and so it
> falls through to completion even if the needed file could not be found.
Is that true? I thought a failure
Add a work around for segfaults we're seeing with qemu 8.2.0 when
compiling webkitgtk on debian 11 autobuilder workers.
The issue has been reported upstream to work out an official fix.
[YOCTO #15367]
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
On Fri, 2024-01-26 at 14:33 +0100, Alexander Kanavin via lists.openembedded.org
wrote:
> On Fri, 26 Jan 2024 at 14:21, Joakim Tjernlund
> wrote:
> > I will try workaround these somehow but will not go so far as creating a
> > new MACHINE just to
> > run these tests.
>
> Why would you need a
This was supposed to always be the case from upstream but was exposed
by the 64-bit-time QA checker when file function scanning was enabled.
Signed-off-by: Ola x Nilsson
---
...le-fallocate-on-32-bit-linux-platfor.patch | 51 +++
.../python/python3-numpy_1.26.3.bb|
Upstream has replaced autoconf with cmake, which necessitates a rewrite of the
recipe and available options, and a rebase to cmake of
0001-Do-not-hardcode-lib-rpm-as-the-installation-path-for.patch
Correct a mistake in 0001-Do-not-read-config-files-from-HOME.patch :
the patch was removing the
Discovery of the test file was happening in a class initializer.
That block of code cannot fail (it's not a test), and so it
falls through to completion even if the needed file could not be found.
Then the tests themselves fail later due to class variables not
being set, but all information as to
rpm 4.19 automatically generates provides and depends for user and
groups:
https://github.com/rpm-software-management/rpm/blob/rpm-4.19.x/docs/manual/users_and_groups.md#dependencies
This mechanism relies on sysusers.d for the 'provides'
part, and thus is systemd-only at best. So we need to
Since
https://github.com/rpm-software-management/rpm/commit/f3eaeeb7341085e1850e914350cf1f33d538320d
rpm does its own parsing of /etc/passwd and /etc/group instead of relying on
getpwnam() and friends.
This has an unfortunate effect of leaking build host uid/gid values for users
and groups
Otherwise, PACKAGE_WRITE_DEPS would contain non-multilib variants
of dependencies even when building multilib items, resulting in
sysroots being populated with entirely wrong versions of them.
This hasn't been noticed until now through sheer (bad) luck, I think,
except in the cpio recipe, but the
Per
https://github.com/rpm-software-management/rpm/commit/77d3529c31ca090a40b8d3959a0bcdd721a556d6
rpm 4.19.1+ will not consider actual filesystem permissions and ownership, and
will quietly default
to root if not expictly set otherwise in .spec file.
There's also additional diagnostics
This particularly helps with user management postinsts as otherwise
there's no trace left of what was run, in which order, and what was the output.
Here's an example from the logs:
NOTE: Running postinst
This exposes the following failure in a multilib setup, when everything
up to do_package_write_rpm is in sstate, but do_package_write_rpm is not
(there's a similar fail for lib64-man-db, and the failures themselves will be
fixed separately
in the next commit):
Exception:
On Fri, 26 Jan 2024 at 14:21, Joakim Tjernlund
wrote:
> I will try workaround these somehow but will not go so far as creating a new
> MACHINE just to
> run these tests.
Why would you need a new machine? You only need a new configuration
template in addition to existing one (e.g.
On Fri, 2024-01-26 at 13:18 +0100, Alexander Kanavin wrote:
> On Fri, 26 Jan 2024 at 12:09, Joakim Tjernlund via
> lists.openembedded.org
> wrote:
> > These are hardcoded settings too of which some could need need tewaking,
> > DISTRO_FEATURES for sure.
> >
> > So reproducible builds does not
On Fri, 26 Jan 2024, Alexander Kanavin wrote:
> Note that there is a selftest for this in
> meta/lib/oeqa/selftest/cases/externalsrc.py, so you could check why
> that seems to work.
>
> Alex
ah, i had forgotten about the directory of selftests. my bad.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You
Note that there is a selftest for this in
meta/lib/oeqa/selftest/cases/externalsrc.py, so you could check why
that seems to work.
Alex
On Fri, 26 Jan 2024 at 13:47, Robert P. J. Day wrote:
>
>
> i've been trying to put together a really basic example of a recipe
> using "externalsrc" that
i've been trying to put together a really basic example of a recipe
using "externalsrc" that refers to some local source, and cannot get
it to work. so here's what i'm trying.
as a demo, i selected a random simple OE recipe -- in this case,
"dmidecode", whose recipe you can see here (and
On Fri, 26 Jan 2024 at 12:09, Joakim Tjernlund via
lists.openembedded.org
wrote:
> These are hardcoded settings too of which some could need need tewaking,
> DISTRO_FEATURES for sure.
>
> So reproducible builds does not seem usable outside poky or am I missing
> something here ?
That is not
On Fri, Jan 26, 2024 at 12:14 PM Böszörményi Zoltán
wrote:
> 2024. 01. 26. 11:53 keltezéssel, Martin Jansa írta:
> > > I copied vercmp_string_op() and all others called by it from
> bitbake/lib/bb/utils.py
> > into a new python script.
> >
> > It's not an issue in vercmp_string_op itself,
>
> I
2024. 01. 26. 12:14 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org
írta:
2024. 01. 26. 11:53 keltezéssel, Martin Jansa írta:
> I copied vercmp_string_op() and all others called by it from bitbake/lib/bb/utils.py
into a new python script.
It's not an issue in vercmp_string_op
2024. 01. 26. 11:53 keltezéssel, Martin Jansa írta:
> I copied vercmp_string_op() and all others called by it from bitbake/lib/bb/utils.py
into a new python script.
It's not an issue in vercmp_string_op itself,
I already know this.
Apparently you haven't read my mail fully for the
In poky/meta/lib/oeqa/selftest/context.py there is:
if "buildhistory.bbclass" in self.tc.td["BBINCLUDED"]:
self.tc.logger.error("You have buildhistory enabled already and
this isn't recommended for selftest, please disable it first.")
raise OEQAPreRun
if
See
https://git.openembedded.org/meta-openembedded/commit/?h=kirkstone=8a042b540db5421785edcf21d5114be6358246fd
On Fri, Jan 26, 2024 at 11:53 AM Martin Jansa
wrote:
> > I copied vercmp_string_op() and all others called by it from
> bitbake/lib/bb/utils.py into a new python script.
>
> It's not
> I copied vercmp_string_op() and all others called by it from
bitbake/lib/bb/utils.py into a new python script.
It's not an issue in vercmp_string_op itself, but the version value it gets
from waf --version isn't just the version itself but also SyntaxWarning
from waf.
So you need to update waf
Hi,
Just a FYI.
After the bitbake-server getting stuck after bitbake exited
with Python 3.12 issue was fixed, here's another one.
This time it's semi-reliably triggered by the jack recipe
in meta-openembedded:
ERROR: jack-1.19.22-r0 do_configure: Error executing a python function in
On 1/25/24 17:29, 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.
On Thu, 25 Jan 2024 at 10:25, Yu, Mingli wrote:
From: Mingli Yu
Correct the PV
86 matches
Mail list logo
