Date   

[meta-security][PATCH] tpm2-pkcs11: build and package python tools

Ioan-Adrian Ratiu
 

Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com>
---
.../tpm2-pkcs11/tpm2-pkcs11_1.4.0.bb | 25 +++++++++++++++++--
1 file changed, 23 insertions(+), 2 deletions(-)

diff --git a/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.4.0.bb b/met=
a-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.4.0.bb
index 4865733..6beb67a 100644
--- a/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.4.0.bb
+++ b/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.4.0.bb
@@ -4,7 +4,7 @@ SECTION =3D "security/tpm"
LICENSE =3D "BSD-2-Clause"
LIC_FILES_CHKSUM =3D "file://LICENSE;md5=3D0fc19f620a102768d6dbd1e7166e7=
8ab"
=20
-DEPENDS =3D "autoconf-archive pkgconfig dstat sqlite3 openssl libtss2-de=
v tpm2-tools libyaml"
+DEPENDS =3D "autoconf-archive pkgconfig dstat sqlite3 openssl libtss2-de=
v tpm2-tools libyaml python3-setuptools-native"
=20
SRC_URI =3D "git://github.com/tpm2-software/tpm2-pkcs11.git;branch=3D1.X=
\
file://bootstrap_fixup.patch \
@@ -14,10 +14,31 @@ SRCREV =3D "78bbf6a0237351830d0c3923b25ba0b57ae0b7e9"
=20
S =3D "${WORKDIR}/git"
=20
-inherit autotools-brokensep pkgconfig
+inherit autotools-brokensep pkgconfig python3native
=20
do_configure_prepend () {
${S}/bootstrap
}
=20
+do_compile_append() {
+ cd ${S}/tools
+ python3 setup.py build
+}
+
+do_install_append() {
+ cd ${S}/tools
+ export PYTHONPATH=3D"${D}${PYTHON_SITEPACKAGES_DIR}"
+ ${PYTHON_PN} setup.py install --root=3D"${D}" --prefix=3D"${prefix}"=
--install-lib=3D"${PYTHON_SITEPACKAGES_DIR}" --optimize=3D1 --skip-build
+
+ sed -i -e "s:${PYTHON}:${USRBINPATH}/env ${PYTHON_PN}:g" "${D}${bind=
ir}"/tpm2_ptool
+}
+
RDEPNDS_${PN} =3D "tpm2-tools"
+
+PACKAGES =3D+ "${PN}-tools"
+RDEPENDS_${PN}-tools +=3D "${PYTHON_PN}-setuptools ${PYTHON_PN}-pyyaml $=
{PYTHON_PN}-cryptography ${PYTHON_PN}-pyasn1-modules"
+
+FILES_${PN}-tools =3D "\
+ ${bindir}/tpm2_ptool \
+ ${libdir}/${PYTHON_DIR}/* \
+"
--=20
2.29.2


Re: Parsing recipes: 0% | - hangs for a while

Jean-Marie Lemetayer
 

Maybe related to this: meta/conf/distro/include/default-distrovars.inc

# The CONNECTIVITY_CHECK_URIS are used to test whether we can succesfully
# fetch from the network (and warn you if not). To disable the test set
# the variable to be empty.
# Git example url:
git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=master
CONNECTIVITY_CHECK_URIS ?= "https://www.example.com/"

Try to overwrite CONNECTIVITY_CHECK_URIS in your local.conf by
something like google.com or even an empty string and see the result.

Best regards,
Jean-Marie

On Wed, Nov 25, 2020 at 12:46 PM Sergey Ivanov <icegood1980@gmail.com> wrote:

The issue was located. I had overridden to the local path of one recipe via

"devtool modify -n <my_recipe>" /my/local/path
and during parsing it hangs at
"Inheriting /yocto/sources/poky/meta/classes/externalsrc.bbclass" from custom devtools bbappend for my recipe.
Moreover, "devtool reset -n <my_recipe>" turned out into other errors:



NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
NOTE: Retrying server connection (#1)...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#2)...
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#2)...
NOTE: Retrying server connection (#2)...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#3)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#3)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Retrying server connection (#3)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#4)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#4)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Retrying server connection (#4)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#5)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#5)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Retrying server connection (#5)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#6)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#6)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Retrying server connection (#6)... (Traceback (most recent call last):
File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
server_connection = bb.server.process.connectProcessServer(sockname, featureset)
File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Starting bitbake server...


I wonder why devtool needs bitbake server.





ср, 25 нояб. 2020 г. в 13:14, Sergey Ivanov via lists.yoctoproject.org <icegood1980=gmail.com@lists.yoctoproject.org>:

Since today i encountered issue in the topic.

I had this issue before when i forgot to turn on vpn (somehow parsing depends on it). But today is everything is OK and i wonder what went wrong. More precisely, i'm interested in two points:

1) at which stage parsing of receipts is interested in remote resources?
2) how to disable remote resource usage during parsing in some sophisticated way?

P.S. after waiting for a while bitbake continues but it is annoying anyway.

--
Kind regards,
Sergey Ivanov



--
Kind regards,
Sergey Ivanov



Re: How to add Python3 json module in Yocto

Robert P. J. Day
 

On Wed, 25 Nov 2020, vijayrakeshmunganda@gmail.com wrote:

Hi, can anyone please guide me on adding json module to my python
library in yocto. I had download .bb file from OE Layer and placed
it under recipe-devtool/python folder, but it is not including to
the build. Also guide me how to select a suitable .bb file as there
are many recipes available on json.
simply adding a recipe to your layer is not sufficient ... you need
to specifically say you want a package added to your image with,
perhaps, adding the line:

IMAGE_INSTALL_append = " <package> <package> ..."

to your local.conf file.

rday


How to add Python3 json module in Yocto

Vijay Rakesh Munganda
 

Hi, can anyone please guide me on adding json module to my python library in yocto. I had download .bb file from OE Layer and placed it under recipe-devtool/python folder, but it is not including to the build. Also guide me how to select a suitable .bb file as there are many recipes available on json.   

Thanks & Regards,
Vijay.


Re: Parsing recipes: 0% | - hangs for a while

Sergey Ivanov <icegood1980@...>
 

The issue was located. I had overridden to the local path of one recipe via

"devtool modify -n <my_recipe>" /my/local/path
and during parsing it hangs at
"Inheriting /yocto/sources/poky/meta/classes/externalsrc.bbclass" from custom devtools bbappend for my recipe.
Moreover, "devtool reset -n <my_recipe>" turned out into other errors:



NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
NOTE: Retrying server connection (#1)...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#2)...
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#2)...
NOTE: Retrying server connection (#2)...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#3)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#3)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Retrying server connection (#3)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#4)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#4)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Retrying server connection (#4)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#5)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#5)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Retrying server connection (#5)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#6)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Reconnecting to bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#6)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Retrying server connection (#6)... (Traceback (most recent call last):
  File "/yocto/sources/poky/bitbake/lib/bb/main.py", line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File "/yocto/sources/poky/bitbake/lib/bb/server/process.py", line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
NOTE: Starting bitbake server...


I wonder why devtool needs bitbake server.





ср, 25 нояб. 2020 г. в 13:14, Sergey Ivanov via lists.yoctoproject.org <icegood1980=gmail.com@...>:

Since today i encountered issue in the topic.

I had this issue before when i forgot to turn on vpn (somehow parsing depends on it). But today is everything is OK and i wonder what went wrong. More precisely, i'm interested in two points:

1) at which stage parsing of receipts is interested in remote resources?
2) how to disable remote resource usage during parsing in some sophisticated way?

P.S. after waiting for a while bitbake continues but it is annoying anyway.

--
Kind regards,
Sergey Ivanov





--
Kind regards,
Sergey Ivanov


Parsing recipes: 0% | - hangs for a while

Sergey Ivanov <icegood1980@...>
 

Since today i encountered issue in the topic.

I had this issue before when i forgot to turn on vpn (somehow parsing depends on it). But today is everything is OK and i wonder what went wrong. More precisely, i'm interested in two points:

1) at which stage parsing of receipts is interested in remote resources?
2) how to disable remote resource usage during parsing in some sophisticated way?

P.S. after waiting for a while bitbake continues but it is annoying anyway.

--
Kind regards,
Sergey Ivanov


Error when building eSDK for a "linux-dummy"

Andrej Valek <andrej.valek@...>
 

Hello Khem,

 

I was, that you were trying to figure you, what’s going wrong with “linux-dummy” kernel in eSDK case. Did you or somebody else find something?

 

