[OE-core] [PATCH] gstreamer1.0-plugins-bad: fix msdk pkgconfig build failure

Error log: | Run-time dependency libmfx found: YES 1.34 | Has header "mfx/mfxdefs.h" : YES | | ../gst-plugins-bad-1.18.2/sys/msdk/meson.build:75:2: ERROR: Include dir /usr/include/mfx does not exist. | | A full log can be found at /home/s When msdk is enable in PACKAGECONFIG, plugin fails to

[OE-core] [PATCH] libyaml: Enable static lib on native/nativesdk

Helps building static tools which depend on libyaml during build or shipped with SDK libyaml is MIT licensed so static linking would not be as prohibitive Signed-off-by: Khem Raj --- meta/recipes-support/libyaml/libyaml_0.2.5.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git

[OE-core] [PATCH 1/2] qemu-system-native: install qmp python module

The qmp python module supports the Qemu Machine Protocol [0]. This module needs to be installed in a known location so the qemurunner python script can find the qmp module. This change causes it to be installed in the recipe-sysroot-native of the target image and that directory can be added to

[OE-core] [PATCH 0/2] Enable QMP Dumping for testimage

This is the second pass at enabling getting debug information from QEMU via the Qemu Machine Protocol interface. The Qemu source provides a qmp.py module which I install in the recipe-sysroot-native location. The initial commands that I issue to qmp with a failure is detected is: query-status and

[OE-core] [PATCH] qemurunner: Add support for qmp commands

This adds support for the Qemu Machine Protocol [0] extending the current dump process for Host and Target. The commands are added in the testimage.bbclass. Currently, we setup qemu to stall until qmp gets connected and sends the initialization and continue commands, this works correctly. With

[OE-core] [PATCH 2/2] qemurunner: Add support for qmp commands

This adds support for the Qemu Machine Protocol [0] extending the current dump process for Host and Target. The commands are added in the testimage.bbclass. Currently, we setup qemu to stall until qmp gets connected and sends the initialization and continue commands, this works correctly. With

[OE-core][dunfell 00/12] Pull request (cover letter only)

The following changes since commit af4fbea9a1656bdf95d85831cae13cae3a60d5ee: patch: fix CVE-2019-20633 (2021-01-04 04:50:23 -1000) are available in the Git repository at: git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next

[OE-core] [PATCH 3/4] linux-yocto/5.4: update to v5.4.87

From: Bruce Ashfield Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: b3f656a592f3 Linux 5.4.87 41ae3e574ccf dm verity: skip verity work if I/O error when system is shutting down 8b3c00977264 ALSA: pcm: Clear the full allocated

[OE-core] [PATCH 2/4] linux-yocto/5.10: update to v5.10.5

From: Bruce Ashfield Updating linux-yocto/5.10 to the latest korg -stable release that comprises the following commits: f5247949c0a9 Linux 5.10.5 12d377b93eef device-dax: Fix range release aceb8ae8e3b1 ext4: avoid s_mb_prefetch to be zero in individual scenarios aff18aa806fd dm

[OE-core] [PATCH 4/4] linux-yocto/5.10/cfg: x86 and beaglebone config fixes

From: Bruce Ashfield Integrating the following commit(s) to the linux-yocto config: 47c7a3148a4 soc/skylake: remove CONFIG_SND_SOC_INTEL_SST_ACPI 8124c015448 features/security: remove CONFIG_REFCOUNT_FULL 7073e149653 media-usb-tv: remove CONFIG_VIDEO_USBVISION 4480a5c5784

[OE-core] [PATCH 1/4] linux-yocto/5.10: update to v5.10.4

From: Bruce Ashfield Updating linux-yocto/5.10 to the latest korg -stable release that comprises the following commits: b1313fe517ca Linux 5.10.4 700d098acec5 x86/CPU/AMD: Save AMD NodeId as cpu_die_id bb25fd492693 drm/edid: fix objtool warning in drm_cvt_modes() c13edadf1029

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

From: Bruce Ashfield Richard, Here's the next set of -stable and configuration tweaks for the reference kernels. I'm holding back the 5.8 removal just a bit longer, since I want to see that these + the 5.10 hardware reference bumps aren't causing issues before I shake that branch. Cheers,

[OE-core] [PATCH] libpam: remove entries for pam_tally and pam_tally2

