Re: [yocto] Adding openjdk-11 to Yocto

2023-04-03 Thread Richard Leitner via lists.yoctoproject.org
Hi, On Mon, Mar 27, 2023 at 08:13:38PM -0700, Robert Joslyn wrote: > I did send a patch back in February, but never got a response from Richard L: > https://lists.openembedded.org/g/openembedded-devel/message/100934 Sorry, I've seen the patch and the discussion on it, but I'm currently very busy

[yocto] [meta-raspberrypi][PATCH] machines: simplify MACHINEOVERRIDES definitions

2023-04-03 Thread Zachary T Welch
Prepending new definitions should be preferred to assignment, as it is simpler and more conducive to defining new machine configurations that reuse these configurations. --- conf/machine/raspberrypi-cm.conf | 2 +- conf/machine/raspberrypi0-2w-64.conf | 4 ++--

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

2023-04-03 Thread Stephen Jolley
All, YP M+ or high bugs which moved to a new milestone in WW13 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 7600 syslinux: port extX support patches to syslinux community

[yocto] Enhancements/Bugs closed WW13!

2023-04-03 Thread Stephen Jolley
All, The below were the owners of enhancements or bugs closed during the last week! Who Count geoffrey.g...@smile.fr 2 randy.macl...@windriver.com 2 ross.bur...@arm.com 2 yoann.con...@smile.fr 2 fawzi.kha...@smile.fr 1 Grand Total 9 Thanks, Stephen K. Jolley Yocto

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

2023-04-03 Thread Stephen Jolley
All, Below is the list as of top 37 bug owners as of the end of WW13 of who have open medium or higher bugs and enhancements against YP 4.2. There are 143 possible work days left until the final release candidates for YP 4.2 needs to be released. Who Count michael.opdenac...@bootlin.com

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2023-04-03 Thread Stephen Jolley
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:

Re: [yocto] error when try to use sudo command in recipe

2023-04-03 Thread Bruce Ashfield
On Mon, Apr 3, 2023 at 11:42 AM Adrian Dudau wrote: > Hi Khem, > > Thanks for the reply, though I am not sure I fully understand the first > part of your answer. I'm trying to do something similar to the thread > creator, i.e running "podman pull" at build time to populate an image store > that

Re: [yocto] error when try to use sudo command in recipe

2023-04-03 Thread Adrian Dudau
Hi Khem, Thanks for the reply, though I am not sure I fully understand the first part of your answer. I'm trying to do something similar to the thread creator, i.e running "podman pull" at build time to populate an image store that I can later install into the target rootfs. Still, I am

Re: [yocto] error when try to use sudo command in recipe

2023-04-03 Thread Khem Raj
On Mon, Apr 3, 2023 at 12:25 AM wrote: > On Mon, Feb 6, 2023 at 01:13 AM, Richard Purdie wrote: > Hi Richard, > > Jumping on this thread to provide some clarifications as I hit the same > bug. > I can confirm that this is not an environment issue. I could reproduce it > by adding a sudo call in

[yocto] [meta-security][v2][PATCH] krill: forced to inclued fetch hashes.

2023-04-03 Thread Armin Kuster
Now manditory via Poky commit: https://git.yoctoproject.org/poky/commit/bitbake/lib/bb/fetch2?id=4d9886e1435dba3785973cc920865f8ab67e644d used cargo-update-recipe-crates to fixup Drop krill.inc in favor of new crate file name Signed-off-by: Armin Kuster --- [V2] Add missing new file ---

[yocto] [meta-security][PATCH] krill: forced to inclued fetch hashes.

2023-04-03 Thread Armin Kuster
Now manditory via Poky commit: https://git.yoctoproject.org/poky/commit/bitbake/lib/bb/fetch2?id=4d9886e1435dba3785973cc920865f8ab67e644d used cargo-update-recipe-crates to fixup Drop krill.inc in favor of new crate file name Signed-off-by: Armin Kuster --- recipes-security/krill/krill.inc

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-03 Thread Armin Kuster
On 4/3/23 6:53 AM, Anton Antonov wrote: On Sat, Apr 1, 2023 at 05:50 AM, Armin Kuster wrote: parsec-service 1.1.0 fails to compile with latest tpm2-tss update in meta-security: Thanks for the update. This patch is currently in a test build. Just a note. If this

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-03 Thread Anton Antonov
On Sat, Apr 1, 2023 at 05:50 AM, Armin Kuster wrote: > > >> parsec-service 1.1.0 fails to compile with latest tpm2-tss update >> in meta-security: > > Thanks for the update. > This patch is currently in a test build. > Just a note. If this version ends up being the official one being >

Re: [yocto] [meta-security][PATCH v3] parsec-service: update from 1.1.0 to 1.2.0-rc1

2023-04-03 Thread Anton Antonov
On Sat, Apr 1, 2023 at 05:50 AM, Armin Kuster wrote: > > >> parsec-service 1.1.0 fails to compile with latest tpm2-tss update >> in meta-security: > > Thanks for the update. > This patch is currently in a test build. > Just a note. If this version ends up being the official one being >

Re: [yocto] error when try to use sudo command in recipe

2023-04-03 Thread adrian . dudau
On Mon, Feb 6, 2023 at 01:13 AM, Richard Purdie wrote: Hi Richard, Jumping on this thread to provide some clarifications as I hit the same bug. I can confirm that this is not an environment issue. I could reproduce it by adding a sudo call in an empty recipe like this: SUMMARY = "" HOMEPAGE =