Re: [OE-core][PATCH] resolvconf: make it work

On Tue, Nov 15, 2022 at 5:45 AM Chen Qi wrote: > > The current resolvconf does not work. Make it work with the > following changes. > 1. Install normalize-resolvconf, which is used by resolvconf. > 2. Add dependencies sed, coreutils, util-linux-flock. >util-linux-flock is needed by our

[OE-core][master][PATCH] python3: Fix CVE-2022-45061

From: Omkar Fix CVE-2022-45061, referenced as https://github.com/python/cpython/issues/98433 patch taken from https://github.com/python/cpython/pull/99231/commits/064ec20bf7a181ba5fa961aaa12973812aa6ca5d Signed-off-by: Omkar --- .../python/files/CVE-2022-45061.patch | 100

Re: [OE-core][PATCH] resolvconf: make it work

Got it. It seems that after adding those RDEPENDS, resolvconf cannot remain as allarch. I'll send out V2. Regards, Qi -Original Message- From: Alexandre Belloni Sent: Wednesday, November 16, 2022 4:39 AM To: Chen, Qi Cc: openembedded-core@lists.openembedded.org Subject: Re:

[OE-core][dunfell][PATCH] python3: Fix CVE-2022-45061

From: Omkar Fix CVE-2022-45061, referenced as https://github.com/python/cpython/issues/98433 patch taken from https://github.com/python/cpython/pull/99231/commits/064ec20bf7a181ba5fa961aaa12973812aa6ca5d Signed-off-by: Omkar --- .../python/files/CVE-2022-45061.patch | 100

[OE-core] [PATCH] libpipeline: upgrade 1.5.6 -> 1.5.7

From: Wang Mingyu Changelog: * Add notes to libpipeline(3) of when functions were added. * Transferred Git repository to https://gitlab.com/libpipeline/libpipeline. * Make `socketpair` tests used by `./configure --enable-socketpair-pipe` compatible with C23. Signed-off-by:

[OE-core] [PATCH] btrfs-tools: upgrade 6.0 -> 6.0.1

From: Wang Mingyu Changelog: == * send: minor speed up for v2 due to increased buffer size * resize: invalid command line options fail with error code * quota rescan: * add long options --status and --wait * new option to wait but don't start rescan * qgroup show: print path by

[OE-core] [kirkstone][PATCH] systemd: CVE-2022-3821 Fix buffer overrun

Upstream-Status: Backport from https://github.com/systemd/systemd-stable/commit/72d4c15a946d20143cd4c6783c802124bc894dc7 Affects "systemd <= 251" Signed-off-by: Hitendra Prajapati --- .../systemd/systemd/CVE-2022-3821.patch | 45 +++

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

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 09/10] kernel-devsrc: fix for v6.1+

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 08/10] linux-yocto-dev: bump to v6.1

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 05/10] linux-yocto/5.15: update to v5.15.76

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 07/10] kern-tools: integrate ZFS speedup patch

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/10] linux-yocto/5.19: cfg: intel and vesa updates

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 04/10] linux-yocto/5.19: update to v5.19.17

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 03/10] linux-yocto/5.15: update to v5.15.74

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/10] linux-yocto/5.19: update to v5.19.16

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 01/10] linux-yocto-dev: bump to v6.0+

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] [PATCH 00/10] kernel: consolidated pull request

From: Bruce Ashfield Richard, Here's the batched up -stable and -dev updates that I've been testing for a while. I've included both the 6.0 and 6.1 dev kernel updates, as both were tested, and someone might want to use v6.0 as a development kernel, and could use that commit as a baseline. I

[OE-core] [PATCH] kernel_dep_check.bbclass: help track kernel depend

From: John Edward Broadbent This recipe can be used to identify kernel dependencies, and immediately throw build errors if those dependencies are not met. Signed-off-by: John Edward Broadbent --- meta/classes-global/kernel_dep_check.bbclass | 81 1 file changed, 81

Re: [OE-core] [AUH] webkitgtk: upgrading to 2.38.2 FAILED

Thanks, once you get it all into a shape that can be given to the AB test matrix, I can add your patches to my branch. Alex On Tue, 15 Nov 2022 at 23:51, Tim Orling wrote: > > Ugly working branch > https://git.yoctoproject.org/poky-contrib/log/?h=timo/at-spi2-core_2.46.0 > > Dropped some

Re: [OE-core] [AUH] webkitgtk: upgrading to 2.38.2 FAILED

