Date   

VS: VS: [yocto] Make do_image_complete wait for an earlier task

Mikko Murto
 

-----Alkuperäinen viesti-----
Lähettäjä: Richard Purdie <richard.purdie@...>
Lähetetty: tiistai 18. toukokuuta 2021 12.19
There is no direct dependency from do_image_complete on the do_create_spdx
tasks.

You can add:

do_rootfs[recrdeptask] += "do_create_spdx"

but this will have the side effect that the build will never use sstate and always
rebuild since that task isn't an sstate task.
Thanks, I'll give that a go!

I did have a quick look and you're going further than I'd been thinking of, at least
initially.

What I'm thinking of in core YP initially is to have do_packagedata generate
SPDX data for the output packaged files in do_package/do_packagedata. I
noticed you go further and process all the input sources and I'm not sure we're
ready to do that yet.

Doing it at do_package/do_packagedata time would still access any of the
sources included from a debug perspective, hence it should correctly find the
shipped manifest/license info without the complexity of having to scan all the
sources

For your level of source scanning, I'd look at the existing do_populate_lic task
which is sstate and generates license info. I think I'd be in favour of totally
replacing that with something generating spdx output...
I'll give do_populate_lic task a look.

I'm actually hoping we could simply what we're doing today however the more I
look at all the information you can put into SPDX, the more I worry that whilst
we can generate tons of data and huge SPDX files, I'm not sure they're actually
useful to anyone to actually use :/.
We're working on this as a part of a workflow that utilizes the SPDX files. Our tool uploads the source code archived by the layer to a Fossology instance, after which it queries Fossology's API for the file level license and copyright data. We then utilize OSS Review Toolkit by converting the SPDX file to ORT's data format and use ORT's Evaluator and Reporter to evaluate license compliance and create notice files and other reports.

This is done to evaluate the image not based on the declared licenses of packages, which may omit some licenses of individual files, but those individual files.

For the SBOM information, we do need to somehow make something as useful
as our normal manifest to people for this to be useful and adopted, at least from
my perspective.
The huge SPDX files created might indeed not be super useful for all use cases. Long term, some kind of configurability regarding e.g. the level of granularity (packages vs. files) could enable the layer to be used for more use cases than the one we're currently working on.

Mikko


[meta-zephyr][PATCH 2/2] zephyr-kernel-src.inc: set default preferred version to 2.6.0-rc1

Wojciech Zmuda
 

From: Zbigniew Bodek <zbigniew.bodek@...>

Signed-off-by: Zbigniew Bodek <zbigniew.bodek@...>
---
recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
index 5ee40d4..9fc08ba 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -2,7 +2,7 @@ LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc"

# Default to a stable version
-PREFERRED_VERSION_zephyr-kernel ??= "2.5.0"
+PREFERRED_VERSION_zephyr-kernel ??= "2.6.0-rc1"
include zephyr-kernel-src-${PREFERRED_VERSION_zephyr-kernel}.inc

inherit cmake
--
2.25.1


[meta-zephyr][PATCH 1/2] zephyr-kernel-src-2.6.0-rc1.inc: Add support for zephyr kernel version 2.6.0-rc1

Wojciech Zmuda
 

From: Zbigniew Bodek <zbigniew.bodek@...>

This version can be selected defining
PREFERRED_VERSION_zephyr-kernel ??= "2.6.0-rc1"

Signed-off-by: Zbigniew Bodek <zbigniew.bodek@...>
---
.../zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc | 10 ++++++++++
1 file changed, 10 insertions(+)
create mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc
new file mode 100644
index 0000000..6ea1593
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc
@@ -0,0 +1,10 @@
+SRCREV_FORMAT = "default_cmsis"
+SRCREV_default = "v2.6.0-rc1"
+SRCREV_cmsis = "c3bd2094f92d574377f7af2aec147ae181aa5f8e"
+SRCREV_nordic = "574493fe29c79140df4827ab5d4a23df79d03681"
+SRCREV_stm32 = "f8ff8d25aa0a9e65948040c7b47ec67f3fa300df"
+SRCREV_open-amp = "6010f0523cbc75f551d9256cf782f173177acdef"
+SRCREV_libmetal = "39d049d4ae68e6f6d595fce7de1dcfc1024fb4eb"
+SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
+
+PV = "2.6.0-rc1+git${SRCPV}"
--
2.25.1


