Date   

Re: Inactive service of hello world #yocto

Nicolas Jeker
 

On Tue, 2021-09-07 at 10:43 -0700, Rudolf J Streif wrote:
What does your 'Hello World' service do? Just print 'Hello World' to
the console and then exit?

If so that would be the reason why it is inactive. Systemd starts it
and then it exits. Typically, services keep running (except for some
special cases) once they are started. That's what makes them a service.
To stop them 'systemctl stop <service>' is used. By default systemctl
sends SIGTERM to tell the service to clean up and terminate itself.
To piggyback on that, it is possible to set Type=oneshot[1] for the
service so that systemd considers the service to be up after it exited.
I find it useful for init or migration scripts that another service can
then depend upon.

[1]:
https://www.freedesktop.org/software/systemd/man/systemd.service.html#Type=


:rjs


On Tue, Sep 7, 2021, 10:20 <yasminebenghozzi6@...> wrote:
Hi everyone, 

I wanted to run the helloworld service, but it keeps telling that its
inactive , I really cant find why, I changed the service many times
but no solution.
I m sorry I ant copy paste from putty




Re: Building Yocto on AWS container getting ERROR: The postinstall intercept hook 'update_icon_cache' failed, #yocto

mail2uvijay@...
 

For the error,  i have tried installed below package in aws container
libgdk-pixbuf2.0-0 in container,
and added DEPENDS += "qemuwrapper-cross" in bb file.

Will try the option building "core-image-minimal" or "core-image-sato"

Regards,
Vijay


Re: Building Yocto on AWS container getting ERROR: The postinstall intercept hook 'update_icon_cache' failed, #yocto

Alexander Kanavin
 

It's right there at the very end:
NOTE: Exit code 127. Output:
/home/wlsom/YoctoCode/poky/build-microchip/tmp/work/sama5d27_wlsom1_ek_sd-poky-linux-gnueabi/utec-mcdgrill-image/1.0-r0/intercept_scripts-7f1ca27092c337bb8d06dfe7837dad99a9fb3e5e5ff266e8ce34762c23025acb/update_icon_cache: 9: /home/wlsom/YoctoCode/poky/build-microchip/tmp/work/sama5d27_wlsom1_ek_sd-poky-linux-gnueabi/utec-mcdgrill-image/1.0-r0/intercept_scripts-7f1ca27092c337bb8d06dfe7837dad99a9fb3e5e5ff266e8ce34762c23025acb/update_icon_cache: /home/wlsom/YoctoCode/poky/build-microchip/tmp/work/sama5d27_wlsom1_ek_sd-poky-linux-gnueabi/utec-mcdgrill-image/1.0-r0/recipe-sysroot-native//gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: not found

This isn't easy to diagnose without having access to your build tree, but you can build plain core-image-sato for example and check that the binary does exist there and gets executed, and then untangle where the difference come from.

Alex


On Wed, 8 Sept 2021 at 06:47, <mail2uvijay@...> wrote:

Raj thanks for the response. Couldnt able to find error from the logs..

Attached detailed logs..



multilib SDK

Arun
 

I have a custom project where I am building for 64-bit kernel and 32-bit userspace using multilib config

# for 32bit userspace build
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "armv7athf-neon"


I am successfully able to build the target image as
MACHINE=<custom_machine> bitbake lib32-<custom_target>

However, when I try to build the SDK, I am noticing that the userspace recipes are being built for  both 64-bit and 32-bit. I am running into errors for 64-bit. I have no need for 64-bit, is there any way I can disable 64-bit build for SDK?

note: I am building SDK via this command without lib32- prefix for target, following details from this commit message stating that lib32- prefix is not required
MACHINE=<custom_machine> bitbake -c populate_sdk <custom_target>

thanks
-Arun


Re: Building Yocto on AWS container getting ERROR: The postinstall intercept hook 'update_icon_cache' failed, #yocto

mail2uvijay@...
 


Raj thanks for the response. Couldnt able to find error from the logs..

Attached detailed logs..


