Date   

Enhancements/Bugs closed WW18

Stephen Jolley
 

All,

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

Who

Count

randy.macleod@...

6

ross.burton@...

2

akuster808@...

2

mhalstead@...

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 4.1

Stephen Jolley
 

All,

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

Who

Count

michael.opdenacker@...

37

ross.burton@...

23

david.reyna@...

21

bruce.ashfield@...

20

randy.macleod@...

19

sakib.sajal@...

12

richard.purdie@...

10

JPEWhacker@...

9

saul.wold@...

7

tim.orling@...

7

mhalstead@...

6

bluelightning@...

5

kai.kang@...

4

chee.yang.lee@...

3

Qi.Chen@...

3

jon.mason@...

3

hongxu.jia@...

3

akuster808@...

3

pgowda.cve@...

2

abongwabonalais@...

2

alejandro@...

2

tvgamblin@...

2

Martin.Jansa@...

1

pokylinux@...

1

jay.shen.teoh@...

1

steve@...

1

nicolas.dechesne@...

1

aehs29@...

1

thomas.perrot@...

1

raj.khem@...

1

open.source@...

1

sundeep.kokkonda@...

1

martin.beeger@...

1

kexin.hao@...

1

mostthingsweb@...

1

liezhi.yang@...

1

mark.hatle@...

1

shachar@...

1

alexandre.belloni@...

1

Grand Total

220

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 427 unassigned or newcomer bugs.

 

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

 

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@...

 


Re: Adding systemd to yocto

Scott Murray
 

On Tue, 3 May 2022, Edgar Mobile wrote:

Apparently, this is not enough:

