date:20230403

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 with other things. I hope I get some time for this topic
within the next 2 weeks.

I'll come back to you as soon I have done some review.

regards;rl

> 
> I’d still like to see it merged, but understand if it’s not what’s wanted in 
> meta-java. I can certainly resend or make changes if desired.
> 
> Thanks,
> Robert
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59608): https://lists.yoctoproject.org/g/yocto/message/59608
Mute This Topic: https://lists.yoctoproject.org/mt/96632702/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[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 ++--
 conf/machine/raspberrypi0-2w.conf| 4 ++--
 conf/machine/raspberrypi0.conf   | 2 +-
 conf/machine/raspberrypi3-64.conf| 2 +-
 conf/machine/raspberrypi4-64.conf| 2 +-
 6 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/conf/machine/raspberrypi-cm.conf b/conf/machine/raspberrypi-cm.conf
index f9371df..365d030 100644
--- a/conf/machine/raspberrypi-cm.conf
+++ b/conf/machine/raspberrypi-cm.conf
@@ -2,7 +2,7 @@
 #@NAME: RaspberryPi Compute Module (CM1)
 #@DESCRIPTION: Machine configuration for the RaspberryPi Compute Module (CM1)
 
-MACHINEOVERRIDES = "raspberrypi:${MACHINE}"
+MACHINEOVERRIDES =. "raspberrypi:"
 include conf/machine/raspberrypi.conf
 
 ARMSTUB ?= "armstub.bin"
diff --git a/conf/machine/raspberrypi0-2w-64.conf 
b/conf/machine/raspberrypi0-2w-64.conf
index 8e4729a..0264107 100644
--- a/conf/machine/raspberrypi0-2w-64.conf
+++ b/conf/machine/raspberrypi0-2w-64.conf
@@ -2,9 +2,9 @@
 #@NAME: RaspberryPi0 2 Wifi Development Board
 #@DESCRIPTION: Machine configuration for the RaspberryPi0 2 Wifi in 64 bits 
mode
 
-include conf/machine/raspberrypi3-64.conf
+MACHINEOVERRIDES =. "raspberrypi3-64:"
 
-MACHINEOVERRIDES := 
"${@'${MACHINEOVERRIDES}'.replace(':${MACHINE}',':raspberrypi3-64:${MACHINE}')}"
+include conf/machine/raspberrypi3-64.conf
 
 MACHINE_EXTRA_RRECOMMENDS += "\
 linux-firmware-rpidistro-bcm43436 \
diff --git a/conf/machine/raspberrypi0-2w.conf 
b/conf/machine/raspberrypi0-2w.conf
index c360d90..cc11b9d 100644
--- a/conf/machine/raspberrypi0-2w.conf
+++ b/conf/machine/raspberrypi0-2w.conf
@@ -2,9 +2,9 @@
 #@NAME: RaspberryPi0 2 Wifi Development Board
 #@DESCRIPTION: Machine configuration for the RaspberryPi0 2 Wifi in 32 bits 
mode
 
-include conf/machine/raspberrypi3.conf
+MACHINEOVERRIDES =. "raspberrypi3:"
 
-MACHINEOVERRIDES := 
"${@'${MACHINEOVERRIDES}'.replace(':${MACHINE}',':raspberrypi3:${MACHINE}')}"
+include conf/machine/raspberrypi3.conf
 
 MACHINE_EXTRA_RRECOMMENDS += "\
 linux-firmware-rpidistro-bcm43436 \
diff --git a/conf/machine/raspberrypi0.conf b/conf/machine/raspberrypi0.conf
index 80297b5..597918a 100644
--- a/conf/machine/raspberrypi0.conf
+++ b/conf/machine/raspberrypi0.conf
@@ -2,7 +2,7 @@
 #@NAME: RaspberryPi Zero Development Board
 #@DESCRIPTION: Machine configuration for the RaspberryPi Zero board 
