[yocto-announce] [ANNOUNCEMENT] Yocto Project 3.1.6 (Dunfell 23.0.6) is Released

[Vineela]

Hello,

We are pleased to announce the Yocto Project 3.1.6 (dunfell-23.0.6) Release is 
now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2

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

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

Full Test Report:

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

Thank you for everyone's contributions to this release.

Sincerely,

Vineela Tummalapalli
Yocto Project Build and Release
vineela.tummalapa...@intel.com


--
yocto-3.1.6 Release Notes
--


--
 Repositories/Downloads
--

Repository Name: poky
Repository Location: https://git.yoctoproject.org/git/poky
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: a13bda44fcda4e79e9aed39ca1495eabecb6a7b7
Release Artefact: poky-dunfell-23.0.6
sha: a2480100f6326df25f301e461ace52dad23b77e9ff9e6f0197cb7243703c61c6
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: dunfell
Tag: 2020-04.6-dunfell
Git Revision: a8debddd6cbdd70db74e096d72f97fbee008ee63
Release Artefact: oecore-dunfell-23.0.6
sha: 4fc63ad2e738181c2de0106d5c039021aa3b9b7e0ab539e5c3d2f116bfe9ae16
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/oecore-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/oecore-dunfell-23.0.6.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/git/meta-mingw
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: 524de686205b5d6736661d4532f5f98fee8589b7
Release Artefact: meta-mingw-dunfell-23.0.6
sha: edc0c0310eb6d58d8991af07bbd6725686d07c40d9dabd66d7c4c36f5cb9554d
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/meta-mingw-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/meta-mingw-dunfell-23.0.6.tar.bz2

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
Release Artefact: meta-gplv2-dunfell-23.0.6
sha: d322dd47bbf193d4f03348b24b4b0737f36d69aea9be3ba556c0d7f3617df3fb
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/meta-gplv2-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/meta-gplv2-dunfell-23.0.6.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: dunfell
Tag: 2020-04.6-dunfell
Git Revision: fa94374baea75a94e3a488126ca7d8e241a77acd
Release Artefact: bitbake-dunfell-23.0.6
sha: 03154eaaf28173de561c274b118452182787a410a1fdcc827eadd9247f57921b
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/bitbake-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/bitbake-dunfell-23.0.6.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/git/yocto-docs
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: 660684b1a1ece4bdedfd63b9fc65d14f05c226d5

--
Contributors
-
Adrian Herrera
Alexander Kanavin
Anatol Belski
Andrey Mozzhuhin
Armin Kuster
Awais Belal
Bruce Ashfield
Chris Laplante
Dorinda
Jack Mitchell
Joe Slater
Jon Mason
Joshua Watt
Julien Massot
Khem Raj
Lee Chee Yang
Mans Rullgard
Marek Vasut
Mark Hatle
Martin Jansa
Matt Hoosier
Mauro Queirós
Michael Halstead
Michael Ho
Mikko Rapeli
Mingli Yu
Oleksiy Obitotskyy
Oleksiy Obitotskyy yIEf0zt.mo
Ovidiu Panait
Paul Barker
Peter Bergin
Peter Kjellerstedt
Ricardo Ribalda
Ricardo Ribalda Delgado
Richard Purdie
Robert Joslyn
Ross Burton
saloni
Sangeeta Jain
Scott Murray
Sourabh Banerjee
Stephen Jolley
Steve Sakoman
Thomas Perrot
Tomasz Dziendzielski
Vyacheslav Yurkov
Wang Mingyu
Yi Fan Yu
Yi Zhao
zangrc
zhengruoqin

---
 Known Issues
---
N/A


---
Security Fixes
---
libcroco: Added CVE
libgcrypt: Whitelisted CVEs
glib-2.0: Rename patch file for CVE-2020-35457
openssl: set CVE_VERSION_SUFFIX
cve_check: add CVE_VERSION_SUFFIX to indicate suffix in versioning
ppp: Whitelist CVE-2020-15704
zip: whitelist CVE-2018-13410 and CVE-2018-13684
glibc: CVE-2019-25013
glibc: Security fix for CVE-2020-29573
xorg: Security fix for CVE-2020-14345
curl: fix CVE-2020-8231/8284/8285/8286


---
Fixes
---
build-appliance-image: Update to dunfell head revision
python3targetconfig.bbclass: Make py3 dep and tasks only for target recipes
gpgme: use python3targetconfig
meta: drop _PYTHON_SYSCONFIGDATA_NAME hacks
distutils3-base.bbclass: use 

