Re: [OE-core] make-mod-scripts doesn't know KERNEL_LOCALVERSION

On Thu, Jul 20, 2023 at 4:12 PM Bruce Ashfield via lists.openembedded.org wrote: > > On Thu, Jul 20, 2023 at 9:19 AM Bruce Ashfield via > lists.openembedded.org > wrote: > > > > On Thu, Jul 20, 2023 at 9:16 AM Petr Gotthard > > wrote: > > > > > > > My question was about CONFIG_LOCALVERSION_AUTO

[OE-core] [PATCH] kernel: make LOCALVERSION consistent between recipes

From: Bruce Ashfield The initial fix for localversion setting in 6.3+ broke older recipes and also broke recipes setting localversion in a kernel recipe, as make-mod-scripts (and other locations) can trigger a regeneration of files and don't have access to the variable. Moving the setting of

ODP: [OE-Core][PATCH v7][master-next 1/5] package_ipk.bbclass: add support for ACLs and xattr

Alexandre, Is it possible for you to create a docker file or some image etc. with all commands from autobuilder which will re-create the failure and pass it to me? Because can grope, find nothing and waste our time... Cheers, Piotr Od: Alexandre Belloni

Re: [OE-Core][PATCH v7][master-next 1/5] package_ipk.bbclass: add support for ACLs and xattr

I confirm this still fails on the autobuilders: This is a-full: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5631 On 21/07/2023 14:07:19+0200, Piotr Łobacz wrote: > Extend OPKGBUILDCMD variable, with additional parameters, depending > on target distro features, in order to

[OE-core][dunfell] openssl: fix intermittent openssl-ptest reproducibility issue

Adds two missing key sorts in generation of unified_info Backported from a similar (but more invasive) patch in the 3.x source code: https://github.com/openssl/openssl/commit/764cf5b26306a8712e8b3d41599c44dc5ed07a25] Signed-off-by: Steve Sakoman ---

Re: [oe-core][kirkstone][PATCH 1/1] bind: fix CVE-2023-2911

There is already a fix for this CVE in kirkstone: https://git.openembedded.org/openembedded-core/commit/?h=kirkstone=08810d3fe6988ea821805eca16105b4632335654 Steve On Thu, Jul 20, 2023 at 8:50 PM Urade, Yogita via lists.openembedded.org wrote: > If the `recursive-clients` quota is reached on

[OE-core] [mickledore][PATCH] go: fix CVE-2023-24531

Backport required commits to fix CVE-2023-24531. Signed-off-by: Sakib Sajal --- meta/recipes-devtools/go/go-1.20.5.inc| 2 + .../go/go/CVE-2023-24531_1.patch | 266 ++ .../go/go/CVE-2023-24531_2.patch | 47 3 files changed, 315

Re: [OE-core][PATCH v2] iproute2: upgrade 6.3.0 -> 6.4.0

Thanks! Alex On Fri 21. Jul 2023 at 15.48, Trevor Gamblin wrote: > Changelog: > https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/log/ > > Added a patch for including limits.h with musl builds, or else > we get failures such as: > > | mdb.c: In function 'mdb_parse_vni': > |

[OE-core][PATCH] git: upgrade 2.39.3 -> 2.41.0

Changelog for 2.41.0: https://github.com/git/git/blob/master/Documentation/RelNotes/2.41.0.txt Changelog for 2.40.0: https://github.com/git/git/blob/master/Documentation/RelNotes/2.40.0.txt git-add--interactive was removed in 2.40.0 in favor of git add -i, which caused the AUH upgrade failure

[OE-core] [nvd-news] Keyword and Keyword Exact Match Searches Temporarily Disabled

We might see some difficulties in the next days. Marta -- Forwarded message - From: nvd-news Date: Fri, Jul 21, 2023 at 5:57 PM Subject: [nvd-news] Keyword and Keyword Exact Match Searches Temporarily Disabled To: nvd-news *Keyword and Keyword Exact Match Searches Temporarily

[OE-core][PATCH v2] python3-dtc: add from meta-virtualization