I have the same problem as described here https://lists.yoctoproject.org/g/yocto/topic/78096462#51336.

 

 

Regards,

Andrej


Re: Problem with recipe that depends on a binary that is generated during its build

Matteo Iervasi
 

Ok I've found a solution by myself. Basically I just used the trick showed in the Technical FAQ and put a bunch of install commands in the do_install task.
Now the only problem I have is that the do_install task for target complains that needs administrative privileges (maybe I'm just doing it wrong, I'm still not that experienced with Yocto).

| [100%] Built target boosttest-test-livestatus
| make[1]: Leaving directory '/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build'
| /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/recipe-sysroot-native/usr/bin/cmake -E cmake_progress_start /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build/CMakeFiles 0
| make -f CMakeFiles/Makefile2 preinstall
| make[1]: Entering directory '/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build'
| make[1]: Nothing to be done for 'preinstall'.
| make[1]: Leaving directory '/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build'
| Install the project...
| /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/recipe-sysroot-native/usr/bin/cmake -P cmake_install.cmake
| -- Install configuration: "Release"
| CMake Error at cmake_install.cmake:36 (file):
|   file cannot create directory: /usr/share/doc/icinga2.  Maybe need
|   administrative privileges.
|
|
| Makefile:74: recipe for target 'install' failed
| make: *** [install] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_install (log file is located at /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/temp/log.do_install.25788)
ERROR: Task (/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/../layers/meta-boxio-colibri-imx6ull/recipes-extended/icinga-core/icinga-core_2.12.0.bb:do_install) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3457 tasks of which 3447 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory

The recipe that now compiles ok is attached here.

Thanks
Matteo Iervasi


M+ & H bugs with Milestone Movements WW47

Stephen Jolley
 

All,

YP M+ or high bugs which moved to a new milestone in WW47 are listed below:

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

13338

SDK  build fails if image contains bash

randy.macleod@...

akuster@...

2.6.3

3.3 M1

 

13566

Write tests for multiconfig files in layers and document

randy.macleod@...

mostthingsweb@...

3.2 M4

3.3 M1

 

13722

Debugging With the GNU Project Debugger enhancements

randy.macleod@...

newcomer@...

3.2 M4

3.3 M1

 

13822

Easy to have misleading warnings if env script is executed instead of sourced

randy.macleod@...

newcomer@...

3.2 M4

3.3 M1

 

14040

recipetool: creating binary recipe from upstream git repo without explicit PV causes circular reference in SRC_URI

randy.macleod@...

mostthingsweb@...

3.2 M4

3.3 M1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Enhancements/Bugs closed WW47!

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

5

randy.macleod@...

4

mhalstead@...

1

ross@...

1

Grand Total

11

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Current high bug count owners for Yocto Project 3.3

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

36

ross@...

24

david.reyna@...

21

bruce.ashfield@...

20

bluelightning@...

19

JPEWhacker@...

12

timothy.t.orling@...

12

sakib.sajal@...

11

mark.morton@...

11

kai.kang@...

9

akuster808@...

9

trevor.gamblin@...

9

Qi.Chen@...

6

stacy.gaikovaia@...

5

raj.khem@...

5

mingli.yu@...

4

yi.zhao@...

4

idadelm@...

4

randy.macleod@...

4

chee.yang.lee@...

3

hongxu.jia@...

3

mostthingsweb@...

3

alejandro@...

3

jon.mason@...

2

matthewzmd@...

2

jeanmarie.lemetayer@...

2

saul.wold@...

2

ydirson@...

2

mark.hatle@...

2

pokylinux@...

2

jaewon@...

2

nicolas.dechesne@...

2

fede@...

1

anuj.mittal@...

1

aehs29@...

1

mhalstead@...

1

apoorvsangal@...

1

shachar@...

1

matt.ranostay@...

1

dl9pf@...

1

kai.ruhnau@...

1

kexin.hao@...

1

Martin.Jansa@...

1

liezhi.yang@...

1

joe.slater@...

1

jpuhlman@...

1

kergoth@...

1

maxime.roussinbelanger@...

1

akuster@...

1

kamensky@...

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

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

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

 

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

 

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

 

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

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Yocto Project Status WW47'20

Stephen Jolley
 

