[OE-Core][langdale][PATCH] sysstat: upgrade to 12.6.1

2022-11-18 Thread Xiangyu Chen
This small version fixes several bugs, one of which has been the object of a security advisory (CVE-2022-39377). Signed-off-by: Xiangyu Chen --- .../sysstat/{sysstat_12.6.0.bb => sysstat_12.6.1.bb}| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

Re: [OE-core] [langdale][master][PATCH] rust: Do not use default compiler flags defined in CC crate

2022-11-18 Thread Peter Kjellerstedt
> -Original Message- > From: openembedded-core@lists.openembedded.org > On Behalf Of Richard Purdie > Sent: den 18 november 2022 17:36 > To: Anton Antonov ; > openembedded-core@lists.openembedded.org > Subject: Re: [OE-core] [langdale][master][PATCH] rust: Do not use default > compiler

[OE-core] [PATCH 15/15] linux-yocto/5.19: fix elfutils run-backtrace-native-core ptest failure

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield The following commit was integrated into the 5.19.15 -stable series and breaks the elfutils backtrace ptests. don't use __kernel_write() on kmap_local_page() It could be that other commits are also required in -stable, but a revert is the easiest way to deal with the

[OE-core] [PATCH 12/15] linux-yocto/5.15: update to v5.15.78

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Updating to the latest korg -stable release that comprises the following commits: 509a32764e1a Linux 5.15.78 7038af4ce951 wifi: brcmfmac: Fix potential buffer overflow in brcmf_fweh_event_worker() b66617cc3c2f drm/i915/sdvo: Setup DDC fully before output init

[OE-core] [PATCH 13/15] linux-yocto/5.19: fix CONFIG_CRYPTO_CCM mismatch warnings

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Integrating the following commit(s) to linux-yocto/.: 0cba9aa4044 qat: fix CONFIG_CRYPTO_CCM mismatch warnings Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_5.19.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_5.19.bb | 2 +-

[OE-core] [PATCH 14/15] linux-yocto/5.15: fix CONFIG_CRYPTO_CCM mismatch warnings

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Integrating the following commit(s) to linux-yocto/.: f475b1a9ded qat: fix CONFIG_CRYPTO_CCM mismatch warnings Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb | 2 +-

[OE-core] [PATCH 11/15] linux-yocto/5.19: security.cfg: remove configs which have been dropped

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Integrating the following commit(s) to linux-yocto/.: 5e122351f62 security.cfg: remove configs which have been dropped Signed-off-by: Bruce Ashfield --- .../linux/linux-yocto-rt_5.19.bb | 4 ++-- .../linux/linux-yocto-tiny_5.19.bb| 4 ++--

[OE-core] [PATCH 10/15] lttng-modules: fix build for v6.1+

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Backporting a patch from the lttng git repository to address a build failure when the 6.1-dev kernel is used. Signed-off-by: Bruce Ashfield --- ...on-drop-kmem_alloc-avoid-dereferenci.patch | 278 ++ .../lttng/lttng-modules_2.13.7.bb | 1 + 2

[OE-core] [PATCH 08/15] linux-yocto-dev: bump to v6.1

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield v6.1 is available, and could likely be the next LTS kernel, so we bump our -dev kernel to start testing with this version. Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[OE-core] [PATCH 09/15] kernel-devsrc: fix for v6.1+

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield The 6.1 kernel has a number of Kbuild and architecture changes that required us to update our devsrc recipe. With these changes we are once again able to build on target modules for all supported archectures. Signed-off-by: Bruce Ashfield ---

[OE-core] [PATCH 05/15] linux-yocto/5.15: update to v5.15.76

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Updating to the latest korg -stable release that comprises the following commits: 4f5365f77018 Linux 5.15.76 33fc9e26b7cb mm: /proc/pid/smaps_rollup: fix no vma's null-deref b9d8cbe90a0f mmc: core: Add SD card quirk for broken discard 0ee2f0567a56

[OE-core] [PATCH 04/15] linux-yocto/5.19: update to v5.19.17

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Updating to the latest korg -stable release that comprises the following commits: 2b525314c7b5 Linux 5.19.17 65ea3311ce7c drm/i915/bios: Use hardcoded fp_timing size for generating LFP data pointers a34bc0ff223f drm/i915/bios: Validate fp_timing terminator