(https://www.raspberrypi.org/blog/raspberry-pi-zero)
 
-MACHINEOVERRIDES = "raspberrypi:${MACHINE}"
+MACHINEOVERRIDES =. "raspberrypi:"
 include conf/machine/raspberrypi.conf
 
 SERIAL_CONSOLES ?= "115200;ttyAMA0"
diff --git a/conf/machine/raspberrypi3-64.conf 
b/conf/machine/raspberrypi3-64.conf
index 95475f3..ff22f48 100644
--- a/conf/machine/raspberrypi3-64.conf
+++ b/conf/machine/raspberrypi3-64.conf
@@ -2,7 +2,7 @@
 #@NAME: RaspberryPi 3 Development Board
 #@DESCRIPTION: Machine configuration for the RaspberryPi 3 in 64 bits mode
 
-MACHINEOVERRIDES = "raspberrypi3:${MACHINE}"
+MACHINEOVERRIDES =. "raspberrypi3:"
 
 MACHINE_EXTRA_RRECOMMENDS += "\
 linux-firmware-rpidistro-bcm43430 \
diff --git a/conf/machine/raspberrypi4-64.conf 
b/conf/machine/raspberrypi4-64.conf
index 0cf7d51..a6e2073 100644
--- a/conf/machine/raspberrypi4-64.conf
+++ b/conf/machine/raspberrypi4-64.conf
@@ -2,7 +2,7 @@
 #@NAME: RaspberryPi 4 Development Board (64bit)
 #@DESCRIPTION: Machine configuration for the RaspberryPi 4 in 64 bits mode
 
-MACHINEOVERRIDES = "raspberrypi4:${MACHINE}"
+MACHINEOVERRIDES =. "raspberrypi4:"
 
 MACHINE_FEATURES += "pci"
 MACHINE_EXTRA_RRECOMMENDS += "\
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59607): https://lists.yoctoproject.org/g/yocto/message/59607
Mute This Topic: https://lists.yoctoproject.org/mt/98050530/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[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

randy.macl...@windriver.com

sakib.sa...@windriver.com

4.2 M3

4.3 M1


 

  10731

bitbake --observe-only doesn't work with memres

randy.macl...@windriver.com

pa...@zhukoff.net

4.2 M3

4.3 M1


 

  10820

devtool: -d/--debug doesn't show bitbake debug output

randy.macl...@windriver.com

pi...@pidge.org

4.2 M3

4.3 M1


 

  13338

SDK  build fails if image contains bash

randy.macl...@windriver.com

pa...@zhukoff.net

4.2 M3

4.3 M1


 

  14066

bitbake core-image-base -c populate_sdk fails when image contains bash, 
core-utils and package_deb is used

randy.macl...@windriver.com

pa...@zhukoff.net

4.2 M3

4.3 M1


 

  14572

mozjs doesn't build for armv5

randy.macl...@windriver.com

jon.ma...@arm.com

4.2 M3

4.3 M1


 

  14723

patches not applied by devtool when using overrides in SRC_URI

randy.macl...@windriver.com

pi...@pidge.org

4.2 M3

4.3 M1


 

  14745

cve-checker update to support NVD json 5.0 format

randy.macl...@windriver.com

rybczyn...@gmail.com

4.2 M3

4.2 M4


 

  14837

devtool modify doesnt fetch all the crates on rust based recipes

randy.macl...@windriver.com

pi...@pidge.org

4.2 M3

4.3 M1


 

  14938

gitsm fetcher failure when LFS content is present and git smudge fails

randy.macl...@windriver.com

martin.ja...@gmail.com

4.2 M3

4.3 M1


 

  14991

When forcing WARN_QA as ERROR_QA patch-fuzz QA checks are not fatal

randy.macl...@windriver.com

mathew.pro...@gmail.com

4.2 M3

4.3 M1


 

  14995

do_populate_sdk: target-sdk-provides-dummy fails to provide perl for postgresql

randy.macl...@windriver.com

pa...@zhukoff.net

4.2 M3

4.3 M1


 

  15023

Cannot build SDK with api-documentation enabled

randy.macl...@windriver.com

pa...@zhukoff.net

4.2 M3

4.3 M1


 

  15084

For some reason using of same user in two recipes does not work properly

randy.macl...@windriver.com

pa...@zhukoff.net

0.0.0

4.3


 

 

 

 

4.3

4.3 M1


 

  15085

Add a testcase for the devtool add "-b" flag

randy.macl...@windriver.com

fawzi.kha...@smile.fr

0.0.0

4.3 M1


 

  15083

libgcc_s.so wrong file format

randy.macl...@windriver.com

virend...@kpit.com

0.0.0

3.1.25


 

  15088

AB-INT: do_fetch unable to fetch local file

randy.macl...@windriver.com

unassig...@yoctoproject.org

0.0.0

4.3 M1

Thanks, 

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com  

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59606): https://lists.yoctoproject.org/g/yocto/message/59606
Mute This Topic: https://lists.yoctoproject.org/mt/98044298/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[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 Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59605): https://lists.yoctoproject.org/g/yocto/message/59605
Mute This Topic: https://lists.yoctoproject.org/mt/98044271/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[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