[meta-zephyr][PATCH 0/2] Update Zephyr version to 2.6.0-rc1

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@...>

2.6.0-rc1 has been released 9 days ago and contains a vast number
of improvements. Release notes available here:
https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.6.0-rc1

I'm sending this patch set on behalf of the original author
Zbigniew Bodek <zbigniew.bodek@...>

Zbigniew Bodek (2):
zephyr-kernel-src-2.6.0-rc1.inc: Add support for zephyr kernel version
2.6.0-rc1
zephyr-kernel-src.inc: set default preferred version to 2.6.0-rc1

.../zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc | 10 ++++++++++
recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 2 +-
2 files changed, 11 insertions(+), 1 deletion(-)
create mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc

--
2.25.1


[meta-zephyr][PATCH 2/2] nrf52840dk_nrf52840.conf: Add nRF52840 DK support

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@...>

Add support for Nordic Semiconductor nRF52840 Development
Kit board.

This is a generic MACHINE over nRF52 SoC family config
plus PyOCD flashing ability.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@...>
---
conf/machine/nrf52840dk_nrf52840.conf | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 conf/machine/nrf52840dk_nrf52840.conf

diff --git a/conf/machine/nrf52840dk_nrf52840.conf b/conf/machine/nrf52840dk_nrf52840.conf
new file mode 100644
index 0000000..0aa50e0
--- /dev/null
+++ b/conf/machine/nrf52840dk_nrf52840.conf
@@ -0,0 +1,8 @@
+#@TYPE: Machine
+#@NAME: nrf52840dk_nrf52840
+
+#@DESCRIPTION: Machine configuration for Nordic Semiconductor nRF52840 Development Kit.
+
+require conf/machine/include/nrf52.inc
+ZEPHYR_INHERIT_CLASSES += "zephyr-flash-pyocd"
+ARCH_nrf52840dk_nrf52840 = "arm"
--
2.25.1


[meta-zephyr][PATCH 1/2] nrf52832.inc: Rename to nrf52.inc

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@...>

The file is so generic anyway it can be targeted for
the nRF52 family without any harm.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@...>
---
conf/machine/96b-nitrogen.conf | 2 +-
conf/machine/include/{nrf52832.inc => nrf52.inc} | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
rename conf/machine/include/{nrf52832.inc => nrf52.inc} (86%)

diff --git a/conf/machine/96b-nitrogen.conf b/conf/machine/96b-nitrogen.conf
index 998db4c..48f2041 100644
--- a/conf/machine/96b-nitrogen.conf
+++ b/conf/machine/96b-nitrogen.conf
@@ -3,6 +3,6 @@

#@DESCRIPTION: Machine configuration for 96Boards Nitrogen Board.

-require conf/machine/include/nrf52832.inc
+require conf/machine/include/nrf52.inc
ZEPHYR_INHERIT_CLASSES += "zephyr-flash-pyocd"
ARCH_96b-nitrogen = "arm"
diff --git a/conf/machine/include/nrf52832.inc b/conf/machine/include/nrf52.inc
similarity index 86%
rename from conf/machine/include/nrf52832.inc
rename to conf/machine/include/nrf52.inc
index e938aa6..d22f8bc 100644
--- a/conf/machine/include/nrf52832.inc
+++ b/conf/machine/include/nrf52.inc
@@ -1,7 +1,7 @@
#@TYPE: Machine
-#@NAME: nrf52832
+#@NAME: nrf52xxx

-#@DESCRIPTION: Machine configuration for Nordic Semiconductor nRF52832 (Cortex-M4) SoC.
+#@DESCRIPTION: Machine configuration for Nordic Semiconductor nRF52xxx (Cortex-M4) SoC.

require conf/machine/include/tune-cortexm4.inc

--
2.25.1


[meta-zephyr][PATCH 0/2] Add nRF52840 DK support

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@...>

This patch set adds support for Nordic Semiconductor nRF5284
Development Kit board. Since there already is nRF52xx family
chip support added (specifically nRF52832 used in 96Boards
Nitrogen), make this support a bit more generic to cover
the whole family, then add a platform-specific configs
for both nRF-based boards on top of it.