Ugly working branch https://git.yoctoproject.org/poky-contrib/log/?h=timo/at-spi2-core_2.46.0 Dropped some patches. Refreshed some patches. Replace atk/at-spi2-atk with at-spi2-core. Fails in do_compile (and all the various configuration options not explored yet). On Tue, Nov 15, 2022 at 5:06 AM

Re: [OE-core] [AUH] at-spi2-core: upgrading to 2.46.0 FAILED

Ugly working branch: https://git.yoctoproject.org/poky-contrib/log/?h=timo/at-spi2-core_2.46.0 This upgrade merges atk and at-spi2-atk into at-spi2-core. The most obvious collateral damage is in webkitgtk. On Tue, Nov 15, 2022 at 5:07 AM Auto Upgrade Helper wrote: > Hello, > > this email is a

Re: [OE-core] [PATCH] sanity: Drop data finalize call

On Tue, 2022-11-15 at 15:10 +, Peter Kjellerstedt wrote: > > -Original Message- > > From: openembedded-core@lists.openembedded.org > > On Behalf Of Richard > > Purdie > > Sent: den 11 november 2022 23:58 > > To: openembedded-core@lists.openembedded.org > > Subject: [OE-core] [PATCH]

Re: [OE-core][PATCH] scripts: convert-overrides: Allow command-line customizations

On Tue, Nov 15, 2022, 9:42 AM Joshua Watt wrote: > Steve, > > Please backport this to kirkstone and langdale. > > Thanks! > Ok, will do! Steve > On Fri, Nov 11, 2022 at 8:55 AM Joshua Watt wrote: > > > > Adds argument parsing to the conversion script so that the fields that > > the script

Re: [OE-core][PATCH] resolvconf: make it work

Hello, This fails sstatetests.SStateTests.test_sstate_allarch_samesigs: https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/4409/steps/14/logs/stdio - 'resolvconf/do_package_qa': 'a309bf7fd05364ea8b524a605246f7929768bca185713f913df0f3f1e5f1ce55', -

Re: [OE-core][PATCH] scripts: convert-overrides: Allow command-line customizations

Steve, Please backport this to kirkstone and langdale. Thanks! On Fri, Nov 11, 2022 at 8:55 AM Joshua Watt wrote: > > Adds argument parsing to the conversion script so that the fields that > the script uses to do conversions can be customized on the command line. > The intention is to allows

Re: [OE-Core][kirkstone][PATCH] sudo: fix CVE-2022-43995 potential heap overflow for passwords < 8 characters

On 2022-11-15 14:08, Randy MacLeod wrote: Thanks Xiangyu but for kirkstone/langdale I think we should take the patch update:   sudo: upgrade 1.9.12 -> 1.9.12p1 that was sent to the list for master since it includes this CVE fix and more bug fixes: $ git log --oneline

Re: [OE-Core][kirkstone][PATCH] sudo: fix CVE-2022-43995 potential heap overflow for passwords < 8 characters

Thanks Xiangyu but for kirkstone/langdale I think we should take the patch update:   sudo: upgrade 1.9.12 -> 1.9.12p1 that was sent to the list for master since it includes this CVE fix and more bug fixes: $ git log --oneline SUDO_1_9_12..SUDO_1_9_12p1 | cut -c -99 7a103879a Merge sudo

[OE-core] [PATCH] python3-hypothesis: upgrade 6.56.4 -> 6.57.1

6.57.1 - 2022-11-14 This patch updates some internal type annotations and fixes a formatting bug in the explain phase reporting. 6.57.0 - 2022-11-14 Hypothesis now raises an error if you passed a strategy as the alphabet= argument to text(), and it generated something which was not a length-one

[OE-Core][dunfell][PATCH] systemd: Fix CVE-2022-3821 issue

Hi Steve, Please find the attached patch for the fix of CVE-2022-3821 systemd issue. Thanks, Best Regards, Ranjitsinh Rathod Technical Leader | | KPIT Technologies Ltd. Cellphone: +91-84606 92403 __ KPIT | Follow us on

Re: [OE-core] [PATCH] wic: implement bootloader --password

No, the password is provided through wks file. ksparser.py is a wic subsystem which parses those kikstart files. -- With best wishes, Sergei Zhmylev Engineering consultant OS development department On Tue, 2022-11-15 at 16:45 +0100, Alexander Kanavin wrote: > > Wait, is the password provided

Re: [OE-core] [PATCH] wic: implement bootloader --password