Both were removed in 1.5.0 and one should use pam_faillock [1] [1] https://github.com/linux-pam/linux-pam/releases/tag/v1.5.0 Signed-off-by: Andreas Müller --- meta/recipes-extended/pam/libpam_1.5.1.bb | 2 -- 1 file changed, 2 deletions(-) diff --git

Re: [OE-core] [RFC PATCH 1/1] classes/npm: utilize lockfile in do_fetch to avoid multiconfig problems

> > But it would happen even without multiconfig, if there is overlap in > > the node modules that two recipes try to fetch. For some reason the > > npmsw fetcher (or the proxy fetcher it is using, see > > bitbake/lib/bb/fetch2/npmsw.py around lines 168-181) are not guarding > > against two

Re: [OE-core] [PATCH] binutils: upgrade 2.35 -> 2.35.1

This change is fine, they are bugfix release only. and yes they can be backported to release as well. On 1/12/21 8:29 AM, Alexander Kanavin wrote: Maybe Khem also has a patch in progress? This update has been pending for a while. Alex On Tue, 12 Jan 2021 at 16:33, Mikko Rapeli

Re: [OE-core] [meta-oe][PATCH v5] procps: split ps and sysctl into individual packages

On 1/12/2021 9:09 AM, Ross Burton wrote: > On Wed, 16 Dec 2020 at 22:16, Sinan Kaya wrote: >> Move the ps and sysctl tools into its own package. Useful for >> size constrained systems that only want the ps and/or sysctl tools. > Both of these are part of busybox. If you're in massively size >

Re: [OE-core] [RFC PATCH 1/1] classes/npm: utilize lockfile in do_fetch to avoid multiconfig problems

On Tue, 2021-01-12 at 17:53 +, chris.lapla...@agilent.com wrote: > Hi Richard, > > > > > > > +do_fetch[lockfiles] += "${DL_DIR}/npm2_fetch.lock" > > > + > > >  def npm_global_configs(d): > > >  """Get the npm global configuration""" > > >  configs = [] > > > > If its just multilib,

Re: [OE-core] [RFC PATCH 1/1] classes/npm: utilize lockfile in do_fetch to avoid multiconfig problems

Hi Richard, > > > > +do_fetch[lockfiles] += "${DL_DIR}/npm2_fetch.lock" > > + > > def npm_global_configs(d): > > """Get the npm global configuration""" > > configs = [] > > If its just multilib, you could put a ${BPN} in the lock name? or is it > conflicting > general recipes?

Re: [OE-core] [RFC PATCH 1/1] classes/npm: utilize lockfile in do_fetch to avoid multiconfig problems

On Tue, 2021-01-12 at 11:53 -0500, Chris Laplante via lists.openembedded.org wrote: > From: Chris Laplante > > The npmsw fetcher doesn't play nice with multiconfig for some reason. > Concurrent do_fetch tasks for npm recipes can try to download modules at > the same time to ${DL_DIR}/npm2,

Re: [OE-core] [PATCH] rootfs_ipk: allow do_populate_sdk in parallel to do_rootfs

Hi RP, I would trust your judgement call here, I understand not taking this type of patch in to avoid complicating the ipk package management. We will soon start running in our CI essentially the dunfell patch soon so we can test for race conditions quite heavily there. But given the

[OE-core] [RFC PATCH 1/1] classes/npm: utilize lockfile in do_fetch to avoid multiconfig problems

From: Chris Laplante The npmsw fetcher doesn't play nice with multiconfig for some reason. Concurrent do_fetch tasks for npm recipes can try to download modules at the same time to ${DL_DIR}/npm2, resulting in races and failed downloads. Signed-off-by: Chris Laplante ---

[OE-core] [RFC PATCH 0/1] Workaround for npm + multiconfig

From: Chris Laplante I didn't have time to dig into the npmsw fetcher to understand exactly why the conflicts happen, but this fixes things in the meantime. Chris Laplante (1): classes/npm: utilize lockfile in do_fetch to avoid multiconfig problems meta/classes/npm.bbclass | 2 ++ 1

Re: [OE-core] [PATCH] binutils: upgrade 2.35 -> 2.35.1

Maybe Khem also has a patch in progress? This update has been pending for a while. Alex On Tue, 12 Jan 2021 at 16:33, Mikko Rapeli wrote: > Hi, > > Would be nice to know a bit more of the update, e.g. a changelog summary > and wether API/ABI changes are in it. > > It's important to know if the