[yocto] [ANNOUNCEMENT] Yocto Project 3.1.6 (Dunfell 23.0.6) is Released

[Vineela]

Hello,

We are pleased to announce the Yocto Project 3.1.6 (dunfell-23.0.6) Release is 
now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2

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

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

Full Test Report:

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

Thank you for everyone's contributions to this release.

Sincerely,

Vineela Tummalapalli
Yocto Project Build and Release
vineela.tummalapa...@intel.com


--
yocto-3.1.6 Release Notes
--


--
 Repositories/Downloads
--

Repository Name: poky
Repository Location: https://git.yoctoproject.org/git/poky
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: a13bda44fcda4e79e9aed39ca1495eabecb6a7b7
Release Artefact: poky-dunfell-23.0.6
sha: a2480100f6326df25f301e461ace52dad23b77e9ff9e6f0197cb7243703c61c6
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/poky-dunfell-23.0.6.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: dunfell
Tag: 2020-04.6-dunfell
Git Revision: a8debddd6cbdd70db74e096d72f97fbee008ee63
Release Artefact: oecore-dunfell-23.0.6
sha: 4fc63ad2e738181c2de0106d5c039021aa3b9b7e0ab539e5c3d2f116bfe9ae16
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/oecore-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/oecore-dunfell-23.0.6.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/git/meta-mingw
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: 524de686205b5d6736661d4532f5f98fee8589b7
Release Artefact: meta-mingw-dunfell-23.0.6
sha: edc0c0310eb6d58d8991af07bbd6725686d07c40d9dabd66d7c4c36f5cb9554d
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/meta-mingw-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/meta-mingw-dunfell-23.0.6.tar.bz2

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
Release Artefact: meta-gplv2-dunfell-23.0.6
sha: d322dd47bbf193d4f03348b24b4b0737f36d69aea9be3ba556c0d7f3617df3fb
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/meta-gplv2-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/meta-gplv2-dunfell-23.0.6.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: dunfell
Tag: 2020-04.6-dunfell
Git Revision: fa94374baea75a94e3a488126ca7d8e241a77acd
Release Artefact: bitbake-dunfell-23.0.6
sha: 03154eaaf28173de561c274b118452182787a410a1fdcc827eadd9247f57921b
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.6/bitbake-dunfell-23.0.6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.6/bitbake-dunfell-23.0.6.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/git/yocto-docs
Branch: dunfell
Tag: yocto-3.1.6
Git Revision: 660684b1a1ece4bdedfd63b9fc65d14f05c226d5

--
Contributors
-
Adrian Herrera
Alexander Kanavin
Anatol Belski
Andrey Mozzhuhin
Armin Kuster
Awais Belal
Bruce Ashfield
Chris Laplante
Dorinda
Jack Mitchell
Joe Slater
Jon Mason
Joshua Watt
Julien Massot
Khem Raj
Lee Chee Yang
Mans Rullgard
Marek Vasut
Mark Hatle
Martin Jansa
Matt Hoosier
Mauro Queirós
Michael Halstead
Michael Ho
Mikko Rapeli
Mingli Yu
Oleksiy Obitotskyy
Oleksiy Obitotskyy yIEf0zt.mo
Ovidiu Panait
Paul Barker
Peter Bergin
Peter Kjellerstedt
Ricardo Ribalda
Ricardo Ribalda Delgado
Richard Purdie
Robert Joslyn
Ross Burton
saloni
Sangeeta Jain
Scott Murray
Sourabh Banerjee
Stephen Jolley
Steve Sakoman
Thomas Perrot
Tomasz Dziendzielski
Vyacheslav Yurkov
Wang Mingyu
Yi Fan Yu
Yi Zhao
zangrc
zhengruoqin

---
 Known Issues
---
N/A


---
Security Fixes
---
libcroco: Added CVE
libgcrypt: Whitelisted CVEs
glib-2.0: Rename patch file for CVE-2020-35457
openssl: set CVE_VERSION_SUFFIX
cve_check: add CVE_VERSION_SUFFIX to indicate suffix in versioning
ppp: Whitelist CVE-2020-15704
zip: whitelist CVE-2018-13410 and CVE-2018-13684
glibc: CVE-2019-25013
glibc: Security fix for CVE-2020-29573
xorg: Security fix for CVE-2020-14345
curl: fix CVE-2020-8231/8284/8285/8286


---
Fixes
---
build-appliance-image: Update to dunfell head revision
python3targetconfig.bbclass: Make py3 dep and tasks only for target recipes
gpgme: use python3targetconfig
meta: drop _PYTHON_SYSCONFIGDATA_NAME hacks
distutils3-base.bbclass: use 

