Date   

M+ & H bugs with Milestone Movements WW06

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

5322

Global DNS fallback mechanism not present in poky distro

kai.kang@...

kai.kang@...

3.3 M2

3.3 M3

 

7600

syslinux: port extX support patches to syslinux community

randy.macleod@...

sakib.sajal@...

3.3 M3

3.4 M1

 

11385

poky-container: clarify that meta-data should be checked out using native tools that run the host and not with tools in container

timothy.t.orling@...

timothy.t.orling@...

3.3 M2

3.4 M1

 

11766

nobody group added by systemd sysusers.d

yi.zhao@...

yi.zhao@...

3.3 M2

3.3 M3

 

12060

It is possible to specify a PACKAGE and a PKG_ rename that conflict

kai.kang@...

kai.kang@...

3.3 M2

3.3 M4

 

12279

enhance manifest not found warning

kai.kang@...

kai.kang@...

3.3 M2

3.3 M3

 

12342

lib32-core-image-sato -ctestimage failed due to wrong package names

kai.kang@...

kai.kang@...

3.3 M2

3.3 M3

 

12917

Warnings from nightly-multilib builds (build-deps)

kai.kang@...

kai.kang@...

3.3 M2

3.3 M3

 

13288

pseudo should not follow symlinks in /proc

randy.macleod@...

sakib.sajal@...

3.3 M4

3.3 M3

 

13320

Update license files to match current SPDX names and license contents

randy.macleod@...

idadelm@...

3.3 M2

3.3 M3

 

13355

RDEPENDS does not work properly for native builds (only supports recipe names, not package names)

richard.purdie@...

richard.purdie@...

3.3 M2

3.3 M3

 

13411

ptest-perl.bbclass run-ptest is too greedy for SKIP

timothy.t.orling@...

timothy.t.orling@...

3.3 M2

3.4 M1

 

13520

many valgrind tests fail for arm64

randy.macleod@...

stacygaikovaia@...

3.3 M2

3.4 M1

 

13508

Meson detects googletest installed on system

hongxu.jia@...

hongxu.jia@...

3.3 M2

3.4 M4

 

13527

Add SPDX license headers to all source files for layerindex-web

randy.macleod@...

idadelm@...

3.3 M2

3.3 M3

 

13529

Add SPDX license headers to all source files for prelink-cross

randy.macleod@...

idadelm@...

3.3 M2

3.3 M3

 

13631

core-image-full-cmdline qemumips systemd boot failure

randy.macleod@...

unassigned@...

3.3 M2

3.3 M3

 

13690

runqemu with slirp, forwarded host ports are not available on host

timothy.t.orling@...

timothy.t.orling@...

3.3 M2

3.4 M1

 

13766

Using TCLIB=musl results in SDKs producing incompatible binaries

randy.macleod@...

sakib.sajal@...

3.3 M4

3.4 M1

 

13841

quilt ptest intermittent failure

joe.slater@...

joe.slater@...

3.3 M2

3.3 M3

 

13841

quilt ptest intermittent failure

joe.slater@...

joe.slater@...

3.3 M3

Future

 

13930

Port the CROPS toaster-container selenium tests to the Autobuilder

timothy.t.orling@...

timothy.t.orling@...

3.3 M2

3.4 M2

 

13938

devtool modify virtual/kernel fails when EXTRAVERSION field is empty in Makefile

timothy.t.orling@...

timothy.t.orling@...

3.3 M2

3.4 M1

 

14098

absolute path in TEMPLATECONF should be rejected or warned, makes ext-sdk uninstallable

timothy.t.orling@...

timothy.t.orling@...

3.3 M2

3.4 M2

 

14099

PACKAGE_EXCLUDE not removing packages when PACKAGE_CLASSES = "package_deb"

randy.macleod@...

stacygaikovaia@...

3.3 M2

3.3 M3

 

14117

When ifupdown ist configured for DHCP with IPv6 the system boot hangs

yi.zhao@...

yi.zhao@...

3.3 M2

3.3 M3

 

14118

systemd services not enabled when using package feed

kai.kang@...

kai.kang@...

3.3 M2

3.3 M3

 

14126

resolvconf incompatible with busybox flock

randy.macleod@...

newcomer@...

3.3 M2

3.3 M3

 

14139

systemd user/groups different on opkg vs rpm images

hongxu.jia@...

hongxu.jia@...

3.3 M2

3.4 M4

 

14152

cups: under systemd needs to use /run/cups as rundir

kai.kang@...

kai.kang@...

3.3 M2

3.3 M3

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Enhancements/Bugs closed WW06!

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

5

kai.kang@...

1

Grand Total

6

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 WW06 of who have open medium or higher bugs and enhancements against YP 3.3.   There are 57 possible work days left until the final release candidates for YP 3.3 needs to be released.

Who

Count

richard.purdie@...

35

ross@...

26

david.reyna@...

20

bluelightning@...

16

bruce.ashfield@...

