[OE-core] [dunfell][PATCH] QEMU: CVE-2022-4144 QXL: qxl_phys2virt unsafe address translation can lead to out-of-bounds read

Upstream-Status: Backport from https://gitlab.com/qemu-project/qemu/-/commit/6dbbf055148c6f1b7d8a3251a65bd6f3d1e1f622 Signed-off-by: Hitendra Prajapati --- meta/recipes-devtools/qemu/qemu.inc | 1 + .../qemu/qemu/CVE-2022-4144.patch | 103 ++ 2 files

[OE-core][PATCH 2/2] rpm: do not export MAGIC in SDK

This MAGIC variable is used by libmagic (file), and should be exported by the file recipe. As the rpm recipe has 'file' in its DEPENDS, its sub-packages which links to libmagic will be automatically added the 'file' runtime dependency. More specifically, it's the rpm-build package. So in case

[OE-core][PATCH 1/2] file: export MAGIC in SDK

Previously, a wrapper is used for file, which adds '--magic-file' option to it. But other components might use libmagic and in such case, if there's no MAGIC environent variable set correctly, things do not work. For example, rpmbuild makes use of libmagic and it requries MAGIC to be set

Re: [OE-Core][PATCH 3/3] qemuppc64: set the qemuppc64 nfs r/wsize mount options to 524288

On Mon, Jan 16, 2023 at 6:05 PM Xiangyu Chen wrote: > > From: Xiangyu Chen > > On master oe, build a qemuppc64 with systemd as default init, when we > use nfs bootup, the kernel might panic due to missing symbol in dynamic > libraries as below: > > hid-generic 0003:0627:0001.0003: input: USB

[OE-core] Current high bug count owners for Yocto Project 4.2

All, Below is the list as of top 34 bug owners as of the end of WW02 of who have open medium or higher bugs and enhancements against YP 4.2. There are 71 possible work days left until the final release candidates for YP 4.2 needs to be released. Who Count michael.opdenac...@bootlin.com 34

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

[OE-Core][PATCH 0/3] set qemuppc64 default nfs rootfs mount r/w size to 524288

From: Xiangyu Chen On master oe, build a qemuppc64 with systemd as default init, when we use nfs bootup, the kernel might panic due to missing symbol in dynamic libraries as below: hid-generic 0003:0627:0001.0003: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-:00:01.0-3/input0

[OE-Core][PATCH 3/3] qemuppc64: set the qemuppc64 nfs r/wsize mount options to 524288

From: Xiangyu Chen On master oe, build a qemuppc64 with systemd as default init, when we use nfs bootup, the kernel might panic due to missing symbol in dynamic libraries as below: hid-generic 0003:0627:0001.0003: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-:00:01.0-3/input0

[OE-Core][PATCH 1/3] qemuboot.bbclass: add QB_NFSROOTFS_EXTRA_OPT for nfs rootfs extra option

From: Xiangyu Chen This extra options to be appended to the nfs rootfs options in kernel boot arg. Signed-off-by: Xiangyu Chen --- meta/classes-recipe/qemuboot.bbclass | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/classes-recipe/qemuboot.bbclass

[OE-Core][PATCH 2/3] runqemu: add process of option QB_NFSROOTFS_EXTRA_OPT

From: Xiangyu Chen This extra options to be appended to the nfs rootfs options in kernel boot arg. Example config with qemuppc64 in machine config: add r/w size in the nfs rootfs extra option: QB_NFSROOTFS_EXTRA_OPT = "wsize=524288,rsize=524288" re-build and runqemu with nfs again, we can

[OE-core] [PATCH v2] scripts/oe-setup-layers: Make efficiently idempotent

The effect of subsequent setup-layers executions is now either a NOOP or the minimal set of changes required to ensure layers precisely match the JSON configuration. This change allows setup-layers to be incorporated into a team's configuration management strategy. In particular, the

Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.22.rc1)

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.22.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. NUC 7 3. ADL 4.

Re: [OE-core] [PATCH] Make oe-setup-layers efficiently idempotent