This provides pylibfdt, which is a runtime dependency for the dtschema module that we already carry in oe-core. Signed-off-by: Trevor Gamblin --- v2 adds maintainer info to maintainers.inc. meta/conf/distro/include/maintainers.inc | 1 + ...erlay-make-overlay_get_target-public.patch |

Re: [OE-core] [PATCH 1/2] tunes: Add support for sve instructions on armv8/armv9

Hello Khem, On 12/07/2023 09:12:54-0700, Khem Raj wrote: > On Wed, Jul 12, 2023 at 3:29 AM Ross Burton wrote: > > > > On 11 Jul 2023, at 21:10, Khem Raj via lists.openembedded.org > > wrote: > > > > > > This helps in defining correct compiler options and configure options > > > for glibc and

Re: [OE-core][PATCH 2/3] python3-dtc: add from meta-virtualization

On 2023-07-21 10:15, Alexandre Belloni wrote: The following recipes do not have a maintainer assigned to them. Please add an entry to meta/conf/distro/include/maintainers.inc file. python3-dtc

[OE-core] [RFC v2 2/2] scripts/bblock: add a script to lock/unlock recipes

bblock script allows to lock/unlock recipes to latest signatures. The idea is to prevent some recipes to be rebuilt during development. For example when working on rust recipe, one may not want rust-native to be rebuilt. This tool can be used, with proper environment set up, using the following

[OE-core] [RFC v2 1/2] bitbake.conf: include bblock.conf

include conf/bblock.conf. This file is generated by the bblock tool. It locks some package tasks by fixing their signature. See bblock -h for more details Signed-off-by: Julien Stephan --- meta/conf/bitbake.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/conf/bitbake.conf

[OE-core] [RFC v2 0/2] Add bblock helper script

Hi all, This is the v2 of bblock script. Improvement from V1: * Signatures are now package architecture specific meaning that if you switch MACHINE, the lock sig will not be taken into account * I added the -r option to unlock recipes * I added a -d option to display the current bblock.conf *

Re: [OE-core] kirkstone boost upgrade?

thank you, Ross - will try. Cheers, Thomas Von: Ross Burton Gesendet: Freitag, 21. Juli 2023 13:42:02 An: Roos, Thomas Cc: Vyacheslav Yurkov; openembedded-core@lists.openembedded.org Betreff: RE: [EXTERNAL][OE-core] kirkstone boost upgrade? CAUTION: This email

Re: [OE-core][PATCH 2/3] python3-dtc: add from meta-virtualization

The following recipes do not have a maintainer assigned to them. Please add an entry to meta/conf/distro/include/maintainers.inc file. python3-dtc (/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/recipes-devtools/python/python3-dtc_1.6.1.bb) ;) On 17/07/2023 12:41:23-0400, Trevor

[OE-core][PATCH v2] iproute2: upgrade 6.3.0 -> 6.4.0

Changelog: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/log/ Added a patch for including limits.h with musl builds, or else we get failures such as: | mdb.c: In function 'mdb_parse_vni': | mdb.c:666:47: error: 'ULONG_MAX' undeclared (first use in this function) | 666 |

ODP: ODP: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro native features support

I haven't noticed due to rebasing:P nevertheless I have done it on top of master-next from openembedded-core and verified if patches apply on openembedded-core-contrib/abelloni/master-next and it works. Please check the latest v7 patchset release. Cheers, Piotr

[OE-Core][PATCH v7][master-next 3/5] opkg-utils: add acl and xattr support

Add support for tar archives created with --acls and/or --xattrs options, PAX header format. GNU tar and libarchive already supports ACLs and extended attributes. We can now add this support as well to opkg-build script in order to use fsetattr or setcap inside do_install command and end up with

[OE-Core][PATCH v7][master-next 5/5] opkg: set locale from system environment variables

A C program inherits its locale environment variables when it starts up. This happens automatically. However, these variables do not automatically control the locale used by the library functions, because ISO C says that all programs start by default in the standard ‘C’ locale. Fixes warnings:

[OE-Core][PATCH v7][master-next 2/5] package.bbclass: add support for ACLs and xattr