Wait, is the password provided through command line? Alex On Tue, 15 Nov 2022 at 15:40, Sergey Zhmylev wrote: > > From: Sergei Zhmylev > > Currently the only way to specify a password for bootloader > is to supply a complete user-defined bootloader config file > to the build process. This

[OE-core] Yocto Project Status 15 November 2022 (WW46)

Current Dev Position: YP 4.2 M1 Next Deadline: 5th December 2022 YP 4.2 Build Next Team Meetings: * Bug Triage meeting Thursday November 17th 7:30 am PDT (

Re: [OE-core] [PATCH] sanity: Drop data finalize call

> -Original Message- > From: openembedded-core@lists.openembedded.org > On Behalf Of Richard Purdie > Sent: den 11 november 2022 23:58 > To: openembedded-core@lists.openembedded.org > Subject: [OE-core] [PATCH] sanity: Drop data finalize call > > This call was effectively like

[OE-core] [PATCH] wic: implement bootloader --password

From: Sergei Zhmylev Currently the only way to specify a password for bootloader is to supply a complete user-defined bootloader config file to the build process. This patch introduces a --password paramenter in order to simplify bootloaders hardening. Signed-off-by: Sergei Zhmylev ---

[OE-core][PATCH] resolvconf: make it work

The current resolvconf does not work. Make it work with the following changes. 1. Install normalize-resolvconf, which is used by resolvconf. 2. Add dependencies sed, coreutils, util-linux-flock. util-linux-flock is needed by our busybox does not support '-w' by default. coreutils is needed

[OE-core] OEDvM 2022.11

Users, contributors, members! [1] It is about time again to gather - in virtual form - for some hours of knowledge exchange, discussion, and designing the future of OpenEmbedded. The OpenEmbedded Developers virtual Meeting 2022.11 will take place on December 2nd, 2022 [2], and you are invited to

[OE-core] [AUH] kmscube: upgrading to 345111481d654b38a72b5c3629151dc74f7a82bc SUCCEEDED

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

[OE-core] [AUH] at-spi2-core: upgrading to 2.46.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *at-spi2-core* to *2.46.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

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

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

[OE-core] [AUH] libgpg-error: upgrading to 1.46 FAILED

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

[OE-core] [AUH] wayland-protocols: upgrading to 1.29 SUCCEEDED

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

[OE-core] [AUH] babeltrace: upgrading to 1.5.11 SUCCEEDED

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

[OE-core] [AUH] ghostscript: upgrading to 10.0.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ghostscript* to *10.0.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] xf86-input-mouse: upgrading to 1.9.4 FAILED

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

[OE-core] [AUH] epiphany: upgrading to 43.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *epiphany* to *43.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-epiphany-upgrade-42.4-43.0.patch -

[OE-core] [AUH] puzzles: upgrading to ff406d4edc62af1f459ba2b17a9110a8e3ef71bc SUCCEEDED

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

[OE-core] [AUH] systemtap-uprobes: upgrading to 4.8 SUCCEEDED

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

[OE-core] [AUH] systemtap: upgrading to 4.8 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *systemtap* to *4.8* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-systemtap-upgrade-4.7-4.8.patch -

[OE-core] [AUH] iso-codes: upgrading to 4.12.0 SUCCEEDED

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

[OE-core] [AUH] piglit: upgrading to 71eb7b6880c842da2c2414f2be9468e9fd95d525 SUCCEEDED

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

[OE-core] [AUH] icu: upgrading to 72-1 FAILED

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

[OE-core] [AUH] flac: upgrading to 1.4.2 FAILED

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

[OE-core] [AUH] webkitgtk: upgrading to 2.38.2 FAILED

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

[OE-core] [AUH] llvm: upgrading to 15.0.4 FAILED

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

[OE-core] [AUH] popt: upgrading to 1.19 FAILED

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

[OE-core] [AUH] gobject-introspection: upgrading to 1.74.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gobject-introspection* to *1.74.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] libsoup: upgrading to 3.2.2 SUCCEEDED

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

[OE-core] [AUH] vte: upgrading to 0.70.1 FAILED

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

[OE-core] [AUH] diffoscope: upgrading to 226 SUCCEEDED

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

[OE-core] [AUH] gcr: upgrading to 4.0.0 FAILED

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

[OE-core] [AUH] vulkan-samples: upgrading to 3a9a0c455e9f45b5645a40fbd8cff2b2744ce3fb FAILED

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