On 1/16/23, 9:00 AM, "Richard Purdie" mailto:richard.pur...@linuxfoundation.org>> wrote: %< SNIP %< > Making the script rerun successfully seems sensible so the change > itself is reasonable. I was a little confused by some of the comments > in the commit message as oe-setup-layers doesn't

Re: [OE-core] [PATCH v2] rust: Merge all rustc-source patches into rust-source.inc

On 2023-01-16 07:17, Kokkonda, Sundeep via lists.openembedded.org wrote: Adding 'IMAGE_INSTALL:append = " packagegroup-core-buildessential" ' Please make the target build of rust (cargo?) depend on just the parts need packagegroup-core-buildessential, i.e. you don't need autoconf, make,

Re: [OE-core] [PATCH] uninative-tarball: Add libgcc

On Mon, 2023-01-16 at 19:21 +, Jose Quaresma wrote: > Hi Richard, > > I am seeing some build errors like this at the end of the build whre bibake > segment fault. > My problem is this happens on a build that doesn't use uninative, > does bitbake require uninative to build on master? No, it

Re: [OE-core] [PATCH 2/6] glib-2.0: Switch to using C11 std

upstream glib-2,0 has not accepted these patches so lets hold on to them for now. On Sun, Jan 15, 2023 at 10:51 AM Khem Raj wrote: > > Signed-off-by: Khem Raj > --- > ...0001-Switch-from-C99-to-C11-standard.patch | 40 + > ...efine-check_alignof-for-std-c11-and-.patch | 44

Re: [OE-core] [PATCH] uninative-tarball: Add libgcc

Hi Richard, I am seeing some build errors like this at the end of the build whre bibake segment fault. My problem is this happens on a build that doesn't use uninative, does bitbake require uninative to build on master? This is my build log where bitbake crash at the end: INFO: Build completion

Re: [OE-core] [kirkstone][PATCH 1/1] gcc: Refactor linker patches and fix linker on arm with usrmerge