bitbake core-image-weston
/usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
Loading cache: 100% |############################################| Time: 0:00:00
Loaded 1472 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'pam' (but /media/user/SSD1TB/yoctoqemu/poky/meta/recipes-graphics/images/core-image-weston.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'pam' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['pam']
ERROR: Required build target 'core-image-weston' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-weston', 'pam']

These are my current additions to local.conf:

INIT_MANAGER="systemd"
CORE_IMAGE_EXTRA_INSTALL += " mesa-demos gdb"
IMAGE_INSTALL:append += " pam"
^ This line what is causing your error, remove it. With pam in
DISTRO_FEATURES the required packages will get pulled in via dependencies.

DISTRO_FEATURES:append = " systemd wayland pam x11"
If you specify INIT_MANAGER = "systemd", then you do not need to add
systemd here.

VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
Similarly, with INIT_MANAGER = "systemd" these 3 lines are not required.
If you look at meta/conf/distro/include/init-manager-systemd.inc you can
see what INIT_MANAGER = "systemd" tweaks.

IMAGE_ROOTFS_EXTRA_SPACE = "38048576"
[snip]

Scott


Re: Adding systemd to yocto

Jack Mitchell
 

On 03/05/2022 11:57, Edgar Mobile wrote:
Apparently, this is not enough:

bitbake core-image-weston
/usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't
resolve package from __spec__ or __package__, falling back on __name__
and __path__
  return f(*args, **kwds)
Loading cache: 100% |############################################| Time:
0:00:00
Loaded 1472 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'pam' (but
/media/user/SSD1TB/yoctoqemu/poky/meta/recipes-graphics/images/core-image-weston.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'pam' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['pam']
ERROR: Required build target 'core-image-weston' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-weston', 'pam']

These are my current additions to local.conf:

INIT_MANAGER="systemd"
CORE_IMAGE_EXTRA_INSTALL += " mesa-demos gdb"
IMAGE_INSTALL:append += " pam"
pam is a DISTRO_FEATURE as below, not a package as you've added above.

DISTRO_FEATURES:append = " systemd wayland pam x11"
VIRTUAL-RUNTIME_init_manager = "systemd" 
DISTRO_FEATURES_BACKFILL_CONSIDERED =
"sysvinit"VIRTUAL-RUNTIME_initscripts = ""
IMAGE_ROOTFS_EXTRA_SPACE = "38048576"


------------------------------------------------------------------------
*From:* Scott Murray <scott.murray@...>
*Sent:* Monday, May 2, 2022 2:32 PM
*To:* Edgar Mobile <heideggm@...>
*Cc:* Joel Winarske <joel.winarske@...>; Yocto-mailing-list
<yocto@...>
*Subject:* Re: [yocto] Adding systemd to yocto
 
On Mon, 2 May 2022, Edgar Mobile wrote:

Ok, correction: I complains about pam missing.
My apologies, I'd forgotten that wrinkle as we'd been sidestepping it for
a while in AGL with some custom Weston startup.  There are a few recipes
in the Weston stuff that explicitly mark pam as a required feature when
using systemd, so you'll also need to have:

DISTRO_FEATURES:append = " pam"

Scott



--
Jack Mitchell, Consultant
https://www.tuxable.co.uk


Re: Adding systemd to yocto

Edgar Mobile
 

Apparently, this is not enough:

bitbake core-image-weston
/usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
Loading cache: 100% |############################################| Time: 0:00:00
Loaded 1472 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'pam' (but /media/user/SSD1TB/yoctoqemu/poky/meta/recipes-graphics/images/core-image-weston.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'pam' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['pam']
ERROR: Required build target 'core-image-weston' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-weston', 'pam']

These are my current additions to local.conf:

INIT_MANAGER="systemd"

CORE_IMAGE_EXTRA_INSTALL += " mesa-demos gdb"
IMAGE_INSTALL:append += " pam"
DISTRO_FEATURES:append = " systemd wayland pam x11" VIRTUAL-RUNTIME_init_manager = "systemd" 
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"VIRTUAL-RUNTIME_initscripts = ""
IMAGE_ROOTFS_EXTRA_SPACE = "38048576"



From: Scott Murray <scott.murray@...>
Sent: Monday, May 2, 2022 2:32 PM
To: Edgar Mobile <heideggm@...>
Cc: Joel Winarske <joel.winarske@...>; Yocto-mailing-list <yocto@...>
Subject: Re: [yocto] Adding systemd to yocto
 
On Mon, 2 May 2022, Edgar Mobile wrote:

> Ok, correction: I complains about pam missing.

My apologies, I'd forgotten that wrinkle as we'd been sidestepping it for
a while in AGL with some custom Weston startup.  There are a few recipes
in the Weston stuff that explicitly mark pam as a required feature when
using systemd, so you'll also need to have:

DISTRO_FEATURES:append = " pam"

Scott


Re: [PATCH yocto-autobuilder-helper v12] Add a banner on the old documentation docs.

Quentin Schulz
 

Hi Amahnui,

On 4/27/22 19:27, Abongwa Amahnui Bonalais wrote:> Signed-off-by: Abongwa Bonalais Amahnui <abongwabonalais@...>> ---


Adding a comment in the commit log to explain why this patch is needed and what it does would be great.

scripts/docs_fix_all_html_css.py | 111 +++++++++++++++++++++++++++++++
scripts/run-docs-build | 2 +
2 files changed, 113 insertions(+)
create mode 100644 scripts/docs_fix_all_html_css.py
diff --git a/scripts/docs_fix_all_html_css.py b/scripts/docs_fix_all_html_css.py
new file mode 100644
index 0000000..db99054
--- /dev/null
+++ b/scripts/docs_fix_all_html_css.py
@@ -0,0 +1,111 @@
+#!/usr/bin/env python3
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+#Signed-off-by: Abongwa Bonalais Amahnui <abongwabonalais@...>
+#
+#
+# function to append to the content of a html file below the body tag
+#
Please add a comment as to what this script is supposed to to. You're discussing the implementation here more than the finality. We need to know when opening the file and reading the comment what this should/would be used for.

+#
+
+import os
+
+
+
+html_content_dunfell = '''
+<div id="outdated-warning">This document is outdated, you should select the <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.yoctoproject.org_&;d=DwMDAg&amp;c=_sEr5x9kUWhuk4_nFwjJtA&amp;r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&amp;m=aRH3jUhIOsO6ovQMKiTHiW-F3Xwnx9HWg6yTF99QSvNBJXbkOkdzSNhwGt6I4zHl&amp;s=QnWAweVmLt12aTlVPVFZsjAeYelStsO_8RsqIskX0Sk&amp;e=">latest release version</a> in this series.</div>
+<div xml:lang="en" class="body" lang="en">
+'''
I would nitpick here and say we should probably point to https://docs.yoctoproject.org/dunfell in the href. But that can be fixed/discussed later.

+html_content = '''
+<div id="outdated-warning">This version of the project is now considered obsolete, please select and use a <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.yoctoproject.org&;d=DwMDAg&amp;c=_sEr5x9kUWhuk4_nFwjJtA&amp;r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&amp;m=aRH3jUhIOsO6ovQMKiTHiW-F3Xwnx9HWg6yTF99QSvNBJXbkOkdzSNhwGt6I4zHl&amp;s=XxAPqWFTh9XMmtK4eywrsIFkuOGfwEs8acOxvNGck2g&amp;e=">more recent version</a>.</div>
+<div xml:lang="en" class="body" lang="en">
+'''
+
+# <div xml:lang="en" class="body" lang="en"> and </div> are added to the html files to wrap all the content below the body tag in a div tag whose class is known so it can be controlled in the css file
You are explaining what you are doing, which we can usually understand by reading the code, instead of explaining why you're doing it which is something we cannot guess. Why was it not possible to just insert the banner in the body tag as a div before any other element/tag?

+last_div = '''
+</div>
+
+'''
+
+css_replacement_content = '''
+
+ font-family: Verdana, Sans, sans-serif;
+
+ /*min-width: 640px;*/
You can remove this commented part as it does not provide any context or help.

+ width: 100%;
+ margin: 0;
+ padding: 0;
+ color: #333;
+ overflow-x: hidden;
+ }
+
+ /*added books too*/
Not sure what I am supposed to understand with this comment?

+.body{
+margin: 0 auto;
+min-width: 640px;
+padding: 0 5em 5em 5em;
+}
+/* added the id below to make the banner show and be fixed*/
+#outdated-warning{
+text-align: center;
+background-color: rgb(255, 186, 186);
+color: rgb(106, 14, 14);
+padding: 0.5em 0;
+width: 100%;
+position: fixed;
+top: 0;
+
+
+'''
+ # pattern = '^3.1*'
+ # exclude = re.search(pattern, dir)
Useless comments, please remove.

+def loop_through_html_directories(dir):
+ exclude = []
+ for root, dirs, filenames in os.walk(dir):
+ # exclude banner for 3.1.x upward as it is an LTS release and is still supported
+ exclude = [ name for name in os.listdir(dir) if name.startswith('3.1') ]
+ for d in dirs:
+ if d in exclude:
+ dirs.remove(d)
+ for filename in filenames:
+ if filename.endswith('.html'):
+ with open(os.path.join(root, filename), 'r', encoding="ISO-8859-1") as f:
+ current_content = f.read()
+ with open(os.path.join(root, filename), 'w') as f:
+ f.write(current_content.replace('<body>', '<body>' + html_content))
+ f.write(current_content.replace('</body>', last_div + '</body>'))
+ if filename.endswith('.css'):
+ with open(os.path.join(root, filename), 'r', encoding="ISO-8859-1") as f:
+ css_content = f.read()
+ with open(os.path.join(root, filename), 'w') as f:
+ f.write(css_content.replace(css_content[css_content.find('body {'):css_content.find('}'[0])], 'body {' + css_replacement_content ))
+ print(exclude)
+loop_through_html_directories('.')
+
The function name is not really helpful, you're explaining the implementation more than the outcome of it. I should call this function if I want to add a banner for olds docs. I could suggest add_banner_old_docs as a function name instead, though other people could probably come up with something more meaningful.

+
+
+
+def dunfell_tags(dir):
+ dunfell_banners = []
+ for root, dirs, filenames in os.walk(dir):
+ dunfell_banners = [ name for name in os.listdir(dir) if not name.startswith('3.1') ]
+ for d in dirs:
+ if d in dunfell_banners:
+ dirs.remove(d)
+
+ for filename in filenames:
+ if filename.endswith('.html'):
+ with open(os.path.join(root, filename), 'r', encoding="ISO-8859-1") as f:
+ current_content = f.read()
+ with open(os.path.join(root, filename), 'w') as f:
+ f.write(current_content.replace('<body>', '<body>' + html_content_dunfell))
+ f.write(current_content.replace('</body>', last_div + '</body>'))
+ if filename.endswith('.css'):
+ with open(os.path.join(root, filename), 'r', encoding="ISO-8859-1") as f:
+ css_content = f.read()
+ with open(os.path.join(root, filename), 'w') as f:
+ f.write(css_content.replace(css_content[css_content.find('body {'):css_content.find('}'[0])], 'body {' + css_replacement_content ))
+ print(dunfell_banners)
This is all extremely complex just for using a different variable depending on the name of the directory.

+def add_banner_old_docs(dir):
+ exclude = []
+ for root, dirs, filenames in os.walk(dir):
+ if root.startswith('./3.1'):
+ html_replacement = html_content_dunfell
+ else:
+ html_replacement = html_content
+
+ for filename in filenames:
+ if filename.endswith('.html'):
+ with open(os.path.join(root, filename), 'r', encoding="ISO-8859-1") as f:
+ current_content = f.read()
+ with open(os.path.join(root, filename), 'w') as f:
+ f.write(current_content.replace('<body>', '<body>' + html_replacement))
+ f.write(current_content.replace('</body>', last_div + '</body>'))
+ if filename.endswith('.css'):
+ with open(os.path.join(root, filename), 'r', encoding="ISO-8859-1") as f:
+ css_content = f.read()
+ with open(os.path.join(root, filename), 'w') as f:
+ f.write(css_content.replace(css_content[css_content.find('body {'):css_content.find('}'[0])], 'body {' + css_replacement_content ))
+ print(exclude)
+add_banner_old_docs('.')

Cheers,
Quentin


Re: Yocto cyrillic characters support #yocto

Nicolas Jeker
 

On Fri, 2022-04-29 at 06:48 -0700, Ashutosh Naik wrote:
I am having trouble creating files with cyrillic characters on a
yocto generated image.
 
For eg. If I try to create a file like :
# touch  1Черная
 
I do get:
 
# ls
1?????? 
Is your file created with the wrong name or is it actually just the
'ls' output that doesn't support unicode characters?

If you're using busybox, I think these configuration options could be
of interest:

CONFIG_UNICODE_SUPPORT
CONFIG_LAST_SUPPORTED_WCHAR

You'll find this at the bottom of "Settings -> Support Unicode" when
using menuconfig.

I have verified that my locale has utf8 support:
 
# locale
LANG=en_GB.utf8
LC_CTYPE="en_GB.utf8"
LC_NUMERIC="en_GB.utf8"
LC_TIME="en_GB.utf8"
LC_COLLATE="en_GB.utf8"
LC_MONETARY="en_GB.utf8"
LC_MESSAGES="en_GB.utf8"
LC_PAPER="en_GB.utf8"
LC_NAME="en_GB.utf8"
LC_ADDRESS="en_GB.utf8"
LC_TELEPHONE="en_GB.utf8"
LC_MEASUREMENT="en_GB.utf8"
LC_IDENTIFICATION="en_GB.utf8"
LC_ALL=en_GB.utf8
 
What could I be missing and how can I create files with cyrillic
characters?
 
Regards
Ash


[PATCH] schedulers: update branches for repos that now support kirkstone

Steve Sakoman
 

Signed-off-by: Steve Sakoman <steve@...>
---
schedulers.py | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/schedulers.py b/schedulers.py
index d21c6bb..c0a4261 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -55,12 +55,12 @@ branchdefaults = {
'branch': 'kirkstone',
'branch_poky': 'kirkstone',
'branch_bitbake': '2.0',
- 'branch_meta-arm': 'master',
- 'branch_meta-aws': 'master',
+ 'branch_meta-arm': 'kirkstone',
+ 'branch_meta-aws': 'kirkstone',
'branch_meta-gplv2': 'kirkstone',
- 'branch_meta-intel': 'master',
+ 'branch_meta-intel': 'kirkstone',
'branch_meta-mingw': 'kirkstone',
- 'branch_meta-openembedded': 'master',
+ 'branch_meta-openembedded': 'kirkstone',
'branch_meta-ti': 'master',
'branch_meta-virtualization': 'master',
'branch_oecore': 'kirkstone',
--
2.25.1


Re: Maintaining ABI Compatibility for LTS branch

Sinan Kaya <okaya@...>
 

On 2/9/2022 4:38 PM, Richard Purdie wrote:
This probably does need a discussion on the architecture list and we need some
discussion and decisions about where/what buildhistory could/should do. Adding
this to buildhistory is all well and good but we don't have a meaningful
integration/monitoring of existing buildhistory issues in our
autobuilder/workflow today even before adding new things.
I was hoping for free cycles. I didn't get one. This will be an intern
project.

The way I'm thinking is to have the ABI compat XML be part of the state
cache tgz file and come up with a CVE check kind of hook maybe called
"ABI check" that will start flagging problems.

Would this be a better architecture?


Re: Adding systemd to yocto

Scott Murray
 

On Mon, 2 May 2022, Edgar Mobile wrote:

Ok, correction: I complains about pam missing.
My apologies, I'd forgotten that wrinkle as we'd been sidestepping it for
a while in AGL with some custom Weston startup. There are a few recipes
in the Weston stuff that explicitly mark pam as a required feature when
using systemd, so you'll also need to have:

DISTRO_FEATURES:append = " pam"

Scott


Re: OS-less SDK

Jose Quaresma
 

Hi Alessio,

meta-arm have some binary baremetal toolchains for arm and aarch64 at:

Jose

Khem Raj <raj.khem@...> escreveu no dia sexta, 29/04/2022 à(s) 16:53:



On 4/29/22 4:51 AM, Alessio Igor Bogani wrote:
> Dear Yocto developers,
>
> Is there a way to generate an SDK which contains the toolchain for
> bare-metal systems (i.e. MCU without operating system)?
>

its possible to build baremetal toolchains, e.g. look at meta-riscv
baremetal machines e.g.


https://github.com/riscv/meta-riscv/blob/master/conf/machine/baremetal-riscv32.conf


you can do

MACHINE=baremetal-riscv32 bitbake meta-toolchain

Which will give you a toolchain, but if you want more like what we can
do with MCU OSes like freertos and zephyr take a look at

meta-zephyr (https://git.yoctoproject.org/meta-zephyr/) and
meta-freertos (https://github.com/aehs29/meta-freertos)

> Thanks in advance!
>
> Ciao,
> Alessio
>
>
>
>
>





--
Best regards,

José Quaresma


Re: Adding systemd to yocto

Edgar Mobile
 

Ok, correction: I complains about pam missing.


From: Edgar Mobile <heideggm@...>
Sent: Monday, May 2, 2022 7:47 AM
To: Scott Murray <scott.murray@...>; Joel Winarske <joel.winarske@...>
Cc: Yocto-mailing-list <yocto@...>
Subject: Re: [yocto] Adding systemd to yocto
 
I added

INIT_MANAGER="systemd"

To local.conf. Now it complains that weston-xwayland is missing which sounds weird for core-image-weston.
Am I missing something?

Regardss


From: Scott Murray <scott.murray@...>
Sent: Friday, April 29, 2022 3:07 PM
To: Joel Winarske <joel.winarske@...>; Edgar Mobile <heideggm@...>
Cc: Yocto-mailing-list <yocto@...>
Subject: Re: [yocto] Adding systemd to yocto
 
On Thu, 28 Apr 2022, Joel Winarske wrote:

> Line 30-36 include changes to convert a sysvinit image to systemd.
> https://github.com/jwinarske/manifests/blob/honister/conf/rpi64_config#L30

The INIT_MANAGER variable added in zeus removes the need to tinker with
DISTRO_FEATURES and VIRTUAL-RUNTIME* variables, all it takes to use
systemd is INIT_MANAGER = "systemd". See:

meta/conf/distro/include/init-manager-systemd.inc

for what it tweaks.

Scott


Re: Adding systemd to yocto

Edgar Mobile
 

I added

INIT_MANAGER="systemd"

To local.conf. Now it complains that weston-xwayland is missing which sounds weird for core-image-weston.
Am I missing something?

Regardss


From: Scott Murray <scott.murray@...>
Sent: Friday, April 29, 2022 3:07 PM
To: Joel Winarske <joel.winarske@...>; Edgar Mobile <heideggm@...>
Cc: Yocto-mailing-list <yocto@...>
Subject: Re: [yocto] Adding systemd to yocto
 
On Thu, 28 Apr 2022, Joel Winarske wrote:

> Line 30-36 include changes to convert a sysvinit image to systemd.
> https://github.com/jwinarske/manifests/blob/honister/conf/rpi64_config#L30

The INIT_MANAGER variable added in zeus removes the need to tinker with
DISTRO_FEATURES and VIRTUAL-RUNTIME* variables, all it takes to use
systemd is INIT_MANAGER = "systemd". See:

meta/conf/distro/include/init-manager-systemd.inc

for what it tweaks.

Scott


Re: [meta-security][PATCH] tpm2-tools: libtss added to RDEPENDS

Michał Kotyla
 

On 01.05.2022 19:20, Armin Kuster wrote:


On 4/27/22 02:48, Michał Kotyla wrote:
To use tpm2-tools like tpm2_pcrread on the system image should be installed
additional software. Without adding libtss packages to the RDEPENDS attempt to
run with tss2-tcti fails like:

ERROR:tcti:../tpm2-tss-3.0.3/src/tss2-tcti/tcti-swtpm.c:592:
Tss2_Tcti_Swtpm_Init() Cannot connect to swtpm TPM socket
The current version of tpm2-tools is 5.2.  Was this meant for honister?

- armin
Yes. We do not have tested this on kirkstone, so this patch is for honister only now.


---
  meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb b/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb
index dbd324a..cb2e3d8 100644
--- a/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb
+++ b/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb
@@ -6,6 +6,8 @@ SECTION = "tpm"
    DEPENDS = "tpm2-abrmd tpm2-tss openssl curl autoconf-archive"
  +RDEPENDS:${PN} = "libtss2 libtss2-mu libtss2-tcti-device libtss2-tcti-mssim"
+
  SRC_URI = "https://github.com/tpm2-software/${BPN}/releases/download/${PV}/${BPN}-${PV}.tar.gz"
    SRC_URI[sha256sum] = "e1b907fe29877628052e08ad84eebc6c3f7646d29505ed4862e96162a8c91ba1"

--
Michał Kotyla
Embedded Linux Developer
GPG: 14FC54DC259CF70A
https://3mdeb.com | @3mdeb_com



--
Michał Kotyla
Embedded Linux Developer
GPG: 14FC54DC259CF70A
https://3mdeb.com | @3mdeb_com


Re: [meta-security][PATCH] tpm2-tools: libtss added to RDEPENDS

Armin Kuster
 

On 4/27/22 02:48, Michał Kotyla wrote:
To use tpm2-tools like tpm2_pcrread on the system image should be installed
additional software. Without adding libtss packages to the RDEPENDS attempt to
run with tss2-tcti fails like:

ERROR:tcti:../tpm2-tss-3.0.3/src/tss2-tcti/tcti-swtpm.c:592:
Tss2_Tcti_Swtpm_Init() Cannot connect to swtpm TPM socket
The current version of tpm2-tools is 5.2.  Was this meant for honister?

- armin
---
meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb | 2 ++
1 file changed, 2 insertions(+)

diff --git a/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb b/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb
index dbd324a..cb2e3d8 100644
--- a/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb
+++ b/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_5.0.bb
@@ -6,6 +6,8 @@ SECTION = "tpm"
DEPENDS = "tpm2-abrmd tpm2-tss openssl curl autoconf-archive"
+RDEPENDS:${PN} = "libtss2 libtss2-mu libtss2-tcti-device libtss2-tcti-mssim"
+
SRC_URI = "https://github.com/tpm2-software/${BPN}/releases/download/${PV}/${BPN}-${PV}.tar.gz"
SRC_URI[sha256sum] = "e1b907fe29877628052e08ad84eebc6c3f7646d29505ed4862e96162a8c91ba1"


Re: OS-less SDK

Khem Raj
 

On 4/29/22 4:51 AM, Alessio Igor Bogani wrote:
Dear Yocto developers,
Is there a way to generate an SDK which contains the toolchain for
bare-metal systems (i.e. MCU without operating system)?
its possible to build baremetal toolchains, e.g. look at meta-riscv baremetal machines e.g.


https://github.com/riscv/meta-riscv/blob/master/conf/machine/baremetal-riscv32.conf


you can do

MACHINE=baremetal-riscv32 bitbake meta-toolchain

Which will give you a toolchain, but if you want more like what we can do with MCU OSes like freertos and zephyr take a look at

meta-zephyr (https://git.yoctoproject.org/meta-zephyr/) and meta-freertos (https://github.com/aehs29/meta-freertos)

Thanks in advance!
Ciao,
Alessio


Re: Adding systemd to yocto

Scott Murray
 

On Thu, 28 Apr 2022, Joel Winarske wrote:

Line 30-36 include changes to convert a sysvinit image to systemd.
https://github.com/jwinarske/manifests/blob/honister/conf/rpi64_config#L30
The INIT_MANAGER variable added in zeus removes the need to tinker with
DISTRO_FEATURES and VIRTUAL-RUNTIME* variables, all it takes to use
systemd is INIT_MANAGER = "systemd". See:

meta/conf/distro/include/init-manager-systemd.inc

for what it tweaks.

Scott


Re: Question about initramfs and fitImage

Zoran
 

Hello Khoi,

This might be is your starting point:
https://www.yoctoproject.org/pipermail/yocto/2018-July/041680.html

Zee
_______

On Thu, Apr 28, 2022 at 11:13 PM Khoi Dinh Trinh
<khoidinhtrinh@...> wrote:

Hi All,

I'm trying to build an image that uses the currently built image as the initramfs instead of having to specify it in "INITRAMFS_IMAGE". For example, when I run "bibake image-something", I'm hoping to use the recipe "image-something" as the initramfs with the end goal that it's used in creating a fit image. AFAIK, INITRAMFS_IMAGE has to be hardcoded instead of being dynamically set to the name of the currently built recipe(which I completely understand since the recipe being built might not necessarily be an image) and this makes it easy to boot the wrong thing since the recipe specified with bitbake isn't the thing being used for booting.

My workaround so far is to create my own image recipe and set it to depend on the image being built(specifically depend on the .cpio.gz one), however, a lot of it is duplicate of the current fit image code.

Our use case is that we use initramfs as our only rootfs storage to make checksum at boot easier(since the final rootfs is a .cpio.gz blob) and also to avoid any writes to rootfs to persist across reboot.

--
Best,
Khoi Trinh



Yocto cyrillic characters support #yocto

Ashutosh Naik
 

I am having trouble creating files with cyrillic characters on a yocto generated image.
 
For eg. If I try to create a file like :
# touch  1Черная
 
I do get:
 
# ls
1??????
 
I have verified that my locale has utf8 support:
 
# locale
LANG=en_GB.utf8
LC_CTYPE="en_GB.utf8"
LC_NUMERIC="en_GB.utf8"
LC_TIME="en_GB.utf8"
LC_COLLATE="en_GB.utf8"
LC_MONETARY="en_GB.utf8"
LC_MESSAGES="en_GB.utf8"
LC_PAPER="en_GB.utf8"
LC_NAME="en_GB.utf8"
LC_ADDRESS="en_GB.utf8"
LC_TELEPHONE="en_GB.utf8"
LC_MEASUREMENT="en_GB.utf8"
LC_IDENTIFICATION="en_GB.utf8"
LC_ALL=en_GB.utf8
 
What could I be missing and how can I create files with cyrillic characters?
 
Regards
Ash

1661 - 1680 of 58593