[OE-core] [PATCH 07/15] kern-tools: integrate ZFS speedup patch

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Bumping the SRCREV to integrat the following kern-tools change: commit 2d01f24bc78256c709728eb3f204491bce13e0e5 Author: Volodymyr Babchuk Date: Fri Nov 4 23:32:38 2022 + kconf_check: store some files in tmpdir Some file systems, like ZFS, are

[OE-core] [PATCH 06/15] linux-yocto/5.19: cfg: intel and vesa updates

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Integrating the following commit(s) to linux-yocto/.: 399055aee2f vesafb.cfg: rename FB_BOOT_VESA_SUPPORT -> BOOT_VESA_SUPPORT fe0fe0945fb media-radio.cfg: switch RADIO_ADAPTERS from y to m 9724cfa270c bsp/common-pc-64 : add igc driver 39431755e59

[OE-core] [PATCH 03/15] linux-yocto/5.15: update to v5.15.74

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Updating to the latest korg -stable release that comprises the following commits: a3f2f5ac9d61 Linux 5.15.74 de124365a7d2 wifi: mac80211: fix MBSSID parsing use-after-free 7d998f6b7365 mac80211: fix memory leaks with element parsing fee48f3bdd75 mac80211:

[OE-core] [PATCH 02/15] linux-yocto/5.19: update to v5.19.16

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Updating to the latest korg -stable release that comprises the following commits: d235c2b1f470 Linux 5.19.16 279116cb0bc5 misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic d472808756b3 misc: pci_endpoint_test: Aggregate params checking

[OE-core] [PATCH 00/15][v2] kernel: consolidated pull request

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Richard, This is a resend of the 10 patches in my first pull request, with additional -stable and warning fixes on top. We need those extra patches to pickup the one of most interest: linux-yocto/5.19: fix elfutils run-backtrace-native-core ptest failure I was able to

[OE-core] [PATCH 01/15] linux-yocto-dev: bump to v6.0+

2022-11-18 Thread Bruce Ashfield
From: Bruce Ashfield Introducing the 6.0+ development kernel branches. These have been sanity tested on all supported architectures. Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[OE-core] useradd: shadow RDEPEND

2022-11-18 Thread Patrick Williams
Hello, It seems like ever since useradd.bbclass was written it added an RDEPEND on "shadow". See commit a82885db00956734922291d8a17eb135461204fa for an ancient reference. I'm wondering if this is really necessary? Recent commit 84efd72d48616405dbe4d73ec95917077144ed09 added systemd's udev to

Re: [OE-core] [PATCH 0/5] liburi-perl upgrade

2022-11-18 Thread Alexander Kanavin
On Fri, 18 Nov 2022 at 19:57, Tim Orling wrote: > So for ALL perl modules, we would need some other scheme for checking if the > author changed. For example: > https://metacpan.org/pod/URI This should work as UPSTREAM_CHECK_URI/REGEX, as long as the latest tarball is linked from it. Alex

Re: [OE-core] [PATCH 0/5] liburi-perl upgrade

2022-11-18 Thread Tim Orling
On Fri, Nov 18, 2022 at 10:35 AM Alexander Kanavin wrote: > On Fri, 18 Nov 2022 at 19:24, Tim Orling wrote: > >> I trust all of the affected recipes still pass 'devtool > >> check-upgrade-status'? AUH won't work if that is broken. > >> > > It doesn't matter when the author changes and CPAN

Re: [OE-core] [PATCH 0/5] liburi-perl upgrade

2022-11-18 Thread Alexander Kanavin
On Fri, 18 Nov 2022 at 19:24, Tim Orling wrote: >> I trust all of the affected recipes still pass 'devtool >> check-upgrade-status'? AUH won't work if that is broken. >> > It doesn't matter when the author changes and CPAN changes the URL out from > under us. Unless we figure out a different URL

Re: [OE-core] [PATCH 0/5] liburi-perl upgrade