Current Dev Position: YP 3.3 M1 development

Next Deadline: 7th December 2020 YP 3.3 M1 build

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.1.4 will build later this week.
  • YP 3.3 development in master is continuing as patches are reviewed, tested and merged.
  • We plan to backport the sphinx documentation transition back to our LTS after 3.1.4 is built.
  • A small but important issue was identified related to build reproducibility where the host umask was influencing the build output in relatively minor ways. We plan to run a mixture of umasks on the autobuilder infrastructure in future to avoid this source of reproducibility issues. There are patches for the issues queued for master and will be backported in due course.
  • Support for fedora33 has been resolved but required making pseudo-native host specific and not ‘uninative’ due to differences in the way pseudo builds depending on the presence of headers.
  • Hashserve “passthrough” support has merged allowing hashservers to be chained together, thanks Joshua.
  • Intermittent autobuilder issues continue to occur. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
  • Further autobuilder improvements have been submitted and accepted into upstream buildbot (field history, triggered build summary stats and work name display in build summary). As these are released and deployed, they will make small but important improvements to the autobuilder usability.

 

Ways to contribute:

 

YP 3.3 Milestone Dates:

  • YP 3.3 M1 build date 2020/12/07
  • YP 3.3 M1 Release date 2020/12/18
  • YP 3.3 M2 build date 2021/01/18
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

 

Planned upcoming dot releases:

  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13
  • YP 3.2.1 build date 2020/11/16
  • YP 3.2.1 release date 2020/12/4
  • YP 3.1.5 build date 2021/01/11
  • YP 3.1.5 release date 2021/01/22
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Re: How to add python application into the build. #python #toolchain

Nicolas Jeker
 

On Tue, 2020-11-24 at 04:33 -0800, vijayrakeshmunganda@gmail.com wrote:
Hi,
Hi Vijay

I'm new to the Yocto Project, trying to include my python application
into the build. Can anyone guide me how to write a bitbake recipe .bb
file or any example recipe would be helpful.
Reading and following the section about "Writing a New Recipe" in the
manual is probably a good starting point:

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#new-recipe-writing-a-new-recipe

I usually look at related recipes that already exist (in your case some
other python recipe) and try to start with a minimal recipe and fix
build errors/missing dependencies/etc. iteratively.

Thank & Regards,
Vijay.



How to add python application into the build. #python #toolchain

Vijay Rakesh Munganda
 

Hi,

I'm new to the Yocto Project, trying to include my python application into the build. Can anyone guide me how to write a bitbake recipe .bb file or any example recipe would be helpful.

Thank & Regards,
Vijay.


Re: Yocto Project Outreachy interns

Dorinda
 

Thank you all,
I appreciate the opportunity given to me to intern with the Yocto Project. I am excited about this internship and I look forward to working with you on my project.

Sincerely,
Dorinda.

On Nov 24, 2020 08:47, "Nicolas Dechesne" <nicolas.dechesne@...> wrote:
Dear all,

We are very excited to be part of the Outreachy program again for the
December round this year, let me congratulate Ida and Dorinda for
being accepted as interns for the next three months.

I want to give a warm thank you to our mentors as well, Paul, Ross,
Tim. Without mentors there isn't much we can do, so this is very much
appreciated. A big thank you to Microsoft and Arm who are sponsoring
the internships.

Ida and Dorinda will engage on the following topics:

== Enhance Yocto Project License Tracing
The Yocto Project build system is typically used to build customised
Linux images from source for embedded applications. Along with the
image, a manifest of packages and their corresponding licenses is
prepared, however the accuracy of the license information in the
manifest is dependent on the accuracy of the metadata we have for each
package (i.e. what is in the recipe file). As part of the build, we
have an internal mapping from output files to source files which is
currently used to prepare source packages to aid in debugging, however
with the increasing presence of SPDX headers in source files it could
also be used to allow tracing the license of sources used in building
a package/image to help improve our metadata and future license
manifests.

== Add support for elfutils debug info server"
The Yocto Project build system is typically used to build customised
Linux images from source for embedded applications. debuginfod (part
of elfutils 0.178 onwards) is a way to share debuginfo files, which
provide debugging symbols for gdb to enable it to debug a running
program on a target device. Users of the Yocto Project would benefit
from integrating support for debuginfod such that binaries in an image
produced by the Yocto Project build system could be debugged more
easily.