The change has been tested with the actual nRF52840 DK
board by building and flashing with `-c flash_usb`
some sample applications.

Wojciech Zmuda (2):
nrf52832.inc: Rename to nrf52.inc
nrf52840dk_nrf52840.conf: Add nRF52840 DK support

conf/machine/96b-nitrogen.conf | 2 +-
conf/machine/include/{nrf52832.inc => nrf52.inc} | 4 ++--
conf/machine/nrf52840dk_nrf52840.conf | 8 ++++++++
3 files changed, 11 insertions(+), 3 deletions(-)
rename conf/machine/include/{nrf52832.inc => nrf52.inc} (86%)
create mode 100644 conf/machine/nrf52840dk_nrf52840.conf

--
2.25.1


Re: VS: [yocto] Make do_image_complete wait for an earlier task

Richard Purdie
 

On Tue, 2021-05-18 at 07:09 +0000, Mikko Murto wrote:
Lähettäjä: Richard Purdie <richard.purdie@...>
Lähetetty: tiistai 18. toukokuuta 2021 9.57

On Tue, 2021-05-18 at 06:15 +0000, Mikko Murto wrote:
Hi,

I've created a task do_create_spdx that gets some data from packages
after do_package. The task is currently added with `addtask
do_create_spdx after do_package before do_packagedata` The data is
then enriched and combined in do_image_complete by adding the combining
function to IMAGE_POSTPROCESS_COMMAND.
For the most part everything works as expected, but for some packages
do_create_spdx does not complete in time for the combination step in
do_image_complete.
Is there a way for me force do_image_complete to wait for
do_create_spdx to have been completed for all packages?
This seems a little odd since image.bbclass has:

do_rootfs[recrdeptask] += "do_packagedata"

which means do_rootfs should only happen after all do_packagedata have run.
Your task is added before do_packagedata.
do_image and do_image_complete should run after do_rootfs.

I'm wondering if the issue is more to do with reuse of previous build artefacts
where sstate is involved. Does your added task account for sstate?
That is odd indeed. I need to give it another go. As for accounting for sstate, 
no, at least not intentionally.
I don't have much to go on but guessing, if you run some test and then rerun that
test, the second build would come from sstate. If a build comes from sstate, it will 
skip tasks that precede the sstate artefact.

More specifically, if sstate exists for do_packagedata, it would skip any tasks 
preceeding that task including your do_create_spdx task.

There is no direct dependency from do_image_complete on the do_create_spdx tasks.

You can add:

do_rootfs[recrdeptask] += "do_create_spdx"

but this will have the side effect that the build will never use sstate and always
rebuild since that task isn't an sstate task.

I've been giving some thought to SDPX and SBOM during our build process so I
am curious what you're doing, is the work public anywhere?
Public at https://github.com/doubleopen-project/meta-doubleopen. The usual 
disclaimers about PoC-level spaghetti apply; all questions and comments 
very much appreciated! 😊
I did have a quick look and you're going further than I'd been thinking of, at 
least initially.

What I'm thinking of in core YP initially is to have do_packagedata generate SPDX 
data for the output packaged files in do_package/do_packagedata. I noticed you go
further and process all the input sources and I'm not sure we're ready to do that
yet.

Doing it at do_package/do_packagedata time would still access any of the sources
included from a debug perspective, hence it should correctly find the shipped 
manifest/license info without the complexity of having to scan all the sources

For your level of source scanning, I'd look at the existing do_populate_lic task
which is sstate and generates license info. I think I'd be in favour of totally 
replacing that with something generating spdx output...

I'm actually hoping we could simply what we're doing today however the more I look
at all the information you can put into SPDX, the more I worry that whilst we can
generate tons of data and huge SPDX files, I'm not sure they're actually useful
to anyone to actually use :/.

For the SBOM information, we do need to somehow make something as useful as our
normal manifest to people for this to be useful and adopted, at least from my 
perspective.

Cheers,

Richard


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

Sangeeta Jain
 

Hi all,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.3.1.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. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. Beaglebone

ETA for completion is next Thursday, May 20.


Thanks,
Sangeeta