2022-11-18 Thread Tim Orling
On Fri, Nov 18, 2022 at 9:59 AM Alexander Kanavin wrote: > I trust all of the affected recipes still pass 'devtool > check-upgrade-status'? AUH won't work if that is broken. > > It doesn't matter when the author changes and CPAN changes the URL out from under us. Unless we figure out a different

Re: [OE-core] [PATCH 0/5] liburi-perl upgrade

2022-11-18 Thread Alexander Kanavin
I trust all of the affected recipes still pass 'devtool check-upgrade-status'? AUH won't work if that is broken. Alex On Fri, 18 Nov 2022 at 18:52, Tim Orling wrote: > > AUH has been missing upgrades to liburi-perl because the author changed > back from ETHER to OALDERS, which changes the

[OE-core] [PATCH 5/5] liburi-perl: upgrade 5.08 -> 5.17

2022-11-18 Thread Tim Orling
* Author changed back from ETHER to OALDERS * Use CPAN_MIRROR for SRC_URI * Update HOMEPAGE * Update RPEPENDS for -ptest * Patch to skip TODO test cases For changes, see: https://metacpan.org/release/OALDERS/URI-5.17/changes License-Update: whitespace changes Signed-off-by: Tim Orling ---

[OE-core] [PATCH 4/5] libtest-warnings-perl: move from meta-perl

2022-11-18 Thread Tim Orling
liburi-perl in oe-core now RDEPENDS on libtest-warnings-perl for ptest * Update HOMEPAGE; fix syntax * Add SUMMARY * Add BUGTRACKER * Use CPAN_MIRROR for SRC_URI * Use actual LICENCE file for LIC_FILES_CHKSUM * Add RDEPENDS * Add RDEPENDS on perl-modules for ptest - Too many hidden dependencies

[OE-core] [PATCH 3/5] libtest-fatal-perl: add recipe for 0.016

2022-11-18 Thread Tim Orling
Test::Fatal - incredibly simple helpers for testing code with exceptions https://metacpan.org/release/RJBS/Test-Fatal-0.016 * Dependency for liburi-perl ptest. * Add self as maintainer * Add to ptest-packages.inc (fast) Signed-off-by: Tim Orling --- meta/conf/distro/include/maintainers.inc

[OE-core] [PATCH 2/5] libtry-tiny-perl: add recipe for 0.31

2022-11-18 Thread Tim Orling
Try::Tiny - Minimal try/catch with proper preservation of $@ https://metacpan.org/release/ETHER/Try-Tiny-0.31 * Dependency for libtest-fatal-perl * Add self as maintainer * Add to ptest-packagelists.inc (fast) Signed-off-by: Tim Orling --- meta/conf/distro/include/maintainers.inc | 1 +

[OE-core] [PATCH 1/5] mirrors.bbclass: update CPAN_MIRROR

2022-11-18 Thread Tim Orling
Both of these redirect to https://cpan.metacpan.org/: http://cpan.metacpan.org/ http://search.cpan.org/CPAN/ Signed-off-by: Tim Orling --- meta/classes-global/mirrors.bbclass | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta/classes-global/mirrors.bbclass

[OE-core] [PATCH 0/5] liburi-perl upgrade

2022-11-18 Thread Tim Orling
AUH has been missing upgrades to liburi-perl because the author changed back from ETHER to OALDERS, which changes the SRC_URI. In the mean time, the dependencies for -ptest have grown a little bit, so we add two new recipes and import one from meta-perl. While we are at it, correct the redirects

[v2][oe-core][kirkstone][PATCH 1/1] python3: advance to version 3.10.8

2022-11-18 Thread Joe Slater
Fixes CVE-2022-37460. Also add patch to fix CVE-2022-37454. Signed-off-by: Joe Slater --- .../python/python3/cve-2022-37454.patch | 108 ++ .../{python3_3.10.7.bb => python3_3.10.8.bb} | 4 +- 2 files changed, 110 insertions(+), 2 deletions(-) create mode 100644

[oe-core][PATCH 1/1] python3: Fix CVE-2022-37460

2022-11-18 Thread Joe Slater
Apply patch created after the release of 3.11.0. Signed-off-by: Joe Slater --- .../python/python3/cve-2022-37460.patch | 95 +++ .../recipes-devtools/python/python3_3.11.0.bb | 1 + 2 files changed, 96 insertions(+) create mode 100644