Extend `tar` command, with additional parameters, depending on choosen package class and target distro features, in order to support ACLs and xattr. Currently only `package_ipk` supports fully ACLs and xattr. Signed-off-by: Piotr Łobacz --- meta/classes-global/package.bbclass | 9 +++-- 1

[OE-Core][PATCH v7][master-next 4/5] opkg: add options to enable support for acl and xattr

The libarchive library, which is being used by opkg, supports ACLs and xattr already. More informations can be read at this link: https://github.com/libarchive/libarchive/pull/691 Signed-off-by: Piotr Łobacz --- ...-to-enable-support-for-acl-and-xattr.patch | 70 +++

[OE-Core][PATCH v7][master-next 1/5] package_ipk.bbclass: add support for ACLs and xattr

Extend OPKGBUILDCMD variable, with additional parameters, depending on target distro features, in order to support ACLs and xattr. With fix pushed to the opkg-devel: https://groups.google.com/g/opkg-devel/c/dYNHrLjDwg8 opkg-build is able to create tar archives with ACLs and xattr. Signed-off-by:

Re: ODP: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro native features support

On 21/07/2023 11:23:10+, Piotr Łobacz wrote: > OK do you want it to be on top of > openembedded-core-contrib/origin/abelloni/master-next or just > openembedded-core/master-next? Now that the opkg upgrade had been merged in master, you can rebase on top of master. >

Re: [OE-core] kirkstone boost upgrade?

On 21 Jul 2023, at 09:25, Thomas Roos via lists.openembedded.org wrote: > > Hi Vyacheslav, > I think it's this error: boost beast "Fixed WebSocket handshake response on > failure." > Fixed in 1.79. > My question was what is the policy of upgrading boost in an LTS branch? I > guess there is no

ODP: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro native features support

OK do you want it to be on top of openembedded-core-contrib/origin/abelloni/master-next or just openembedded-core/master-next? Od: openembedded-core@lists.openembedded.org w imieniu użytkownika Piotr Łobacz via lists.openembedded.org Wysłane: piątek, 21 lipca

[OE-core] [yocto][bitbake] variable expansion in files

Can confirm that no attempt or submission was made to merge meta-bitbake-variable-substitution into mainline/core. I'm happy if people are finding it useful, but it was written very much for my use case(s). I didn't spend much time designing it or thinking through how other people may prefer it to

[OE-Core][PATCH] scripts/resulttool: add mention about new detected tests

From: Alexis Lothoré Some regression reports show a lot of "PASSED->None" transitions. When such big lot of identical transitions are observed, it could be that tests are now failing, but it could also be that some tests has been renamed. To detect such case, add a log in regression report to

[OE-core] [PATCH] mdadm: add util-linux-blockdev ptest dependency

From: Ovidiu Panait 07revert-inplace test logs contain the following: func.sh: line 335: /sbin/blockdev: No such file or directory Add the missing util-linux-blockdev dependency. Signed-off-by: Ovidiu Panait --- meta/recipes-extended/mdadm/mdadm_4.2.bb | 9 - 1 file changed, 8

Re: [OE-core] [yocto][bitbake] variable expansion in files

On 21 Jul 2023, at 10:24, Yann CARDAILLAC via lists.openembedded.org wrote: > There's something that has always been missing in my experience of Yocto, > it's the ability to simply configure files with yocto variables. > > Basically the idea is to have a class that will automatically sed all

Re: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro native features support

Yes but within an hour? Wysyłane z aplikacji Outlook dla systemu iOS Od: Alexandre Belloni Wysłane: Friday, July 21, 2023 11:30:54 AM Do: Piotr Łobacz DW: openembedded-core@lists.openembedded.org Temat: Re: [OE-Core][PATCH v6 1/6]

Re: [OE-Core][PATCH v6 1/6] bitbake.conf: add acl and xattr distro native features support

Hello, I want to give this a shot again, can you rebase on top of my master-next branch ? On 19/07/2023 21:48:38+0200, Piotr Łobacz wrote: > Include support for ACLs and extended file attributes for native > builds, by default. > > Signed-off-by: Piotr Łobacz > --- > meta/conf/bitbake.conf |

