[yocto] M+ & H bugs with Milestone Movements WW19

All, YP M+ or high bugs which moved to a new milestone in WW19 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 14905 Error in compiling rustfmt does not cause do_compile to fail randy.macl

[yocto] Enhancements/Bugs closed WW19!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macl...@windriver.com 1 Grand Total 1 Thanks, Stephen K. Jolley Yocto Project Program Manager *Cell:(208) 244-4460 * Email: sjolley.yp...@gmail.com

[yocto] Current high bug count owners for Yocto Project 4.3

All, Below is the list as of top 36 bug owners as of the end of WW19 of who have open medium or higher bugs and enhancements against YP 4.3. There are 114 possible work days left until the final release candidates for YP 4.3 needs to be released. Who Count ross.bur...@arm.com 33 michael.

[yocto] 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: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc

[yocto] [meta-selinux][PATCH] selinux: Set CVE_PRODUCT

The CVE product name for selinux-* package is (usually) the selinux (and not our recipe name), so use selinux as the default. See also: http://lists.openembedded.org/pipermail/openembedded-core/2017-July/139897.html "Results from cve-check are not very good at the moment. One of the reasons for t

[yocto] [meta-tensorflow][PATCH] bazel.bbclass: Fix build with bazel from sstate-cache

Random errors can occur when bazel is taken from sstate-cache and the dynamic loader is no longer available. Setting DYNAMIC_LOADER and letting populate_sysroot_setscene modify the UNINATIVE_LOADER is not enough. That way we just modify the loader of bazel binary, but bazel is also a self-extractin

Re: [yocto] [dunfell][PATCH] pypi.bbclass: Set CVE_PRODUCT to PYPI_PACKAGE

This patch should go to openembedded-c...@lists.openembedded.org . Thanks, Ross > On 15 May 2023, at 11:55, Sanjaykumar kantibhai Chitroda -X (schitrod - > E-INFO CHIPS INC at Cisco) via lists.yoctoproject.org > wrote: > > From: Alex Kiernan

[yocto] [dunfell][PATCH] pypi.bbclass: Set CVE_PRODUCT to PYPI_PACKAGE

From: Alex Kiernan The CVE product name for PyPI packages is (usually) the same as the PyPI package name (and not our recipe name), so use that as the default. Signed-off-by: Alex Kiernan Signed-off-by: Alex Kiernan Signed-off-by: Richard Purdie (cherry picked from commit 61f6b0ad09bf87cdc2d3

Re: [yocto] OTA Updates

Hi Hassan, Am Donnerstag, dem 11.05.2023 um 20:03 +0530 schrieb MOHAMMED HASSAN: > Hi all, > So I am referring this page for OTA updates  > https://wiki.yoctoproject.org/wiki/System_Update > > However are these all paid or free services. Any more info about these > services is welcomed.  > Also

Re: [yocto][meta-python2] Kirkstone EXTRANATIVEPATH is not in effect

Yes. Everything works fine after I inherit pythonnative. I mistakenly thought that there was no need to inhert it manually. Martin Jansa 于2023年5月15日周一 17:46写道： > > > I don't know why my EXTRANATIVEPATH doesn't contain python-native > > Because you didn't inherit pythonnative? > > On Mon, May 15,

Re: [yocto][meta-python2] Kirkstone EXTRANATIVEPATH is not in effect

> I don't know why my EXTRANATIVEPATH doesn't contain python-native Because you didn't inherit pythonnative? On Mon, May 15, 2023 at 11:38 AM Jiliang Cai wrote: > I added: > DEPENDS += "python-native python-setuptools-native". > > I think it should work just fine, because: > python-setuptools.b

Re: [yocto][meta-python2] Kirkstone EXTRANATIVEPATH is not in effect

I added: DEPENDS += "python-native python-setuptools-native". I think it should work just fine, because: python-setuptools.bbinherit setuptools --> setuptools.bbclass inherit distutils --> distutils.bbclass inherit distutils-base --> distutils-base.bbclass inherit pytho

Re: [yocto] LTS EOLs

Regardless of the current situation with EOL dates, the point of upgrading is not that, but one's ability to fulfil current and future business requirements and keep products secure. This is always easier with a more recent stack for the target and tooling on the build host. Alex On Mon, 15 May 2

Re: [yocto][meta-python2] Kirkstone EXTRANATIVEPATH is not in effect

Did you add "inherit pythonnative" or DEPENDS += "python-native"? You need just the inherit line. On Mon, May 15, 2023 at 10:23 AM Jiliang Cai wrote: > I have a bb file abc_1.0.bb: > DEPENDS += "python3-native" > And EXTRANATIVEPATH contains "python3-native" as expected, so command > 'python3'

[yocto][meta-python2] Kirkstone EXTRANATIVEPATH is not in effect

I have a bb file abc_1.0.bb: DEPENDS += "python3-native" And EXTRANATIVEPATH contains "python3-native" as expected, so command 'python3' can be searched. Then I add DEPENDS += "python-native", but EXTRANATIVEPATH doesn't contains "python-native", so command 'python' can not be searched. python3na

Re: [yocto] LTS EOLs

> On 15 May 2023, at 00:55, Tom Isaacson via lists.yoctoproject.org > wrote: > > I was just looking up the Yocto LTS and I found > https://endoflife.date/yocto. It says: > 3.1 'Dunfell' (LTS) Ends in 10 months (01 Apr 2024) > 4.0 'Kirkstone' (LTS) Ends in 11 months (27 Apr 2024) FWIW, eol.dat