33


ross.bur...@arm.com

32


randy.macl...@windriver.com

28


david.re...@windriver.com

25


richard.pur...@linuxfoundation.org

25


bruce.ashfi...@gmail.com

21


jpewhac...@gmail.com

11


pa...@zhukoff.net

10


sakib.sa...@windriver.com

6


pi...@pidge.org

4


tim.orl...@konsulko.com

4


sundeep.kokko...@gmail.com

4


yash.shi...@windriver.com

3


p.lob...@welotec.com

2


alexis.loth...@bootlin.com

2


jon.ma...@arm.com

2


rybczyn...@gmail.com

2


sundeep.kokko...@windriver.com

2


wen.yan@intel.com

1


jens.ge...@desy.de

1


louis.ran...@syslinbit.com

1


tvgamb...@gmail.com

1


mark.asselst...@windriver.com

1


martin.ja...@gmail.com

1


geissona...@yahoo.com

1


thr...@amazon.de

1


pokyli...@reliableembeddedsystems.com

1


hongxu@windriver.com

1


fawzi.kha...@smile.fr

1


fathi.bou...@linaro.org

1


romuald.jea...@st.com

1


st...@sakoman.com

1


frank.wo...@smile.fr

1


mathew.pro...@gmail.com

1


alexandre.bell...@bootlin.com

1


thomas.per...@bootlin.com

1


yashinde...@gmail.com

1


Grand Total

235

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59604): https://lists.yoctoproject.org/g/yocto/message/59604
Mute This Topic: https://lists.yoctoproject.org/mt/98044129/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.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:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 425
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now,  "4.2", "4.3", "4.99" and "Future", the more pressing/urgent
issues being in "4.2" and then "4.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59603): https://lists.yoctoproject.org/g/yocto/message/59603
Mute This Topic: https://lists.yoctoproject.org/mt/98044105/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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 I can later install into the target rootfs.
>
>
FWIW. The above is something that I have almost working, but had to drop
the completion of the support for the upcoming release (it was too late,
and I had to get some kernel changes done). I'm hoping to have something
usable in the next few months.

If you are trying to generate containers (I don't recommend pulling them)
and installing them into a container store that is part of the rootfs, then
collaborating on the meta-virtualization mailing list is a good starting
point.

Bruce



> Still, I am failing to understand why /usr/bin/sudo doesn't show up as
> owned by the root user, even when running under pseudo. Also, why has this
> changed between Dunfell and master and where exactly has the changed
> happened..
>
> Best regards,
> --Adrian
> --
> *From:* Khem Raj 
> *Sent:* Monday, April 3, 2023 4:57 PM
> *To:* Adrian Dudau 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] error when try to use sudo command in recipe
>
> You don't often get email from raj.k...@gmail.com. Learn why this is
> important 
> CAUTION: External Sender - Be cautious when clicking links or opening
> attachments. Please email info...@keyfactor.com with any questions.
>
>
>
> 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 an empty recipe like this:
>
> SUMMARY = ""
> HOMEPAGE = ""
> LICENSE = ""
> SECTION = ""
> DEPENDS = ""
>
> SRC_URI = ""
>
> do_install() {
> ls -l /usr/bin/sudo
> sudo ls -l /usr/bin/sudo
> }
>
>
> Build already use a fake root environment using pseudo to intercept the
> calls so this might not be out of line here. What is the original issue you
> are running into ?
>
>
>
> Running bitbake barebone on my x86 machine produces this error:
>
> | -rwxr-xr-x 1 nobody 65534 232416 Mar  1 13:59 /usr/bin/sudo
> | sudo: /etc/sudo.conf is owned by uid 65534, should be 0
> | sudo: /etc/sudo.conf is owned by uid 65534, should be 0
> | sudo: error in /etc/sudo.conf, line 0 while loading plugin
> "sudoers_policy"
> | sudo: /usr/libexec/sudo/sudoers.so must be owned by uid 0
> | sudo: fatal error, unable to load plugins
>
> Indeed it seems that ownership is broken somehow in the bb environment.
> The issue was introduced somewhere between dunfell and kirkstone. I know
> it's a large timespan but it's a bit time consuming to narrow it down.
>
> Hoping to get some help on this. I would try to investigate further myself
> but I have no idea where to start to be honest.
>
> Best regards,
> --Adrian
>
>
>
>
> 
>
>