[OE-core] [yocto][bitbake] variable expansion in files

Hi, There's something that has always been missing in my experience of Yocto, it's the ability to simply configure files with yocto variables. Basically the idea is to have a class that will automatically sed all variables from yocto inside a file using a delimiter, or to reuse the way it is

Re: [OE-core] [RFC PATCH 0/4] Bump Protobuf/gRPC

Hi Martin, On Thu, 20 Jul 2023 at 18:38, Martin Jansa wrote: > These patches should be sent to openembedded-devel not openembedded-core. > Sorry about that. I will send the next version in the correct ML > > ERROR: abseil-cpp-20230125.3-r0 do_package: Variable Requires: > absl_config =

[OE-core] [kirkstone][PATCH] package.bbclass: moving field data process before variable process in process_pkgconfig

From: Xiangyu Chen Currently, the latest version abseil-cpp contains a new library named "absl_log_internal_format", it's basic package config(.pc file) as below: prefix=/usr exec_prefix=${prefix} .. Requires: absl_config = 20230125, absl_core_headers = 20230125,

Re: [OE-core] kirkstone boost upgrade?

Hi Vyacheslav, I think it's this error: boost beast "Fixed WebSocket handshake response on failure." Fixed in 1.79. My question was what is the policy of upgrading boost in an LTS branch? I guess there is no change? I totally agree that there are breaking changes - I had experienced a lot in

Re: [OE-core] kirkstone boost upgrade?

For this purpose @LGE we're using meta-webos-backports layers for various backports we need as in: https://github.com/webosose/meta-webosose/tree/master/meta-webos-backports https://github.com/webosose/meta-webosose/commits/master/meta-webos-backports So we can easily just drop the layers

[OE-core] [PATCH] file: return wrapper to fix builds when file is in buildtools-tarball

From: Oleksandr Hnatiuk Wrapper that adds proper path to magic file was removed in 47db876d09d9a4394048579c21d0b394450ce681 in favor of environment-setup.d/file.sh which now contains `MAGIC` environment variable. This breaks builds that rely on external buildtools with `file` included in

Re: [OE-core] [meta][kirkstone][PATCH] json-c: disable -Werror for x86-64

Hi, On Thu, 20 Jul 2023 20:45:44 +0200 "Alexander Kanavin" wrote: > Also, does the issue occur on oe-core master? > I couldn't reproduce on amster. > Alex > > On Thu, 20 Jul 2023 at 20:44, Alexander Kanavin > wrote: > > > > This needs to be reported upstream and the ticket linked (ideally,

[oe-core][kirkstone][PATCH 1/1] bind: fix CVE-2023-2911

If the `recursive-clients` quota is reached on a BIND 9 resolver configured with both `stale-answer-enable yes;` and `stale-answer-client-timeout 0;`, a sequence of serve-stale-related lookups could cause `named` to loop and terminate unexpectedly due to a stack overflow. This issue affects BIND 9

Re: [OE-core] kirkstone boost upgrade?

On Friday, 21 July 2023, 06:49:24 CEST, Thomas Roos via lists.openembedded.org wrote: > Hi, > we are hitting an issue with boost version 1.78 and like to ask if and how > there is a boost upgrade on kirkstone branch? Another option: Yesterday there were two posts on the d...@yoctoproject.org

Re: [OE-core] kirkstone boost upgrade?

Hi Thomas, On Friday, 21 July 2023, 06:49:24 CEST, Thomas Roos via lists.openembedded.org wrote: > Hi, > we are hitting an issue with boost version 1.78 and like to ask if and how > there is a boost upgrade on kirkstone branch? I've a similar situation and decided to update boost by copying

Re: [OE-core] kirkstone boost upgrade?

I would be cautious with boost upgrade in stable branch. Boost is known for having breaking changes almost each new version. I only had a glance at 1.79-1.81 https://www.boost.org/users/history/ and there are a couple of them. Are you affected by some particular bug or vulnerability in 1.78?