11

JPEWhacker@...

10

trevor.gamblin@...

9

kai.kang@...

7

mark.morton@...

7

akuster808@...

7

chee.yang.lee@...

6

raj.khem@...

5

Qi.Chen@...

5

sakib.sajal@...

5

yifan.yu@...

5

yi.zhao@...

4

randy.macleod@...

4

idadelm@...

4

hongxu.jia@...

4

stacygaikovaia@...

3

alejandro@...

3

mingli.yu@...

3

timothy.t.orling@...

3

mostthingsweb@...

3

matthewzmd@...

2

jon.mason@...

2

nicolas.dechesne@...

2

pokylinux@...

2

jeanmarie.lemetayer@...

2

sangeeta.jain@...

2

saul.wold@...

2

anuj.mittal@...

2

ydirson@...

2

jaewon@...

2

mhalstead@...

1

maxime.roussinbelanger@...

1

kamensky@...

1

pbarker@...

1

changqing.li@...

1

dl9pf@...

1

akuster@...

1

twoerner@...

1

liezhi.yang@...

1

kexin.hao@...

1

kergoth@...

1

Martin.Jansa@...

1

dorindabassey@...

1

mshah@...

1

shachar@...

1

steve@...

1

mister_rs@...

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

 


Re: #yocto #zeus #sdk populate_sdk_ext build failing #yocto #zeus #sdk

Khem Raj
 

That means it’s having issues with checksums is there any AUTOREV being used ?

I would suggest to build without your changes and see if you can get an eSDK 

On Mon, Feb 8, 2021 at 9:09 AM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote:

I configured SDK for:

SDK_EXT_TYPE = "minimal"
SDK_INCLUDE_TOOLCHAIN = "1"
SDK_INCLUDE_PKGDATA = "0"

And I still see "Error:  Failed to generate filtered task list for extensible SDK..."

In my latest log I also see:

"Error: Task quilt-native.do_fetch attempted to execute unexpectedly...
 ...
 This is usually due to missing ser=tscene tasks...
..."

Why might the filtered task list fail to generate correctly ?

This appears to be the real issue, and then it dies a slow death...

Thanks,
Steve


-----Original Message-----
From: Khem Raj <raj.khem@...>
Sent: Tuesday, February 2, 2021 10:37 PM
To: Monsees, Steven C (US) <steven.monsees@...>
Cc: yocto@...
Subject: Re: [yocto] #yocto #zeus #sdk populate_sdk_ext build failing

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


it seems bitbake does not execute when its trying to configure eSDK for install. Perhaps you can try to see some logs inside the esdk build area to check if there is further info.
secondly, try to build an esdk for core-image-minimal and see if that works.