-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59602): https://lists.yoctoproject.org/g/yocto/message/59602
Mute This Topic: https://lists.yoctoproject.org/mt/96733939/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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 failing to understand why /usr/bin/sudo doesn't show up as owned by 
the root user, even when running under pseudo. Also, why has this changed 
between Dunfell and master and where exactly has the changed happened..

Best regards,
--Adrian

From: Khem Raj 
Sent: Monday, April 3, 2023 4:57 PM
To: Adrian Dudau 
Cc: yocto@lists.yoctoproject.org 
Subject: Re: [yocto] error when try to use sudo command in recipe

You don't often get email from raj.k...@gmail.com. Learn why this is 
important
CAUTION: External Sender - Be cautious when clicking links or opening 
attachments. Please email info...@keyfactor.com with any questions.



On Mon, Apr 3, 2023 at 12:25 AM 
mailto:adrian.du...@keyfactor.com>> 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 an empty recipe like this:

SUMMARY = ""
HOMEPAGE = ""
LICENSE = ""
SECTION = ""
DEPENDS = ""

SRC_URI = ""

do_install() {
ls -l /usr/bin/sudo
sudo ls -l /usr/bin/sudo
}

Build already use a fake root environment using pseudo to intercept the calls 
so this might not be out of line here. What is the original issue you are 
running into ?



Running bitbake barebone on my x86 machine produces this error:

| -rwxr-xr-x 1 nobody 65534 232416 Mar  1 13:59 /usr/bin/sudo
| sudo: /etc/sudo.conf is owned by uid 65534, should be 0
| sudo: /etc/sudo.conf is owned by uid 65534, should be 0
| sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
| sudo: /usr/libexec/sudo/sudoers.so must be owned by uid 0
| sudo: fatal error, unable to load plugins

Indeed it seems that ownership is broken somehow in the bb environment. The 
issue was introduced somewhere between dunfell and kirkstone. I know it's a 
large timespan but it's a bit time consuming to narrow it down.

Hoping to get some help on this. I would try to investigate further myself but 
I have no idea where to start to be honest.

Best regards,
--Adrian




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59601): https://lists.yoctoproject.org/g/yocto/message/59601
Mute This Topic: https://lists.yoctoproject.org/mt/96733939/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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 an empty recipe like this:
>
> SUMMARY = ""
> HOMEPAGE = ""
> LICENSE = ""
> SECTION = ""
> DEPENDS = ""
>
> SRC_URI = ""
>
> do_install() {
> ls -l /usr/bin/sudo
> sudo ls -l /usr/bin/sudo
> }
>

Build already use a fake root environment using pseudo to intercept the
calls so this might not be out of line here. What is the original issue you
are running into ?