On Mon, Jan 16, 2023 at 7:32 AM Khem Raj wrote: > > > > On Sun, Jan 15, 2023 at 11:56 PM Pavel Zhukov wrote: >> >> Backport fix from master to allow gcc to use proper linker path for >> musl [Yocto #14977]. > > > Lgtm Of the two, I think this seems to be closer to master and perhaps easier to

Re: [oe-core][PATCH] neard: dont pull in wpa-supplicant unconditionally

On Mon, 2023-01-16 at 18:20 +0100, Markus Volk wrote: > Yes, that's right, of course. What would be the preferred way to deal > with this. The dependency on wpa-supplicant is a bit annoying. Should > I use a bbappend to remove it, or is the RRECOMMEND on wpa-supplicant > perhaps removable from the

Re: [oe-core][PATCH] neard: dont pull in wpa-supplicant unconditionally

Hi Markus, Markus Volk escreveu no dia segunda, 16/01/2023 à(s) 17:20: > Yes, that's right, of course. What would be the preferred way to deal with > this. The dependency on wpa-supplicant is a bit annoying. Should I use a > bbappend to remove it, or is the RRECOMMEND on wpa-supplicant perhaps

Re: [oe-core][PATCH] neard: dont pull in wpa-supplicant unconditionally

Yes, that's right, of course. What would be the preferred way to deal with this. The dependency on wpa-supplicant is a bit annoying. Should I use a bbappend to remove it, or is the RRECOMMEND on wpa-supplicant perhaps removable from the neard recipe? Am Mo, 16. Jan 2023 um 17:03:09 +

Re: [oe-core][PATCH] neard: dont pull in wpa-supplicant unconditionally

On Mon, 2023-01-16 at 17:49 +0100, Markus Volk wrote: > > That isn't going to work as there is no default value for > > WIRELESS_DAEMON ? > > > > We have it set here > > https://git.yoctoproject.org/poky/commit/?id=1eaf64fbe16d2ceb472623c65c961b36aee33608 > Sure, but the neard recipe can't

Re: [OE-core] [PATCH] Make oe-setup-layers efficiently idempotent

On Sat, 2023-01-14 at 16:53 -0800, Chuck Wolber wrote: > The effect of subsequent setup-layers executions is now either a NOOP > or the minimal set of changes required to ensure layers precisely match > the JSON configuration. > > This change allows setup-layers to be incorporated into a team's >

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

On Wed, 2022-12-28 at 13:47 -0800, John Broadbent via lists.openembedded.org wrote: > 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 > ---

Re: [oe-core][PATCH] neard: dont pull in wpa-supplicant unconditionally

We have it set here Am Mo, 16. Jan 2023 um 16:47:16 + schrieb Richard Purdie : On Mon, 2023-01-16 at 17:43 +0100, Markus Volk wrote: Signed-off-by: Markus Volk > ---

Re: [oe-core][PATCH] neard: dont pull in wpa-supplicant unconditionally

On Mon, 2023-01-16 at 17:43 +0100, Markus Volk wrote: > Signed-off-by: Markus Volk > --- > meta/recipes-connectivity/neard/neard_0.18.bb | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/meta/recipes-connectivity/neard/neard_0.18.bb >

[oe-core][PATCH] neard: dont pull in wpa-supplicant unconditionally

Signed-off-by: Markus Volk --- meta/recipes-connectivity/neard/neard_0.18.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-connectivity/neard/neard_0.18.bb b/meta/recipes-connectivity/neard/neard_0.18.bb index 23e999acc4..17dbfc4378 100644 ---

Re: [OE-core] [PATCH 6/7] gdk-pixbuf: remove ptest support

On Mon 16. Jan 2023 at 17.10, Ross Burton wrote: > On 13 Jan 2023, at 14:56, Alexander Kanavin via lists.openembedded.org > wrote: > > > > Moving to x86-64-v3 instructions revealed that the recipe was doing an > entirely > > incorrect thing: running native gdk-pixbuf-query-loaders executable >

Re: [OE-core] [kirkstone][PATCH] gcc: Fix build with musl and usrmerge on arm

On Mon, Jan 16, 2023 at 5:31 AM Khem Raj wrote: > > > > On Sun, Jan 15, 2023 at 10:59 PM Pavel Zhukov wrote: >> >> Backport fix from master to allow gcc to use proper linker path for >> musl [Yocto #14977] > > > Lgtm Hi Khem, Which of the two versions of the fix do you prefer that I take?

Re: [OE-core] [PATCH 6/7] gdk-pixbuf: remove ptest support

On 13 Jan 2023, at 14:56, Alexander Kanavin via lists.openembedded.org wrote: > > Moving to x86-64-v3 instructions revealed that the recipe was doing an > entirely > incorrect thing: running native gdk-pixbuf-query-loaders executable against > the target set > of loader .so binaries. This

Re: [OE-core] [PATCH] mesa: update submitted patch with backported version

Kai: can you please test it on ubuntu-18.04? I've tested it with DEBUG_BUILD in native and target build on a host with new toolchain (gentoo with gcc-12.2.1) and according to https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17439 it works with old toolchain as well. On Mon, Jan 16, 2023

Re: [OE-core] [kirkstone][PATCH 1/1] gcc: Refactor linker patches and fix linker on arm with usrmerge

On Sun, Jan 15, 2023 at 11:56 PM Pavel Zhukov wrote: > Backport fix from master to allow gcc to use proper linker path for > musl [Yocto #14977]. Lgtm > > Fixes: > | qemu-arm: Could not open '/lib/ld-musl-armhf.so.1': No such file or > directory > > Signed-off-by: Pavel Zhukov > --- >

Re: [OE-core] [kirkstone][PATCH] gcc: Fix build with musl and usrmerge on arm

On Sun, Jan 15, 2023 at 10:59 PM Pavel Zhukov wrote: > Backport fix from master to allow gcc to use proper linker path for > musl [Yocto #14977] Lgtm > > > Fixes: > | qemu-arm: Could not open '/lib/ld-musl-armhf.so.1': No such file or > directory > > Signed-off-by: Pavel Zhukov > --- >

[OE-core] [PATCH] mesa: update submitted patch with backported version

* this version was merged to main in: https://gitlab.freedesktop.org/mesa/mesa/-/commit/267dd1f4d571ee606141aa66f1665aa152b4e911 and cherry-picked to staging/23.0 as well in: https://gitlab.freedesktop.org/mesa/mesa/-/commit/54cfb552abc50e8167cdc46d87455a9a414d7c65 and as a bonus it

Re: [OE-core] [PATCH] rust: Upgrade 1.66.0 -> 1.66.1

Rust community said the security fixes are only for the current stable relases. https://internals.rust-lang.org/t/cargo-cve-2022-46176-fix-for-older-releases/18152/3?u=sundeep-kokkonda For old release we've to backport the patches ourselves. So, for the Kirkstone & Langdale we've to back port the

[OE-core] [PATCH 4/4] linux-yocto/5.15: update to v5.15.87

From: Bruce Ashfield Updating to the latest korg -stable release that comprises the following commits: d57287729e22 Linux 5.15.87 24186c682288 drm/mgag200: Fix PLL setup for G200_SE_A rev >=4 e326ee018a24 io_uring: Fix unsigned 'res' comparison with zero in io_fixup_rw_res()

[OE-core] [PATCH 2/4] linux-yocto/6.1: qemuriscv32: Enable CONFIG_NONPORTABLE

From: Bruce Ashfield Integrating the following commit(s) to linux-yocto/.: 30825f43170 qemuriscv32: Enable CONFIG_NONPORTABLE [ Allow configurations that result in non-portable kernels, this is required for rv32 kernels starting 6.0+ see [1] [1]

[OE-core] [PATCH 3/4] linux-yocto/6.1: update to v6.1.5

From: Bruce Ashfield Updating to the latest korg -stable release that comprises the following commits: 90ca7a874a90 Linux 6.1.5 177055b94fb5 wifi: ath11k: Send PME message during wakeup from D3cold 15f818d4b682 efi: random: combine bootloader provided RNG seed with RNG protocol

[OE-core] [PATCH 1/4] linux-yocto/6.1: edgerouter: Replace OCTEON_USB with USB_OCTEON_HCD

From: Bruce Ashfield The OCTEON_USB has been converted into USB_OCTEON_HCD by mainline commit 9dbdac024d4d ("staging: octeon-usb: move driver out of staging"). So adjust the BSP cfg according to that change. Signed-off-by: Kevin Hao Signed-off-by: Bruce Ashfield ---

[OE-core] [PATCH 0/4] kernel-yocto: pull request

From: Bruce Ashfield Richard, Two -stable updates, and configuration tweaks that should remove the warnings from Kevin's h/w reference version bump. Once these merge, I'll follow up with default kernel version changes and remove 5.19 from master. Bruce The following changes since commit

Re: [OE-core][kirkstone 03/11] ffmpeg: fix for CVE-2022-3109

> Not sure why this didn't show up in my testing! It's shown only when do_patch task is really executed and it doesn't cause the do_patch to fail completely. So it's possible that you've built it once with the warning/error shown and then the next time you were doing the final test for kirkstone

Re: [OE-core][kirkstone 03/11] ffmpeg: fix for CVE-2022-3109

On Mon, Jan 16, 2023 at 4:32 AM Steve Sakoman via lists.openembedded.org wrote: > > On Mon, Jan 16, 2023 at 2:00 AM Martin Jansa wrote: > > > > This patch doesn't apply cleanly on ffmpeg-5.0.1: > > Thanks for the review Martin. > > Not sure why this didn't show up in my testing! But since

Re: [OE-core][kirkstone 03/11] ffmpeg: fix for CVE-2022-3109

On Mon, Jan 16, 2023 at 2:00 AM Martin Jansa wrote: > > This patch doesn't apply cleanly on ffmpeg-5.0.1: Thanks for the review Martin. Not sure why this didn't show up in my testing! But since Richard hasn't taken the pull request yet I will remove this patch from the current pull request and

[OE-core] [PATCH] devtool: fix devtool finish when gitmodules file is empty

From: Thomas Roos When a .gitmodules file is exsisting, but empty then devtool finish fails. This fix is adding an additional check for this. [YOCTO #14999] Signed-off-by: Thomas Roos --- meta/classes/externalsrc.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH v2] webkitgtk: fix perl-native dependency

From: Ovidiu Panait Currently, perl-native is missing from DEPENDS for webkitgtk even though perlnative bbclass is inherited. This happens because the DEPENDS variable is reassigned right after perlnative class is inherited: inherit perlnative (DEPENDS += "perl-native") ... DEPENDS = " \

Re: [OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

MAGIC=... was added in the first place to the native rpm 4.x wrapper by me because rpm links with libmagic (which is a part of file recipe/component), and libmagic would try to find it in file's recipe-specific sysroot if not overridden from environment. I'd say the right fix would be to make

Re: [OE-core] [PATCH] oe-setup-build: add a tool for discovering config templates and setting up builds

On Thu, 2022-11-10 at 10:24 +0100, Alexander Kanavin wrote: > This is the last (I believe) piece of the puzzle in setting up builds from > nothing > without having to write custom scripts or use external tools. > > After layers have been fetched and placed into their respective locations, > one

Re: [OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

The use case I was fixing in: https://git.openembedded.org/openembedded-core/commit/?id=f40a2658f5be6739c5dddab7f9f11e1f85a17102 was just about rpmdeps not being able to find rpmrc due to wrong path in the wrapper. MAGIC was moved to environment-setup.d/rpm.sh just to set all variables (which

Re: [OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

Richard, I'm going to check how rpm uses 'file' and will come up with a better solution. Martin, could you please tell me your use case, if convenient? I will ensure I don't break it. Regards, Qi -Original Message- From: Richard Purdie Sent: Monday, January 16, 2023 7:14 PM To: Chen,

Re: [OE-core] [PATCH v2] rust: Merge all rustc-source patches into rust-source.inc

Adding 'IMAGE_INSTALL:append = " packagegroup-core-buildessential" ' fixed this linker issue. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#175980): https://lists.openembedded.org/g/openembedded-core/message/175980 Mute This Topic:

[OE-core] [PATCH][kirkstone] ffmpeg: refresh patches to apply cleanly

* the last patch added in: https://git.openembedded.org/openembedded-core/commit/?h=kirkstone=874b72fe259cd3a23f4613fccfe2e9cc3f79cd6a doesn't apply cleanly. * fixes: ERROR: ffmpeg-5.0.1-r0 do_patch: Fuzz detected: Applying patch 0001-avcodec-vp3-Add-missing-check-for-av_malloc.patch

Re: [OE-core][kirkstone 03/11] ffmpeg: fix for CVE-2022-3109

This patch doesn't apply cleanly on ffmpeg-5.0.1: ERROR: ffmpeg-5.0.1-r0 do_patch: Fuzz detected: Applying patch 0001-avcodec-vp3-Add-missing-check-for-av_malloc.patch patching file libavcodec/vp3.c Hunk #1 succeeded at 2677 with fuzz 1 (offset -2 lines). The context lines in the patches can

[OE-core] [PATCH] cve-check: write the cve manifest to IMGDEPLOYDIR

From: Jermain Horsman When building an image cve_check_write_rootfs_manifest() would sometimes fail with a FileNotFoundError when writing the manifest.cve due to the parent directory (DEPLOY_DIR_IMAGE) not (yet) existing. The image task will provide the manifest in the deploy directory

Re: [OE-core] [PATCH] rust: Upgrade 1.66.0 -> 1.66.1

Topic created on Rust community https://internals.rust-lang.org/t/cargo-cve-2022-46176-fix-for-older-releases/18152 Based on the community feedback we will take a decision for Kirkstone & Langdale branches update. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group.

Re: [OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

On Mon, 2023-01-16 at 10:39 +, Richard Purdie via lists.openembedded.org wrote: > On Mon, 2023-01-16 at 16:48 +0800, Chen Qi wrote: > > For now, running `file' inside SDK errors out. > > file: could not find any valid magic files! > > > > This is because nativesdk-rpm exports MAGIC. So

Re: [OE-core] [PATCH] classes: decode output data to text

That is a good point, looking at the codebase I think that the go-to for dealing with it is using the call to ".decode('utf8')". Thanks, Pawel On Mon, 16 Jan 2023 at 11:01, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Thu, 2022-12-22 at 10:38 +, Pawel Zalewski wrote: > >

Re: [OE-core] [PATCH] classes: decode output data to text

On Thu, 2022-12-22 at 10:38 +, Pawel Zalewski wrote: > The default return value from subprocess.check_output is an encoded byte. > The applied fix will decode the value to a string. > > Signed-off-by: Pawel Zalewski > --- > meta/classes/fs-uuid.bbclass | 2 +- > 1 file changed, 1

Re: [OE-core] [PATCH] classes: decode output data to text

On Fri, 2023-01-06 at 14:32 +0100, Alexander Kanavin wrote: > Now I see what's going on. The fs-uuid class contains two functions: > get_rootfs_uuid, and replace_rootfs_uuid. The former is not used > anywhere, but the latter is. Can you introduce get_rootfs_uuid() into > something in oe-core,

Re: [OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

On Mon, 2023-01-16 at 16:48 +0800, Chen Qi wrote: > For now, running `file' inside SDK errors out. > file: could not find any valid magic files! > > This is because nativesdk-rpm exports MAGIC. So let's > make nativesdk-rpm depend on file for better user > experiences. > > Signed-off-by: Chen

Re: [OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

Acked-by: Martin Jansa On Mon, Jan 16, 2023 at 9:48 AM Chen Qi wrote: > For now, running `file' inside SDK errors out. > file: could not find any valid magic files! > > This is because nativesdk-rpm exports MAGIC. So let's > make nativesdk-rpm depend on file for better user > experiences. >

Re: [OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

Thanks, it's fine then. Alex On Mon, 16 Jan 2023 at 10:26, Chen, Qi wrote: > > This is because the MAGIC var is pointing a file that does not exist. And the > file is provided by nativesdk-file. > > Some of the strace output: > openat(AT_FDCWD, >

Re: [OE-core] [PATCH v2] rust: Merge all rustc-source patches into rust-source.inc

I guess we need to add a target RDEPENDS on gcc as its using that as the linker (possibly interesting upstream commentary https://github.com/rust-lang/rust/issues/71515). I'm just wondering what happens if you have TOOLCHAIN = "clang"? On Mon, Jan 16, 2023 at 7:00 AM Kokkonda, Sundeep wrote: > >

Re: [OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

This is because the MAGIC var is pointing a file that does not exist. And the file is provided by nativesdk-file. Some of the strace output: openat(AT_FDCWD, "/buildarea2/chenqi/builds/build-poky-sysvinit/sdkinst/sysroots/x86_64-pokysdk-linux/usr/share/misc/magic.mgc", O_RDONLY) = -1 ENOENT

Re: [OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

I'm not sure I understand the issue. Why isn't file from the host working properly in the presence of the MAGIC env var? Alex On Mon, 16 Jan 2023 at 09:48, Chen Qi wrote: > > For now, running `file' inside SDK errors out. > file: could not find any valid magic files! > > This is because

Re: [OE-core] [PATCH 1/2] nativesdk-rpm: export RPM_ETCCONFIGDIR and MAGIC in environment like RPM_CONFIGDIR

Hi Martin, This patch is causing a regression: running `file xxx' inside SDK errors out. e.g., sdkinst [3][0] $ file environment-setup-core2-64-poky-linux file: could not find any valid magic files! sdkinst [3][0] $ which file /usr/bin/file I've sent out a patch to fix the issue: rpm: make

[OE-core][PATCH] rpm: make nativesdk-rpm rdepend on nativesdk-file

For now, running `file' inside SDK errors out. file: could not find any valid magic files! This is because nativesdk-rpm exports MAGIC. So let's make nativesdk-rpm depend on file for better user experiences. Signed-off-by: Chen Qi --- meta/recipes-devtools/rpm/rpm_4.18.0.bb | 1 + 1 file