-----Original Message-----
From: qa-build-notification@... <qa-build-
notification@...> On Behalf Of Pokybuild User
Sent: Monday, 17 May, 2021 9:47 PM
To: yocto@...
Cc: qa-build-notification@...
Subject: [qa-build-notification] QA notification for completed autobuilder
build (yocto-3.3.1.rc1)


A build flagged for QA (yocto-3.3.1.rc1) was completed on the autobuilder
and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.3.1.rc1


Build hash information:

bitbake: b67476d4758915db7a5d9f58bc903ae7501a1774
meta-arm: 7ca13b4f15cc8f51d6c99b40b7ffafeb47dce28e
meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
meta-intel: 4d5791d9ff515ba1660234b1987eae4d4e90eeca
meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
oecore: efce6334bf122a64f63d46c1c04e3dbffe298c51
poky: 05a8aad57ce250b124db16705acec557819905ae



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...







VS: [yocto] Make do_image_complete wait for an earlier task

Mikko Murto
 

Lähettäjä: Richard Purdie <richard.purdie@...>
Lähetetty: tiistai 18. toukokuuta 2021 9.57

On Tue, 2021-05-18 at 06:15 +0000, Mikko Murto wrote:
Hi,

I've created a task do_create_spdx that gets some data from packages
after do_package. The task is currently added with `addtask
do_create_spdx after do_package before do_packagedata` The data is
then enriched and combined in do_image_complete by adding the combining
function to IMAGE_POSTPROCESS_COMMAND.
For the most part everything works as expected, but for some packages
do_create_spdx does not complete in time for the combination step in
do_image_complete.
Is there a way for me force do_image_complete to wait for
do_create_spdx to have been completed for all packages?
This seems a little odd since image.bbclass has:

do_rootfs[recrdeptask] += "do_packagedata"

which means do_rootfs should only happen after all do_packagedata have run.
Your task is added before do_packagedata.
do_image and do_image_complete should run after do_rootfs.

I'm wondering if the issue is more to do with reuse of previous build artefacts
where sstate is involved. Does your added task account for sstate?
That is odd indeed. I need to give it another go. As for accounting for sstate, no, at least not intentionally.

I've been giving some thought to SDPX and SBOM during our build process so I
am curious what you're doing, is the work public anywhere?
Public at https://github.com/doubleopen-project/meta-doubleopen. The usual disclaimers about PoC-level spaghetti apply; all questions and comments very much appreciated! 😊

Mikko


Re: Make do_image_complete wait for an earlier task

Richard Purdie
 

On Tue, 2021-05-18 at 06:15 +0000, Mikko Murto wrote:
Hi,

I've created a task do_create_spdx that gets some data from packages after 
do_package. The task is currently added with `addtask do_create_spdx after 
do_package before do_packagedata` The data is then enriched and combined in 
do_image_complete by adding the combining function to IMAGE_POSTPROCESS_COMMAND. 
For the most part everything works as expected, but for some packages 
do_create_spdx does not complete in time for the combination step in do_image_complete. 
Is there a way for me force do_image_complete to wait for do_create_spdx to have been 
completed for all packages?
This seems a little odd since image.bbclass has:

do_rootfs[recrdeptask] += "do_packagedata"

which means do_rootfs should only happen after all do_packagedata have run.
Your task is added before do_packagedata.
do_image and do_image_complete should run after do_rootfs.

I'm wondering if the issue is more to do with reuse of previous build artefacts where
sstate is involved. Does your added task account for sstate?

I've been giving some thought to SDPX and SBOM during our build process
so I am curious what you're doing, is the work public anywhere?

Cheers,

Richard


Make do_image_complete wait for an earlier task

Mikko Murto
 

Hi,

I've created a task do_create_spdx that gets some data from packages after do_package. The task is currently added with `addtask do_create_spdx after do_package before do_packagedata` The data is then enriched and combined in do_image_complete by adding the combining function to IMAGE_POSTPROCESS_COMMAND. For the most part everything works as expected, but for some packages do_create_spdx does not complete in time for the combination step in do_image_complete. Is there a way for me force do_image_complete to wait for do_create_spdx to have been completed for all packages?

Best regards,
Mikko Murto


Re: vlc 3.0.11 package issue

Khem Raj
 

On Mon, May 17, 2021 at 10:57 PM sateesh m <sateesh0457@...> wrote:

Hi ,