>
> Running bitbake barebone on my x86 machine produces this error:
>
> | -rwxr-xr-x 1 nobody 65534 232416 Mar  1 13:59 /usr/bin/sudo
> | sudo: /etc/sudo.conf is owned by uid 65534, should be 0
> | sudo: /etc/sudo.conf is owned by uid 65534, should be 0
> | sudo: error in /etc/sudo.conf, line 0 while loading plugin
> "sudoers_policy"
> | sudo: /usr/libexec/sudo/sudoers.so must be owned by uid 0
> | sudo: fatal error, unable to load plugins
>
> Indeed it seems that ownership is broken somehow in the bb environment.
> The issue was introduced somewhere between dunfell and kirkstone. I know
> it's a large timespan but it's a bit time consuming to narrow it down.
>
> Hoping to get some help on this. I would try to investigate further myself
> but I have no idea where to start to be honest.
>
> Best regards,
> --Adrian
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59600): https://lists.yoctoproject.org/g/yocto/message/59600
Mute This Topic: https://lists.yoctoproject.org/mt/96733939/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[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
---
 recipes-security/krill/krill-crates.inc | 550 
 recipes-security/krill/krill.inc| 279 
 recipes-security/krill/krill_0.12.3.bb  |   4 +-
 3 files changed, 552 insertions(+), 281 deletions(-)
 create mode 100644 recipes-security/krill/krill-crates.inc
 delete mode 100644 recipes-security/krill/krill.inc

diff --git a/recipes-security/krill/krill-crates.inc 
b/recipes-security/krill/krill-crates.inc
new file mode 100644
index 000..85830ec
--- /dev/null
+++ b/recipes-security/krill/krill-crates.inc
@@ -0,0 +1,550 @@
+# Autogenerated with 'bitbake -c update_crates krill'
+
+# from Cargo.lock
+SRC_URI += " \
+crate://crates.io/addr2line/0.17.0;name=addr2line-0.17.0 \
+crate://crates.io/adler/1.0.2;name=adler-1.0.2 \
+crate://crates.io/adler32/1.2.0;name=adler32-1.2.0 \
+crate://crates.io/aho-corasick/0.7.18;name=aho-corasick-0.7.18 \
+
crate://crates.io/android_system_properties/0.1.5;name=android_system_properties-0.1.5
 \