Re: [yocto] Error during do_image_wic

[Darcy Watkins]

Hi,

In follow-up to my previous email, it appears that this error in do_image_wic 
is triggered by something that the meta-security/meta-integrity layer does.



Regards,

Darcy

Darcy Watkins ::  Senior Staff Engineer, Firmware

SIERRA WIRELESS
Direct  +1 604 233 7989   ::  Fax  +1 604 231 1109  ::  Main  +1 604 231 1100
13811 Wireless Way  :: Richmond, BC Canada V6V 3A4
[M4]
dwatk...@sierrawireless.com :: 
www.sierrawireless.com

From:  on behalf of "Darcy Watkins via 
lists.yoctoproject.org" 
Reply-To: Darcy Watkins 
Date: Tuesday, February 9, 2021 at 10:51 AM
To: "yocto@lists.yoctoproject.org" 
Subject: [yocto] Error during do_image_wic

Hi,

I have a puzzling error during do_image_wic.  It says a ‘1’ is returned as an 
error rather than 0, but I don’t see in the output what went wrong.  Anyone 
recognize it?  (I am not that familiar with the inner workings of the wic image 
generation tool).

This used to work but broke during a fresh build from scratch.





dwatkins@carmd-ed-n11377:64bit build $ bitbake core-image-selinux-minimal

Loading cache: 100% 
|#|
 Time: 0:00:00

Loaded 3633 entries from dependency cache.

WARNING: No recipes available for:

  
/home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-kernel/firmware/linux-firmware_git.bbappend

  
/home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-kernel/linux/linux-qoriq_4.19.bbappend

  
/home/dwatkins/workspace/zeta/skylab_mg90-BSP/meta-MG-os-bsp/recipes-kernel/linux/linux-yocto_3.4.bbappend

NOTE: Resolving any missing task queue dependencies



Build Configuration:

BB_VERSION   = "1.46.0"

BUILD_SYS= "x86_64-linux"

NATIVELSBSTRING  = "universal"

TARGET_SYS   = "arm-poky-linux-gnueabi"

MACHINE  = "mg90"

DISTRO   = "poky"

DISTRO_VERSION   = "3.1.5"

TUNE_FEATURES= "arm vfp cortexa7 neon callconvention-hard"

TARGET_FPU   = "hard"

meta-MG-os-bsp   = "master:db03c4adb9ffe9bd0135538ebe399821036e"

meta

meta-poky

meta-yocto-bsp   = "HEAD:6e89d668246fb37b2217aae7ae57390e793696d8"

meta-oe

meta-networking

meta-python

meta-perl= "HEAD:de37512b25c1f8c6bb6ab2b3782ac0fe01443483"

meta-selinux = "HEAD:7af62c91d7d00a260cf28e7908955539304d100d"

meta-security

meta-integrity

meta-security-isafw  = "HEAD:c74cc97641fd93e0e7a4383255e9a0ab3deaf9d7"

meta-freescale   = "HEAD:99bd73bec2a9d84509cb012a08f9062cb65fb24e"



Initialising tasks: 100% 
||
 Time: 0:00:03

Sstate summary: Wanted 2 Found 0 Missed 2 Current 1870 (0% match, 99% complete)

NOTE: Executing Tasks