I am trying to run vlc-3.0.11 media player on my riscv target board. I am facing problem this package

[cli] lua interface error: Error loading script /usr/lib/vlc/lua/intf/cli.luac: ../../vlc-3.0.11.1/share/lua/modules/common.lua:3: attempt to call a nil value (global 'module')

lua package also I installed version is 5.3.6 .
usually it means lua version mismatch. You might be hitting same issue
as reported here

https://trac.videolan.org/vlc/ticket/25036

there is a patch attached to that ticket. Please try to apply that and
see if it helps.

https://trac.videolan.org/vlc/attachment/ticket/25036/0001-lua-Make-scripts-compatible-to-lua-5.4.patch

How can I fix this issue. Is I need to apply patch for this?if patch is present please give me guidance. Can anybody knows this problem help me.

Thanking you in advance.
--
Regards,
Sateesh


vlc 3.0.11 package issue

sateesh m
 

Hi ,

   I am trying to run vlc-3.0.11 media player on my riscv target board.  I am facing problem this package 

 [cli] lua interface error: Error loading script /usr/lib/vlc/lua/intf/cli.luac: ../../vlc-3.0.11.1/share/lua/modules/common.lua:3: attempt to call a nil value (global 'module')

lua package also I installed version is 5.3.6 .

How can I fix this issue. Is I need to apply patch for this?if patch is present please give me guidance. Can anybody knows this problem help me.

Thanking you in advance.
--
Regards,
Sateesh


vlc 3.0.11 package issue

sateesh m
 

Hi ,

   I am trying to run vlc-3.0.11 media player on my riscv target board.  I am facing problem this package 

 [cli] lua interface error: Error loading script /usr/lib/vlc/lua/intf/cli.luac: ../../vlc-3.0.11.1/share/lua/modules/common.lua:3: attempt to call a nil value (global 'module')

lua package also I installed version is 5.3.6 .

How can I fix this issue. Is I need to apply patch for this?if patch is present please give me guidance. Can anybody knows this problem help me.

Thanking you in advance.
--
Regards,
Sateesh


Enhancements/Bugs closed WW20!

Stephen Jolley
 

All,

 

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

randy.macleod@...

7

richard.purdie@...

5

mhalstead@...

1

timothy.t.orling@...

1

Grand Total

14

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.4

Stephen Jolley
 

All,

Below is the list as of top 50 bug owners as of the end of WW20 of who have open medium or higher bugs and enhancements against YP 3.4.   There are 115 possible work days left until the final release candidates for YP 3.4 needs to be released.

Who

Count

ross@...

31

richard.purdie@...

30

david.reyna@...

22

bruce.ashfield@...

20

michael.opdenacker@...

18

trevor.gamblin@...

13

bluelightning@...

12

JPEWhacker@...

11

timothy.t.orling@...

11

akuster808@...

10

randy.macleod@...

10

sakib.sajal@...

9

kai.kang@...

8

hongxu.jia@...

7

Qi.Chen@...

6

chee.yang.lee@...

6

mingli.yu@...

6

raj.khem@...

5

yi.zhao@...

4

alexandre.belloni@...

3

mostthingsweb@...

3

yf3yu@...

2

jon.mason@...

2

alejandro@...

2

pokylinux@...

2

nicolas.dechesne@...

2

ydirson@...

2

jaewon@...

2

mshah@...

2

mister_rs@...

1

sangeeta.jain@...

1

devendra.tewari@...

1

Martin.Jansa@...

1

shachar@...

1

naveen.kumar.saini@...

1

john.kaldas.enpj@...

1

dl9pf@...

1

prabin.ca@...

1

open.source@...

1

mhalstead@...

1

kexin.hao@...

1

stacygaikovaia@...

1

changqing.li@...

1

yoctoproject@...

1

Nathan.Dunne@...

1

kergoth@...

1

thomas.perrot@...

1

liezhi.yang@...

1

aehs29@...

1

diego.sueiro@...

1

matthewzmd@...

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

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 353 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, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.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.pm@...) 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.pm@...

 


[ANNOUNCEMENT] Yocto Project 3.2.4 (gatesgarth-24.0.4) is Released

Vineela
 

Hello,

 