On Fri, Jan 29, 2021 at 3:04 PM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote:
>
>
>
> I need some help in understanding why the SDK EXT is failing to build
> under zeus…
>
>
>
> Can someone explain why the extended sdk build fails and how I might resolve ?
>
>
>
> sbcb-defaultfs kernel builds and boots correctly…
>
>
>
> SDK builds under zeus for sbcb-defaultfs :
>
>
>
> bitbake sbcb-defaultfs-full -c populate_sdk    -WORKING CORRECTLY
>
>
>
> bitbake sbcb-defaultfs-full -c populate_sdk_ext  -Fails build with the following Errors:
>
>
>
> 17:13 smonsees@yix490016
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/s
> bcb-default> bitbake sbcb-defaultfs-full -c populate_sdk_ext
>
> Loading cache: 100%
> |###########################################################| Time:
> 0:00:00
>
> Loaded 3645 entries from dependency cache.
>
> NOTE: Resolving any missing task queue dependencies
>
>
>
> Build Configuration:
>
> BB_VERSION           = "1.44.0"
>
> BUILD_SYS            = "x86_64-linux"
>
> NATIVELSBSTRING      = "rhel-7.9"
>
> TARGET_SYS           = "x86_64-poky-linux"
>
> MACHINE              = "sbcb-default"
>
> DISTRO               = "limws"
>
> DISTRO_VERSION       = "3.0.4"
>
> TUNE_FEATURES        = "m64 corei7"
>
> TARGET_FPU           = ""
>
> meta
>
> meta-poky            = "my_yocto_3.0.4:f2eb22a8783f1eecf99bd4042695bab920eed00e"
>
> meta-perl
>
> meta-python
>
> meta-filesystems
>
> meta-networking
>
> meta-initramfs
>
> meta-oe              = "zeus:2b5dd1eb81cd08bc065bc76125f2856e9383e98b"
>
> meta                 = "master:a32ddd2b2a51b26c011fa50e441df39304651503"
>
> meta-intel           = "zeus:d9942d4c3a710406b051852de7232db03c297f4e"
>
> meta-intel
>
> workspace            = "v2019.02:f635a364c55f1fb12519aff54924a0a5b947091e"
>
>
>
> Initialising tasks: 100%
> |######################################################| Time: 0:00:04
>
> Checking sstate mirror object availability: 100%
> |##############################| Time: 0:00:00
>
> Sstate summary: Wanted 503 Found 298 Missed 205 Current 1936 (59%
> match, 91% complete)
>
> NOTE: Executing Tasks
>
> NOTE: Setscene tasks completed
>
> WARNING: rpcsvc-proto-native-1.4+gitAUTOINC+9bc3b5b785-r0 do_fetch:
> Failed to fetch URL git://github.com/thkukuk/rpcsvc-proto, attempting
> MIRRORS if available
>
> WARNING: nativesdk-libnss-nis-3.1+gitAUTOINC+062f31999b-r0 do_fetch:
> Failed to fetch URL git://github.com/thkukuk/libnss_nis, attempting
> MIRRORS if available
>
> NOTE: Excluding local workspace layer
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/s
> bcb-default/workspace from extensible SDK
>
> ERROR: sbcb-defaultfs-full-1.0-r0 do_populate_sdk_ext: Failed to generate filtered task list for extensible SDK:
>
> /bin/bash: line 0: .: .: is a directory
>
> ERROR: bitbake failed:
>
> /bin/sh: bitbake: command not found
>
> ERROR: sbcb-defaultfs-full-1.0-r0 do_populate_sdk_ext: Error executing a python function in exec_python_func() autogenerated:
>
>
>
> The stack trace of python calls that resulted in this exception/failure was:
>
> File: 'exec_python_func() autogenerated', lineno: 2, function:
> <module>
>
>      0001:
>
> *** 0002:copy_buildsystem(d)
>
>      0003:
>
> File:
> '/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/classes/populate_
> sdk_ext.bbclass', lineno: 444, function: copy_buildsystem
>
>      0440:    sdk_ext_type = d.getVar('SDK_EXT_TYPE')
>
>      0441:    if (sdk_ext_type != 'minimal' or sdk_include_toolchain or derivative) and not sdk_include_nativesdk:
>
>      0442:        # Create the filtered task list used to generate the sstate cache shipped with the SDK
>
>      0443:        tasklistfn = d.getVar('WORKDIR') + '/tasklist.txt'
>
> *** 0444:        create_filtered_tasklist(d, baseoutpath, tasklistfn, conf_initpath)
>
>      0445:    else:
>
>      0446:        tasklistfn = None
>
>      0447:
>
>      0448:    if os.path.exists(builddir + '/cache/bb_unihashes.dat'):
>
> File:
> '/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/classes/populate_
> sdk_ext.bbclass', lineno: 180, function: create_filtered_tasklist
>
>      0176:        # Clean out residue of running bitbake, which check_sstate_task_list()
>
>      0177:        # will effectively do
>
>      0178:        clean_esdk_builddir(d, sdkbasepath)
>
>      0179:    finally:
>
> *** 0180:        os.replace(sdkbasepath + '/conf/local.conf.bak', sdkbasepath + '/conf/local.conf')
>
>      0181:
>
>      0182:python copy_buildsystem () {
>
>      0183:    import re
>
>      0184:    import shutil
>
> Exception: FileNotFoundError: [Errno 2] No such file or directory: '/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-full/1.0-r0/sdk-ext/image//opt/limws/3.0.4/conf/local.conf.bak' -> '/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-full/1.0-r0/sdk-ext/image//opt/limws/3.0.4/conf/local.conf'
>
>
>
> ERROR: Logfile of failure stored in:
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/s
> bcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-full/1.0-r
> 0/temp/log.do_populate_sdk_ext.14130
>
> ERROR: Task (/disk0/scratch/smonsees/yocto/workspace_3/poky/../meta-bae/meta-limws/meta-intel/recipes-core/images/sbcb-defaultfs-full.bb:do_populate_sdk_ext) failed with exit code '1'
>
> NOTE: Tasks Summary: Attempted 6770 tasks of which 6274 didn't need to be rerun and 1 failed.
>
>
>
> Summary: 1 task failed:
>
>   
> /disk0/scratch/smonsees/yocto/workspace_3/poky/../meta-bae/meta-limws/
> meta-intel/recipes-core/images/sbcb-defaultfs-full.bb:do_populate_sdk_
> ext
>
> Summary: There were 2 WARNING messages shown.
>
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>
> 17:49 smonsees@yix490016
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/s
> bcb-default>
>
>
>
>




Re: #yocto #zeus #sdk populate_sdk_ext build failing #yocto #zeus #sdk

Monsees, Steven C (US)
 

I configured SDK for:

SDK_EXT_TYPE = "minimal"
SDK_INCLUDE_TOOLCHAIN = "1"
SDK_INCLUDE_PKGDATA = "0"

And I still see "Error: Failed to generate filtered task list for extensible SDK..."

In my latest log I also see:

"Error: Task quilt-native.do_fetch attempted to execute unexpectedly...
...
This is usually due to missing ser=tscene tasks...
..."

Why might the filtered task list fail to generate correctly ?

This appears to be the real issue, and then it dies a slow death...

Thanks,
Steve

-----Original Message-----
From: Khem Raj <raj.khem@gmail.com>
Sent: Tuesday, February 2, 2021 10:37 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #zeus #sdk populate_sdk_ext build failing

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


it seems bitbake does not execute when its trying to configure eSDK for install. Perhaps you can try to see some logs inside the esdk build area to check if there is further info.
secondly, try to build an esdk for core-image-minimal and see if that works.

On Fri, Jan 29, 2021 at 3:04 PM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@lists.yoctoproject.org> wrote:



I need some help in understanding why the SDK EXT is failing to build
under zeus…



Can someone explain why the extended sdk build fails and how I might resolve ?



sbcb-defaultfs kernel builds and boots correctly…



SDK builds under zeus for sbcb-defaultfs :



bitbake sbcb-defaultfs-full -c populate_sdk -WORKING CORRECTLY



bitbake sbcb-defaultfs-full -c populate_sdk_ext -Fails build with the following Errors:



17:13 smonsees@yix490016
/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/s
bcb-default> bitbake sbcb-defaultfs-full -c populate_sdk_ext

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

Loaded 3645 entries from dependency cache.

NOTE: Resolving any missing task queue dependencies



Build Configuration:

BB_VERSION = "1.44.0"

BUILD_SYS = "x86_64-linux"

NATIVELSBSTRING = "rhel-7.9"

TARGET_SYS = "x86_64-poky-linux"

MACHINE = "sbcb-default"

DISTRO = "limws"

DISTRO_VERSION = "3.0.4"

TUNE_FEATURES = "m64 corei7"

TARGET_FPU = ""

meta

meta-poky = "my_yocto_3.0.4:f2eb22a8783f1eecf99bd4042695bab920eed00e"

meta-perl

meta-python

meta-filesystems

meta-networking

meta-initramfs

meta-oe = "zeus:2b5dd1eb81cd08bc065bc76125f2856e9383e98b"

meta = "master:a32ddd2b2a51b26c011fa50e441df39304651503"

meta-intel = "zeus:d9942d4c3a710406b051852de7232db03c297f4e"

meta-intel

workspace = "v2019.02:f635a364c55f1fb12519aff54924a0a5b947091e"



Initialising tasks: 100%
|######################################################| Time: 0:00:04

Checking sstate mirror object availability: 100%
|##############################| Time: 0:00:00

Sstate summary: Wanted 503 Found 298 Missed 205 Current 1936 (59%
match, 91% complete)

NOTE: Executing Tasks

NOTE: Setscene tasks completed

WARNING: rpcsvc-proto-native-1.4+gitAUTOINC+9bc3b5b785-r0 do_fetch:
Failed to fetch URL git://github.com/thkukuk/rpcsvc-proto, attempting
MIRRORS if available

WARNING: nativesdk-libnss-nis-3.1+gitAUTOINC+062f31999b-r0 do_fetch:
Failed to fetch URL git://github.com/thkukuk/libnss_nis, attempting
MIRRORS if available

NOTE: Excluding local workspace layer
/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/s
bcb-default/workspace from extensible SDK

ERROR: sbcb-defaultfs-full-1.0-r0 do_populate_sdk_ext: Failed to generate filtered task list for extensible SDK:

/bin/bash: line 0: .: .: is a directory

ERROR: bitbake failed:

/bin/sh: bitbake: command not found

ERROR: sbcb-defaultfs-full-1.0-r0 do_populate_sdk_ext: Error executing a python function in exec_python_func() autogenerated:



The stack trace of python calls that resulted in this exception/failure was:

File: 'exec_python_func() autogenerated', lineno: 2, function:
<module>

0001:

*** 0002:copy_buildsystem(d)

0003:

File:
'/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/classes/populate_
sdk_ext.bbclass', lineno: 444, function: copy_buildsystem

0440: sdk_ext_type = d.getVar('SDK_EXT_TYPE')

0441: if (sdk_ext_type != 'minimal' or sdk_include_toolchain or derivative) and not sdk_include_nativesdk:

0442: # Create the filtered task list used to generate the sstate cache shipped with the SDK

0443: tasklistfn = d.getVar('WORKDIR') + '/tasklist.txt'

*** 0444: create_filtered_tasklist(d, baseoutpath, tasklistfn, conf_initpath)

0445: else:

0446: tasklistfn = None

0447:

0448: if os.path.exists(builddir + '/cache/bb_unihashes.dat'):

File:
'/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/classes/populate_
sdk_ext.bbclass', lineno: 180, function: create_filtered_tasklist

0176: # Clean out residue of running bitbake, which check_sstate_task_list()

0177: # will effectively do

0178: clean_esdk_builddir(d, sdkbasepath)

0179: finally:

*** 0180: os.replace(sdkbasepath + '/conf/local.conf.bak', sdkbasepath + '/conf/local.conf')

0181:

0182:python copy_buildsystem () {

0183: import re

0184: import shutil

Exception: FileNotFoundError: [Errno 2] No such file or directory: '/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-full/1.0-r0/sdk-ext/image//opt/limws/3.0.4/conf/local.conf.bak' -> '/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-full/1.0-r0/sdk-ext/image//opt/limws/3.0.4/conf/local.conf'



ERROR: Logfile of failure stored in:
/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/s
bcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-full/1.0-r
0/temp/log.do_populate_sdk_ext.14130

ERROR: Task (/disk0/scratch/smonsees/yocto/workspace_3/poky/../meta-bae/meta-limws/meta-intel/recipes-core/images/sbcb-defaultfs-full.bb:do_populate_sdk_ext) failed with exit code '1'

NOTE: Tasks Summary: Attempted 6770 tasks of which 6274 didn't need to be rerun and 1 failed.



Summary: 1 task failed:


/disk0/scratch/smonsees/yocto/workspace_3/poky/../meta-bae/meta-limws/
meta-intel/recipes-core/images/sbcb-defaultfs-full.bb:do_populate_sdk_
ext

Summary: There were 2 WARNING messages shown.

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

17:49 smonsees@yix490016
/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/s
bcb-default>




Re: PREFERRED_VERSION_pn-: which version is selected?

Quentin Schulz
 

Hi Mauro,

On Mon, Feb 08, 2021 at 05:23:36PM +0100, Mauro Ziliani wrote:
My purpose is this.

For image-recipe_1.0.0 I need recip1 version 0.9

For image-recipe_1.1.0 I need recip1 version 1.0
You can't. Because recipes cannot impact other recipes.

Now there's a catch, which applies to a VERY specific corner case.

Let's say recip1 is a final package (recip1 recipe is in no DEPENDS of any
recipe, recip1 recipe packages are in no RDEPENDS, only recip1 packages are
mentioned in image recipes).

You can rename recip1_0.9 to recip109_0.9.bb and in your
image-recipe_1.0.0 add recip109 to IMAGE_INSTALL.
in image-recipe_1.1.0 have recip1 in IMAGE_INSTALL.

Obviously, since the recipe name is now different, they are different
recipes to Yocto, which means DEPENDS and RDEPENDS won't be
automatically "updated" to get the version you selected in image-recipe
(because... recipes can't modify other recipes).

Cheers,
Quentin


Re: PREFERRED_VERSION_pn-: which version is selected?

Mauro Ziliani
 

Thanks all for suggestions ed corrections

MZ

Il 08/02/21 12:14, Quentin Schulz ha scritto:
Hi Mauro,

On Mon, Feb 08, 2021 at 11:52:33AM +0100, Mauro Ziliani wrote:
Hi all.

I'm working with Krogoth on imx6


I have the same recipe with different versions

recipe1_0.9.bb

recipe1_1.0.bb


In the image recipe I put


image-recipe.bb

IMAGE_INSTALL_append := " \

    recipe1 \

"

PREFERRED_VERSION_pn-recipe1 := "0.9"
Yocto chant #1: Recipe data is local, conf data is global.

In other words, you cannot modify other recipes from one recipe.

Since image recipes are recipes, your PREFERRED_VERSION ni your image
recipe is effectively a no-op.

On a side note, := operator is rarely seen outside of
FILESEXTRAPATHS_prepend in bbappend, try to keep it this way.

If I do

 bitbake -s

I get

recipe1    :1.0-r0


If I do

bitbake image-recipe


in image-recipe.manifest I look

recipe1  1.0-r0


Why is not selected the preferred version?

How can I choose the recipe's version I'd like?
In a configuration file: local.conf, distro.conf, machine.conf.

Though, it is heavily discouraged to use local.conf for anything except
debugging sessions, as it is meant only for **local** configuration and
isn't supposed to be versioned.

Cheers,
Quentin


Re: PREFERRED_VERSION_pn-: which version is selected?

Mauro Ziliani
 

My purpose is this.

For image-recipe_1.0.0 I need recip1 version 0.9

For image-recipe_1.1.0 I need recip1 version 1.0


How I can solve this?


Best regards

  MZ

Il 08/02/21 12:09, Josef Holzmayr ha scritto:
Howdy!

Am Mo., 8. Feb. 2021 um 11:52 Uhr schrieb Mauro Ziliani <mauro@faresoftware.it>:
In the image recipe I put

image-recipe.bb

IMAGE_INSTALL_append := " \
recipe1 \
"

PREFERRED_VERSION_pn-recipe1 := "0.9"
As usual, recipe data is local, conf data is global. Setting things
that should affect other recipes (like PREFERRED_VERSION) does not
work inside a recipe - and an image recipe is still just a recipe.
This needs to go into the DISTRO config, usually.

Greetz


Re: PREFERRED_VERSION_pn-: which version is selected?

Quentin Schulz
 

Hi Mauro,

On Mon, Feb 08, 2021 at 11:52:33AM +0100, Mauro Ziliani wrote:
Hi all.

I'm working with Krogoth on imx6


I have the same recipe with different versions

recipe1_0.9.bb

recipe1_1.0.bb


In the image recipe I put


image-recipe.bb

IMAGE_INSTALL_append := " \

    recipe1 \

"

PREFERRED_VERSION_pn-recipe1 := "0.9"
Yocto chant #1: Recipe data is local, conf data is global.

In other words, you cannot modify other recipes from one recipe.

Since image recipes are recipes, your PREFERRED_VERSION ni your image
recipe is effectively a no-op.

On a side note, := operator is rarely seen outside of
FILESEXTRAPATHS_prepend in bbappend, try to keep it this way.


If I do

 bitbake -s

I get

recipe1    :1.0-r0


If I do

bitbake image-recipe


in image-recipe.manifest I look

recipe1  1.0-r0


Why is not selected the preferred version?

How can I choose the recipe's version I'd like?
In a configuration file: local.conf, distro.conf, machine.conf.

Though, it is heavily discouraged to use local.conf for anything except
debugging sessions, as it is meant only for **local** configuration and
isn't supposed to be versioned.

Cheers,
Quentin


Re: PREFERRED_VERSION_pn-: which version is selected?

Martin Jansa
 

And the variable should be named PREFERRED_VERSION_recipe1 (it's not using pn as an override).


On Mon, Feb 8, 2021 at 12:10 PM Josef Holzmayr <jester@...> wrote:
Howdy!

Am Mo., 8. Feb. 2021 um 11:52 Uhr schrieb Mauro Ziliani <mauro@...>:
> In the image recipe I put
>
> image-recipe.bb
>
> IMAGE_INSTALL_append := " \
>      recipe1 \
> "
>
> PREFERRED_VERSION_pn-recipe1 := "0.9"

As usual, recipe data is local, conf data is global. Setting things
that should affect other recipes (like PREFERRED_VERSION) does not
work inside a recipe - and an image recipe is still just a recipe.
This needs to go into the DISTRO config, usually.

Greetz




Re: PREFERRED_VERSION_pn-: which version is selected?

Josef Holzmayr
 

Howdy!

Am Mo., 8. Feb. 2021 um 11:52 Uhr schrieb Mauro Ziliani <mauro@faresoftware.it>:
In the image recipe I put

image-recipe.bb

IMAGE_INSTALL_append := " \
recipe1 \
"

PREFERRED_VERSION_pn-recipe1 := "0.9"
As usual, recipe data is local, conf data is global. Setting things
that should affect other recipes (like PREFERRED_VERSION) does not
work inside a recipe - and an image recipe is still just a recipe.
This needs to go into the DISTRO config, usually.

Greetz


PREFERRED_VERSION_pn-: which version is selected?

Mauro Ziliani
 

Hi all.

I'm working with Krogoth on imx6


I have the same recipe with different versions

recipe1_0.9.bb

recipe1_1.0.bb


In the image recipe I put


image-recipe.bb

IMAGE_INSTALL_append := " \

    recipe1 \

"

PREFERRED_VERSION_pn-recipe1 := "0.9"


If I do

 bitbake -s

I get

recipe1    :1.0-r0


If I do

bitbake image-recipe


in image-recipe.manifest I look

recipe1  1.0-r0


Why is not selected the preferred version?

How can I choose the recipe's version I'd like?


Best regards,

   MZ


Re: devtool question/issue

Josef Holzmayr
 

Hi David!

Am Mo., 8. Feb. 2021 um 01:01 Uhr schrieb David Gartner <gartnerd@gmail.com>:
I found the issue that was causing my problem. Just an FYI if anyone else happens to run into this.

There was a file named ".devtoolbase" in /mnt/YB. I think this was a remenant of some previous work I was doing with yocto. I'm not sure what the purpose of this file is but once I removed it devtool no longer errorred out.
Oh great, thanks for the heads up. I am actually the one who did the
video, and just returned into office mondayishly and would have tried
probably this afternoon. But that I would have never found, as I
usually start out in clean slate containers, and I use devtool a lot
in there with builds even scattered out over multiple mount points.So
glad you figurede out and took the time to share!

Greetz


Re: #yocto CORE_IMAGE_EXTRA_INSTALL Where can I find a list of valid package names? #yocto

Mike Looijmans
 

Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: mike.looijmans@topicproducts.com
W: www.topicproducts.com

Please consider the environment before printing this e-mail
On 04-02-2021 09:12, Josef Holzmayr via lists.yoctoproject.org wrote:
oe-pkgdata-util list-pkgs
Oh, I've been using OE from the times I still had hair on my head, but never found this gem. Thanks for the tip!

--
Mike Looijmans


[meta-selinux][PATCH] remove obsolete e2fsprogs bbappend

hongxu
 

Since oe-core commit [f51835e022 e2fsprogs: upgrade 1.45.6 -> 1.45.7] applied,
the backport misc_create_inode.c-label_rootfs.patch is not required

The lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch is not used by the recipe,
so also remove it.

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
---
.../e2fsprogs/e2fsprogs_%.bbappend | 1 -
.../e2fsprogs/e2fsprogs_selinux.inc | 3 --
...t2fs-ext2_ext_attr.h-add-xattr-index.patch | 20 ---------
.../misc_create_inode.c-label_rootfs.patch | 45 -------------------
4 files changed, 69 deletions(-)
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
delete mode 100644 recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
delete mode 100644 recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch

diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend b/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
deleted file mode 100644
index 7719d3b..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-require ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', '${BPN}_selinux.inc', '', d)}
diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc b/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
deleted file mode 100644
index 9cbb7fe..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
-
-SRC_URI += "file://misc_create_inode.c-label_rootfs.patch"
diff --git a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch b/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
deleted file mode 100644
index b87c414..0000000
--- a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-Add xattr name index for xattrs with the 'security' prefix. These are defined
-in the ext(2|3|4)/xattr.h in the kernel. We use the EXT2 prefix for consistency
-with e2fslibs naming.
-
-Signed-off-by: Philip Tricca <flihp@twobit.us>
-
-Index: e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-===================================================================
---- e2fsprogs-1.42.9.orig/lib/ext2fs/ext2_ext_attr.h
-+++ e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-@@ -15,6 +15,9 @@
- /* Maximum number of references to one attribute block */
- #define EXT2_EXT_ATTR_REFCOUNT_MAX 1024
-
-+/* Name indexes */
-+#define EXT2_XATTR_INDEX_SECURITY 6
-+
- struct ext2_ext_attr_header {
- __u32 h_magic; /* magic number for identification */
- __u32 h_refcount; /* reference count */
diff --git a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch b/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
deleted file mode 100644
index 046e521..0000000
--- a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-From: Philip Tricca <flihp@twobit.us>
-To: tytso@mit.edu
-Cc: liezhi.yang@windriver.com
-Date: Sat, 20 Feb 2016 18:58:58 +0000
-Subject: [PATCH] misc/create_inode.c: Copy xattrs from root directory when populating fs.
-
-When copying a file system using the -d option the xattrs from the root
-directory need to be copied before the populate_fs recusion starts.
-
-Signed-off-by: Philip Tricca <flihp@twobit.us>
-Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
-
----
- misc/create_inode.c | 8 ++++++++
- 1 file changed, 8 insertions(+)
-
-diff --git a/misc/create_inode.c b/misc/create_inode.c
-index a7b6d348..cfd15922 100644
---- a/misc/create_inode.c
-+++ b/misc/create_inode.c
-@@ -979,6 +979,13 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- return retval;
- }
-
-+ retval = set_inode_xattr(fs, root, source_dir);
-+ if (retval) {
-+ com_err(__func__, retval,
-+ _("while setting xattrs for \"%s\""), source_dir);
-+ goto out;
-+ }
-+
- file_info.path_len = 0;
- file_info.path_max_len = 255;
- file_info.path = calloc(file_info.path_max_len, 1);
-@@ -987,6 +994,7 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- &file_info, fs_callbacks);
-
- free(file_info.path);
-+out:
- free(hdlinks.hdl);
- return retval;
- }
---
-2.11.1
-
--
2.29.2


Re: devtool question/issue

David Gartner <gartnerd@...>
 

I found the issue that was causing my problem. Just an FYI if anyone else happens to run into this.

There was a file named ".devtoolbase" in /mnt/YB. I think this was a remenant of some previous work I was doing with yocto. I'm not sure what the purpose of this file is but once I removed it devtool no longer errorred out.


[meta-selinux][PATCH] e2fsprogs: remove bbappend

Yi Zhao
 

Remove bbappend since the misc_create_inode.c-label_rootfs.patch has
been merged upstream[1].

[1] https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=7616fd6a599e44c5700c2c3a2e08979c6c5c747e

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
---
.../e2fsprogs/e2fsprogs_%.bbappend | 1 -
.../e2fsprogs/e2fsprogs_selinux.inc | 3 --
...t2fs-ext2_ext_attr.h-add-xattr-index.patch | 20 ---------
.../misc_create_inode.c-label_rootfs.patch | 45 -------------------
4 files changed, 69 deletions(-)
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
delete mode 100644 recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
delete mode 100644 recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch

diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend b/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
deleted file mode 100644
index 7719d3b..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-require ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', '${BPN}_selinux.inc', '', d)}
diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc b/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
deleted file mode 100644
index 9cbb7fe..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
-
-SRC_URI += "file://misc_create_inode.c-label_rootfs.patch"
diff --git a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch b/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
deleted file mode 100644
index b87c414..0000000
--- a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-Add xattr name index for xattrs with the 'security' prefix. These are defined
-in the ext(2|3|4)/xattr.h in the kernel. We use the EXT2 prefix for consistency
-with e2fslibs naming.
-
-Signed-off-by: Philip Tricca <flihp@twobit.us>
-
-Index: e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-===================================================================
---- e2fsprogs-1.42.9.orig/lib/ext2fs/ext2_ext_attr.h
-+++ e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-@@ -15,6 +15,9 @@
- /* Maximum number of references to one attribute block */
- #define EXT2_EXT_ATTR_REFCOUNT_MAX 1024
-
-+/* Name indexes */
-+#define EXT2_XATTR_INDEX_SECURITY 6
-+
- struct ext2_ext_attr_header {
- __u32 h_magic; /* magic number for identification */
- __u32 h_refcount; /* reference count */
diff --git a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch b/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
deleted file mode 100644
index 046e521..0000000
--- a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-From: Philip Tricca <flihp@twobit.us>
-To: tytso@mit.edu
-Cc: liezhi.yang@windriver.com
-Date: Sat, 20 Feb 2016 18:58:58 +0000
-Subject: [PATCH] misc/create_inode.c: Copy xattrs from root directory when populating fs.
-
-When copying a file system using the -d option the xattrs from the root
-directory need to be copied before the populate_fs recusion starts.
-
-Signed-off-by: Philip Tricca <flihp@twobit.us>
-Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
-
----
- misc/create_inode.c | 8 ++++++++
- 1 file changed, 8 insertions(+)
-
-diff --git a/misc/create_inode.c b/misc/create_inode.c
-index a7b6d348..cfd15922 100644
---- a/misc/create_inode.c
-+++ b/misc/create_inode.c
-@@ -979,6 +979,13 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- return retval;
- }
-
-+ retval = set_inode_xattr(fs, root, source_dir);
-+ if (retval) {
-+ com_err(__func__, retval,
-+ _("while setting xattrs for \"%s\""), source_dir);
-+ goto out;
-+ }
-+
- file_info.path_len = 0;
- file_info.path_max_len = 255;
- file_info.path = calloc(file_info.path_max_len, 1);
-@@ -987,6 +994,7 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- &file_info, fs_callbacks);
-
- free(file_info.path);
-+out:
- free(hdlinks.hdl);
- return retval;
- }
---
-2.11.1
-
--
2.25.1