WARNING: cve-update-db-native-1.0-r0 do_populate_cve_db: Failed to fetch CVE 
data ([SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get 
local issuer certificate (_ssl.c:1108))

Image CVE report stored in: 
/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/deploy/images/mg90/core-image-selinux-minimal-mg90-20210209182741.rootfs.cve

ERROR: core-image-selinux-minimal-1.0-r0 do_image_wic: Execution of 
'/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/temp/run.do_image_wic.14994'
 failed with exit code 1:

INFO: Creating image(s)...



ERROR: _exec_cmd: export 
PATH=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/sbin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/usr/sbin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/usr/bin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/recipe-sysroot-native/bin:/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/hosttools:$PATH;export
 
PSEUDO_PREFIX=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/sysroots-components/x86_64/pseudo-native/usr;export
 
PSEUDO_LOCALSTATEDIR=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/rootfs/../pseudo;export
 
PSEUDO_PASSWD=/home/dwatkins/workspace/zeta/skylab_mg90-BSP/build/tmp/work/mg90-poky-linux-gnueabi/core-image-selinux-minimal/1.0-r0/rootfs;export
 PSEUDO_NOSYMLINKEXP=1;export 

[yocto] Package bash-completion was not found - dunfell

[Darcy Watkins]

Hi,

 

I observe something unusual in dunfell.  After the setting up environment for 
build, if I invoke ‘bash’ I see the following:

 

Package bash-completion was not found in the pkg-config search path.

Perhaps you should add the directory containing `bash-completion.pc'

to the PKG_CONFIG_PATH environment variable

No package 'bash-completion' found

bash: /yum: No such file or directory

 

Is this normal?  (I am using CentOS7 as build machine OS and have the extra 
packages, buildtools installed, etc).

 

I have determined that this is not prior to setting up the environment, but 
will occur if using bash any time afterwards.

 

Is Yocto’s setup environment perhaps being overaggressive with sanitizing the 
paths, etc?

 

 

--

 

Regards,

 

Darcy

 

Equipping worship teams and worshipers

http://xstreamworship.com

[M4]

 


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

Re: [licensing] [yocto] Package names in IMAGE_MANIFEST and PACKAGES

[Jérôme Carretero]

On Fri, 26 Feb 2021 15:21:10 +
"Mikko Rapeli"  wrote:

> FWIW, the mapping from binary package names recipes and recipe metadata like
> LICENSE is available from buildhistory. Also binary package content of images
> is available from buildhistory.

Definitely more powerful than just image manifest + packages.

> With some scripting it is possible to list
> recipes which produce binaries to images, except for static linking and
> header-only recipes but I hope these cought via some other way.

Yeah, that "except" part is something that should be accounted for.

The thing is, I don't see how recipes make any difference between a
build-time dependency such as a build tool, or a statically linked
library, so that some additional information should be input somewhere;
failing to provide that, since I don't feel like finding static library
symbols in binaries to perform a discovery, I just tell my clients to
distribute everything except their proprietary bits...

-- 
Jérôme


pgpdbwN9KGnwc.pgp
Description: OpenPGP digital signature

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

Re: [yocto] Package names in IMAGE_MANIFEST and PACKAGES

[Richard Purdie]

On Fri, 2021-02-26 at 14:18 +, Mikko Murto wrote:
> Hello,
> 
> I'm developing a meta layer to save details about an image created by Yocto 
> to an 
> SPDX document ( https://github.com/doubleopen-project/meta-doubleopen).
> 
> I've encountered two issues regarding package names in IMAGE_MANIFEST 
> and PACKAGES variables,   
> 
> https://github.com/doubleopen-project/meta-doubleopen/issues/2 and 
> https://github.com/doubleopen-project/meta-doubleopen/issues/3.
> 
> The crux of the matter is that I need to find packages created by recipes 
> and to link the packages listed in image's manifest files to these packages. 
> 
> First, the PACKAGES variable of all recipes doesn't seem to include all 
> packages created. For example util-linux's PACKAGES doesn't include 
> util-linux-sulogin, but util-linux-sulogin may be included in an image's 
> manifest and it has a directory in the packages-split directory of 
> util-linux. 
> What would be the correct way to get information about all packages?
> 
> Second, the package names in the image manifest may differ from those in 
> the PACKAGES variable or in packages-split directory. As an example, a
>  manifest file may include libkmod2, but recipe for kmod creates package 
> named libkmod. How to make the link from libkmod2 to libkmod?

I'd suggesting looking at packagedata which is how do_package and friends 
internally looks up things like which recipe provides which package and 
what the final package name is.

An example of this in action is scripts/oe-pkgdata-util.

There is also meta/lib/oe/packagedata.py. Sadly the API is horrible, it 
was never really designed for "public" use but I would love to see a better
API around that (maybe one oe-pkgdata-util could use too).

Cheers,

Richard





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

Re: [licensing] [yocto] Package names in IMAGE_MANIFEST and PACKAGES

[Mikko Rapeli]

Hi,

On Fri, Feb 26, 2021 at 10:08:47AM -0500, Jérôme Carretero wrote:
> On Fri, 26 Feb 2021 14:18:59 +
> "Mikko Murto"  wrote:
> 
> > The crux of the matter is that I need to find packages created by recipes 
> > and to link the packages listed in image's manifest files to these 
> > packages. 
> 
> The way I've been doing it, which is probably not optimal and specific
> to one package format, is to lookup .ipk packages from the image
> manifest, then use the .ipk control info "OE" key to find the
> originating recipe.

FWIW, the mapping from binary package names recipes and recipe metadata like
LICENSE is available from buildhistory. Also binary package content of images
is available from buildhistory. With some scripting it is possible to list
recipes which produce binaries to images, except for static linking and
header-only recipes but I hope these cought via some other way.

Cheers,

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

Re: [yocto] Package names in IMAGE_MANIFEST and PACKAGES

[Jérôme Carretero]

Hi Mikko,


On Fri, 26 Feb 2021 14:18:59 +
"Mikko Murto"  wrote:

> The crux of the matter is that I need to find packages created by recipes and 
> to link the packages listed in image's manifest files to these packages. 

The way I've been doing it, which is probably not optimal and specific
to one package format, is to lookup .ipk packages from the image
manifest, then use the .ipk control info "OE" key to find the
originating recipe.

Here's a link of this method in use in order to try and identify
license-related obligations from an image:
 https://gitlab.com/exmakhina/xm_oe/-/blob/47183b74/licenses.py#L24


Hoping to help,

-- 
Jérôme


pgpIm9J0xbqgg.pgp
Description: OpenPGP digital signature

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

Re: [yocto][PATCH] lib/oeqa/selftest/cases/reproducible.py : updated test to faketime in future when buiding the second test build.

[Alexander Kanavin]

Wait, this needs to be explained a bit better. What reproducibility issues
does this address that the existing test does not?

Alex

On Fri, 26 Feb 2021 at 15:27, Sangeeta Jain  wrote:

>
> This update will ensure that recipes are not including time stamps by
> creating an image with modified system
>
>  time. It uses libfaketime recipe to fake system time to advance by
> 34308122 seconds.
>
> Signed-off-by: sangeeta jain 
> ---
>  meta/lib/oeqa/selftest/cases/reproducible.py | 19 ---
>  1 file changed, 16 insertions(+), 3 deletions(-)
>
> diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py
> b/meta/lib/oeqa/selftest/cases/reproducible.py
> index 8849c95..831a304 100644
> --- a/meta/lib/oeqa/selftest/cases/reproducible.py
> +++ b/meta/lib/oeqa/selftest/cases/reproducible.py
> @@ -180,6 +180,7 @@ class ReproducibleTests(OESelftestTestCase):
>  # will test that and also make the test run faster. If your sstate is
> not
>  # reproducible, disable this in your derived test class
>  build_from_sstate = True
> +use_faketime = False
>
>  def setUpLocal(self):
>  super().setUpLocal()
> @@ -227,7 +228,7 @@ class ReproducibleTests(OESelftestTestCase):
>  bb.utils.mkdirhier(os.path.dirname(dest))
>  shutil.copyfile(source, dest)
>
> -def do_test_build(self, name, use_sstate):
> +def do_test_build(self, name, use_sstate, use_faketime):
>  capture_vars = ['DEPLOY_DIR_' + c.upper() for c in
> self.package_classes]
>
>  tmpdir = os.path.join(self.topdir, name, 'tmp') @@ -256,6 +257,18
> @@ class ReproducibleTests(OESelftestTestCase):
>  SSTATE_MIRRORS = ""
>  ''')
>
> +if use_faketime:  ##sangeeta
> +# This config fragment will enable to fake system time
> +# advance by 34308122 sec
> +bitbake("libfaketime")
> +find_binary = "find . -path '*/image/*/libfaketime.so.1"
> +full_path_to_binary = runCmd(find_binary)
> +binary_path = full_path_to_binary.split("./")
> +ld_preload_path = os.path.join(os.environ.get('BUILDDIR'),
> binary_path[1])
> +seconds_add_to_system_time = "+34308122"
> +cmd = 'LD_PRELOAD=%s FAKETIME=%s' %(ld_preload_path,
> seconds_add_to_system_time)
> +runCmd(cmd)
> +
>  self.logger.info("Building %s (sstate%s allowed)..." % (name, ''
> if use_sstate else ' NOT'))
>  self.write_config(config)
>  d = get_bb_vars(capture_vars)
> @@ -282,9 +295,9 @@ class ReproducibleTests(OESelftestTestCase):
>  os.chmod(save_dir, stat.S_IRWXU | stat.S_IRGRP | stat.S_IXGRP
> | stat.S_IROTH | stat.S_IXOTH)
>  self.logger.info('Non-reproducible packages will be copied
> to %s', save_dir)
>
> -vars_A = self.do_test_build('reproducibleA',
> self.build_from_sstate)
> +vars_A = self.do_test_build('reproducibleA',
> + self.build_from_sstate, self.use_faketime))
>
> -vars_B = self.do_test_build('reproducibleB', False)
> +vars_B = self.do_test_build('reproducibleB', False, True)
>
>  # NOTE: The temp directories from the reproducible build are
> purposely
>  # kept after the build so it can be diffed for debugging.
> --
> 2.7.4
>
>
> 
>
>

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

[yocto][PATCH] lib/oeqa/selftest/cases/reproducible.py : updated test to faketime in future when buiding the second test build.

[Sangeeta Jain]

This update will ensure that recipes are not including time stamps by creating 
an image with modified system

 time. It uses libfaketime recipe to fake system time to advance by 34308122 
seconds.

Signed-off-by: sangeeta jain 
---
 meta/lib/oeqa/selftest/cases/reproducible.py | 19 ---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 8849c95..831a304 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -180,6 +180,7 @@ class ReproducibleTests(OESelftestTestCase):
 # will test that and also make the test run faster. If your sstate is not
 # reproducible, disable this in your derived test class
 build_from_sstate = True
+use_faketime = False
 
 def setUpLocal(self):
 super().setUpLocal()
@@ -227,7 +228,7 @@ class ReproducibleTests(OESelftestTestCase):
 bb.utils.mkdirhier(os.path.dirname(dest))
 shutil.copyfile(source, dest)
 
-def do_test_build(self, name, use_sstate):
+def do_test_build(self, name, use_sstate, use_faketime):
 capture_vars = ['DEPLOY_DIR_' + c.upper() for c in 
self.package_classes]
 
 tmpdir = os.path.join(self.topdir, name, 'tmp') @@ -256,6 +257,18 @@ 
class ReproducibleTests(OESelftestTestCase):
 SSTATE_MIRRORS = ""
 ''')
 
+if use_faketime:  ##sangeeta
+# This config fragment will enable to fake system time
+# advance by 34308122 sec
+bitbake("libfaketime")
+find_binary = "find . -path '*/image/*/libfaketime.so.1"
+full_path_to_binary = runCmd(find_binary)
+binary_path = full_path_to_binary.split("./")
+ld_preload_path = os.path.join(os.environ.get('BUILDDIR'), 
binary_path[1])
+seconds_add_to_system_time = "+34308122"
+cmd = 'LD_PRELOAD=%s FAKETIME=%s' %(ld_preload_path, 
seconds_add_to_system_time)
+runCmd(cmd)
+
 self.logger.info("Building %s (sstate%s allowed)..." % (name, '' if 
use_sstate else ' NOT'))
 self.write_config(config)
 d = get_bb_vars(capture_vars)
@@ -282,9 +295,9 @@ class ReproducibleTests(OESelftestTestCase):
 os.chmod(save_dir, stat.S_IRWXU | stat.S_IRGRP | stat.S_IXGRP | 
stat.S_IROTH | stat.S_IXOTH)
 self.logger.info('Non-reproducible packages will be copied to %s', 
save_dir)
 
-vars_A = self.do_test_build('reproducibleA', self.build_from_sstate)
+vars_A = self.do_test_build('reproducibleA', 
+ self.build_from_sstate, self.use_faketime))
 
-vars_B = self.do_test_build('reproducibleB', False)
+vars_B = self.do_test_build('reproducibleB', False, True)
 
 # NOTE: The temp directories from the reproducible build are purposely
 # kept after the build so it can be diffed for debugging.
--
2.7.4


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

[yocto] Package names in IMAGE_MANIFEST and PACKAGES

[Mikko Murto]

Hello,

I'm developing a meta layer to save details about an image created by Yocto to 
an SPDX document (https://github.com/doubleopen-project/meta-doubleopen).

I've encountered two issues regarding package names in IMAGE_MANIFEST and 
PACKAGES variables, 
https://github.com/doubleopen-project/meta-doubleopen/issues/2 and 
https://github.com/doubleopen-project/meta-doubleopen/issues/3.

The crux of the matter is that I need to find packages created by recipes and 
to link the packages listed in image's manifest files to these packages. 

First, the PACKAGES variable of all recipes doesn't seem to include all 
packages created. For example util-linux's PACKAGES doesn't include 
util-linux-sulogin, but util-linux-sulogin may be included in an image's 
manifest and it has a directory in the packages-split directory of util-linux. 
What would be the correct way to get information about all packages?

Second, the package names in the image manifest may differ from those in the 
PACKAGES variable or in packages-split directory. As an example, a manifest 
file may include libkmod2, but recipe for kmod creates package named libkmod. 
How to make the link from libkmod2 to libkmod?

Best regards,

Mikko Murto
Associate

HH Partners, Attorneys-at-law Ltd
Eteläesplanadi 22 a, 00130 Helsinki, Finland
P.O. Box 232, 00101 Helsinki, Finland
Tel: +358 9 177 613, Fax: +358 9 653 873
mikko.mu...@hhpartners.fi 
www.hhpartners.fi

HH Partners shines in international rankings. See details at hhpartners.fi.

Privileged and confidential information may be contained in this message. If 
you are not the addressee indicated in this message (or responsible for the 
delivery of the message to such person), you may not copy or deliver this 
message to anyone. In such case, kindly notify us by reply e-mail and delete 
this message immediately. Thank you.



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

[yocto] [meta-selinux][PATCH] openssh: don't overwrite sshd_config unconditionally

[Purushottam choudhary]

The current implementation was overwriting the sshd_config and sshd
assuming PAM is needed by default.

openssh should use the default sshd_config packaged with the component
if no distro specific needs are present and not overwrite the full
sshd_config file.

1. If PAM is enabled as a distro then enable the UsePAM option in sshd_config.
2. Moved the file sshd to pam directory so that when pam is enabled,
   then replace the default from poky by installing the same.

Signed-off-by: Purushottam Choudhary 
---
 recipes-connectivity/openssh/files/{ => pam}/sshd |   0
 recipes-connectivity/openssh/files/sshd_config| 118 --
 recipes-connectivity/openssh/openssh_%.bbappend   |  14 +++
 3 files changed, 14 insertions(+), 118 deletions(-)
 rename recipes-connectivity/openssh/files/{ => pam}/sshd (100%)
 delete mode 100644 recipes-connectivity/openssh/files/sshd_config

diff --git a/recipes-connectivity/openssh/files/sshd 
b/recipes-connectivity/openssh/files/pam/sshd
similarity index 100%
rename from recipes-connectivity/openssh/files/sshd
rename to recipes-connectivity/openssh/files/pam/sshd
diff --git a/recipes-connectivity/openssh/files/sshd_config 
b/recipes-connectivity/openssh/files/sshd_config
deleted file mode 100644
index 1c33ad0..000
--- a/recipes-connectivity/openssh/files/sshd_config
+++ /dev/null
@@ -1,118 +0,0 @@
-#  $OpenBSD: sshd_config,v 1.102 2018/02/16 02:32:40 djm Exp $
-
-# This is the sshd server system-wide configuration file.  See
-# sshd_config(5) for more information.
-
-# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
-
-# The strategy used for options in the default sshd_config shipped with
-# OpenSSH is to specify options with their default value where
-# possible, but leave them commented.  Uncommented options override the
-# default value.
-
-#Port 22
-#AddressFamily any
-#ListenAddress 0.0.0.0
-#ListenAddress ::
-
-#HostKey /etc/ssh/ssh_host_rsa_key
-#HostKey /etc/ssh/ssh_host_ecdsa_key
-#HostKey /etc/ssh/ssh_host_ed25519_key
-
-# Ciphers and keying
-#RekeyLimit default none
-
-# Logging
-#SyslogFacility AUTH
-#LogLevel INFO
-
-# Authentication:
-
-#LoginGraceTime 2m
-#PermitRootLogin prohibit-password
-#StrictModes yes
-#MaxAuthTries 6
-#MaxSessions 10
-
-#PubkeyAuthentication yes
-
-# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
-# but this is overridden so installations will only check .ssh/authorized_keys
-#AuthorizedKeysFile.ssh/authorized_keys
-
-#AuthorizedPrincipalsFile none
-
-#AuthorizedKeysCommand none
-#AuthorizedKeysCommandUser nobody
-
-# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
-#HostbasedAuthentication no
-# Change to yes if you don't trust ~/.ssh/known_hosts for
-# HostbasedAuthentication
-#IgnoreUserKnownHosts no
-# Don't read the user's ~/.rhosts and ~/.shosts files
-#IgnoreRhosts yes
-
-# To disable tunneled clear text passwords, change to no here!
-#PasswordAuthentication yes
-#PermitEmptyPasswords no
-
-# Change to yes to enable challenge-response passwords (beware issues with
-# some PAM modules and threads)
-ChallengeResponseAuthentication no
-
-# Kerberos options
-#KerberosAuthentication no
-#KerberosOrLocalPasswd yes
-#KerberosTicketCleanup yes
-#KerberosGetAFSToken no
-
-# GSSAPI options
-#GSSAPIAuthentication no
-#GSSAPICleanupCredentials yes
-
-# Set this to 'yes' to enable PAM authentication, account processing,
-# and session processing. If this is enabled, PAM authentication will
-# be allowed through the ChallengeResponseAuthentication and
-# PasswordAuthentication.  Depending on your PAM configuration,
-# PAM authentication via ChallengeResponseAuthentication may bypass
-# the setting of "PermitRootLogin without-password".
-# If you just want the PAM account and session checks to run without
-# PAM authentication, then enable this but set PasswordAuthentication
-# and ChallengeResponseAuthentication to 'no'.
-UsePAM yes
-
-#AllowAgentForwarding yes
-#AllowTcpForwarding yes
-#GatewayPorts no
-#X11Forwarding no
-#X11DisplayOffset 10
-#X11UseLocalhost yes
-#PermitTTY yes
-#PrintMotd yes
-#PrintLastLog yes
-#TCPKeepAlive yes
-#UseLogin no
-#PermitUserEnvironment no
-Compression no
-ClientAliveInterval 15
-ClientAliveCountMax 4
-#UseDNS no
-#PidFile /var/run/sshd.pid
-#MaxStartups 10:30:100
-#PermitTunnel no
-#ChrootDirectory none
-#VersionAddendum none
-
-# no default banner path
-#Banner none
-
-# override default of no subsystems
-Subsystem  sftp/usr/libexec/sftp-server
-
-# Example of overriding settings on a per-user basis
-#Match User anoncvs
-#  X11Forwarding no
-#  AllowTcpForwarding no
-#  PermitTTY no
-#  ForceCommand cvs server
diff --git a/recipes-connectivity/openssh/openssh_%.bbappend 
b/recipes-connectivity/openssh/openssh_%.bbappend
index 7719d3b..b541c3e 100644
--- a/recipes-connectivity/openssh/openssh_%.bbappend
+++ b/recipes-connectivity/openssh/openssh_%.bbappend
@@ -1 +1,15 @@
 require 

Re: [External] Re: [yocto] Yocto- Apache2 build guide

[D, Sharmila via lists.yoctoproject.org]

Hi MacLeod,

Thanks for your e-mail. 
Yes, without apach2 I am able to build the core-image-minimal 
successfully. The issue is only when I addapache2 in IMAGE_INSTALL.
I am using TI processor SDK and I have setup the arago based yocto 
environment based on TI user guide.
 version is THUD.
Do you need any further details about the setup?
Please provide me the steps to include apache2 package into my final 
image.

Looking forward to hearing from you at your earliest convenience.

With Best Regards,
Sharmila D

-Original Message-
From: Randy MacLeod  
Sent: Thursday, February 25, 2021 12:08 AM
To: D, Sharmila ; yocto@lists.yoctoproject.org
Subject: [External] Re: [yocto] Yocto- Apache2 build guide

On 2021-02-24 5:04 a.m., D, Sharmila via lists.yoctoproject.org wrote:
> Hi,
> 
> I am trying to enable httpd package into my yocto build, steps I 
> followed is as below
> 
> 1. Added below layer in bblayer.conf file
> 
> sources/meta-openembedded/meta-webserver
> 
> 2. Added below line in local.conf file
> 
> IMAGE_INSTALL_append = "apache2"
> 
> The yocto build using bitbake core-image-minimal gives below error
> 
> WARNING: core-image-minimal-1.0-r0 do_rootfs: busybox.postinst 
> returned 1, marking as unpacked only, configuration required on target.
> ERROR: core-image-minimal-1.0-r0 do_rootfs: Postinstall scriptlets of 
> ['busybox'] have failed. If the intention is to defer them to first 
> boot, then please place them into pkg_postinst_ontarget_${PN} ().
> Deferring to first boot via 'exit 1' is no longer supported.
> Details of the failure are in
> /home/h440246/Projects/rfid/BSP/tisdk/build/arago-tmp-glibc/work/omapl138_lcdk-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.
> ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
> ERROR: Logfile of failure stored in: 
> /home/h440246/Projects/rfid/BSP/tisdk/build/arago-tmp-glibc/work/omapl
> 138_lcdk-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs
> .2937
> ERROR: Task
> (/home/h440246/Projects/rfid/BSP/tisdk/sources/oe-core/meta/recipes-co
> re/images/core-image-minimal.bb:do_rootfs)
> failed with exit code '1'
> 
> Please provide the solution for the same

Hi Sharmila,

This doesn't appear to be related to adding apache.
Are you able to build core-image-minimal without adding apache2?

Can you provide detailed steps wrt what layers and HEAD commits for each layer 
you are using? Ideally, you'd reproduce on a supported release or on master. 
That's Dunfell/3.1 or later:
   https://wiki.yoctoproject.org/wiki/Releases

../Randy

> 
> With Best Regards,
> 
> Sharmila D
> 
> 
> 
> 
> 


--
# Randy MacLeod
# Wind River Linux

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