We are pleased to announce the Yocto Project 3.2.4 (gatesgarth-24.0.4) Release is now available for download.

 

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.4/poky-gatesgarth-24.0.4.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.2.4/poky-gatesgarth-24.0.4.tar.bz2

 

A gpg signed version of these release notes is available at:

 

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.4/RELEASENOTES

 

Full Test Report:

 

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.4/testreport.txt

 

Thank you for everyone's contributions to this release.

 

Vineela Tummalapalli

Yocto Project Build and Release

vineela.tummalapalli@...

 

--------------------------

yocto-3.2.4 Release Notes

--------------------------

 

 

--------------------------

Repositories/Downloads

--------------------------

 

Repository Name: poky

Repository Location: https://git.yoctoproject.org/git/poky

Branch: gatesgarth

Tag: yocto-3.2.4

Git Revision: 60c8482769f38a4db6f38d525405c887794511a9

Release Artefact: poky-gatesgarth-24.0.4

sha: 4e16bf6b800f0891e6c932fecc0d17b771713d9a5f2d38f79a77096636891997

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.4/poky-gatesgarth-24.0.4.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.2.4/poky-gatesgarth-24.0.4.tar.bz2

 

Repository Name: openembedded-core

Repository Location: https://git.openembedded.org/openembedded-core

Branch: gatesgarth

Tag: 2020-10.4-gatesgarth

Git Revision: d47b7cdc3508343349f3bb3eacb2dc3227dd94d2

Release Artefact: oecore-gatesgarth-24.0.4

sha: e0cc7b43260477b83eec7724ae1d0bf6ffe073e80927897ba547073b29c8972d

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.4/oecore-gatesgarth-24.0.4.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.2.4/oecore-gatesgarth-24.0.4.tar.bz2

 

Repository Name: meta-mingw

Repository Location: https://git.yoctoproject.org/git/meta-mingw

Branch: gatesgarth

Tag: yocto-3.2.4

Git Revision: 352d8b0aa3c7bbd5060a4cc2ebe7c0e964de4879

Release Artefact: meta-mingw-gatesgarth-24.0.4

sha: b9b0be763656ec62202a4644976f64a1d58fe9db2113bc3ca0d68bb509336e68

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.4/meta-mingw-gatesgarth-24.0.4.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.2.4/meta-mingw-gatesgarth-24.0.4.tar.bz2

 

Repository Name: meta-gplv2

Repository Location: https://git.yoctoproject.org/git/meta-gplv2

Branch: gatesgarth

Tag: yocto-3.2.4

Git Revision: 6e8e969590a22a729db1ff342de57f2fd5d02d43

Release Artefact: meta-gplv2-gatesgarth-24.0.4

sha: e4809d3b4c37acdc1f38211b0acf52a8d839a856c533e0b15485c11dec158350

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.4/meta-gplv2-gatesgarth-24.0.4.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.2.4/meta-gplv2-gatesgarth-24.0.4.tar.bz2

 

Repository Name: bitbake

Repository Location: https://git.openembedded.org/bitbake

Branch: 1.48

Tag: 2020-10.4-gatesgarth

Git Revision: e05d79a6ed92c9ce17b90fd5fb6186898a7b3bf8

Release Artefact: bitbake-gatesgarth-24.0.4

sha: a6374818045135d710f557b2789699c12418adf9139287d863f8667c06b395d2

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.4/bitbake-gatesgarth-24.0.4.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.2.4/bitbake-gatesgarth-24.0.4.tar.bz2

 

Repository Name: yocto-docs

Repository Location: https://git.yoctoproject.org/git/yocto-docs

Branch: gatesgarth

Tag: yocto-3.2.4

Git Revision:657ce3c16b7ffecd0246b7386b7cb5e0d50ee9fb

 

-------------

Contributors

-------------

Anatol Belski

Anton D. Kachalov

Anuj Mittal

Bruce Ashfield

Changqing Li

Chen Qi

Christopher Larson

Dorinda Bassey

Douglas Royds

Gavin Li

Guillaume Champagne

hongxu

Khem Raj

Konrad Weihmann

Lee Chee Yang

Marek Vasut

Mark Hatle

Martin Jansa

Michael Halstead

Michael Trensch

Mikko Rapeli

Mingli Yu

Minjae Kim

Niels Avonds

Peter Budny

