Date   

[meta-security][PATCH 2/2] python3-privacyidea: update to 3.6.2

Armin Kuster
 

Fix license.

Signed-off-by: Armin Kuster <akuster808@...>
---
...hon3-privacyidea_3.5.2.bb => python3-privacyidea_3.6.2.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename recipes-security/mfa/{python3-privacyidea_3.5.2.bb => python3-privacyidea_3.6.2.bb} (95%)

diff --git a/recipes-security/mfa/python3-privacyidea_3.5.2.bb b/recipes-security/mfa/python3-privacyidea_3.6.2.bb
similarity index 95%
rename from recipes-security/mfa/python3-privacyidea_3.5.2.bb
rename to recipes-security/mfa/python3-privacyidea_3.6.2.bb
index 043cbfd..ecfeca6 100644
--- a/recipes-security/mfa/python3-privacyidea_3.5.2.bb
+++ b/recipes-security/mfa/python3-privacyidea_3.6.2.bb
@@ -2,11 +2,11 @@ SUMMARY = "identity, multifactor authentication (OTP), authorization, audit"
DESCRIPTION = "privacyIDEA is an open solution for strong two-factor authentication like OTP tokens, SMS, smartphones or SSH keys. Using privacyIDEA you can enhance your existing applications like local login (PAM, Windows Credential Provider), VPN, remote access, SSH connections, access to web sites or web portals with a second factor during authentication. Thus boosting the security of your existing applications."

HOMEPAGE = "http://www.privacyidea.org/"
-LICENSE = "AGPL-3.0"
+LICENSE = "AGPL-3.0-only"
LIC_FILES_CHKSUM = "file://LICENSE;md5=c0acfa7a8a03b718abee9135bc1a1c55"

PYPI_PACKAGE = "privacyIDEA"
-SRC_URI[sha256sum] = "26aeb0d353af1f212c4df476202516953c20f7f31566cfe0b67cbb553de04763"
+SRC_URI[sha256sum] = "4441282d086331dac0aee336286de8262d9ac8eb11e14b7f9aa69f865caebe17"

inherit pypi setuptools3

--
2.25.1


[meta-security][PATCH 1/2] python3-privacyidea: fix QA ERROR

Armin Kuster
 

ERROR: python3-privacyidea-3.5.2-r0 do_package: QA Issue: python3-privacyidea: Files/directories were installed but not shipped in any package:
/usr/etc
/usr/etc/privacyidea
/usr/etc/privacyidea/dictionary
/usr/etc/privacyidea/privacyideaapp.wsgi

Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-security/mfa/python3-privacyidea_3.5.2.bb | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/recipes-security/mfa/python3-privacyidea_3.5.2.bb b/recipes-security/mfa/python3-privacyidea_3.5.2.bb
index a4ab59d..043cbfd 100644
--- a/recipes-security/mfa/python3-privacyidea_3.5.2.bb
+++ b/recipes-security/mfa/python3-privacyidea_3.5.2.bb
@@ -11,8 +11,6 @@ SRC_URI[sha256sum] = "26aeb0d353af1f212c4df476202516953c20f7f31566cfe0b67cbb553d
inherit pypi setuptools3

do_install:append () {
- #install ${D}/var/log/privacyidea
-
rm -fr ${D}${libdir}/${PYTHON_DIR}/site-packages/tests
}

@@ -21,7 +19,7 @@ GROUPADD_PARAM:${PN} = "--system privacyidea"
USERADD_PARAM:${PN} = "--system -g privacyidea -o -r -d /opt/${BPN} \
--shell /bin/false privacyidea"

-FILES:${PN} += " ${datadir}/etc/privacyidea/* ${datadir}/lib/privacyidea/*"
+FILES:${PN} += " ${prefix}/etc/privacyidea/* ${datadir}/lib/privacyidea/*"

RDEPENDS:${PN} += " bash perl freeradius-mysql freeradius-utils"

--
2.25.1


[ANNOUNCEMENT] Yocto Project 3.3.5 (hardknott-25.0.5) is Released

Lee Chee Yang
 

Hello,

 

We are pleased to announce the Yocto Project 3.3.5 (hardknott-25.0.5) Release is now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.5/poky-hardknott-25.0.5.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.5/poky-hardknott-25.0.5.tar.bz2

 

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

 

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

 

Full Test Report:

 

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

 

Thank you for everyone's contributions to this release.

 

 

Chee Yang Lee chee.yang.lee@...

Yocto Project Build and Release

 

 

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

yocto-3.3.5 Release Notes

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

 

 

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

Repositories/Downloads

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

 

Repository Name: poky

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

Branch: hardknott

Tag: yocto-3.3.5

Git Revision: 8d3e054f6d432b5ca0fcd613e0c767fab3c85f24

Release Artefact: poky-hardknott-25.0.5

sha: f8c0248ea25e7b90a0cf68450835403ca41f386672b9ec2d6f019750b1a185a6

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.5/poky-hardknott-25.0.5.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.5/poky-hardknott-25.0.5.tar.bz2

 

Repository Name: openembedded-core

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

Branch: hardknott

Tag: yocto-3.3.5

Git Revision: 29cd1d796057ef5599fe17c39b42aa099f7b1c29

Release Artefact: oecore-hardknott-25.0.5

sha: f892b4e412ebd780e814abcdf676600ed13de167970f8711ea226066fd4624e6

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.5/oecore-hardknott-25.0.5.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.5/oecore-hardknott-25.0.5.tar.bz2

 

Repository Name: meta-mingw

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

Branch: hardknott

Tag: yocto-3.3.5

Git Revision: 422b96cb2b6116442be1f40dfb5bd77447d1219e

Release Artefact: meta-mingw-hardknott-25.0.5

sha: 8bdf3d62c0974af8bab66a6cbbf70ef5e431c0d4e9eef3acb8da8fef116ca70c

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.5/meta-mingw-hardknott-25.0.5.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.5/meta-mingw-hardknott-25.0.5.tar.bz2

 

Repository Name: meta-gplv2

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

Branch: hardknott

Tag: yocto-3.3.5

Git Revision: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f

Release Artefact: meta-gplv2-hardknott-25.0.5

sha: ee8c5f3ec99177d9a0b8c041f92fc512b4a25bde99750772b119739a4750ccc1

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.5/meta-gplv2-hardknott-25.0.5.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.5/meta-gplv2-hardknott-25.0.5.tar.bz2

 

Repository Name: bitbake

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

Branch: hardknott

Tag: yocto-3.3.5

Git Revision: aaa7f7af23d5f89fe4a5ed48c57ea3dfca07c79d

Release Artefact: bitbake-hardknott-25.0.5

sha: f96a82a79a80cc3581c16ce9dad59f83370801427f9e1b798df02d07c6ac8bb3

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.5/bitbake-hardknott-25.0.5.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.3.5/bitbake-hardknott-25.0.5.tar.bz2

 

Repository Name: yocto-docs

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

Branch: hardknott

Tag: yocto-3.3.5

Git Revision: cba66e3a284b852b0da9a3b53f5f2540244d1072

 

 

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

Known Issues

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

N/A

 

 

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

Security Fixes

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

vim: update to include latest CVE fixes

expat: fix CVE-2022-23852

qemu: fix CVE-2021-20196

qemu: fix CVE-2021-3930

qemu: fix CVE-2021-3748

qemu: fix CVE-2021-3713

lighttpd: backport a fix for CVE-2022-22707

speex: fix CVE-2020-23903

expat: fix CVE-2021-46143

expat: fix CVE-2021-45960

expat fix CVE-2022-22822 through CVE-2022-22827

linux-yocto/5.10: amdgpu: updates for CVE-2021-42327

xserver-xorg: whitelist two CVEs

curl: Backport CVE fixes

libsndfile1: fix CVE-2021-4156

glibc: Backport fix for CVE-2021-43396

busybox: backport patches to fix CVEs

gcc: Fix CVE-2021-42574

grub2: fix CVE-2021-3981

webkitgtk: fix fix CVE-2021-42762

xserver-xorg: update CVE_PRODUCT

binutils: Fix CVE-2021-45078

xserver-xorg: fix CVE-2021-4011

xserver-xorg: fix CVE-2021-4010

xserver-xorg: fix CVE-2021-4009

xserver-xorg: fix CVE-2021-4008

binutils: CVE-2021-42574

gcc: Add CVE-2021-37322 to the list of CVEs to ignore

gmp: fix CVE-2021-43618

squashfs-tools: fix CVE-2021-41072

vim: fix CVE-2021-3927 and CVE-2021-3928