Re: [OE-core] [langdale][master][PATCH] rust: Do not use default compiler flags defined in CC crate

2022-11-18 Thread Anton Antonov
Hi Richard, I’ve already unsuccessfully tried all these combinations with both “if” and oe.utils.conditional. $ MACHINE=qemuarm bitbake rust-native -e |grep CRATE_CC_NO_DEFAULTS # $CRATE_CC_NO_DEFAULTS [3 operations] # [export] "${@1 if d.getVar('CRATE_CC_NO_DEFAULTS') == 'true' else 0}"

Re: [OE-core] [langdale][master][PATCH] rust: Do not use default compiler flags defined in CC crate

2022-11-18 Thread Richard Purdie
On Fri, 2022-11-18 at 16:21 +, Anton Antonov wrote: >   I’ve tested your approach. It doesn’t work for whatever reason. > CRATE_CC_NO_DEFAULTS is empty exported for native recipes: > > $ MACHINE=qemuarm bitbake rust-native -e |grep CRATE_CC_NO_DEFAULTS > # $CRATE_CC_NO_DEFAULTS [3 operations]

Re: [OE-core] [PATCH v3 1/2] qemurunner.py: support setting slirp host IP address

2022-11-18 Thread Quentin Schulz via lists.openembedded.org
Hi Mikko, On 11/18/22 17:08, Mikko Rapeli wrote: By default host side IP address is not set and qemu listens on all IP addresses on the host machine which is not a good idea when images have root login enabled without password. It make sense to listen only on localhost IP address 127.0.0.1

Re: [OE-core] [langdale][master][PATCH] rust: Do not use default compiler flags defined in CC crate

2022-11-18 Thread Anton Antonov
Hi Richard, I’ve tested your approach. It doesn’t work for whatever reason. CRATE_CC_NO_DEFAULTS is empty exported for native recipes: $ MACHINE=qemuarm bitbake rust-native -e |grep CRATE_CC_NO_DEFAULTS # $CRATE_CC_NO_DEFAULTS [3 operations] # [export] "${'1' if

