[OE-core] [PATCH] python3-pyparsing: rdepends on python3-html

From: Kai Kang It fails to import python module 'pyparsing': | root@qemux86-64:~# python3 -c 'import pyparsing' | Traceback (most recent call last): | File "", line 1, in | File "/usr/lib64/python3.10/site-packages/pyparsing/__init__.py", line 141, in | from .helpers import * | File

[OE-core] [PATCH v2] dpkg: upgrade 1.21.1 -> 1.21.2

The following patches refreshed for new version: 0001-build.c-ignore-return-of-1-from-tar-cf.patch 0003-Our-pre-postinsts-expect-D-to-be-set-when-running-in.patch 0004-The-lutimes-function-doesn-t-work-properly-for-all-s.patch 0007-dpkg-deb-build.c-Remove-usage-of-clamp-mtime-in-tar.patch noman.pat

Re: [OE-core] [honister][PATCH] gcc: sanitizer: Fix tsan against glibc 2.34

> -Original Message- > From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Sundeep KOKKONDA > Sent: Tuesday, March 15, 2022 11:55 PM > To: openembedded-core@lists.openembedded.org > Cc: rwmacl...@gmail.com; umesh.kalap...@gmail.com; Sundeep KOKKONDA >

[OE-core][PATCH] mobile-broadband-provider-info: upgrade 20210805 -> 20220315

62e9fb81193c" -PV = "20210805" + +SRCREV = "4cbb44a9fe26aa6f0b28beb79f9488b37c097b5e" +PV = "20220315" PE = "1" -SRC_URI = "git://gitlab.gnome.org/GNOME/mobile-broadband-provider-info.git;protocol=https;branch=master" +SRC_URI = "git://g

[oe-core][PATCH 1/1] expect: modify fixline1 script

fixline1 needs to be processed by fixline1, but we short-circuit that. Enter the multi-line shebang which I am a bit queasy about, but expect loves it. Signed-off-by: Joe Slater --- .../expect/0001-fixline1-fix-line-1.patch | 31 +++ meta/recipes-devtools/expect/expect_5.45.

Re: [OE-core] [PATCH 1/2] create-spdx: Use function rather than AVAILABLE_LICENSES

On Tue, 2022-03-15 at 17:48 +, Peter Kjellerstedt wrote: > > -Original Message- > > From: openembedded-core@lists.openembedded.org > > On Behalf Of Richard Purdie > > Sent: den 15 mars 2022 18:33 > > To: openembedded-core@lists.openembedded.org > > Subject: [OE-core] [PATCH 1/2] create

Re: [OE-core] [PATCH 1/2] create-spdx: Use function rather than AVAILABLE_LICENSES

> -Original Message- > From: openembedded-core@lists.openembedded.org > On Behalf Of Richard Purdie > Sent: den 15 mars 2022 18:33 > To: openembedded-core@lists.openembedded.org > Subject: [OE-core] [PATCH 1/2] create-spdx: Use function rather than > AVAILABLE_LICENSES > > We can direct

[OE-core] [PATCH] license: Drop AVAILABLE_LICENSES

This variable is a performance liability and is highly dependent on which layers are added to the configuration which can cause signature issues for users. We have no users left in OE-Coreso remove it. Signed-off-by: Richard Purdie --- meta/classes/license.bbclass | 4 meta/conf/documentati

[OE-core] [PATCH 2/2] sstate: Allow optimisation of do_create_spdx task dependencies

do_create_spdx tasks don't need their dependencies so we can optimistion this as we do for some other tasks. Signed-off-by: Richard Purdie --- meta/classes/sstate.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass

[OE-core] [PATCH 1/2] create-spdx: Use function rather than AVAILABLE_LICENSES