+crate://crates.io/ansi_term/0.12.1;name=ansi_term-0.12.1 \
+crate://crates.io/ascii/1.0.0;name=ascii-1.0.0 \
+crate://crates.io/ascii-canvas/3.0.0;name=ascii-canvas-3.0.0 \
+crate://crates.io/atty/0.2.14;name=atty-0.2.14 \
+crate://crates.io/autocfg/1.1.0;name=autocfg-1.1.0 \
+crate://crates.io/backoff/0.3.0;name=backoff-0.3.0 \
+crate://crates.io/backtrace/0.3.66;name=backtrace-0.3.66 \
+crate://crates.io/base64/0.13.0;name=base64-0.13.0 \
+crate://crates.io/basic-cookies/0.1.4;name=basic-cookies-0.1.4 \
+crate://crates.io/bcder/0.7.0;name=bcder-0.7.0 \
+crate://crates.io/bit-set/0.5.2;name=bit-set-0.5.2 \
+crate://crates.io/bit-vec/0.6.3;name=bit-vec-0.6.3 \
+crate://crates.io/bitflags/1.3.2;name=bitflags-1.3.2 \
+crate://crates.io/block-buffer/0.9.0;name=block-buffer-0.9.0 \
+crate://crates.io/block-buffer/0.10.2;name=block-buffer-0.10.2 \
+crate://crates.io/bumpalo/3.10.0;name=bumpalo-3.10.0 \
+crate://crates.io/bytes/1.1.0;name=bytes-1.1.0 \
+crate://crates.io/cc/1.0.73;name=cc-1.0.73 \
+crate://crates.io/cfg-if/1.0.0;name=cfg-if-1.0.0 \
+crate://crates.io/chrono/0.4.22;name=chrono-0.4.22 \
+crate://crates.io/chunked_transfer/1.4.0;name=chunked_transfer-1.4.0 \
+crate://crates.io/cipher/0.2.5;name=cipher-0.2.5 \
+crate://crates.io/clap/2.34.0;name=clap-2.34.0 \
+crate://crates.io/codespan-reporting/0.11.1;name=codespan-reporting-0.11.1 
\
+crate://crates.io/core-foundation/0.9.3;name=core-foundation-0.9.3 \
+crate://crates.io/core-foundation-sys/0.8.3;name=core-foundation-sys-0.8.3 
\
+crate://crates.io/cpufeatures/0.2.2;name=cpufeatures-0.2.2 \
+crate://crates.io/crc32fast/1.3.2;name=crc32fast-1.3.2 \
+crate://crates.io/crunchy/0.2.2;name=crunchy-0.2.2 \
+crate://crates.io/crypto-common/0.1.6;name=crypto-common-0.1.6 \
+crate://crates.io/crypto-mac/0.10.1;name=crypto-mac-0.10.1 \
+crate://crates.io/cryptoki/0.3.0;name=cryptoki-0.3.0 \
+crate://crates.io/cryptoki-sys/0.1.4;name=cryptoki-sys-0.1.4 \
+crate://crates.io/ctrlc/3.2.2;name=ctrlc-3.2.2 \
+crate://crates.io/cxx/1.0.79;name=cxx-1.0.79 \
+crate://crates.io/cxx-build/1.0.79;name=cxx-build-1.0.79 \
+crate://crates.io/cxxbridge-flags/1.0.79;name=cxxbridge-flags-1.0.79 \
+crate://crates.io/cxxbridge-macro/1.0.79;name=cxxbridge-macro-1.0.79 \
+crate://crates.io/derivative/2.2.0;name=derivative-2.2.0 \
+crate://crates.io/deunicode/0.4.3;name=deunicode-0.4.3 \
+crate://crates.io/diff/0.1.13;name=diff-0.1.13 \
+crate://crates.io/digest/0.9.0;name=digest-0.9.0 \
+crate://crates.io/digest/0.10.3;name=digest-0.10.3 \
+crate://crates.io/dirs-next/2.0.0;name=dirs-next-2.0.0 \
+crate://crates.io/dirs-sys-next/0.1.2;name=dirs-sys-next-0.1.2 \
+crate://crates.io/either/1.7.0;name=either-1.7.0 \
+crate://crates.io/ena/0.14.0;name=ena-0.14.0 \
+crate://crates.io/encoding_rs/0.8.31;name=encoding_rs-0.8.31 \
+crate://crates.io/enum-display-derive/0.1.1;name=enum-display-derive-0.1.1 
\
+crate://crates.io/enum-flags/0.1.8;name=enum-flags-0.1.8 \
+crate://crates.io/error-chain/0.11.0;name=error-chain-0.11.0 \
+crate://crates.io/fastrand/1.7.0;name=fastrand-1.7.0 \
+crate://crates.io/fern/0.5.9;name=fern-0.5.9 \
+crate://crates.io/fixedbitset/0.4.2;name=fixedbitset-0.4.2 \
+crate://crates.io/fnv/1.0.7;name=fnv-1.0.7 \
+crate://crates.io/foreign-types/0.3.2;name=foreign-types-0.3.2 \
+
crate://crates.io/foreign-types-shared/0.1.1;name=foreign-types-shared-0.1.1 \
+crate://crates.io/form_urlencoded/1.0.1;name=form_urlencoded-1.0.1 \
+