Ida and Dorinda, welcome into our open source community, you can count
on everyone's support during your internship!

cheers
nico


Re: Python function caching question

Quentin Schulz
 

Hi Michael,

On Mon, Nov 23, 2020 at 04:49:30PM -0700, Michael Callahan wrote:
I do not want do_compile to run again, it rebuilds the whole image.
What is the best way to always run find_version?
Use an anonymous python function that sets VERSION, e.g.:

python __anonymous() {
d.setVar('VERSION', find_version(d))
}

as anonymous python functions are always executed during parsing.

Then add the following to your recipe:
do_compile[vardepsexclude] += "VERSION"

VERSION will always be set appropriately every time the recipe is parsed
but do_compile will only be rerun when a change in the task has occurred
to the exception of the VERSION variable.

No idea if that works as I don't use those, but that's an hint. Anyway, you
probably want a behavior similar to DATETIME's.

Cheers,
Quentin

On Sun, Nov 22, 2020 at 7:53 PM Khem Raj <raj.khem@gmail.com> wrote:

On Sun, Nov 22, 2020 at 6:17 PM Michael Callahan
<coder.callahan@gmail.com> wrote:

I am having trouble with sstate caching of my os-release.bbappend and
am stuck. The simple example file looks like something below, where I
am setting a variable from a computed python function. What's the magic
to make the find_version(d) always run but do_compile to only run if
VERSION changes? I basically want something like
`find_version[nostamp]="1"` but that seems to only work for tasks.

def find_version(d):
import subprocess
cmd = "git describe --long"
return subprocess.check_output(cmd).rstrip().decode('utf-8')

VERSION = "${@find_version(d)}"
# do_compile uses $VERSION
perhaps mark the task which is using this variable as nostamp.





--
StreamUnlimited Engineering GmbH
High Tech Campus Vienna, Gutheil-Schoder-Gasse 10, 1100 Vienna, Austria
Fax: +43 1 667 20 02 4401
quentin.schulz@streamunlimited.com, www.streamunlimited.com


Re: Yocto Project Outreachy interns

Meh Mbeh Ida Delphine
 

Thank you all so much for having us. I learned so much about embedded linux and the Yocto Project in a very short while. I can't wait to start working with you and on my project.


Cheers,
Ida.

On Tue, 24 Nov 2020, 8:47 am Nicolas Dechesne, <nicolas.dechesne@...> wrote:
Dear all,

We are very excited to be part of the Outreachy program again for the
December round this year, let me congratulate Ida and Dorinda for
being accepted as interns for the next three months.

I want to give a warm thank you to our mentors as well, Paul, Ross,
Tim. Without mentors there isn't much we can do, so this is very much
appreciated. A big thank you to Microsoft and Arm who are sponsoring
the internships.

Ida and Dorinda will engage on the following topics:

== Enhance Yocto Project License Tracing
The Yocto Project build system is typically used to build customised
Linux images from source for embedded applications. Along with the
image, a manifest of packages and their corresponding licenses is
prepared, however the accuracy of the license information in the
manifest is dependent on the accuracy of the metadata we have for each
package (i.e. what is in the recipe file). As part of the build, we
have an internal mapping from output files to source files which is
currently used to prepare source packages to aid in debugging, however
with the increasing presence of SPDX headers in source files it could
also be used to allow tracing the license of sources used in building
a package/image to help improve our metadata and future license
manifests.

== Add support for elfutils debug info server"
The Yocto Project build system is typically used to build customised
Linux images from source for embedded applications. debuginfod (part
of elfutils 0.178 onwards) is a way to share debuginfo files, which
provide debugging symbols for gdb to enable it to debug a running
program on a target device. Users of the Yocto Project would benefit
from integrating support for debuginfod such that binaries in an image
produced by the Yocto Project build system could be debugged more
easily.

Ida and Dorinda, welcome into our open source community, you can count
on everyone's support during your internship!

cheers
nico


Re: Disable systemd-timesyncd.service in image

Damien LEFEVRE
 

Yes SYSTEMD_AUTO_ENABLE_${PN} doesn't apply to systemd recipe core services as they are not installed as separate packages.

But I got it working now.

The default enable/disable service are defined in https://github.com/systemd/systemd/blob/master/presets/90-systemd.preset