[OE-core] [AUH] python3-dbusmock: upgrading to 0.28.6 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-dbusmock* to *0.28.6* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] bash: upgrading to 5.2.9 FAILED

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

[OE-core] [AUH] xz: upgrading to 5.2.8 SUCCEEDED

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

[OE-core] [AUH] shadow: upgrading to 4.13 FAILED

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

[OE-core] [AUH] libx11: upgrading to 1.8.2 SUCCEEDED

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

[OE-core] [AUH] quota: upgrading to 4.09 FAILED

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

[OE-core] [AUH] elfutils: upgrading to 0.188 FAILED

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

[OE-core] [AUH] gawk: upgrading to 5.2.0 FAILED

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

[OE-core] [AUH] tzdata: upgrading to 2022f FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *tzdata* to *2022f* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-tzdata-upgrade-2022d-2022f.patch -

[OE-core] [AUH] texinfo: upgrading to 7.0 FAILED

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

[OE-core] [AUH] acpica: upgrading to 20221022 FAILED

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

[OE-core] [AUH] libhandy: upgrading to 1.8.0 FAILED

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

[OE-core] [AUH] tcl: upgrading to 8.6.12 FAILED

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

[OE-core] [AUH] man-db: upgrading to 2.11.0 FAILED

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

[OE-core] [AUH] cmake: upgrading to 3.24.3 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *cmake* to *3.24.3* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-cmake-upgrade-3.24.2-3.24.3.patch -

[OE-core] [AUH] make: upgrading to 4.4 FAILED

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

[OE-core] [AUH] rsync: upgrading to 3.2.7 FAILED

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

[OE-core] [AUH] btrfs-tools: upgrading to 6.0.1 SUCCEEDED

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

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

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

[OE-core] [AUH] swig: upgrading to 4.1.0 FAILED

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

[OE-core] [AUH] unfs3: upgrading to 0.10.0 FAILED

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

[OE-core] [AUH] libpipeline: upgrading to 1.5.7 SUCCEEDED

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

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

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

[OE-core] [AUH] patchelf: upgrading to 0.17.0 SUCCEEDED

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

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

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

[OE-core] [AUH] ccache: upgrading to 4.7.3 SUCCEEDED

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

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

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

[OE-core] [AUH] python3-pathspec: upgrading to 0.10.2 SUCCEEDED

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

[OE-core] [AUH] glib-2.0: upgrading to 2.74.1 FAILED

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

[OE-core] [AUH] readline: upgrading to 8.2 FAILED

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

[OE-core] [AUH] gettext: upgrading to 0.21.1 FAILED

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

[OE-core] [AUH] dropbear: upgrading to 2022.83 SUCCEEDED

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

[OE-core] [AUH] glib-networking: upgrading to 2.74.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *glib-networking* to *2.74.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] libxcrypt-compat: upgrading to 4.4.31 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libxcrypt-compat* to *4.4.31* has Succeeded. Next steps: - apply the patch: git am 0001-libxcrypt-compat-upgrade-4.4.30-4.4.31.patch - check the changes to upstream patches

[OE-core][PATCH v2] tzdata: update to 2022f

From: Priyal Doshi Signed-off-by: Priyal Doshi --- meta/recipes-extended/timezone/timezone.inc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/meta/recipes-extended/timezone/timezone.inc b/meta/recipes-extended/timezone/timezone.inc index d3c78e9..c4cdb77 100644 ---

Re: [OE-core] [meta-oe] [PATCH V2 2/2] Support bitbake compilation when the host is a RISCV platform

thanks, i see what you mean. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#173275): https://lists.openembedded.org/g/openembedded-core/message/173275 Mute This Topic: https://lists.openembedded.org/mt/95040977/21656 Group Owner:

Re: [OE-core] [meta-oe] [PATCH V2 1/2] Support bitbake compilation when the host is a RISCV platform

Thanks for the reminder, it seems that my description is not accurate enough. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#173274): https://lists.openembedded.org/g/openembedded-core/message/173274 Mute This Topic:

Re: [OE-core] [meta-oe] [PATCH V2 2/2] Support bitbake compilation when the host is a RISCV platform

On Tue, 15 Nov 2022 at 13:07, cp0613 wrote: > > From: Chen Pei > > meson should add build_arch:riscv64 to support bitbake on RISCV platform The commit title is "Support bitbake compilation when the host is a RISCV platform" Imagine someone reading the commit log; will that title help them

  1   2   >