We can directly call the function rather than using the variable indirection. As this is the last user of the variable, it then allows removal of it in a followup patch. Signed-off-by: Richard Purdie --- meta/classes/create-spdx.bbclass | 8 1 file changed, 4 insertions(+), 4 deletions(

[OE-core] [PATCH] perf-build-test/report: Drop phantomjs and html email reports support

phantomjs isn't reliable and we've moved to sharing the reports via a webserver. Update the scripts to more match those being used in the autobuilder helper where the html email support was removed. Signed-off-by: Richard Purdie --- scripts/contrib/build-perf-test-wrapper.sh| 15 +- scripts

[OE-core] [PATCH] openssl: upgrade to 3.0.2

From: Ross Burton * Fixed a bug in the BN_mod_sqrt() function that can cause it to loop forever for non-prime moduli ([CVE-2022-0778]) Signed-off-by: Ross Burton --- .../openssl/openssl/reproducibility.patch | 22 --- .../{openssl_3.0.1.bb => openssl_3.0.2.bb}| 3

[OE-core][PATCH] kernel-fitimage: allow overriding FIT configuration prefix

The prefix was recently changed to play ball with the CVE-2021-27138 workaround in U-Boot. Already deployed bootloaders though may still expect a configuration name containing @ or they may not be affected by this issue. Also, uses may want to customize it beyond the [@-] issue: When device trees

[OE-core] [PATCH 2/3] lttng-modules: remove redundant devupstream assignments

These are set by devupstream, so they don't need to be set in the recipe. Signed-off-by: Ross Burton --- meta/recipes-kernel/lttng/lttng-modules_2.13.1.bb | 5 - 1 file changed, 5 deletions(-) diff --git a/meta/recipes-kernel/lttng/lttng-modules_2.13.1.bb b/meta/recipes-kernel/lttng/lttng-

[OE-core] [PATCH 3/3] linux-yocto: remove redundant devupstream assignments

These are set by devupstream, so they don't need to be set in the recipe. Signed-off-by: Ross Burton --- meta/recipes-kernel/linux/linux-yocto_5.15.bb | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/recipes-kernel/linux/linux-yocto_5.15.bb b/meta/recipes-kernel/linux/linux-yocto_5.15.bb

[OE-core] [PATCH 1/3] devupstream: fix handling of SRC_URI

As the class handler runs before overrides are actually applied we need to check both SRC_URI:class-devupstream and SRC_URI, otherwise the automatic assignment of S="${WORKDIR}/git" for git repositories does not work if the base recipe uses http: but :class-devupstream has a git:// entry instead.

[OE-core] [honister][PATCH] gcc: sanitizer: Fix tsan against glibc 2.34

sanitizer: cherry pick 414482751452e54710f16bae58458c66298aaf69 The patch is needed in order to support recent glibc (2.34). libsanitizer/ChangeLog: PR sanitizer/101749 * sanitizer_common/sanitizer_posix_libcdep.cpp: Prevent generation of dependency on _cxa_guard for stati

[OE-core] [PATCH] python3-setuptools-rust-native: use setuptools_build_meta

The wheel generation problems are solved now: a wheel is correctly built to setuptools_rust-1.1.2-py3-none-any.whl, so we can use setuptools_build_meta. Signed-off-by: Ross Burton --- .../python/python3-setuptools-rust-native_1.1.2.bb | 5 + 1 file changed, 1 insertion(+), 4 deleti

[OE-core] [hardknott][PATCH 5/6] vim: Update to 8.2.4524 for further CVE fixes

From: Richard Purdie Includes CVE-2022-0696, CVE-2022-0714, CVE-2022-0729. Signed-off-by: Richard Purdie (cherry picked from commit 0d29988958e48534a0076307bb2393a3c1309e03) Signed-off-by: Anuj Mittal --- meta/recipes-support/vim/vim.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(

[OE-core] [hardknott][PATCH 6/6] wic: Use custom kernel path if provided

From: Bill Pittman If the custom kernel path is provided in options, then use that path instead of the default path. Signed-off-by: Bill Pittman Signed-off-by: Richard Purdie (cherry picked from commit 1068102216a894c467f71f6046fdb37d5577545c) Signed-off-by: Anuj Mittal --- scripts/wic | 3 +

[OE-core] [hardknott][PATCH 4/6] sstate: inside the threadedpool don't write to the shared localdata

From: Jose Quaresma When inside the threadedpool we make a copy of the localdata to avoid some race condition, so we need to use this new localdata2 and stop write the shared localdata. Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie (cherry picked from commit 1fa763b2022822a76fde54

[OE-core] [hardknott][PATCH 3/6] expat: fix CVE-2022-25236

From: Kai Kang Backport patches to fix CVE-2022-25236 for expat. CVE: CVE-2022-25236 Signed-off-by: Kai Kang Signed-off-by: Anuj Mittal --- .../expat/expat/CVE-2022-25236-1.patch| 116 + .../expat/expat/CVE-2022-25236-2.patch| 232 ++ meta/recipes-core

[OE-core] [hardknott][PATCH 2/6] expat: fix CVE-2022-25235

From: Kai Kang Backport patch to fix CVE-2022-25235 for expat. CVE: CVE-2022-25235 Signed-off-by: Kai Kang Signed-off-by: Anuj Mittal --- .../expat/expat/CVE-2022-25235.patch | 261 ++ meta/recipes-core/expat/expat_2.2.10.bb | 1 + 2 files changed, 262 insert

[OE-core] [hardknott][PATCH 1/6] patch.py: Prevent git repo reinitialization

From: Pavel Zhukov There were few bugs in the _isInitialized() function which might trigger git repo to be reinitialized and patches failing to apply. Signed-off-by: Pavel Zhukov Signed-off-by: Richard Purdie Signed-off-by: Anuj Mittal --- .../recipes-test/gitrepotest/gitrepotest.bb| 16

[OE-core] [hardknott][PATCH 0/6] Patch review

Next set of changes for hardknott. No problems seen while testing on the autobuilder. https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3363 Thanks, Anuj The following changes since commit d0b1807edc10835beff9a55a105ac191b6ac2fe7: unfs3: correct configure option (2022-03-07 2

[OE-core] [honister][PATCH 0/6] Pull request

The following changes since commit c2ebef2113d05aefb98b41caf380e03ec368934c: expat: Upgrade 2.4.6 -> 2.4.7 (2022-03-07 11:10:21 +0800) are available in the Git repository at: git://push.openembedded.org/openembedded-core-contrib stable/honister-next Alexander Kanavin (2): util-linux: upda

Re: [OE-core] [PATCH] dpkg: upgrade 1.21.1 -> 1.21.2

On Tue, 2022-03-15 at 18:51 +0800, wangmy wrote: > The following patches refreshed for new version: > 0001-build.c-ignore-return-of-1-from-tar-cf.patch > 0003-Our-pre-postinsts-expect-D-to-be-set-when-running-in.patch > 0004-The-lutimes-function-doesn-t-work-properly-for-all-s.patch > 0007-dpkg-deb

[OE-core] Yocto Project Status WW11`22

Current Dev Position: YP 3.5 M4 Next Deadline: 4th April. 2022 YP 3.5 M4 build Next Team Meetings: * Bug Triage meeting Thursday Mar. 17th 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) *

Re: [OE-core] [PATCH] sdk: support uppercase characters in MACHINE

On 15/03/2022 15:24, Quentin Schulz wrote: Hi Arnout, On 3/15/22 14:56, Arnout Vandecappelle (Essensium/Mind) wrote: There are no real constraints on the values that MACHINE can take, it's perfectly possible to define a machine with uppercase letters, and building for that machine works fine.

[OE-core] [PATCH] openssl: update reproducibility Upstream-Status

This is now upstreamed. Signed-off-by: Ross Burton --- meta/recipes-connectivity/openssl/openssl/reproducibility.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-connectivity/openssl/openssl/reproducibility.patch b/meta/recipes-connectivity/openssl/openssl/

Re: [OE-core] [PATCH] sdk: support uppercase characters in MACHINE

On 15/03/2022 15:07, Richard Purdie wrote: On Tue, 2022-03-15 at 14:56 +0100, Arnout Vandecappelle (Essensium/Mind) wrote: There are no real constraints on the values that MACHINE can take, it's perfectly possible to define a machine with uppercase letters, and building for that machine works

Re: [OE-core] [PATCH] sdk: support uppercase characters in MACHINE

Hi Arnout, On 3/15/22 14:56, Arnout Vandecappelle (Essensium/Mind) wrote: There are no real constraints on the values that MACHINE can take, it's perfectly possible to define a machine with uppercase letters, and building for that machine works fine. However, the (extensible) SDK targets includ

Re: [OE-core] [PATCH] sdk: support uppercase characters in MACHINE

On Tue, 2022-03-15 at 14:56 +0100, Arnout Vandecappelle (Essensium/Mind) wrote: > There are no real constraints on the values that MACHINE can take, it's > perfectly possible to define a machine with uppercase letters, and > building for that machine works fine. > > However, the (extensible) SDK t

[OE-core] [PATCH] sdk: support uppercase characters in MACHINE

There are no real constraints on the values that MACHINE can take, it's perfectly possible to define a machine with uppercase letters, and building for that machine works fine. However, the (extensible) SDK targets include packages and packagegroups that have MACHINE in their name, and uppercase l

[OE-core] [AUH] mesa: upgrading to 22.0.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mesa* to *22.0.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe mesa failed. NOTE: Starting bitbake server... NOTE: Reconnecting to b

[OE-core] [AUH] dbus: upgrading to 1.14.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dbus* to *1.14.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade dbus -V 1.14.0 NOTE: Starting bitbake server... NOTE: Recon

[OE-core] [AUH] gstreamer1.0-rtsp-server: upgrading to 1.20.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gstreamer1.0-rtsp-server* to *1.20.1* has Succeeded. Next steps: - apply the patch: git am 0001-gstreamer1.0-rtsp-server-upgrade-1.20.0-1.20.1.patch - check the changes to

[OE-core] [AUH] sqlite3: upgrading to 3.38.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *sqlite3* to *3.38.1* has Succeeded. Next steps: - apply the patch: git am 0001-sqlite3-upgrade-3.38.0-3.38.1.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] python3-dtschema: upgrading to 2022.3.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-dtschema* to *2022.3.1* has Succeeded. Next steps: - apply the patch: git am 0001-python3-dtschema-upgrade-2022.1-2022.3.1.patch - check the changes to upstream pat

[OE-core] [AUH] lttng-modules: upgrading to 2.13.2 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *lttng-modules* to *2.13.2* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe lttng-modules failed. NOTE: Starting bitbake server... NOTE:

[OE-core] [AUH] Upgrade status: 2022-03-15

Recipe upgrade statistics: * Failed (devtool error): 13 bind, 9.18.0, Armin Kuster dbus-test, 1.14.0, Chen Qi dbus, 1.14.0, Chen Qi libcgroup, 2.0.1, Alexander Kanavin systemd-boot, 250.4, Chen Qi systemd, 250.4, Chen Qi dpkg, 1.21.

[OE-core] [AUH] python3-setuptools: upgrading to 60.9.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-setuptools* to *60.9.3* has Succeeded. Next steps: - apply the patch: git am 0001-python3-setuptools-upgrade-59.5.0-60.9.3.patch - check the changes to upstream pat

[OE-core] [AUH] gstreamer1.0-python: upgrading to 1.20.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gstreamer1.0-python* to *1.20.1* has Succeeded. Next steps: - apply the patch: git am 0001-gstreamer1.0-python-upgrade-1.20.0-1.20.1.patch - check the changes to upstream p

[OE-core] [AUH] gstreamer1.0-plugins-ugly: upgrading to 1.20.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gstreamer1.0-plugins-ugly* to *1.20.1* has Succeeded. Next steps: - apply the patch: git am 0001-gstreamer1.0-plugins-ugly-upgrade-1.20.0-1.20.1.patch - check the changes t

[OE-core] [AUH] gstreamer1.0-libav: upgrading to 1.20.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gstreamer1.0-libav* to *1.20.1* has Succeeded. Next steps: - apply the patch: git am 0001-gstreamer1.0-libav-upgrade-1.20.0-1.20.1.patch - check the changes to upstream pat

[OE-core] [AUH] python3-importlib-metadata: upgrading to 4.11.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-importlib-metadata* to *4.11.3* has Succeeded. Next steps: - apply the patch: git am 0001-python3-importlib-metadata-upgrade-4.11.2-4.11.3.patch - check the changes

[OE-core] [AUH] gtk+3: upgrading to 3.24.33 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gtk+3* to *3.24.33* has Succeeded. Next steps: - apply the patch: git am 0001-gtk-3-upgrade-3.24.31-3.24.33.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] python3-pip: upgrading to 22.0.4 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-pip* to *22.0.4* has Succeeded. Next steps: - apply the patch: git am 0001-python3-pip-upgrade-22.0.3-22.0.4.patch - check the changes to upstream patches and summar

[OE-core] [AUH] vulkan-samples: upgrading to 9e56ef313debe39e6d45c98c5fe3128de612bb8c FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-samples* to *9e56ef313debe39e6d45c98c5fe3128de612bb8c* has Failed(other errors). Detailed error information: 'MACHINE=qemux86 bitbake vulkan-samples' failed Loading cache...

[OE-core] [AUH] python3-numpy: upgrading to 1.22.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-numpy* to *1.22.3* has Succeeded. Next steps: - apply the patch: git am 0001-python3-numpy-upgrade-1.22.2-1.22.3.patch - check the changes to upstream patches and su

[OE-core] [AUH] piglit: upgrading to d1c5c7cc46e29ae88987802d390827e2649e730e SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *piglit* to *d1c5c7cc46e29ae88987802d390827e2649e730e* has Succeeded. Next steps: - apply the patch: git am 0001-piglit-upgrade-to-latest-revision.patch - check the changes t

[OE-core] [AUH] linux-firmware: upgrading to 20220310 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *linux-firmware* to *20220310* has Succeeded. Next steps: - apply the patch: git am 0001-linux-firmware-upgrade-20220209-20220310.patch - check the changes to upstream patch

[OE-core] [AUH] python3-mako: upgrading to 1.2.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-mako* to *1.2.0* has Succeeded. Next steps: - apply the patch: git am 0001-python3-mako-upgrade-1.1.6-1.2.0.patch - check the changes to upstream patches and summari

[OE-core] [AUH] python3-pytest: upgrading to 7.1.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-pytest* to *7.1.0* has Succeeded. Next steps: - apply the patch: git am 0001-python3-pytest-upgrade-7.0.1-7.1.0.patch - check the changes to upstream patches and sum

[OE-core] [AUH] dpkg: upgrading to 1.21.2 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dpkg* to *1.21.2* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe dpkg failed. NOTE: Starting bitbake server... NOTE: Reconnecting to b

[OE-core] [AUH] librsvg: upgrading to 2.52.7 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *librsvg* to *2.52.7* has Succeeded. Next steps: - apply the patch: git am 0001-librsvg-upgrade-2.52.6-2.52.7.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] mtools: upgrading to 4.0.38 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mtools* to *4.0.38* has Succeeded. Next steps: - apply the patch: git am 0001-mtools-upgrade-4.0.37-4.0.38.patch - check the changes to upstream patches and summarize them i

[OE-core] [AUH] python3-hypothesis: upgrading to 6.39.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-hypothesis* to *6.39.3* has Succeeded. Next steps: - apply the patch: git am 0001-python3-hypothesis-upgrade-6.39.2-6.39.3.patch - check the changes to upstream pat

[OE-core] [AUH] systemd: upgrading to 250.4 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *systemd* to *250.4* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe systemd failed. NOTE: Starting bitbake server... NOTE: Reconnecting

[OE-core] [AUH] go-helloworld: upgrading to ad95e7f791d8e1e7e7ec7f7cedfc2f6b29f6c9e2 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go-helloworld* to *ad95e7f791d8e1e7e7ec7f7cedfc2f6b29f6c9e2* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade go-helloworld -S

[OE-core] [AUH] gnu-config: upgrading to c179db1b6f2ae484bfca1e9f8bae273e3319fa7d FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gnu-config* to *c179db1b6f2ae484bfca1e9f8bae273e3319fa7d* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade gnu-config -S c179

[OE-core] [AUH] meson: upgrading to 0.61.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *meson* to *0.61.3* has Succeeded. Next steps: - apply the patch: git am 0001-meson-upgrade-0.61.2-0.61.3.patch - check the changes to upstream patches and summarize them in

[OE-core] [AUH] libdnf: upgrading to 0.66.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libdnf* to *0.66.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe libdnf failed. NOTE: Starting bitbake server... NOTE: Reconnecting

[OE-core] [AUH] createrepo-c: upgrading to 0.19.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *createrepo-c* to *0.19.0* has Succeeded. Next steps: - apply the patch: git am 0001-createrepo-c-upgrade-0.18.0-0.19.0.patch - check the changes to upstream patches and summ

[OE-core] [AUH] libcgroup: upgrading to 2.0.1 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libcgroup* to *2.0.1* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade libcgroup -V 2.0.1 NOTE: Starting bitbake server... NOT

[OE-core] [AUH] perl: upgrading to 5.34.1 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *perl* to *5.34.1* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe perl failed. NOTE: Starting bitbake server... NOTE: Reconnecting to b

[OE-core] [AUH] apt: upgrading to 2.4.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *apt* to *2.4.1* has Succeeded. Next steps: - apply the patch: git am 0001-apt-upgrade-2.4.0-2.4.1.patch - check the changes to upstream patches and summarize them in the comm

[OE-core] [AUH] dnf: upgrading to 4.11.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dnf* to *4.11.1* has Succeeded. Next steps: - apply the patch: git am 0001-dnf-upgrade-4.10.0-4.11.1.patch - check the changes to upstream patches and summarize them in the

[OE-core] [AUH] bind: upgrading to 9.18.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *bind* to *9.18.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe bind failed. NOTE: Starting bitbake server... NOTE: Reconnecting to b

[OE-core] [AUH] systemd-boot: upgrading to 250.4 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *systemd-boot* to *250.4* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe systemd-boot failed. NOTE: Starting bitbake server... NOTE: Re

[OE-core] [AUH] dbus-test: upgrading to 1.14.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dbus-test* to *1.14.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade dbus-test -V 1.14.0 NOTE: Starting bitbake server... N

[OE-core] [PATCH] python3-numpy: upgrade 1.22.2 -> 1.22.3

Signed-off-by: Wang Mingyu --- .../python/{python3-numpy_1.22.2.bb => python3-numpy_1.22.3.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/python/{python3-numpy_1.22.2.bb => python3-numpy_1.22.3.bb} (96%) diff --git a/meta/recipes-devtools/python/python3-

[OE-core] [PATCH] lttng-modules: upgrade 2.13.1 -> 2.13.2

The following patches removed since they're included in 2.13.2 0001-fix-block-remove-GENHD_FL_SUPPRESS_PARTITION_INFO-v5.patch 0002-fix-block-remove-the-rq_disk-field-in-struct-request.patch 0003-fix-mm-compaction-fix-the-migration-stats-in-trace_m.patch 0004-fix-btrfs-pass-fs_info-to-trace_btrfs_t

[OE-core] [PATCH] python3-importlib-metadata: upgrade 4.11.2 -> 4.11.3

Changelog: #372: Removed cast of path items in FastPath, not needed. Signed-off-by: Wang Mingyu --- ...-metadata_4.11.2.bb => python3-importlib-metadata_4.11.3.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/python/{python3-importlib-metadata_4.11.2.bb =>

[OE-core] [PATCH] linux-firmware: upgrade 20220209 -> 20220310

License-Update: year updated to 2022 Version of some driver files updated Added files for some drivers Signed-off-by: Wang Mingyu --- ...inux-firmware_20220209.bb => linux-firmware_20220310.bb} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename meta/recipes-kernel/linux-firmw

[OE-core] [PATCH] libuv: upgrade 1.43.0 -> 1.44.1

License-Update: the following message removed from LICENSE: android-ifaddrs.h, android-ifaddrs.c, copyright Berkeley Software Design Inc, Kenneth MacKay and Emergya (Cloud4all, FP7/2007-2013, grant agreement n?? 289016). Three clause BSD license. Changes since version 1.43.0: =

[OE-core] [PATCH] libcgroup: upgrade 2.0 -> 2.0.1

module.patch musl-decls-compat.patch removed since they're included in 2.0.1 Changelog: == - Allow reading/writing from cgroup.* files in cgroup v2 - Add support for cgroup v2's cgroup.threads file - Fix issue where libcgroup/pam wasn't working properly when cgrulesengd is disabled - Fix

[OE-core] [PATCH] libdnf: upgrade 0.65.0 -> 0.66.0

0001-Add-WITH_TESTS-option.patch 0001-Look-fo-sphinx-only-if-documentation-is-actually-ena.patch removed since they're included in 0.66.0 0001-Get-parameters-for-both-libsolv-and-libsolvext-libdn.patch 0004-Set-libsolv-variables-with-pkg-config-cmake-s-own-mo.patch modified for new version Change

[OE-core] [PATCH] librsvg: upgrade 2.52.6 -> 2.52.7

Changelog: = Backport a fix for the regression that was introduced in the last release: - #851 - Output filled text as text for PDF; fixes regression due to outputting all text as paths. Signed-off-by: Wang Mingyu --- .../librsvg/{librsvg_2.52.6.bb => librsvg_2.52.7.bb}| 2

[OE-core] [PATCH] harfbuzz: upgrade 4.0.0 -> 4.0.1

Changelog: = - Update OpenType to AAT mappings for hist and vrtr features. - Update IANA Language Subtag Registry to 2022-03-02. - Update USE shaper to allow any non-numeric tail in a symbol cluster, and remove obsolete data overrides. - Fix handling of baseline variations to return corr

[OE-core] [PATCH] dnf: upgrade 4.10.0 -> 4.11.1

Signed-off-by: Wang Mingyu --- meta/recipes-devtools/dnf/{dnf_4.10.0.bb => dnf_4.11.1.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/dnf/{dnf_4.10.0.bb => dnf_4.11.1.bb} (98%) diff --git a/meta/recipes-devtools/dnf/dnf_4.10.0.bb b/meta/recipes-devtools/d

[OE-core] [PATCH] dpkg: upgrade 1.21.1 -> 1.21.2

The following patches refreshed for new version: 0001-build.c-ignore-return-of-1-from-tar-cf.patch 0003-Our-pre-postinsts-expect-D-to-be-set-when-running-in.patch 0004-The-lutimes-function-doesn-t-work-properly-for-all-s.patch 0007-dpkg-deb-build.c-Remove-usage-of-clamp-mtime-in-tar.patch noman.pat

[OE-core] [PATCH] createrepo-c: upgrade 0.18.0 -> 0.19.0

Signed-off-by: Wang Mingyu --- .../{createrepo-c_0.18.0.bb => createrepo-c_0.19.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/createrepo-c/{createrepo-c_0.18.0.bb => createrepo-c_0.19.0.bb} (96%) diff --git a/meta/recipes-devtools/createrepo-

Re: [OE-core] [hardknott][PATCH] babeltrace: Handle negative time and offset from Epoch

On 3/14/22 15:08, Mittal, Anuj wrote: > On Wed, 2022-03-09 at 16:26 +0800, He Zhe wrote: >> Backport a patch from upstream to handle negative time and offset >> from Epoch > This is causing ptest failures for both qemux86-64 and qemuarm64: > > https://autobuilder.yoctoproject.org/typhoon/#/builde

Re: [OE-core] [hardknott][PATCH] babeltrace: Handle negative time and offset from Epoch

On 3/14/22 15:08, Mittal, Anuj wrote: > On Wed, 2022-03-09 at 16:26 +0800, He Zhe wrote: >> Backport a patch from upstream to handle negative time and offset >> from Epoch > This is causing ptest failures for both qemux86-64 and qemuarm64: > > https://autobuilder.yoctoproject.org/typhoon/#/builde