[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   | 279 -
 recipes-security/krill/krill_0.12.3.bb |   4 +-
 2 files changed, 2 insertions(+), 281 deletions(-)
 delete mode 100644 recipes-security/krill/krill.inc

diff --git a/recipes-security/krill/krill.inc b/recipes-security/krill/krill.inc
deleted file mode 100644
index 22fe269..000
--- a/recipes-security/krill/krill.inc
+++ /dev/null
@@ -1,279 +0,0 @@
-# Auto-Generated by cargo-bitbake 0.3.16
-#
-
-# please note if you have entries that do not begin with crate://
-# you must change them to how that package can be fetched
-SRC_URI += " \
-crate://crates.io/addr2line/0.17.0 \
-crate://crates.io/adler/1.0.2 \
-crate://crates.io/adler32/1.2.0 \
-crate://crates.io/aho-corasick/0.7.18 \
-crate://crates.io/android_system_properties/0.1.5 \
-crate://crates.io/ansi_term/0.12.1 \
-crate://crates.io/ascii-canvas/3.0.0 \
-crate://crates.io/ascii/1.0.0 \
-crate://crates.io/atty/0.2.14 \
-crate://crates.io/autocfg/1.1.0 \
-crate://crates.io/backoff/0.3.0 \
-crate://crates.io/backtrace/0.3.66 \
-crate://crates.io/base64/0.13.0 \
-crate://crates.io/basic-cookies/0.1.4 \
-crate://crates.io/bcder/0.7.0 \
-crate://crates.io/bit-set/0.5.2 \
-crate://crates.io/bit-vec/0.6.3 \
-crate://crates.io/bitflags/1.3.2 \
-crate://crates.io/block-buffer/0.10.2 \
-crate://crates.io/block-buffer/0.9.0 \
-crate://crates.io/bumpalo/3.10.0 \
-crate://crates.io/bytes/1.1.0 \
-crate://crates.io/cc/1.0.73 \
-crate://crates.io/cfg-if/1.0.0 \
-crate://crates.io/chrono/0.4.22 \
-crate://crates.io/chunked_transfer/1.4.0 \
-crate://crates.io/cipher/0.2.5 \
-crate://crates.io/clap/2.34.0 \
-crate://crates.io/codespan-reporting/0.11.1 \
-crate://crates.io/core-foundation-sys/0.8.3 \
-crate://crates.io/core-foundation/0.9.3 \
-crate://crates.io/cpufeatures/0.2.2 \
-crate://crates.io/crc32fast/1.3.2 \
-crate://crates.io/crunchy/0.2.2 \
-crate://crates.io/crypto-common/0.1.6 \
-crate://crates.io/crypto-mac/0.10.1 \
-crate://crates.io/cryptoki-sys/0.1.4 \
-crate://crates.io/cryptoki/0.3.0 \
-crate://crates.io/ctrlc/3.2.2 \
-crate://crates.io/cxx-build/1.0.79 \
-crate://crates.io/cxx/1.0.79 \
-crate://crates.io/cxxbridge-flags/1.0.79 \
-crate://crates.io/cxxbridge-macro/1.0.79 \
-crate://crates.io/derivative/2.2.0 \
-crate://crates.io/deunicode/0.4.3 \
-crate://crates.io/diff/0.1.13 \
-crate://crates.io/digest/0.10.3 \
-crate://crates.io/digest/0.9.0 \
-crate://crates.io/dirs-next/2.0.0 \
-crate://crates.io/dirs-sys-next/0.1.2 \
-crate://crates.io/either/1.7.0 \
-crate://crates.io/ena/0.14.0 \
-crate://crates.io/encoding_rs/0.8.31 \
-crate://crates.io/enum-display-derive/0.1.1 \
-crate://crates.io/enum-flags/0.1.8 \
-crate://crates.io/error-chain/0.11.0 \
-crate://crates.io/fastrand/1.7.0 \
-crate://crates.io/fern/0.5.9 \
-crate://crates.io/fixedbitset/0.4.2 \
-crate://crates.io/fnv/1.0.7 \
-crate://crates.io/foreign-types-shared/0.1.1 \
-crate://crates.io/foreign-types/0.3.2 \
-crate://crates.io/form_urlencoded/1.0.1 \
-crate://crates.io/fslock/0.2.1 \
-crate://crates.io/futures-channel/0.3.21 \
-crate://crates.io/futures-core/0.3.21 \
-crate://crates.io/futures-executor/0.3.21 \
-crate://crates.io/futures-io/0.3.21 \
-crate://crates.io/futures-macro/0.3.21 \
-crate://crates.io/futures-sink/0.3.21 \
-crate://crates.io/futures-task/0.3.21 \
-crate://crates.io/futures-util/0.3.21 \
-crate://crates.io/futures/0.3.21 \
-crate://crates.io/generic-array/0.14.5 \
-crate://crates.io/getrandom/0.2.7 \
-crate://crates.io/gimli/0.26.2 \
-crate://crates.io/h2/0.3.13 \
-crate://crates.io/hashbrown/0.12.3 \
-crate://crates.io/hermit-abi/0.1.19 \
-crate://crates.io/hex/0.4.3 \
-crate://crates.io/hmac/0.10.1 \
-crate://crates.io/http-body/0.4.5 \
-crate://crates.io/http/0.2.8 \
-crate://crates.io/httparse/1.7.1 \
-crate://crates.io/httpdate/1.0.2 \
-crate://crates.io/hyper-tls/0.5.0 \
-crate://crates.io/hyper/0.14.20 \
-crate://crates.io/iana-time-zone-haiku/0.1.1 \
-crate://crates.io/iana-time-zone/0.1.51 \
-crate://crates.io/idna/0.2.3 \
-crate://crates.io/impl-trait-for-tuples/0.2.2 \
-crate://crates.io/indexmap/1.9.1 \
-crate://crates.io/instant/0.1.12 \
-crate://crates.io/intervaltree/0.2.7 \
-crate://crates.io/ipnet/2.5.0 \
-crate://crates.io/itertools/0.10.3 \
-crate://crates.io/itoa/1.0.2 \
-crate://crates.io/jmespatch/0.3.0 \
-

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 version ends up being the official one being
supported in the upcoming 4.2 release, when parsec-service 1.2.0
official drops and is added, we will need to us "EPOCH" as I
believe "-rc1" being dropped will signal the version going backwards.

I think Parsec would fail to be built with this patch after these 
patches in OE-core:


https://git.yoctoproject.org/poky/commit/?id=2b12c58724d250d1faf24072128e2de75dfe2c15

https://git.yoctoproject.org/poky/commit/?id=4d9886e1435dba3785973cc920865f8ab67e644d



Yep, I am dealing with this on two other rust recipes. Fun.

-armin


Updates for cargo-update-recipe-crates are under review and the 1.2.0 
release recipe would solve the issue.


Cheers,

Anton







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59597): https://lists.yoctoproject.org/g/yocto/message/59597
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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
> supported in the upcoming 4.2 release, when parsec-service 1.2.0 official
> drops and is added, we will need to us "EPOCH" as I believe "-rc1" being
> dropped will signal the version going backwards.