bind: fix CVE-2021-25219

vim: fix CVE-2021-3875

vim: fix CVE-2021-3872 and CVE-2021-3903

rpm: fix CVE-2021-3521

gcc: Fix CVE-2021-35465

inetutils: fix CVE-2021-40491

avahi: update CVE id fixed by local-ping.patch

 

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

Fixes

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

README.OE-Core.md: update URLs

arch-armv8-5a.inc: Add tune include for armv8.5a

armv9a/tune: Add the support for the Neoverse N2 core

binutils: upgrade binutils-2.36 to latest version

bitbake: bitbake: adjust parser error check for python 3.10 compatibility

bitbake: bitbake: correct deprecation warning in process.py

bitbake: bitbake: correct the collections vs collections.abc deprecation

bitbake: bitbake:toaster:test: Update SSTATE URL

bitbake: cooker: Fix task-depends.dot for multiconfig targets

bitbake: cooker: Handle parse threads disappearing to avoid hangs

bitbake: cooker: Handle parsing results queue race

bitbake: cooker: Remove debug code, oops :(

bitbake: cooker: check if upstream hash equivalence server is available

bitbake: fetch/wget: Add timeout for checkstatus calls (30s)

bitbake: fetch2/perforce: Fix typo

bitbake: fetch: Handle mirror user/password replacements correctly

bitbake: hashserv: let asyncio discover the running loop

bitbake: process: Do not mix stderr with stdout

bitbake: runqueue: Fix runall option handling

bitbake: runqueue: Fix runall option task deletion ordering issue

bitbake: tests/fetch: Drop gnu urls from wget connectivity test

bitbake: tests/fetch: Update github urls

bitbake: tests/fetch: Update pcre.org address after github changes

bitbake: utils: Handle lockfile filenames that are too long for filesystems

bitbake: utils: Update to use exec_module() instead of load_module()

build-appliance-image: Update to hardknott head revision

buildhistory: Fix srcrevs output

busybox: upgrade 1.33.1 -> 1.33.2

convert-srcuri.py: use regex to check space in SRC_URI

cross-canadian: correct the location of pkg-config files

cups: Fix missing installation of cups sysv init scripts

cve-check: add lockfile to task

cve-check: create directory of CVE_CHECK_MANIFEST before copy

cve-extra-exclusions: add db CVEs to exclusion list

default-distrovars.inc: Switch connectivity check to a yoctoproject.org page

documentation: conf.py: fix version of bitbake objects.inv

gcc: add aarch64 support for Arm's Neoverse N2 CPU

gcc: add support for Neoverse N2 CPU

gcc: upgrade to gcc-10.3 version

glibc: Fix i586/c3 support

glibc: upgrade glibc-2.33 to latest version

go: upgrade to 1.16.13

lib/oe/reproducible: correctly set .git location when recursively looking for git repos

libpcre/libpcre2: correct SRC_URI

libusb1: correct SRC_URI

linunistring: Add missing gperf-native dependency

linux-firmware: Add CLM blob to linux-firmware-bcm4373 package

linux-firmware: upgrade 20211027 -> 20211216

linux-yocto-rt/5.10: update to -rt56

linux-yocto/5.10/cfg: add kcov feature fragment

linux-yocto/5.10: update genericx86* machines to v5.10.82

linux-yocto/5.10: update to v5.10.99

linux-yocto/5.4: update genericx86* machines to v5.4.158

linux-yocto/5.4: update to v5.4.178

linux-yocto: add libmpc-native to DEPENDS

llvm: bump HASHEQUIV_HASH_VERSION

manuals: releases.rst: move gatesgarth to outdated releases section

meta/scripts: Manual git url branch additions

meta: add explicit branch and protocol to SRC_URI

mirrors: Add kernel.org sources mirror for downloads.yoctoproject.org

mirrors: Add uninative mirror on kernel.org

mklibs-native: drop deprecated cpp17 exceptions

oeqa/parselogs: Fix quoting

oeqa/selftest/bbtests: Use YP sources mirror instead of GNU

openssl: Add reproducibility fix

os-release: Add DISTRO_CODENAME as vardeps for do_compile

patch.py: Initialize git repo before patching

patchelf: fix PT_PHDR program header corruption

pigz: fix one failure of command "unpigz -l"

poky.conf: add debian11 to supported distros

poky.conf: add fedora 34 to supported distros

poky.conf: bump version for 3.3.5 release

populate_sdk_base: remove unneeded dirs such as /dev

pseudo: Add fcntl64 wrapper

pseudo: Add in ability to flush database with shutdown request

python3-pyelftools: Depend on debugger, pprint

python3-pyelftools: fix the override syntax

python3: upgrade to 3.9.9

recipetool: Fix circular reference in SRC_URI

recipetool: Set master branch only as fallback

recipetool: extend curl detection when creating recipes

recipetool: handle GitLab URLs like we do GitHub

ref-manual: fix patch documentation

rootfs-postcommands: update systemd_create_users

runqemu: check the qemu PID has been set before kill()ing it

runtime_test: skip virgl test on fedora 34

scripts/checklayer/common.py: Fixed a minor grammatical error

scripts/convert-srcuri: Backport SRC_URI conversion script from master branch

scripts/lib/wic/help.py: Update Fedora Kickstart URLs

scripts/oe-package-browser: Handle no packages being built

scripts/runqemu-ifdown: Don't treat the last iptables command as special

scripts: Update to use exec_module() instead of load_module()

sdk: fix search for dynamic loader

selftest/devtool: Check branch in git fetch

selftest: reproducible: Set maximum report size

selftest: skip virgl test on centos 8 entirely

selftest: skip virgl test on fedora 34 entirely

socat: update SRC_URI

sstate: A third fix for for touching files inside pseudo

sstate: Account for reserved characters when shortening sstate filenames

sstate: another fix for touching files inside pseudo

tune-cortexa72: Drop the redundant cortexa72-crc tune

tune-cortexa72: Enable the crc extension by default for cortexa72

tune-cortexa72: remove crypto for the default cortex-a72

uboot-sign: fix the concatenation when multiple U-BOOT configurations are specified

uninative: Add version to uninative tarball name

updates for recent releases

vim: upgrade to patch 4269

webkitgtk: Add reproducibility fix

wic: support rootdev identified by partition label

wic: use shutil.which

yocto-check-layer: add debug output for the layers that were found

 

 


Re: Honister on Ubuntu 14.04

Khem Raj
 

On Thu, Mar 3, 2022 at 10:07 AM Daniel Ammann
<daniel.ammann@...> wrote:

Hi,

I'm trying to build honister on Ubuntu 14.04. This is meant as a temporary
solution until the build server can be upgraded to something recent.
For now, I got it running with extended buildtools from poky, but the build of
libnsl2-native fails. It appears that the pkgconfig step is not executed
properly since do_compile fails with a header not found error.

Has anybody done a successful build of honister on Ubuntu 14.04? Is it even
possible?
Honister is newer releases, Always check the tested sanity distros
list for honister ( 3.4.x release)

https://docs.yoctoproject.org/3.4.2/ref-manual/system-requirements.html#detailed-supported-distros

it seems ubuntu 18.04 is oldest tested ubuntu distro.


Kind regards

Daniel

--
bytes at work
Technoparkstrasse 7
CH-8406 Winterthur
Switzerland

phone: +41 52 550 50 67



Re: Honister on Ubuntu 14.04

Josef Holzmayr
 

Howdy!

Just pack a more recent Ubuntu into the container engine of your least dislike - docker usually does the trick well enough if you can go with its license situation, otherwise podman is an interesting option.

Greetz,
Josef

On 3. Mar 2022, at 19:06, Daniel Ammann <daniel.ammann@...> wrote:

Hi,

I'm trying to build honister on Ubuntu 14.04. This is meant as a temporary
solution until the build server can be upgraded to something recent.
For now, I got it running with extended buildtools from poky, but the build of
libnsl2-native fails. It appears that the pkgconfig step is not executed
properly since do_compile fails with a header not found error.

Has anybody done a successful build of honister on Ubuntu 14.04? Is it even
possible?

Kind regards

Daniel

--
bytes at work
Technoparkstrasse 7
CH-8406 Winterthur
Switzerland

phone: +41 52 550 50 67



Honister on Ubuntu 14.04

Daniel Ammann
 

Hi,

I'm trying to build honister on Ubuntu 14.04. This is meant as a temporary
solution until the build server can be upgraded to something recent.
For now, I got it running with extended buildtools from poky, but the build of
libnsl2-native fails. It appears that the pkgconfig step is not executed
properly since do_compile fails with a header not found error.

Has anybody done a successful build of honister on Ubuntu 14.04? Is it even
possible?

Kind regards

Daniel

--
bytes at work
Technoparkstrasse 7
CH-8406 Winterthur
Switzerland

phone: +41 52 550 50 67


[meta-security-isafw][PATCH] meta-security-isafw: Fixes to work with oe-core master

Akshay Bhat
 

Update isafw bbclass to build with oe-core master
- prelink support was dropped in oe-core as part of 23c0be78106f
- do_populate_cve_db was renamed to do_fetch in oe-core as part
of f5f97d33a1703d

Signed-off-by: Akshay Bhat <akshay.bhat@...>
---
meta-security-isafw/classes/isafw.bbclass | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta-security-isafw/classes/isafw.bbclass b/meta-security-isafw/classes/isafw.bbclass
index da6bf76..3854c0f 100644
--- a/meta-security-isafw/classes/isafw.bbclass
+++ b/meta-security-isafw/classes/isafw.bbclass
@@ -105,7 +105,7 @@ python process_reports_handler() {
os.environ["PATH"] = savedenv["PATH"]
}

-do_build[depends] += "cve-update-db-native:do_populate_cve_db ca-certificates-native:do_populate_sysroot"
+do_build[depends] += "cve-update-db-native:do_fetch ca-certificates-native:do_populate_sysroot"
do_build[depends] += "python3-lxml-native:do_populate_sysroot"

# These tasks are intended to be called directly by the user (e.g. bitbake -c)
@@ -179,7 +179,6 @@ fakeroot python do_analyse_image() {
}

do_rootfs[depends] += "checksec-native:do_populate_sysroot ca-certificates-native:do_populate_sysroot"
-do_rootfs[depends] += "prelink-native:do_populate_sysroot"
do_rootfs[depends] += "python3-lxml-native:do_populate_sysroot"

isafw_init[vardepsexclude] = "DATETIME"
--
2.25.1


Minutes: Yocto Project Weekly Triage Meeting 3/3/2022

Trevor Gamblin
 

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage

Attendees: Alexandre, Armin, Daiane, Joshua, Luca, Pavel, Randy, Richard, Saul, Stephen, Steve, Tim, Trevor

ARs:

- Randy to talk to David Reyna about triaging his Toaster Future/3.99 bugs (25)

Notes:

- ~43% of AB workers have been switched to SSDs. Failure rate appears lower, but still TBD. More coming soon!

Medium+ 3.5 Unassigned Enhancements/Bugs: 77 (Last week 71)

Medium+ 3.5 Unassigned Enhancements/Bugs: 6 (new)

Medium+ 3.99 Unassigned Enhancements/Bugs: 38 (Last week 39)

AB Bugs: 71 (Last week 75)


Re: [meta-rockchip][PATCH] layers: Bump to use kirkstone

Trevor Woerner
 



On Thu, Mar 3, 2022 at 2:33 AM Martin Jansa <martin.jansa@...> wrote:
Hi,

can you please create honister branch.

I think 17703ee37b46d15ec369588fbb86dde336df6028 commit (just before this kirkstone change was applied) would be reasonable branching point.

Now there isn't any branch compatible with Honister release.

Done, thanks!
 

Thanks

On Tue, Feb 22, 2022 at 3:16 PM Trevor Woerner <twoerner@...> wrote:
On Mon 2022-02-21 @ 06:28:47 PM, Khem Raj wrote:
> its not going to be backward ABI compatible with honister due to variable renaming.
>
> Signed-off-by: Khem Raj <raj.khem@...>
> ---
>  conf/layer.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to meta-rockchip master and kirkstone.
Thanks!




[PATCH yocto-autobuilder-helper] auh-config: update smtp server to localhost

Alexander Kanavin
 

Current setup only allows sending mail via localhost on alma workers.

Signed-off-by: Alexander Kanavin <alex.kanavin@...>
---
scripts/auh-config/upgrade-helper.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/auh-config/upgrade-helper.conf b/scripts/auh-config/upgrade-helper.conf
index 6255f3f..3a0aa6c 100644
--- a/scripts/auh-config/upgrade-helper.conf
+++ b/scripts/auh-config/upgrade-helper.conf
@@ -9,7 +9,7 @@ blacklist=linux-libc-headers linux-yocto alsa-utils-scripts build-appliance-imag
# only recipes belonging to maintainers in whitelist will be attempted
#maintainers_whitelist=anibal.limon@...
# SMTP server
-smtp=mail.yoctoproject.org:25
+smtp=localhost:25
# from whom should the mails arrive
from=auh@...
# who should get the status mail with statistics, at the end
--
2.35.1


[yocto-autobuilder2][PATCH] config.py: run AUH only on alma8

Alexander Kanavin
 

According to halstead, only those workers are able to send mail
so that it reaches the mailing lists.

Signed-off-by: Alexander Kanavin <alex.kanavin@...>
---
config.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/config.py b/config.py
index a25dfa0..7e15105 100644
--- a/config.py
+++ b/config.py
@@ -143,8 +143,8 @@ workers_bringup = []
workers_wine = ["ubuntu1804-ty-3"]
workers_buildperf = ["perf-ubuntu1604", "perf-centos7"]
workers_arm = ["ubuntu1804-arm-1", "ubuntu2004-arm-1"]
-# workers which don't need buildtools for AUH
-workers_auh = ["ubuntu1804-ty-3", "centos8-ty-1", "centos8-ty-2", "debian10-ty-1"]
+# workers which don't need buildtools for AUH and are able to send email to mailing lists
+workers_auh = ["alma8-ty-1", "alma8-ty-2"]

all_workers = workers + workers_bringup + workers_buildperf + workers_arm

--
2.35.1


Re: [meta-rockchip][PATCH] layers: Bump to use kirkstone

Martin Jansa
 

Hi,

can you please create honister branch.

I think 17703ee37b46d15ec369588fbb86dde336df6028 commit (just before this kirkstone change was applied) would be reasonable branching point.

Now there isn't any branch compatible with Honister release.

Thanks

On Tue, Feb 22, 2022 at 3:16 PM Trevor Woerner <twoerner@...> wrote:
On Mon 2022-02-21 @ 06:28:47 PM, Khem Raj wrote:
> its not going to be backward ABI compatible with honister due to variable renaming.
>
> Signed-off-by: Khem Raj <raj.khem@...>
> ---
>  conf/layer.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to meta-rockchip master and kirkstone.
Thanks!




[meta-gplv2] [PATCH 2/2] disable-gpl3: Update wildcard to new syntax

Richard Purdie
 

INCOMPATIBLE_LICENSE wildcard handling changed in master-next, update
to match.

Signed-off-by: Richard Purdie <richard.purdie@...>
---
conf/distro/include/disable-gplv3.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/distro/include/disable-gplv3.inc b/conf/distro/include/disable-gplv3.inc
index 27cdba2..e8301ce 100644
--- a/conf/distro/include/disable-gplv3.inc
+++ b/conf/distro/include/disable-gplv3.inc
@@ -1,4 +1,4 @@
-INCOMPATIBLE_LICENSE = '*GPLv3*'
+INCOMPATIBLE_LICENSE = 'LGPL-3.0* GPL-3.0*'
WARN_QA:remove = 'incompatible-license'
RDEPENDS:${PN}-ptest:remove:pn-glib-2.0 = "python3-dbusmock"
DISTRO_FEATURES:remove = "ptest"
--
2.32.0


[meta-gplv2] [PATCH 1/2] disable-gplv3: Remove ptest from DISTRO_FEATURES

Richard Purdie
 

There are ptest dependencies which don't have coverage from gplv2 components
so disable ptests for meta-gplv2 usage.

Signed-off-by: Richard Purdie <richard.purdie@...>
---
conf/distro/include/disable-gplv3.inc | 1 +
1 file changed, 1 insertion(+)

diff --git a/conf/distro/include/disable-gplv3.inc b/conf/distro/include/disable-gplv3.inc
index 5d948cc..27cdba2 100644
--- a/conf/distro/include/disable-gplv3.inc
+++ b/conf/distro/include/disable-gplv3.inc
@@ -1,3 +1,4 @@
INCOMPATIBLE_LICENSE = '*GPLv3*'
WARN_QA:remove = 'incompatible-license'
RDEPENDS:${PN}-ptest:remove:pn-glib-2.0 = "python3-dbusmock"
+DISTRO_FEATURES:remove = "ptest"
--
2.32.0


Re: On managing debug and production builds

csimmonds
 

Hi Karthik,

On 02/03/2022 03:22, Karthik Poduval wrote:
This concept of user vs debug builds is there in Android and any
Android developer who gets introduced to yocto may look for these
options. There seem to be many implementation choices here, trying to
summarize some of the options here.
For clarity, I just want to point out that the Android build system does
NOT build the kernel. Linux is built separately and then binary kernel
image and modules are copied into the Android images. So, you get the
same kernel whether you have an eng, userdebug or user build

I mention this because building different kernels for release/debug
seems to be complicating things quite a lot. Maybe that is a separate issue

1. use different image recipes example-image-user.bb vs
example-image-debug.bb but this still poses a problem for kernel
recipes as kernel needs to have different config fragments or
different defconfig for debug vs user variants. One possible option is
to use KTYPE to select tiny vs standard or define own for custom BSP
layers. What about other recipes like u-boot or firmware for other
remote processors, how to percolate the debug vs user options to those
recipes via just an image recipe ?
2. use different configs using multiconfig. Base config (which is
debug) also selects the user config hence always building both build
variants in different tmp directories. Kernel, remote firmware and
image recipes use variables from the multiconfig cof files to decide
whether to build debug or user variants.
3. use different distros. DSITRO=user bitbake example-image,
DISTRO=debug example-image. Kernel and remote firmware recipes use
variables from the distro to decide whether to build debug or user
variants.

Which is the best method ?
All these options seem very BSP layer specific, is there something
more generic and better than the above options ?
If not, should this be a feature request to the Yocto project ?

NOTE: debug variants may include the following.
- more debug related kernel configs and security loosened and UART
ports disabled
- image recipe debug variant may include debug utilities absent from
the user variant

There could be more than just debug and user variants. Android has
engineering, tests, user, tiny and user-debug.

--
Regards,
Karthik Poduval

On Tue, Mar 1, 2022 at 1:26 AM tomzy <tomasz.zyjewski@...> wrote:

Thanks Tomasz. I will check kas.

No problem

Yes, for selecting some of the packages I have created prod and debug image
recipes.But this did not work for the kernel as the kernel recipe is picked
as part of PROVIDERin machine conf.

What are the difference there? You want to use different config on prod and debug images?
Maybe add it as config fragments? Then you would need to add some global variable to
distinguish when use given .cfg file.

[1] https://docs.yoctoproject.org/singleindex.html#creating-configuration-fragments

SoI had to use 2 conf to have the
IMAGE_FEATURES (orany other var)set differently for prod and debug. This is for
building the kernelrecipie differently for prodand debug. Setting the
IMAGE_FEATURES in the image recipe (and not inconf) causes2 problems. One is
that kernel and other bootloaders recipes arepicked early via PROVIDER in conf
and not as packages included in image recipe.

Is that a problem?

Secondly,setting the var in the
image recipe breaks this command for e.g.
"bitbake base-image-prod.bbbase-image-debug.bb".

Didn't you want to distinguish this to builds to be able to run `bitbake base-image-prod` or
`bitbake base-image-debug`?

Since the command parses the recipes only once for both image creation.


Nevertheless I would greatly recommend you to use kas. In simple .yml file you
could prepare different `local.conf` per configuration prod/debug.

[2] https://kas.readthedocs.io/en/latest/userguide.html#project-configuration

Regards,
Tomasz Żyjewski
Embedded Systems Engineer
GPG: 5C495EA3EBEECA59
https://3mdeb.com | @3mdeb_com
Cheers
Chris


Re: On managing debug and production builds

Josef Holzmayr
 

Howdy!

Karthik Poduval <karthik.poduval@...> schrieb am Mi. 2. März 2022 um 04:23:
This concept of user vs debug builds is there in Android and any
Android developer who gets introduced to yocto may look for these
options. There seem to be many implementation choices here, trying to
summarize some of the options here.

1. use different image recipes example-image-user.bb vs
example-image-debug.bb but this still poses a problem for kernel
recipes as kernel needs to have different config fragments or
different defconfig for debug vs user variants. One possible option is
to use KTYPE to select tiny vs standard or define own for custom BSP
layers. What about other recipes like u-boot or firmware for other
remote processors, how to percolate the debug vs user options to those
recipes via just an image recipe ?

As a recipe cannot affect another recipe, and image recipes are obviously recipes too, this is usually not useful.


2. use different configs using multiconfig. Base config (which is
debug) also selects the user config hence always building both build
variants in different tmp directories. Kernel, remote firmware and
image recipes use variables from the multiconfig cof files to decide
whether to build debug or user variants.

The whole point of multiconfig is builds depending on each other. I don’t think it applies here.


3. use different distros. DSITRO=user bitbake example-image,
DISTRO=debug example-image. Kernel and remote firmware recipes use
variables from the distro to decide whether to build debug or user
variants.

This is clearly the standard way.



Which is the best method ?
All these options seem very BSP layer specific, is there something
more generic and better than the above options ?
If not, should this be a feature request to the Yocto project ?

NOTE: debug variants may include the following.
- more debug related kernel configs and security loosened and UART
ports disabled
- image recipe debug variant may include debug utilities absent from
the user variant

Easily archived with 3.



There could be more than just debug and user variants. Android has
engineering, tests, user, tiny and user-debug.

See 3. You can have an arbitrary number of distros, interrelated however you wish.

Greetz


--
Regards,
Karthik Poduval

On Tue, Mar 1, 2022 at 1:26 AM tomzy <tomasz.zyjewski@...> wrote:
>
> Thanks Tomasz. I will check kas.
>
> No problem
>
> Yes, for selecting some of the packages I have created prod and debug image
> recipes.But this did not work for the kernel as the kernel recipe is picked
> as part of PROVIDERin machine conf.
>
> What are the difference there? You want to use different config on prod and debug images?
> Maybe add it as config fragments? Then you would need to add some global variable to
> distinguish when use given .cfg file.
>
> [1] https://docs.yoctoproject.org/singleindex.html#creating-configuration-fragments
>
> SoI had to use 2 conf to have the
> IMAGE_FEATURES (orany other var)set differently for prod and debug. This is for
> building the kernelrecipie differently for prodand debug. Setting the
> IMAGE_FEATURES in the image recipe (and not inconf) causes2 problems. One is
> that kernel and other bootloaders recipes arepicked early via PROVIDER in conf
> and not as packages included in image recipe.
>
> Is that a problem?
>
> Secondly,setting the var in the
> image recipe breaks this command for e.g.
> "bitbake base-image-prod.bbbase-image-debug.bb".
>
> Didn't you want to distinguish this to builds to be able to run `bitbake base-image-prod` or
> `bitbake base-image-debug`?
>
> Since the command parses the recipes only once for both image creation.
>
>
> Nevertheless I would greatly recommend you to use kas. In simple .yml file you
> could prepare different `local.conf` per configuration prod/debug.
>
> [2] https://kas.readthedocs.io/en/latest/userguide.html#project-configuration
>
> Regards,
> Tomasz Żyjewski
> Embedded Systems Engineer
> GPG: 5C495EA3EBEECA59
> https://3mdeb.com | @3mdeb_com
>
>
>
>




Re: On managing debug and production builds

Vinayak Menon
 

Add list. missed earlier.

On Wed, Mar 2, 2022 at 8:11 AM Vinayak Menon <menon.vinayak@...> wrote:

On Tue, Mar 1, 2022 at 2:56 PM tomzy <tomasz.zyjewski@...> wrote:

Thanks Tomasz. I will check kas.

No problem

Yes, for selecting some of the packages I have created prod and debug image
recipes.But this did not work for the kernel as the kernel recipe is picked
as part of PROVIDERin machine conf.

What are the difference there? You want to use different config on prod and debug images?
Maybe add it as config fragments? Then you would need to add some global variable to
distinguish when use given .cfg file.
Ya, and I am using exisitng IMAGE_FEATURE instead of the global var. I
can use global var too.
The only thing is that I am setting the global var from a conf and not
image recipe.


[1] https://docs.yoctoproject.org/singleindex.html#creating-configuration-fragments

SoI had to use 2 conf to have the
IMAGE_FEATURES (orany other var)set differently for prod and debug. This is for
building the kernelrecipie differently for prodand debug. Setting the
IMAGE_FEATURES in the image recipe (and not inconf) causes2 problems. One is
that kernel and other bootloaders recipes are picked early via PROVIDER in conf
and not as packages included in image recipe.

Is that a problem?
Ya you are right, that is not a problem as such. But I have seen in the yocto
documentation that IMAGE_FEATURES are recommended to be set from conf.
Is there any reason for such a recommendation ?


Secondly,setting the var in the
image recipe breaks this command for e.g.
"bitbake base-image-prod.bbbase-image-debug.bb".

Didn't you want to distinguish this to builds to be able to run `bitbake base-image-prod` or
`bitbake base-image-debug`?
Yes I want to distinguish, and as a developer I can give separate
bitbake commands. But the
thought was that later the user can issue commands the way they want.
And if they use it in
combined manner described above, expecting 2 images with different
kernels, it does not work.



Since the command parses the recipes only once for both image creation.


Nevertheless I would greatly recommend you to use kas. In simple .yml file you
could prepare different `local.conf` per configuration prod/debug.
Sure, I will explore this.



[2] https://kas.readthedocs.io/en/latest/userguide.html#project-configuration

Regards,
Tomasz Żyjewski
Embedded Systems Engineer
GPG: 5C495EA3EBEECA59
https://3mdeb.com | @3mdeb_com




--
vinayak
--
vinayak


Re: On managing debug and production builds

Karthik Poduval
 

This concept of user vs debug builds is there in Android and any
Android developer who gets introduced to yocto may look for these
options. There seem to be many implementation choices here, trying to
summarize some of the options here.

1. use different image recipes example-image-user.bb vs
example-image-debug.bb but this still poses a problem for kernel
recipes as kernel needs to have different config fragments or
different defconfig for debug vs user variants. One possible option is
to use KTYPE to select tiny vs standard or define own for custom BSP
layers. What about other recipes like u-boot or firmware for other
remote processors, how to percolate the debug vs user options to those
recipes via just an image recipe ?
2. use different configs using multiconfig. Base config (which is
debug) also selects the user config hence always building both build
variants in different tmp directories. Kernel, remote firmware and
image recipes use variables from the multiconfig cof files to decide
whether to build debug or user variants.
3. use different distros. DSITRO=user bitbake example-image,
DISTRO=debug example-image. Kernel and remote firmware recipes use
variables from the distro to decide whether to build debug or user
variants.

Which is the best method ?
All these options seem very BSP layer specific, is there something
more generic and better than the above options ?
If not, should this be a feature request to the Yocto project ?

NOTE: debug variants may include the following.
- more debug related kernel configs and security loosened and UART
ports disabled
- image recipe debug variant may include debug utilities absent from
the user variant

There could be more than just debug and user variants. Android has
engineering, tests, user, tiny and user-debug.

--
Regards,
Karthik Poduval

On Tue, Mar 1, 2022 at 1:26 AM tomzy <tomasz.zyjewski@...> wrote:

Thanks Tomasz. I will check kas.

No problem

Yes, for selecting some of the packages I have created prod and debug image
recipes.But this did not work for the kernel as the kernel recipe is picked
as part of PROVIDERin machine conf.

What are the difference there? You want to use different config on prod and debug images?
Maybe add it as config fragments? Then you would need to add some global variable to
distinguish when use given .cfg file.

[1] https://docs.yoctoproject.org/singleindex.html#creating-configuration-fragments

SoI had to use 2 conf to have the
IMAGE_FEATURES (orany other var)set differently for prod and debug. This is for
building the kernelrecipie differently for prodand debug. Setting the
IMAGE_FEATURES in the image recipe (and not inconf) causes2 problems. One is
that kernel and other bootloaders recipes arepicked early via PROVIDER in conf
and not as packages included in image recipe.

Is that a problem?

Secondly,setting the var in the
image recipe breaks this command for e.g.
"bitbake base-image-prod.bbbase-image-debug.bb".

Didn't you want to distinguish this to builds to be able to run `bitbake base-image-prod` or
`bitbake base-image-debug`?

Since the command parses the recipes only once for both image creation.


Nevertheless I would greatly recommend you to use kas. In simple .yml file you
could prepare different `local.conf` per configuration prod/debug.

[2] https://kas.readthedocs.io/en/latest/userguide.html#project-configuration

Regards,
Tomasz Żyjewski
Embedded Systems Engineer
GPG: 5C495EA3EBEECA59
https://3mdeb.com | @3mdeb_com




[meta-gplv2] [PATCH] recipes: Convert to use SPDX license names in LICENSE variables

Richard Purdie
 

This uses the script from OE-Core to make the conversion.

Signed-off-by: Richard Purdie <richard.purdie@...>
---
recipes-bsp/grub/grub_0.97.bb | 2 +-
recipes-core/coreutils/coreutils_6.9.bb | 2 +-
recipes-core/gettext/gettext_0.16.1.bb | 2 +-
recipes-core/readline/readline_5.2.bb | 2 +-
recipes-devtools/bison/bison_2.3.bb | 2 +-
recipes-devtools/dosfstools/dosfstools_2.11.bb | 2 +-
recipes-devtools/elfutils/elfutils_0.148.bb | 2 +-
recipes-devtools/m4/m4-1.4.9.inc | 2 +-
recipes-devtools/make/make_3.81.bb | 2 +-
recipes-devtools/mtools/mtools_3.9.9.bb | 2 +-
recipes-devtools/patch/patch_2.5.9.bb | 2 +-
recipes-devtools/rsync/rsync_2.6.9.bb | 2 +-
recipes-extended/bash/bash_3.2.57.bb | 2 +-
recipes-extended/bc/bc_1.06.bb | 2 +-
recipes-extended/cpio/cpio_2.8.bb | 2 +-
recipes-extended/diffutils/diffutils_2.8.1.bb | 2 +-
recipes-extended/ed/ed_0.5.bb | 2 +-
recipes-extended/findutils/findutils_4.2.31.bb | 2 +-
recipes-extended/gawk/gawk_3.1.5.bb | 2 +-
recipes-extended/gperf/gperf.inc | 2 +-
recipes-extended/gperf/gperf_3.0.3.bb | 2 +-
recipes-extended/grep/grep_2.5.1a.bb | 2 +-
recipes-extended/groff/groff_1.18.1.4.bb | 2 +-
recipes-extended/gzip/gzip_1.3.12.bb | 2 +-
recipes-extended/libidn/libidn_0.6.14.bb | 2 +-
recipes-extended/mc/mc_4.7.5.2.bb | 2 +-
recipes-extended/msmtp/msmtp_1.4.12.bb | 2 +-
recipes-extended/sed/sed_4.1.2.bb | 2 +-
recipes-extended/tar/tar_1.17.bb | 2 +-
recipes-extended/texinfo/texinfo_4.8.bb | 2 +-
recipes-extended/time/time_1.7.bb | 2 +-
recipes-extended/which/which_2.18.bb | 2 +-
recipes-sato/rxvt-unicode/rxvt-unicode_9.20.bb | 2 +-
recipes-support/gdbm/gdbm_1.8.3.bb | 2 +-
recipes-support/gmp/gmp_4.2.1.bb | 4 ++--
recipes-support/gnupg/gnupg_1.4.7.bb | 2 +-
recipes-support/gnutls/gnutls.inc | 10 +++++-----
recipes-support/libiconv/libiconv_1.11.1.bb | 2 +-
recipes-support/nettle/nettle_2.7.1.bb | 4 ++--
recipes-support/shared-mime-info/shared-mime-info.inc | 2 +-
40 files changed, 46 insertions(+), 46 deletions(-)

diff --git a/recipes-bsp/grub/grub_0.97.bb b/recipes-bsp/grub/grub_0.97.bb
index 3845c94..e6934b9 100644
--- a/recipes-bsp/grub/grub_0.97.bb
+++ b/recipes-bsp/grub/grub_0.97.bb
@@ -5,7 +5,7 @@ standard, which allows for flexible loading of multiple boot images."
HOMEPAGE = "http://www.gnu.org/software/grub/"
SECTION = "bootloaders"

-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=c93c0550bd3173f4504b2cbd8991e50b \
file://grub/main.c;beginline=3;endline=9;md5=22a5f28d2130fff9f2a17ed54be90ed6"

diff --git a/recipes-core/coreutils/coreutils_6.9.bb b/recipes-core/coreutils/coreutils_6.9.bb
index 8f24556..cc00de0 100644
--- a/recipes-core/coreutils/coreutils_6.9.bb
+++ b/recipes-core/coreutils/coreutils_6.9.bb
@@ -5,7 +5,7 @@ every system."

HOMEPAGE = "http://www.gnu.org/software/coreutils/"
BUGTRACKER = "http://debbugs.gnu.org/coreutils"
-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
file://src/ls.c;beginline=4;endline=16;md5=15ed60f67b1db5fedd5dbc37cf8a9543"
PR = "r5"
diff --git a/recipes-core/gettext/gettext_0.16.1.bb b/recipes-core/gettext/gettext_0.16.1.bb
index 941a9d2..cd632ba 100644
--- a/recipes-core/gettext/gettext_0.16.1.bb
+++ b/recipes-core/gettext/gettext_0.16.1.bb
@@ -2,7 +2,7 @@ SUMMARY = "Utilities and libraries for producing multi-lingual messages"
DESCRIPTION = "GNU gettext is a set of tools that provides a framework to help other programs produce multi-lingual messages. These tools include a set of conventions about how programs should be written to support message catalogs, a directory and file naming organization for the message catalogs themselves, a runtime library supporting the retrieval of translated messages, and a few stand-alone programs to massage in various ways the sets of translatable and already translated strings."
HOMEPAGE = "http://www.gnu.org/software/gettext/gettext.html"
SECTION = "libs"
-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=9ea3144f04c41cd2eada5d3f472e6ea5"

PR = "r6"
diff --git a/recipes-core/readline/readline_5.2.bb b/recipes-core/readline/readline_5.2.bb
index aa2799e..d42ce8b 100644
--- a/recipes-core/readline/readline_5.2.bb
+++ b/recipes-core/readline/readline_5.2.bb
@@ -5,7 +5,7 @@ additional functions to maintain a list of previously-entered command lines, to
lines, and perform csh-like history expansion on previous commands."
SECTION = "libs"

-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=03b36fdd84f74b8d8189a202b980b67f"

DEPENDS += "ncurses"
diff --git a/recipes-devtools/bison/bison_2.3.bb b/recipes-devtools/bison/bison_2.3.bb
index c84fd9a..1faf73f 100644
--- a/recipes-devtools/bison/bison_2.3.bb
+++ b/recipes-devtools/bison/bison_2.3.bb
@@ -4,7 +4,7 @@ an LALR(1) or GLR parser for that grammar. Bison is upward compatible with Yacc
grammars ought to work with Bison with no change. Anyone familiar with Yacc should be able to use Bison with \
little trouble."
HOMEPAGE = "http://www.gnu.org/software/bison/"
-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=eb723b61539feef013de476e68b5c50a"
SECTION = "devel"
DEPENDS = "bison-native flex-native"
diff --git a/recipes-devtools/dosfstools/dosfstools_2.11.bb b/recipes-devtools/dosfstools/dosfstools_2.11.bb
index 37c2181..5298b32 100644
--- a/recipes-devtools/dosfstools/dosfstools_2.11.bb
+++ b/recipes-devtools/dosfstools/dosfstools_2.11.bb
@@ -5,7 +5,7 @@ SUMMARY = "DOS FAT Filesystem Utilities"
HOMEPAGE = "https://github.com/dosfstools/dosfstools"

SECTION = "base"
-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://mkdosfs/COPYING;md5=cbe67f08d6883bff587f615f0cc81aa8"
PR = "r5"

diff --git a/recipes-devtools/elfutils/elfutils_0.148.bb b/recipes-devtools/elfutils/elfutils_0.148.bb
index 97d88a2..f3e3373 100644
--- a/recipes-devtools/elfutils/elfutils_0.148.bb
+++ b/recipes-devtools/elfutils/elfutils_0.148.bb
@@ -1,7 +1,7 @@
SUMMARY = "Utilities and libraries for handling compiled object files"
HOMEPAGE = "https://fedorahosted.org/elfutils"
SECTION = "base"
-LICENSE = "(GPL-2+ & Elfutils-Exception)"
+LICENSE = "(GPL-2.0-or-later & Elfutils-Exception)"
LIC_FILES_CHKSUM = "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3\
file://EXCEPTION;md5=570adcb0c1218ab57f2249c67d0ce417"
DEPENDS = "libtool bzip2 zlib virtual/libintl"
diff --git a/recipes-devtools/m4/m4-1.4.9.inc b/recipes-devtools/m4/m4-1.4.9.inc
index 41f46cd..7cb8c78 100644
--- a/recipes-devtools/m4/m4-1.4.9.inc
+++ b/recipes-devtools/m4/m4-1.4.9.inc
@@ -1,6 +1,6 @@
require m4.inc

-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"

LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe\
file://examples/COPYING;md5=1d49bd61dc590f014cae7173b43e3e5c"
diff --git a/recipes-devtools/make/make_3.81.bb b/recipes-devtools/make/make_3.81.bb
index 9fe22a8..c670476 100644
--- a/recipes-devtools/make/make_3.81.bb
+++ b/recipes-devtools/make/make_3.81.bb
@@ -1,6 +1,6 @@
PR = "r1"

-LICENSE = "GPLv2 & LGPLv2"
+LICENSE = "GPL-2.0-only & LGPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=361b6b837cad26c6900a926b62aada5f \
file://tests/COPYING;md5=8ca43cbc842c2336e835926c2166c28b \
file://glob/COPYING.LIB;md5=4a770b67e6be0f60da244beb2de0fce4"
diff --git a/recipes-devtools/mtools/mtools_3.9.9.bb b/recipes-devtools/mtools/mtools_3.9.9.bb
index 8e106b0..636ee67 100644
--- a/recipes-devtools/mtools/mtools_3.9.9.bb
+++ b/recipes-devtools/mtools/mtools_3.9.9.bb
@@ -2,7 +2,7 @@ SUMMARY = "Utilities to access MS-DOS disks without mounting them"
DESCRIPTION = "Mtools is a collection of utilities to access MS-DOS disks from GNU and Unix without mounting them."
HOMEPAGE = "http://www.gnu.org/software/mtools/"
SECTION = "optional"
-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=92b58ec77696788ce278b044d2a8e9d3"
PR = "r6"

diff --git a/recipes-devtools/patch/patch_2.5.9.bb b/recipes-devtools/patch/patch_2.5.9.bb
index f2970f7..01a4e68 100644
--- a/recipes-devtools/patch/patch_2.5.9.bb
+++ b/recipes-devtools/patch/patch_2.5.9.bb
@@ -1,5 +1,5 @@
require patch.inc
-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"

SRC_URI += " file://debian.patch \
file://install.patch \
diff --git a/recipes-devtools/rsync/rsync_2.6.9.bb b/recipes-devtools/rsync/rsync_2.6.9.bb
index 5c6c9d9..525387d 100644
--- a/recipes-devtools/rsync/rsync_2.6.9.bb
+++ b/recipes-devtools/rsync/rsync_2.6.9.bb
@@ -8,7 +8,7 @@ SRC_URI += "file://rsync-2.6.9-fname-obo.patch \
SRC_URI[md5sum] = "996d8d8831dbca17910094e56dcb5942"
SRC_URI[sha256sum] = "ca437301becd890e73300bc69a39189ff1564baa761948ff149b3dd7bde633f9"

-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=6d5a9d4c4d3af25cd68fd83e8a8cb09c"

PR = "r4"
diff --git a/recipes-extended/bash/bash_3.2.57.bb b/recipes-extended/bash/bash_3.2.57.bb
index 5c288b3..189bdc2 100644
--- a/recipes-extended/bash/bash_3.2.57.bb
+++ b/recipes-extended/bash/bash_3.2.57.bb
@@ -1,6 +1,6 @@
require bash.inc

-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=fd5d9bcabd8ed5a54a01ce8d183d592a"

SRC_URI = "${GNU_MIRROR}/${BPN}/${BP}.tar.gz \
diff --git a/recipes-extended/bc/bc_1.06.bb b/recipes-extended/bc/bc_1.06.bb
index 82143a4..2319f95 100644
--- a/recipes-extended/bc/bc_1.06.bb
+++ b/recipes-extended/bc/bc_1.06.bb
@@ -1,7 +1,7 @@
SUMMARY = "Arbitrary precision calculator language"
HOMEPAGE = "http://www.gnu.org/software/bc/bc.html"

-LICENSE = "GPLv2+ & LGPLv2.1"
+LICENSE = "GPL-2.0-or-later & LGPL-2.1-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
file://COPYING.LIB;md5=d8045f3b8f929c1cb29a1e3fd737b499 \
file://bc/bcdefs.h;endline=31;md5=46dffdaf10a99728dd8ce358e45d46d8 \
diff --git a/recipes-extended/cpio/cpio_2.8.bb b/recipes-extended/cpio/cpio_2.8.bb
index 624906b..581fe1f 100644
--- a/recipes-extended/cpio/cpio_2.8.bb
+++ b/recipes-extended/cpio/cpio_2.8.bb
@@ -1,6 +1,6 @@
require cpio_v2.inc

-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=b7f772ea3a2489231cb4872656cac34b"

PR = "r4"
diff --git a/recipes-extended/diffutils/diffutils_2.8.1.bb b/recipes-extended/diffutils/diffutils_2.8.1.bb
index 6e48dc6..d5d5845 100644
--- a/recipes-extended/diffutils/diffutils_2.8.1.bb
+++ b/recipes-extended/diffutils/diffutils_2.8.1.bb
@@ -1,4 +1,4 @@
-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"

require diffutils.inc
diff --git a/recipes-extended/ed/ed_0.5.bb b/recipes-extended/ed/ed_0.5.bb
index 8305e6b..8e0e05e 100644
--- a/recipes-extended/ed/ed_0.5.bb
+++ b/recipes-extended/ed/ed_0.5.bb
@@ -1,7 +1,7 @@
SUMMARY = "Line-oriented text editor"
HOMEPAGE = "http://www.gnu.org/software/ed/"
SECTION = "base"
-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=6ddd5335ef96fb858a138230af773710 \
file://main.c;beginline=1;endline=17;md5=36d4b85e5ae9028e918d1cc775c2475e"

diff --git a/recipes-extended/findutils/findutils_4.2.31.bb b/recipes-extended/findutils/findutils_4.2.31.bb
index 7dee018..ef4500b 100644
--- a/recipes-extended/findutils/findutils_4.2.31.bb
+++ b/recipes-extended/findutils/findutils_4.2.31.bb
@@ -1,4 +1,4 @@
-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552"
PR = "r4"

diff --git a/recipes-extended/gawk/gawk_3.1.5.bb b/recipes-extended/gawk/gawk_3.1.5.bb
index 933c140..2a75ff2 100644
--- a/recipes-extended/gawk/gawk_3.1.5.bb
+++ b/recipes-extended/gawk/gawk_3.1.5.bb
@@ -8,7 +8,7 @@ SECTION = "console/utils"

# gawk <= 3.1.5: GPLv2
# gawk >= 3.1.6: GPLv3
-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552"

RDEPENDS:gawk += "gawk-common"
diff --git a/recipes-extended/gperf/gperf.inc b/recipes-extended/gperf/gperf.inc
index 10738e4..37fc334 100644
--- a/recipes-extended/gperf/gperf.inc
+++ b/recipes-extended/gperf/gperf.inc
@@ -1,7 +1,7 @@
DESCRIPTION = "GNU gperf is a perfect hash function generator"
HOMEPAGE = "http://www.gnu.org/software/gperf"
SUMMARY = "Generate a perfect hash function from a set of keywords"
-LICENSE = "GPLv3+"
+LICENSE = "GPL-3.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
file://src/main.cc;beginline=8;endline=19;md5=dec8f611845d047387ed56b5b85fa99b"

diff --git a/recipes-extended/gperf/gperf_3.0.3.bb b/recipes-extended/gperf/gperf_3.0.3.bb
index 7728861..d9e4928 100644
--- a/recipes-extended/gperf/gperf_3.0.3.bb
+++ b/recipes-extended/gperf/gperf_3.0.3.bb
@@ -1,6 +1,6 @@
require gperf.inc

-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=a5f84abb0070adf8a0925d7d534b6e0a \
file://src/main.cc;beginline=8;endline=19;md5=72a3034a19e72f08ee48ef8244a121fd"

diff --git a/recipes-extended/grep/grep_2.5.1a.bb b/recipes-extended/grep/grep_2.5.1a.bb
index 1a3231e..c9c076b 100644
--- a/recipes-extended/grep/grep_2.5.1a.bb
+++ b/recipes-extended/grep/grep_2.5.1a.bb
@@ -2,7 +2,7 @@ SUMMARY = "Pattern matching utilities"
DESCRIPTION = "The GNU versions of commonly used grep utilities. The grep command searches one or more input \
files for lines containing a match to a specified pattern."
SECTION = "console/utils"
-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3"

PR = "r2"
diff --git a/recipes-extended/groff/groff_1.18.1.4.bb b/recipes-extended/groff/groff_1.18.1.4.bb
index 84b0d78..293043c 100644
--- a/recipes-extended/groff/groff_1.18.1.4.bb
+++ b/recipes-extended/groff/groff_1.18.1.4.bb
@@ -3,7 +3,7 @@ DESCRIPTION = "The groff (GNU troff) software is a typesetting package which rea
formatting commands and produces formatted output."
SECTION = "console/utils"
HOMEPAGE = "http://www.gnu.org/software/groff/"
-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
PR = "r1"

LIC_FILES_CHKSUM = "file://COPYING;md5=e43fc16fccd8519fba405f0a0ff6e8a3"
diff --git a/recipes-extended/gzip/gzip_1.3.12.bb b/recipes-extended/gzip/gzip_1.3.12.bb
index 5f7f6cd..94998ca 100644
--- a/recipes-extended/gzip/gzip_1.3.12.bb
+++ b/recipes-extended/gzip/gzip_1.3.12.bb
@@ -1,6 +1,6 @@
require gzip.inc

-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
file://gzip.h;endline=22;md5=c0934ad1900d927f86556153d4c76d23 \
file://lzw.h;endline=19;md5=c273e09a02edd9801cc74d39683049e9 "
diff --git a/recipes-extended/libidn/libidn_0.6.14.bb b/recipes-extended/libidn/libidn_0.6.14.bb
index dfd9c6e..f5153a1 100644
--- a/recipes-extended/libidn/libidn_0.6.14.bb
+++ b/recipes-extended/libidn/libidn_0.6.14.bb
@@ -2,7 +2,7 @@ SUMMARY = "Internationalized Domain Name support library"
DESCRIPTION = "Implementation of the Stringprep, Punycode and IDNA specifications defined by the IETF Internationalized Domain Names (IDN) working group."
HOMEPAGE = "http://www.gnu.org/software/libidn/"
SECTION = "libs"
-LICENSE = "LGPLv2.1+ & GPLv2+"
+LICENSE = "LGPL-2.1-or-later & GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=eb723b61539feef013de476e68b5c50a \
file://COPYING.LIB;md5=a6f89e2100d9b6cdffcea4f398e37343 \
file://lib/idna.h;beginline=6;endline=18;md5=1336e848ca7b8e25767c3c7e8fa38a89 \
diff --git a/recipes-extended/mc/mc_4.7.5.2.bb b/recipes-extended/mc/mc_4.7.5.2.bb
index 2d30fe7..0fe4ab0 100644
--- a/recipes-extended/mc/mc_4.7.5.2.bb
+++ b/recipes-extended/mc/mc_4.7.5.2.bb
@@ -1,6 +1,6 @@
SUMMARY = "Midnight Commander is an ncurses based file manager"
HOMEPAGE = "http://www.midnight-commander.org/"
-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552"
SECTION = "console/utils"
DEPENDS = "ncurses glib-2.0"
diff --git a/recipes-extended/msmtp/msmtp_1.4.12.bb b/recipes-extended/msmtp/msmtp_1.4.12.bb
index 21d9f81..f77b2b7 100644
--- a/recipes-extended/msmtp/msmtp_1.4.12.bb
+++ b/recipes-extended/msmtp/msmtp_1.4.12.bb
@@ -3,7 +3,7 @@ DESCRIPTION = "A sendmail replacement for use in MTAs like mutt"
HOMEPAGE = "http://msmtp.sourceforge.net/"
SECTION = "console/network"

-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"

LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"

diff --git a/recipes-extended/sed/sed_4.1.2.bb b/recipes-extended/sed/sed_4.1.2.bb
index 24f479e..dc061ca 100644
--- a/recipes-extended/sed/sed_4.1.2.bb
+++ b/recipes-extended/sed/sed_4.1.2.bb
@@ -1,6 +1,6 @@
SUMMARY = "Stream EDitor (text filtering utility)"
HOMEPAGE = "http://www.gnu.org/software/sed/"
-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
file://sed/sed.h;beginline=1;endline=17;md5=e00ffd1837f298439a214fd197f6a407"
SECTION = "console/utils"
diff --git a/recipes-extended/tar/tar_1.17.bb b/recipes-extended/tar/tar_1.17.bb
index 1ee5e34..e4d4746 100644
--- a/recipes-extended/tar/tar_1.17.bb
+++ b/recipes-extended/tar/tar_1.17.bb
@@ -1,6 +1,6 @@
require tar.inc

-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552"

PR = "r3"
diff --git a/recipes-extended/texinfo/texinfo_4.8.bb b/recipes-extended/texinfo/texinfo_4.8.bb
index ea269cc..c975f48 100644
--- a/recipes-extended/texinfo/texinfo_4.8.bb
+++ b/recipes-extended/texinfo/texinfo_4.8.bb
@@ -4,7 +4,7 @@ online information and printed output from a single source file. The \
GNU Project uses the Texinfo file format for most of its documentation."
HOMEPAGE = "http://www.gnu.org/software/texinfo/"
SECTION = "console/utils"
-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"

PROVIDES:append:class-native = " texinfo-4.8-replacement-native"
diff --git a/recipes-extended/time/time_1.7.bb b/recipes-extended/time/time_1.7.bb
index ccc7788..8807334 100644
--- a/recipes-extended/time/time_1.7.bb
+++ b/recipes-extended/time/time_1.7.bb
@@ -3,7 +3,7 @@ DESCRIPTION = "time measures many of the CPU resources, such as time and \
memory, that other programs use."
HOMEPAGE = "http://www.gnu.org/software/time/"
SECTION = "utils"
-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=8ca43cbc842c2336e835926c2166c28b"

inherit texinfo update-alternatives
diff --git a/recipes-extended/which/which_2.18.bb b/recipes-extended/which/which_2.18.bb
index 63b43c4..42d0bf2 100644
--- a/recipes-extended/which/which_2.18.bb
+++ b/recipes-extended/which/which_2.18.bb
@@ -6,7 +6,7 @@ It does this by using the exact same algorithm as bash."
SECTION = "libs"
HOMEPAGE = "http://carlo17.home.xs4all.nl/which/"

-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"

PR = "r2"
diff --git a/recipes-sato/rxvt-unicode/rxvt-unicode_9.20.bb b/recipes-sato/rxvt-unicode/rxvt-unicode_9.20.bb
index 1f83559..ee84302 100644
--- a/recipes-sato/rxvt-unicode/rxvt-unicode_9.20.bb
+++ b/recipes-sato/rxvt-unicode/rxvt-unicode_9.20.bb
@@ -1,6 +1,6 @@
require rxvt-unicode.inc

-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
file://src/main.C;beginline=1;endline=31;md5=775485398a09fa7aee6f90464af88432"

diff --git a/recipes-support/gdbm/gdbm_1.8.3.bb b/recipes-support/gdbm/gdbm_1.8.3.bb
index b7551ad..2259fb1 100644
--- a/recipes-support/gdbm/gdbm_1.8.3.bb
+++ b/recipes-support/gdbm/gdbm_1.8.3.bb
@@ -1,7 +1,7 @@
SUMMARY = "Key/value database library with extensible hashing"
HOMEPAGE = "http://www.gnu.org/software/gdbm/"
SECTION = "libs"
-LICENSE = "GPLv2+"
+LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=d8e20eece214df8ef953ed5857862150"

PR = "r4"
diff --git a/recipes-support/gmp/gmp_4.2.1.bb b/recipes-support/gmp/gmp_4.2.1.bb
index 88d8f9b..1cb9311 100644
--- a/recipes-support/gmp/gmp_4.2.1.bb
+++ b/recipes-support/gmp/gmp_4.2.1.bb
@@ -1,7 +1,7 @@
require gmp.inc

-LICENSE = "LGPLv2.1+ & GPLv2+"
-LICENSE:${PN} = "LGPLv2.1+"
+LICENSE = "LGPL-2.1-or-later & GPL-2.0-or-later"
+LICENSE:${PN} = "LGPL-2.1-or-later"

LIC_FILES_CHKSUM = "file://COPYING;md5=892f569a555ba9c07a568a7c0c4fa63a \
file://COPYING.LIB;md5=fbc093901857fcd118f065f900982c24 \
diff --git a/recipes-support/gnupg/gnupg_1.4.7.bb b/recipes-support/gnupg/gnupg_1.4.7.bb
index 7f146a1..06d327c 100644
--- a/recipes-support/gnupg/gnupg_1.4.7.bb
+++ b/recipes-support/gnupg/gnupg_1.4.7.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "http://www.gnupg.org/"
DEPENDS = "zlib bzip2 readline"
SECTION = "console/utils"

-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"

LIC_FILES_CHKSUM = "file://COPYING;md5=eb723b61539feef013de476e68b5c50a"

diff --git a/recipes-support/gnutls/gnutls.inc b/recipes-support/gnutls/gnutls.inc
index 491fdbf..b22c533 100644
--- a/recipes-support/gnutls/gnutls.inc
+++ b/recipes-support/gnutls/gnutls.inc
@@ -2,11 +2,11 @@ SUMMARY = "GNU Transport Layer Security Library"
HOMEPAGE = "http://www.gnu.org/software/gnutls/"
BUGTRACKER = "https://savannah.gnu.org/support/?group=gnutls"

-LICENSE = "GPLv3+ & LGPLv2.1+"
-LICENSE:${PN} = "LGPLv2.1+"
-LICENSE:${PN}-xx = "LGPLv2.1+"
-LICENSE:${PN}-bin = "GPLv3+"
-LICENSE:${PN}-openssl = "GPLv3+"
+LICENSE = "GPL-3.0-or-later & LGPL-2.1-or-later"
+LICENSE:${PN} = "LGPL-2.1-or-later"
+LICENSE:${PN}-xx = "LGPL-2.1-or-later"
+LICENSE:${PN}-bin = "GPL-3.0-or-later"
+LICENSE:${PN}-OpenSSL = "GPL-3.0-or-later"

LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
file://COPYING.LESSER;md5=a6f89e2100d9b6cdffcea4f398e37343"
diff --git a/recipes-support/libiconv/libiconv_1.11.1.bb b/recipes-support/libiconv/libiconv_1.11.1.bb
index 1e6668e..20a4f62 100644
--- a/recipes-support/libiconv/libiconv_1.11.1.bb
+++ b/recipes-support/libiconv/libiconv_1.11.1.bb
@@ -6,7 +6,7 @@ SECTION = "libs"
NOTES = "Needs to be stripped down to: ascii iso8859-1 eucjp iso-2022jp gb utf8"
PROVIDES = "virtual/libiconv"

-LICENSE = "LGPLv2.0"
+LICENSE = "LGPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=9f604d8a4f8e74f4f5140845a21b6674 \
file://libcharset/COPYING.LIB;md5=9f604d8a4f8e74f4f5140845a21b6674"

diff --git a/recipes-support/nettle/nettle_2.7.1.bb b/recipes-support/nettle/nettle_2.7.1.bb
index 7ff03dd..d5026b6 100644
--- a/recipes-support/nettle/nettle_2.7.1.bb
+++ b/recipes-support/nettle/nettle_2.7.1.bb
@@ -1,7 +1,7 @@
require nettle.inc

-LICENSE = "LGPLv2.1+ & GPLv2"
-LICENSE:${PN} = "LGPLv2.1+"
+LICENSE = "LGPL-2.1-or-later & GPL-2.0-only"
+LICENSE:${PN} = "LGPL-2.1-or-later"

LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=2d5025d4aa3495befef8f17206a5b0a1 \
file://serpent-decrypt.c;beginline=53;endline=67;md5=bcfd4745d53ca57f82907089898e390d \
diff --git a/recipes-support/shared-mime-info/shared-mime-info.inc b/recipes-support/shared-mime-info/shared-mime-info.inc
index 06d0422..47a7610 100644
--- a/recipes-support/shared-mime-info/shared-mime-info.inc
+++ b/recipes-support/shared-mime-info/shared-mime-info.inc
@@ -2,7 +2,7 @@ SUMMARY = "Shared MIME type database and specification"
HOMEPAGE = "http://freedesktop.org/wiki/Software/shared-mime-info"
SECTION = "base"

-LICENSE = "GPLv2"
+LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"

DEPENDS = "libxml2 intltool-native glib-2.0 shared-mime-info-native"
--
2.32.0


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

Richard Purdie
 

On Tue, 2022-03-01 at 06:13 -0800, Armin Kuster wrote:

On 2/28/22 11:44, Teoh, Jay Shen wrote:
Hi Everyone,

This is the full report for yocto-3.3.5.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.

No new issue found.
As a YP TSC member, I am fine releasing this build.

I will let Richard send the final word once the rest of the YP TSC respond.
The TSC discussed today and is happy to release, thanks!

Cheers,

Richard

1081 - 1100 of 57397