Re: devtool question/issue

David Gartner <gartnerd@...>
 

After some experimentation it appears that devtool does not like running from a filesystem volume that does not contain my home directory. 

My current setup on a virtualized host has the following volumes:

Filesystem      Size  Used Avail Use% Mounted on

udev             32G     0   32G   0% /dev

tmpfs           6.3G  5.7M  6.3G   1% /run

/dev/sda         25G   11G   13G  46% /

tmpfs            32G     0   32G   0% /dev/shm

tmpfs           5.0M     0  5.0M   0% /run/lock

tmpfs            32G     0   32G   0% /sys/fs/cgroup

/dev/sdc        148G   39G  102G  28% /mnt/YB

tmpfs           6.3G     0  6.3G   0% /run/user/1000

My home directory is located on /dev/sda - devtool works for yocto projects on this volume

/dev/sdc - I added this volume so that I'd have more space while using yocto, but devtool complains and doesn't run here. I deleted the contents of /dev/sdc and re-tried following the tutorial given in my initial post. I can reproduce (e.g. create and run qemuarm images) everything upto the step where devtool needs to be used.

The short term solution would be to increase the size of /dev/sdc but this requires moving up to a more expensive plan from my cloud provider.

Any insight as to why this occurs


Re: [meta-virtualization]: dunfell docker run issues

Leon Woestenberg
 

Marek,

This might indeed indicate a configuration mismatch. Lots of stuff
comes up on Google that you might want to check.

One is a change in systemd that affects this. Sorry I don't have a
link ready anymore.

Regards,

Leon.




--
Leon Woestenberg
leon@sidebranch.com
T: +31 40 711 42 76
M: +31 6 472 30 372

Sidebranch Embedded Systems
Eindhoven, The Netherlands
http://www.sidebranch.com

On Thu, Feb 4, 2021 at 4:04 PM Marek Belisko <marek.belisko@gmail.com> wrote:

Hi,

I'm trying to run docker containers on orangepi and use
meta-virtualization layer to add docker. I've installed the docker-ce
package and everything seems to be fine.

But docker service seems fails to start with:
Feb 04 15:00:01 orange-pi-zero dockerd[495]: failed to start daemon:
Devices cgroup isn't mounted

I was trying to add various options to kernel command line like
described here: https://github.com/docker/cli/issues/2104

but it doesn't work. My command-line looks like:
...systemd.unified_cgroup_hierarchy=0 cgroup_enable=memory
cgroup_memory=1 swapaccount=1 cgroup_no_v1=all

Any other ideas what to check? Thanks a lot.

BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


1641 - 1660 of 53882