Re: [poky] Poky:dunfell: SDK install issue (sed: -e expression #1, char 0: no previous regular expression)

Richard Purdie
 

On Tue, 2021-09-07 at 06:10 +0000, Groeting, Claus wrote:
Hi all!

I have a problem with this commit, applied in poky:dunfell on file toolchain-
shar-relocate.sh.
sha1: d6f40be29bf56a835f5825692a22365f04aeb6c3

Author: hongxu <hongxu.jia@...>  2021-08-10 15:33:56
Committer: Richard Purdie <richard.purdie@...>  2021-08-26
09:32:18
Parent: dad6dd12fd6e2512f3bd5591327ee35ee22b913e (toolchain-shar-relocate.sh:
Fix handling files with colons)
Branches: dunfell, remotes/origin/dunfell
Follows: dunfell-23.0.10, yocto-3.1.10
Precedes:

    sdk: fix relocate symlink failed
   
   
    (From OE-Core rev: a155c4d4ca841ef492213a5f0b9121703c62e2b4)
   
    Signed-off-by: Hongxu Jia <hongxu.jia@...>
    Signed-off-by: Alexandre Belloni <alexandre.belloni@...>
    Signed-off-by: Richard Purdie <richard.purdie@...>
    (cherry picked from commit 942c06a7348070b92f722fa5c439c8c4404485b7)
    Signed-off-by: Steve Sakoman <steve@...>
    Signed-off-by: Richard Purdie <richard.purdie@...>

-------------------- meta/files/toolchain-shar-relocate.sh --------------------
index 5433741296..ba873373e2 100644
@@ -72,7 +72,7 @@ fi
 
 # change all symlinks pointing to @SDKPATH@
 for l in $($SUDO_EXEC find $native_sysroot -type l); do
- $SUDO_EXEC ln -sfn $(readlink $l|$SUDO_EXEC sed -e
"s:$DEFAULT_INSTALL_DIR:$target_sdk_dir:") $l
+ $SUDO_EXEC ln -sfn $(readlink $l|$SUDO_EXEC sed -e
"s:$SDK_BUILD_PATH:$target_sdk_dir:") $l
  if [ $? -ne 0 ]; then
  echo "Failed to setup symlinks. Relocate script failed. Abort!"
  exit 1

it looks to me that SDK_BUILD_PATH is not defined in the sed instruction. When
installing the generated SDK shell script, we see a lot of:
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression

Without that commit, everything looks ok. On master-branch SDK_BUILD_PATH is
preset with "@SDKPATH@" but not on dunfell-branch this is missing in the
file toolchain-shar-relocate.sh.
Hi,

I think there is a patch queued in the testing branch for dunfell:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=stable/dunfell-nut


http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=stable/dunfell-nut&id=ed0f6236ceb6a127903241f783a526bcdefc66ce

that should address this.

Cheers,

Richard


Re: Inactive service of hello world #yocto

Rudolf J Streif
 

What does your 'Hello World' service do? Just print 'Hello World' to the console and then exit?

If so that would be the reason why it is inactive. Systemd starts it and then it exits. Typically, services keep running (except for some special cases) once they are started. That's what makes them a service. To stop them 'systemctl stop <service>' is used. By default systemctl sends SIGTERM to tell the service to clean up and terminate itself.

:rjs


On Tue, Sep 7, 2021, 10:20 <yasminebenghozzi6@...> wrote:
Hi everyone, 

I wanted to run the helloworld service, but it keeps telling that its inactive , I really cant find why, I changed the service many times but no solution.
I m sorry I ant copy paste from putty




Inactive service of hello world #yocto

yasminebenghozzi6@...
 

Hi everyone, 

I wanted to run the helloworld service, but it keeps telling that its inactive , I really cant find why, I changed the service many times but no solution.
I m sorry I ant copy paste from putty


Re: Debating best tool to use

KL <deco33000@...>
 

That is exactly what I thought and why I insisted that much.

I will step back and constrict to my app, and not the whole OS.

Thanks!

--

17:38, 7 September 2021, Ross Burton <ross@...>:

On Tue, 7 Sept 2021 at 11:22, KL <deco33000@...> wrote:

 Thanks does that mean that I can reshape the whole "everything is a file" under unix?

 I don't want /etc /var /usr (and any other premade structure you find in every linux distro...) but manage it differently via our db.

 You confirm that doable?


Doable? Yes, everything is open source.

Sensible? Not really. I'm not sure you've considered the scale of
what you're asking. For example, /etc/passwd and /etc/hosts are deeply
tied into large amounts of software.

You can make *your* software use whatever configuration database you
want, but you'll have a lot of work to do if you want to move the user
database or DNS resolver information out of /etc.

Ross


Re: Debating best tool to use

Ross Burton <ross@...>
 

On Tue, 7 Sept 2021 at 11:22, KL <deco33000@...> wrote:
Thanks does that mean that I can reshape the whole "everything is a file" under unix?

I don't want /etc /var /usr (and any other premade structure you find in every linux distro...) but manage it differently via our db.

You confirm that doable?
Doable? Yes, everything is open source.

Sensible? Not really. I'm not sure you've considered the scale of
what you're asking. For example, /etc/passwd and /etc/hosts are deeply
tied into large amounts of software.

You can make *your* software use whatever configuration database you
want, but you'll have a lot of work to do if you want to move the user
database or DNS resolver information out of /etc.

Ross


shadow package not installing groupadd commanf in the filesystem #dunfell

cs.raryu <cs.raryu@...>
 

Hi,

The "shadow" package provides the "groupadd" tool. So I added the package to my recipe. Later when I checked in the rootfs, there is no groupadd command added in the filesystem. 

Can anyone please tell me why so?

Thank you.


Yocto Project Status WW36`21

Stephen Jolley
 

Current Dev Position: YP 3.4 M4

Next Deadline: 4th Oct. 2021 YP 3.4 M4 build

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.4 M3 is built and now in QA. This means we are now feature complete for 3.4 and will be working on stabilization.
  • YP 3.3.3 has been built and is waiting in the queue for QA after 3.4 M3. This includes the override syntax compatibility changes.
  • SBOM generation work was merged in and will be in the release as preliminary work on this topic, there will likely be some further tweaks during M4.
  • Further rust issues were resolved such as the centos7 build issues.
  • A work around for the glibc 2.34 clone3 syscalls in uninative was added and a new uninative built/released.
  • A fix for some of the multiconfig issues where deadlocked tasks and tasks were showing errors being on both the “covered and not covered lists” is available in master-next for review, hopefully addressing the issues that were being reported. This was possible from a better test case that was submitted enabling debugging.
  • Intermittent issues are ongoing and help is very much welcome on these issues. 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

 

Ways to contribute:

 

YP 3.4 Milestone Dates:

  • YP 3.4 M3 built and in QA
  • YP 3.4 M3 Release date 2021/09/03
  • YP 3.4 M4 build date 2021/10/04
  • YP 3.4 M4 Release date 2021/10/29

 

Planned upcoming dot releases:

  • YP 3.3.3 built and in QA
  • YP 3.3.3 release date 2021/10/1
  • YP 3.1.11 build date 2021/09/13
  • YP 3.1.11 release date 2021/9/24

 

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

 


add raspivid to the yocto image for raspberrypi4-64

safouane maaloul
 

Hi, in the first place i succeeded to add raspivid to my image yocto of raspberrypi0-wifi. I did so by adding the userland recipe. But when i try doing so with raspberrypi4-64. Idon't get raspivid when i add the userland recipe to my image. Do you have any idea why it don't work with the raspberrypi4-64?
Thanks,
Safouane


Re: Debating best tool to use

KL <deco33000@...>
 


Thanks does that mean that I can reshape the whole "everything is a file" under unix?

I don't want /etc /var /usr (and any other premade structure you find in every linux distro...) but manage it differently via our db.

You confirm that doable?
--

22:03, 6 September 2021, Khem Raj <raj.khem@...>:

On Mon, Sep 6, 2021 at 9:10 AM KL <deco33000@...> wrote:



 Hi,

 I plan to have a minimal embedded system with BT, wifi, no gui, to host my application with my own webserver.

 My webserver+app are responsible to manage the OS (so I don't want anything else to do it). They receive new programs and load them according to my rules (that is our manager at work).

 I would like to avoid the plague of multiple configuration files put everywhere in files (like now in different profile directories...), but instead have my custom manager handle ALL the different settings for the OS (centralized point).

 We, at the office, compile and maintain the different software needed and send them by wifi.

 I want that OS to be built on top of Linux.

 Would Yocto enable me to do that? Is it the best tool for that?


Yes, it lets you build custom Linux distribution and eases the way to
add needed customization that one might require.


 Thanks,


 --
 MKL


 


Result of hello.service #yocto

yasminebenghozzi6@...
 

Hello, 
AFter creating hello.service, I want to know if this is correct because as saying Active:activated(auto-restart) (Result:exit-code) I really didn't understand iit that much, 
anyone can explain please if its correct? because its supposed to tell me that its working .


Re: [meta-security][PATCH] dm-verity-img.bbclass: Expose --data-block-size for configuration

Armin Kuster
 

merged.

thanks
Armin

On 9/1/21 7:18 AM, Paulo Neves wrote:
From: Christer Fletcher <christer.fletcher@...>

Add DM_VERITY_IMAGE_DATA_BLOCK_SIZE to be able to set the
--data-block-size used in veritysetup. Tuning this value effects the
performance and size of the resulting image.

Signed-off-by: Christer Fletcher <christer.fletcher@...>
Signed-off-by: Paulo Neves <paulo.neves1@...>
---
classes/dm-verity-img.bbclass | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/classes/dm-verity-img.bbclass b/classes/dm-verity-img.bbclass
index 16d395b..b311fc5 100644
--- a/classes/dm-verity-img.bbclass
+++ b/classes/dm-verity-img.bbclass
@@ -22,6 +22,9 @@
# is stored where it can be installed into associated initramfs rootfs.
STAGING_VERITY_DIR ?= "${TMPDIR}/work-shared/${MACHINE}/dm-verity"

+# Define the data block size to use in veritysetup.
+DM_VERITY_IMAGE_DATA_BLOCK_SIZE ?= "1024"
+
# Process the output from veritysetup and generate the corresponding .env
# file. The output from veritysetup is not very machine-friendly so we need to
# convert it to some better format. Let's drop the first line (doesn't contain
@@ -57,7 +60,7 @@ verity_setup() {

# Let's drop the first line of output (doesn't contain any useful info)
# and feed the rest to another function.
- veritysetup --data-block-size=1024 --hash-offset=$SIZE format $OUTPUT $OUTPUT | tail -n +2 | process_verity
+ veritysetup --data-block-size=${DM_VERITY_IMAGE_DATA_BLOCK_SIZE} --hash-offset=$SIZE format $OUTPUT $OUTPUT | tail -n +2 | process_verity
}

VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity"



M+ & H bugs with Milestone Movements WW36

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

14534

Online search feature really needs usability improvments.

randy.macleod@...

michael.opdenacker@...

3.4 M2

3.5 M2

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Enhancements/Bugs closed WW36!

Stephen Jolley
 

All,

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

Who

Count

randy.macleod@...

2

alexandre.belloni@...

1

michael.opdenacker@...

1

richard.purdie@...

1

Grand Total

5

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Current high bug count owners for Yocto Project 3.4

Stephen Jolley
 

All,

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

Who

Count

michael.opdenacker@...

36

ross@...

31

richard.purdie@...

22

david.reyna@...

22

bruce.ashfield@...

16

randy.macleod@...

14

trevor.gamblin@...

13

timothy.t.orling@...

12

sakib.sajal@...

10

JPEWhacker@...

10

bluelightning@...

7

kai.kang@...

7

mhalstead@...

5

tony.tascioglu@...

5

Qi.Chen@...

4

hongxu.jia@...

4

chee.yang.lee@...

3

mingli.yu@...

3

alejandro@...

2

jaewon@...

2

alexandre.belloni@...

2

yf3yu@...

2

akuster808@...

2

yi.zhao@...

2

mshah@...

2

mister_rs@...

1

thomas.perrot@...

1

devendra.tewari@...

1

jon.mason@...

1

tonyb@...

1

paul.gortmaker@...

1

john.kaldas.enpj@...

1

pgowda.cve@...

1

diego.sueiro@...

1

open.source@...

1

douglas.royds@...

1

Martin.Jansa@...

1

mostthingsweb@...

1

pokylinux@...

1

yoctoproject@...

1

jay.shen.teoh@...

1

nicolas.dechesne@...

1

vinay.m.engg@...

1

kergoth@...

1

ydirson@...

1

mark.hatle@...

1

matthewzmd@...

1

sangeeta.jain@...

1

saul.wold@...

1

weaverjs@...

1

raj.khem@...

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 383 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.4”, “3.5, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.

 

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

 

2721 - 2740 of 57361