[OE-core] Yocto Project Status WW02`21

Current Dev Position: YP 3.3 M2 development Next Deadline: 18th January 2021 YP 3.3 M2 build Next Team Meetings: * Bug Triage meeting Thursday Jan. 14th at 7:30am PDT (

Re: [OE-core] [PATCH] binutils: upgrade 2.35 -> 2.35.1

Hi, Would be nice to know a bit more of the update, e.g. a changelog summary and wether API/ABI changes are in it. It's important to know if the patch is also needed in stable branches. Cheers, -Mikko -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online

Re: [OE-core] [meta-oe][PATCH v5] procps: split ps and sysctl into individual packages

On Wed, 16 Dec 2020 at 22:16, Sinan Kaya wrote: > Move the ps and sysctl tools into its own package. Useful for > size constrained systems that only want the ps and/or sysctl tools. Both of these are part of busybox. If you're in massively size constrained systems, why not just use busybox?

Re: [OE-core] [PATCH] rootfs_ipk: allow do_populate_sdk in parallel to do_rootfs

On Tue, 2021-01-12 at 09:21 +, Richard Purdie via lists.openembedded.org wrote: > On Mon, 2021-01-11 at 13:45 +0100, Michael Ho wrote: > > From: Michael Ho > > > > Switch do_populate_sdk for the ipk package manager to use a separate target > > opkg config file and separate the lockfiles

Re: [OE-core] [PATCH] rootfs_ipk: allow do_populate_sdk in parallel to do_rootfs

On Tue, 12 Jan 2021 at 09:21, Richard Purdie wrote: > > On Mon, 2021-01-11 at 13:45 +0100, Michael Ho wrote: > > From: Michael Ho > > > > Switch do_populate_sdk for the ipk package manager to use a separate target > > opkg config file and separate the lockfiles restricting do_rootfs and > >

[OE-core] [PATCH] ffmpeg: Fix CVE-2020-35964, CVE-2020-35965

From: Khairul Rohaizzat Jamaluddin Backport the CVE patches from upstream: https://github.com/FFmpeg/FFmpeg/commit/27a99e2c7d450fef15594671eef4465c8a166bd7 https://github.com/FFmpeg/FFmpeg/commit/3e5959b3457f7f1856d997261e6ac672bba49e8b CVE: CVE-2020-35964 CVE-2020-35965 Signed-off-by: Khairul

Re: [OE-core] [PATCH] socat: upgrade 1.7.3.4 ->1.7.4.0

On Tue, 12 Jan 2021 at 02:03, Wang Mingyu wrote: > LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \ > - > file://README;beginline=257;endline=287;md5=338c05eadd013872abb1d6e198e10a3f" > + > file://README;beginline=257;endline=287;md5=82520b052f322ac2b5b3dfdc7c7eea86" >

Re: [OE-core] [PATCH] systemd: use the absolute path in service file

On Tue, 2021-01-12 at 15:42 +0800, Yu, Mingli wrote: > Hi RP, > > On 1/8/21 4:52 PM, Richard Purdie wrote: > > On Fri, 2021-01-08 at 08:40 +, Yu, Mingli wrote: > > > This is just configuration change which defines the absolute path for > > > the command to silence the warning when

Re: [OE-core] [dunfell][PATCH] rootfs_ipk: allow do_populate_sdk in parallel to do_rootfs

On Mon, 2021-01-11 at 13:46 +0100, Michael Ho wrote: > From: Michael Ho > > Switch do_populate_sdk for the ipk package manager to use a separate target > opkg config file and separate the lockfiles restricting do_rootfs and > do_populate_sdk from running in parallel. > > This way if an image

Re: [OE-core] [PATCH] rootfs_ipk: allow do_populate_sdk in parallel to do_rootfs

On Mon, 2021-01-11 at 13:45 +0100, Michael Ho wrote: > From: Michael Ho > > Switch do_populate_sdk for the ipk package manager to use a separate target > opkg config file and separate the lockfiles restricting do_rootfs and > do_populate_sdk from running in parallel. > > This way if an image

[OE-core] [PATCH] license_image.bbclass: fix missing recipeinfo on self

From: Michael Ho Resolve a build bug where image recipes with a do_deploy task will fail. If the image recipe inheriting license_image.bbclass has a deploy task, then the function get_deployed_dependencies will add itself to the list of recipes to get license information for. However, image