Re: [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests

2022-11-18 Thread Richard Purdie
On Fri, 2022-11-18 at 17:57 +0200, Mikko Rapeli wrote: > On Fri, Nov 18, 2022 at 03:04:29PM +, Richard Purdie wrote: > > > My concern is having multiple different file formats and data streams. > > It means we no longer have one definitive data mechanism but two, then > > the argument for

Re: [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests

2022-11-18 Thread Mikko Rapeli
Hi, On Fri, Nov 18, 2022 at 04:04:01PM +, Richard Purdie wrote: > On Fri, 2022-11-18 at 17:57 +0200, Mikko Rapeli wrote: > > Additionally I'm currently interested in kirkstone LTS branch so would like > > any changes to be there too... > > The idea is that we develop things in master, then

[OE-core] [PATCH v2 2/2] oeqa parselogs.py: use get_data() to fetch image specific error list

2022-11-18 Thread Mikko Rapeli
Runtime oeqa test parselogs.py checks dmesg output for errors. It has hard coded machine specific exceptions for errors which can be ignored. To re-use of this test on other machine targets and images, use get_data() function to get the list of error strings to ignore "ignore_errors" from image

[OE-core] [PATCH v2 1/2] oeqa: add utils/data.py with get_data() function

2022-11-18 Thread Mikko Rapeli
get_data() uses oeqa test method name and an optional key to get data from image specific "testimage_data.json" file located in image deploy directory. Image recipes can provide custom versions of this file which configures generic tests for a specific image when testing with testimage.bbclass

[OE-core] [PATCH v3 2/2] runqemu: limit slirp host port forwarding to localhost 127.0.0.1

2022-11-18 Thread Mikko Rapeli
With default slirp port forwarding config qemu listens on TCP ports and 2323 on all IP addresses available on the build host. Most use cases with runqemu only need it for localhost and it is not safe to run qemu images with root login without password enabled and listening on all available,

[OE-core] [PATCH v3 1/2] qemurunner.py: support setting slirp host IP address

2022-11-18 Thread Mikko Rapeli
By default host side IP address is not set and qemu listens on all IP addresses on the host machine which is not a good idea when images have root login enabled without password. It make sense to listen only on localhost IP address 127.0.0.1 using config change like: QB_SLIRP_OPT = "-netdev

Re: [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests

2022-11-18 Thread Richard Purdie
On Fri, 2022-11-18 at 17:57 +0200, Mikko Rapeli wrote: > Additionally I'm currently interested in kirkstone LTS branch so would like > any changes to be there too... The idea is that we develop things in master, then they become available in the next LTS release, not the previous one. People

Re: [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests

2022-11-18 Thread Mikko Rapeli
On Fri, Nov 18, 2022 at 03:04:29PM +, Richard Purdie wrote: > On Fri, 2022-11-18 at 16:32 +0200, Mikko Rapeli wrote: > > Hi, > > > > On Thu, Nov 17, 2022 at 04:57:36PM +, Richard Purdie wrote: > > > On Thu, 2022-11-17 at 17:39 +0200, Mikko Rapeli wrote: > > > > Hi, > > > > > > > > On

Re: [OE-core] [langdale][master][PATCH] rust: Do not use default compiler flags defined in CC crate

2022-11-18 Thread Anton Antonov
Hi Richard, Thank you for the suggestion. I was wondering how I can conditionally export a variable without updating a task. I will test and submit a new patch Anton -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#173467):

Re: [OE-core] [langdale][master][PATCH] rust: Do not use default compiler flags defined in CC crate

2022-11-18 Thread Richard Purdie
On Fri, 2022-11-18 at 14:42 +, Anton Antonov wrote: > Rust crates build dependecy C libraries using "CC" crate. > This crate adds some default compiler parameters depending on target arch. > For some target archs these parameters conflict with the parameters defined > by OE. > >

Re: [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests

2022-11-18 Thread Richard Purdie
On Fri, 2022-11-18 at 16:32 +0200, Mikko Rapeli wrote: > Hi, > > On Thu, Nov 17, 2022 at 04:57:36PM +, Richard Purdie wrote: > > On Thu, 2022-11-17 at 17:39 +0200, Mikko Rapeli wrote: > > > Hi, > > > > > > On Thu, Nov 17, 2022 at 03:17:43PM +, Richard Purdie wrote: > > > > On Thu,

Re: [OE-core][kirkstone][PATCH V2] local.conf.sample: correct the location of public hashserv

2022-11-18 Thread Steve Sakoman
This commit is already in kirkstone: https://git.yoctoproject.org/poky/commit/?h=kirkstone=24a3f7b3648185e33133f5d96b184a6cb6524f3d Steve On Fri, Nov 18, 2022 at 2:40 AM Ashish Sharma wrote: > > From: Alexander Kanavin > > Source: poky > MR: 121051 > Type: Integration > Disposition: Merged

[OE-core] [langdale][master][PATCH] rust: Do not use default compiler flags defined in CC crate

2022-11-18 Thread Anton Antonov
Rust crates build dependecy C libraries using "CC" crate. This crate adds some default compiler parameters depending on target arch. For some target archs these parameters conflict with the parameters defined by OE. Warnings/errors like this can be seen in the case: cc1: error: switch

Re: [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests

2022-11-18 Thread Mikko Rapeli
Hi, On Thu, Nov 17, 2022 at 04:57:36PM +, Richard Purdie wrote: > On Thu, 2022-11-17 at 17:39 +0200, Mikko Rapeli wrote: > > Hi, > > > > On Thu, Nov 17, 2022 at 03:17:43PM +, Richard Purdie wrote: > > > On Thu, 2022-11-17 at 09:12 +0200, Mikko Rapeli wrote: > > > > Many runtime tests

Re: [OE-core][master][kirkstone][PATCH V2] kernel.bbclass: make KERNEL_DEBUG_TIMESTAMPS work at rebuild

2022-11-18 Thread Chen Qi
Hi Jose, Thanks a lot for your review. I’d like to explain the case in more details. * indeterministic (not reproducible) issue The use case is: the user wants to disable reproducible build for kernel, and wants to get the actual build time of kernel. In other words, we want it to be

[OE-core][master][kirkstone][PATCH] dhcpcd: fix to work with systemd

2022-11-18 Thread Chen Qi
Currently, dhcpcd does not work well with systemd. When using dhcpcd to configure network, the /etc/resolv.conf contents are not correct. This issue could easily be reproduced by using 'qemu + slirp' to start a systemd based image and using dhcpcd to configure network. The expected 'nameserver

[OE-core] [PATCH] oeqa/qemurunner: implement vmdk images support

2022-11-18 Thread Sergey Zhmylev
From: Sergei Zhmylev Qemurunner should not pass rootfs to runqemu in case rootfs is not a filesystem itself. Some images could be built into some disk format like vmdk and this commit makes qemurunner handle such images properly. Signed-off-by: Sergei Zhmylev ---

Re: [OE-core] [PATCH] blktrace: ask for python3 specifically

2022-11-18 Thread Markus Volk
Am Fr, 18. Nov 2022 um 13:36:17 +0100 schrieb Alexander Kanavin : I'd rather force everyone to patch their 2.x scripts to ask for python2. Should anybody still promise Python2 support? I know, reality is still different, but since it is meanwhile unsupported, my idea would rather be to put

[OE-core] [PATCH 2/2] linux-firmware: add new fw file to ${PN}-qcom-adreno-a530

2022-11-18 Thread Dmitry Baryshkov
Extend the linux-firmware-qcom-adreno-a530 package with the squashed Adreno 530 zap shader. Signed-off-by: Dmitry Baryshkov --- meta/recipes-kernel/linux-firmware/linux-firmware_20221109.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 1/2] linux-firmware: upgrade 20221012 -> 20221109

2022-11-18 Thread Dmitry Baryshkov
From: Dmitry Baryshkov License-Update: additional files Signed-off-by: Dmitry Baryshkov --- ...{linux-firmware_20221012.bb => linux-firmware_20221109.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-kernel/linux-firmware/{linux-firmware_20221012.bb =>

Re: [OE-core] [PATCH] blktrace: ask for python3 specifically

2022-11-18 Thread Alexander Kanavin
On Fri, 18 Nov 2022 at 13:21, Markus Volk wrote: > I am tempted to turn this into a patch :-) But imagine all the complaints > this is going to receive. > > > Maybe it would be possible to use a DISTRO_FEATURE 'python2' and make the > creation of the python3 symlink dependent on it? This way

Re: [OE-core] [PATCH] blktrace: ask for python3 specifically

2022-11-18 Thread Markus Volk
Am Do, 17. Nov 2022 um 16:49:01 +0100 schrieb Alexander Kanavin : I am tempted to turn this into a patch :-) But imagine all the complaints this is going to receive. Maybe it would be possible to use a DISTRO_FEATURE 'python2' and make the creation of the python3 symlink dependent on it? This

Re: [OE-core][master][kirkstone][PATCH V2] kernel.bbclass: make KERNEL_DEBUG_TIMESTAMPS work at rebuild

2022-11-18 Thread Jose Quaresma
Chen Qi escreveu no dia quinta, 17/11/2022 à(s) 04:12: > Currently, the KERNEL_DEBUG_TIMESTAMPS is not working as expected > at rebuild. That is, even if we set it to "1", the kernel build time > is not changed. The problem could be reproduced by the following steps. > 1. bitbake

[OE-core][dunfell][PATCH] vim: upgrade 9.0.0614 -> 9.0.0820

2022-11-18 Thread Hugo Simeliere via lists.openembedded.org
From: Tim Orling Includes fixes for CVE-2022-3705 https://nvd.nist.gov/vuln/detail/CVE-2022-3705 For a short list of important changes, see: https://www.arp242.net/vimlog/ Signed-off-by: Tim Orling Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit

Re: [OE-Core][master][kirkstone][PATCH] rng-tools: backport patch to adjust jitterentropy library to timeout/fail on long delay

2022-11-18 Thread Xiangyu Chen
On 11/15/22 16:18, Xiangyu Chen wrote: Backport patch from upstream[1] to adjust jitter to timeout on init after 5 seconds in the event it takes to long to gether jitter entropy.This also fix rng-tools take full cpu usage with whole cores on ARM platforms. [1]