I think Parsec would fail to be built with this patch after these patches in 
OE-core:

https://git.yoctoproject.org/poky/commit/?id=2b12c58724d250d1faf24072128e2de75dfe2c15

https://git.yoctoproject.org/poky/commit/?id=4d9886e1435dba3785973cc920865f8ab67e644d

Updates for cargo-update-recipe-crates are under review and the 1.2.0 release 
recipe would solve the issue.

Cheers,

Anton

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59596): https://lists.yoctoproject.org/g/yocto/message/59596
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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
> supported in the upcoming 4.2 release, when parsec-service 1.2.0 official
> drops and is added, we will need to us "EPOCH" as I believe "-rc1" being
> dropped will signal the version going backwards.

We're planning to include Parsec 1.2.0 release into 4.2. I'm not sure what to 
do with this rc1 recipes tbh.

Miko, can you wait for the Parsec release?

Cheers,

Anton

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59595): https://lists.yoctoproject.org/g/yocto/message/59595
Mute This Topic: https://lists.yoctoproject.org/mt/97876594/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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 = ""
LICENSE = ""
SECTION = ""
DEPENDS = ""

SRC_URI = ""

do_install() {
ls -l /usr/bin/sudo
sudo ls -l /usr/bin/sudo
}

Running bitbake barebone on my x86 machine produces this error:

| -rwxr-xr-x 1 nobody 65534 232416 Mar  1 13:59 /usr/bin/sudo
| sudo: /etc/sudo.conf is owned by uid 65534, should be 0
| sudo: /etc/sudo.conf is owned by uid 65534, should be 0
| sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
| sudo: /usr/libexec/sudo/sudoers.so must be owned by uid 0
| sudo: fatal error, unable to load plugins

Indeed it seems that ownership is broken somehow in the bb environment. The 
issue was introduced somewhere between dunfell and kirkstone. I know it's a 
large timespan but it's a bit time consuming to narrow it down.

Hoping to get some help on this. I would try to investigate further myself but 
I have no idea where to start to be honest.

Best regards,
--Adrian

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59594): https://lists.yoctoproject.org/g/yocto/message/59594
Mute This Topic: https://lists.yoctoproject.org/mt/96733939/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding openjdk-11 to Yocto

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

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

[yocto] Enhancements/Bugs closed WW13!

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

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

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

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

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

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

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

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

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

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

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

15 matches

Site Navigation

Mail list logo

Footer information