Peter Kjellerstedt

Petr Vorel

Richard Purdie

Ross Burton

Sangeeta Jain

Stefan Ghinea

Stephen Jolley

Yi Zhao

 

---------------

Known Issues

---------------

failure in ptest : ptestresult.lttng-tools.tools: This is not a regression and has a fix to disable it.

 

 

---------------

Security Fixes

---------------

gdk-pixbuf: fix CVE-2021-20240

cairo: fix CVE-2020-35492

rsync: fix CVE-2020-14387

busybox: fix CVE-2021-28831

wpa-supplicant: fix CVE-2021-30004

cve-check: CVE_VERSION_SUFFIX to work with patched release

cve-update-db-native: consider version suffix when update CVE db

openssl: update to 1.1.1k to fix CVE-2021-3450 and CVE-2021-3449

git: fix CVE-2021-21300

 

 

---------------

Fixes

---------------

build-appliance-image: Update to gatesgarth head revision

poky.conf: bump version for 3.2.4 release

documentation: prepare for 3.2.4 release

populate_sdk_ext: Avoid copying and producing .pyc files

linux-firmware: Package RSI 911x WiFi firmware

yocto-check-layer: Avoid bug when iterating and autoadding dependencies

deb: apply postinstall on sdk

bitbake: fetch/gitsm: Fix crash when using git LFS and submodules

bitbake: runqueue: Fix deferred task issues

bitbake: bitbake-server: ensure server timeout is a float

sanity: Further improve directory sanity tests

kmod: do not symlink config.guess/config.sub during autoreconf

ca-certificates: Fix openssl runtime cert dependencies

linux-yocto/5.4: fix arm defconfig warnings

linux-yocto/5.4: update to v5.4.112

linux-yocto/5.4: update to v5.4.111

linux-yocto/5.4: update to v5.4.109

cve-update-db-native: skip on empty cpe23Uri

bitbake: cooker: Include all packages a recipe provides in SkippedPackage.rprovides

bitbake: cache: Make CoreRecipeInfo include rprovides_pkg for skipped recipes

externalsrc: Detect code changes in submodules

insane: clean up some more warning messages

sanity: Add error check for '%' in build path

oeqa/selftest: Hardcode test assumptions about heartbeat event timings

lib/oe/terminal: Fix tmux new-session on older tmux versions (<1.9)

pseudo: Upgrade to add trailing slashes ignore path fix

image-live.bbclass: optional depends when ROOTFS empty

image,populate_sdk_base: move 'func' flag setting for sdk command vars

buildhistory: add missing vardepsexcludes

libtool: make sure autoheader run before autoconf

documentation-audit.sh: Fix typo in specifying LICENSE_FLAGS_WHITELIST

run-postinsts: do not remove postinsts directory.

linux-firmware: Fix packaging

selftest/wic: Fix dependency issue in rawcopy test

scripts/verify-bashisms: Update checkbashisms.pl URL

devshell.bbclass: Exceptions displayed within devpyshell

linux-yocto/5.4: update to v5.4.107

linux-yocto/5.4: update to v5.4.105

binutils: backport fix for gold with theads enabled from 2.36.0

glibc: Pull latest 2.32 HEAD


Re: Statically linked libraries and license manifest

Khem Raj
 

On 5/17/21 10:44 AM, Jasper Orschulko wrote:
Hi,
my question more or less reiterates the following:
https://www.yoctoproject.org/pipermail/yocto/2018-July/041854.html
I am trying to find a way to list statically linked libraries in the
license manifest, but so far I am at a loss. To my understanding Yocto
does not understand packages included using DEPENDS and not RDEPENDS as
part of the resulting image, however technically source code from the
dependee can (and will) end up on the image as part of the dependent
package. This is a serious issue from a legal point of view, as the
developer ultimately might end up with an incomplete list of licenses,
when relying on the Yocto license manifest.
Please, do correct me if I'm wrong :)
partly yes. there is a provision to disable static linking using DISABLE_STATIC, so atleast some of packages can be cleared of. depends are effective during build time and its the linking which decides on static vs dynamic linking and bitbake does not have much control over that but you can perhaps easily write a probe and extract this information from linker cmdline perhaps by dumping linker map and post processing it.




4241 - 4260 of 57773