So 
do_configure_append() {
    sed -i -e "s/enable systemd-timesyncd.service/disable systemd-timesyncd.service/g" ${S}/presets/90-systemd.preset
}

does the trick

Cheers,
-Damien

On Mon, Nov 23, 2020 at 10:42 PM Konrad Weihmann <kweihmann@...> wrote:
The service is deployed with standard systemd package, which doesn't
have that set as far as I see it (no SYSTEMD_AUTO_ENABLE_${PN} in the
latest recipe revision)

I think, after browsing through the code of systemd - this "autostart"
behavior comes from [1].
So I would say you can disable it with a drop-in file at
/etc/systemd/system/systemd-timesyncd.service.d/disable.conf
[Install]
WantedBy=

which also would be charming in a way that it isn't that invasive in the
build system

[1]
https://github.com/systemd/systemd/blob/5b639090d0b4a49d77ba58bebe180b2a6f8da322/units/systemd-timesyncd.service.in#L55

haven't tested it though, but you might wanna give that a shot, if
Aaron's approach doesn't work.

On 23.11.20 21:21, Joel A Cohen wrote:
> I think you need to set SYSTEMD_AUTO_ENABLE = “disable” (actually any
> value other than “enable”) in your bbappend.
>
> (It looks like SYSTEMD_AUTO_ENABLE_${PN} is intended to work too, but I
> can’t verify it at the moment and reading over systemd.bbclass I’m not
> sure if it works or not)
>
> —Aaron
>
> On Mon, Nov 23, 2020 at 11:51 AM Damien LEFEVRE <lefevre.da@...
> <mailto:lefevre.da@...>> wrote:
>
>     Hi,
>
>     I would like to have systemd-timesyncd.service as part of an image
>     but have it disabled by default.
>
>     Right now it is enabled by default which causes some issues.
>
>     I've tried systemd_%.bbappend
>
>     do_install_append() {
>          rm "$D/etc/systemd/system/dbus-org.freedesktop.timesync1.service"
>          rm
>     "$D/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service"
>     }
>
>     but those symlinks are not part of the package.
>
>     I've tried this to remove the link during the package deployment
>     during do_rootfs
>     pkg_postinst_${PN}_append() {
>          #!/bin/sh -e
>          rm "$D/etc/systemd/system/dbus-org.freedesktop.timesync1.service"
>          rm
>     "$D/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service"
>     }
>
>     But at this stage the links still don't exist.
>
>     Which package is actually responsible for enabling the default
>     services / creating the symlinks? How can we turn some of them off
>     while keeping them in the image?
>
>     Thanks,
>     -Damien
>
>
>
>
>
>
>


Yocto Project Outreachy interns

Nicolas Dechesne
 

Dear all,

We are very excited to be part of the Outreachy program again for the
December round this year, let me congratulate Ida and Dorinda for
being accepted as interns for the next three months.

I want to give a warm thank you to our mentors as well, Paul, Ross,
Tim. Without mentors there isn't much we can do, so this is very much
appreciated. A big thank you to Microsoft and Arm who are sponsoring
the internships.

Ida and Dorinda will engage on the following topics:

== Enhance Yocto Project License Tracing
The Yocto Project build system is typically used to build customised
Linux images from source for embedded applications. Along with the
image, a manifest of packages and their corresponding licenses is
prepared, however the accuracy of the license information in the
manifest is dependent on the accuracy of the metadata we have for each
package (i.e. what is in the recipe file). As part of the build, we
have an internal mapping from output files to source files which is
currently used to prepare source packages to aid in debugging, however
with the increasing presence of SPDX headers in source files it could
also be used to allow tracing the license of sources used in building
a package/image to help improve our metadata and future license
manifests.

== Add support for elfutils debug info server"
The Yocto Project build system is typically used to build customised
Linux images from source for embedded applications. debuginfod (part
of elfutils 0.178 onwards) is a way to share debuginfo files, which
provide debugging symbols for gdb to enable it to debug a running
program on a target device. Users of the Yocto Project would benefit
from integrating support for debuginfod such that binaries in an image
produced by the Yocto Project build system could be debugged more
easily.

Ida and Dorinda, welcome into our open source community, you can count
on everyone's support during your internship!

cheers
nico

1921 - 1940 of 53453