Date   

Re: [PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Ernst Sjöstrand <ernst.sjostrand@...>
 

There was a long thread about this on oe-core recently:
https://lists.openembedded.org/g/openembedded-core/message/157999

//Ernst


Re: [PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Ross Burton <ross@...>
 

My personal build machine has been crashing and dying due to overload
with the default ZSTD_THREADS, and the AB has had problems with xz due
to overload so I was being proactive and ensuring zstd is limited on
the AB the same way xz is.

Ross

On Tue, 23 Nov 2021 at 17:11, Alexander Kanavin <alex.kanavin@...> wrote:

Is there a particular reason?

Alex

On Tue, 23 Nov 2021 at 16:03, Ross Burton <ross@...> wrote:

Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 1 +
1 file changed, 1 insertion(+)

diff --git a/config.json b/config.json
index 7203783..c0543d9 100644
--- a/config.json
+++ b/config.json
@@ -47,6 +47,7 @@
"PARALLEL_MAKE = '-j 16 -l 52'",
"XZ_MEMLIMIT = '5%'",
"XZ_THREADS = '8'",
+ "ZSTD_THREADS = '8'",
"BB_TASK_NICE_LEVEL = '5'",
"BB_TASK_NICE_LEVEL:task-testimage = '0'",
"BB_TASK_IONICE_LEVEL = '2.7'",
--
2.25.1




Re: [qa-build-notification] [yocto] QA notification for completed autobuilder build (yocto-3.1.12.rc1)

Richard Purdie
 

On Tue, 2021-11-23 at 11:54 +0000, Teoh, Jay Shen wrote:
This is the full report for yocto-3.1.12.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.

new issue found

Bug 14622 - bsps-hw.bsps-hw.Test_Seek_bar_and_volume_control manual test case failure

======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14622

Thanks,
Jay
Thanks Jay.

The TSC discussed 3.1.12 and are happy for rc1 to be released.

Cheers,

Richard


Re: [PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Alexander Kanavin
 

Is there a particular reason?

Alex


On Tue, 23 Nov 2021 at 16:03, Ross Burton <ross@...> wrote:
Signed-off-by: Ross Burton <ross.burton@...>
---
 config.json | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config.json b/config.json
index 7203783..c0543d9 100644
--- a/config.json
+++ b/config.json
@@ -47,6 +47,7 @@
             "PARALLEL_MAKE = '-j 16 -l 52'",
             "XZ_MEMLIMIT = '5%'",
             "XZ_THREADS = '8'",
+            "ZSTD_THREADS = '8'",
             "BB_TASK_NICE_LEVEL = '5'",
             "BB_TASK_NICE_LEVEL:task-testimage = '0'",
             "BB_TASK_IONICE_LEVEL = '2.7'",
--
2.25.1





Yocto Project Status WW46`21

Stephen Jolley
 

Current Dev Position: YP 3.5 M1

Next Deadline: 6th Dec. 2021 YP 3.5 M1 build

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.3.4 was released
  • YP 3.1.12 has been through QA and is pending release approval.
  • YP 3.4.1 is due to be built after the current patchsets are reviewed and merge.
  • Next week is the Yocto Project Virtual Summit https://www.yoctoproject.org/yocto-project-summit-2021-11/ and OpenEmbedded Virtual Developer Meeting on Friday https://www.openembedded.org/wiki/OEDVM_Nov_2021
  • CVEs in hardknott and dunfell rose this week due to 14 busybox issues being added. Master remains roughly stable but we need to upgrade golang to fix some, the other issues in master do not yet have fixes in upstream (qemu, libarchive and nasm).
  • We continue to see a reduction in the number of patches in “Pending” state. Many thanks to everyone who has taken the time to review patch status and handle accordingly, particularly where they were accepted upstream. This will significantly benefit the project in the long term.
  • Intermittent issues continue to rise 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.5 Milestone Dates:

  • YP 3.5 M1 build date 2021/12/06
  • YP 3.5 M1 Release date 2021/12/17
  • YP 3.5 M2 build date 2022/01/10
  • YP 3.5 M2 Release date 2022/1/21
  • YP 3.5 M3 build date 2022/2/21
  • YP 3.5 M3 Release date 2022/03/04
  • YP 3.5 M4 build date 2022/04/04
  • YP 3.5 M4 Release date 2022/04/29

 

Upcoming dot releases:

  • YP 3.3.4 is released
  • YP 3.1.12 is out of QA
  • YP 3.4.1 build date 2021/11/22
  • YP 3.4.1 Release date 2021/12/03
  • YP 3.1.13 build date 2021/12/13
  • YP 3.1.13 Release date 2021/12/22
  • YP 3.1.14 build date 2022/01/24
  • YP 3.1.14 Release date 2022/02/04
  • YP 3.4.2 build date 2022/02/07
  • YP 3.4.2 Release date 2022/02/18
  • YP 3.1.15 build date 2022/03/14
  • YP 3.1.15 Release date 2022/03/25
  • YP 3.4.3 build date 2022/03/21
  • YP 3.4.3 Release date 2022/04/01
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06

 

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

 


[PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Ross Burton <ross@...>
 

Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 1 +
1 file changed, 1 insertion(+)

diff --git a/config.json b/config.json
index 7203783..c0543d9 100644
--- a/config.json
+++ b/config.json
@@ -47,6 +47,7 @@
"PARALLEL_MAKE =3D '-j 16 -l 52'",
"XZ_MEMLIMIT =3D '5%'",
"XZ_THREADS =3D '8'",
+ "ZSTD_THREADS =3D '8'",
"BB_TASK_NICE_LEVEL =3D '5'",
"BB_TASK_NICE_LEVEL:task-testimage =3D '0'",
"BB_TASK_IONICE_LEVEL =3D '2.7'",
--=20
2.25.1


[PATCH yocto-autobuilder-helper] config.json: build generic-arm64 instead of Juno

Ross Burton <ross@...>
 

generic-arm64 is the recommeded generic BSP for modern Arm deployments,
so ensure it is exercised in the autobuilder.

Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/config.json b/config.json
index f152b47..7203783 100644
--- a/config.json
+++ b/config.json
@@ -330,8 +330,8 @@
"SANITYTARGETS" : "core-image-sato:do_testsdk"
},
"step2": {
- "shortname": "Build for juno",
- "MACHINE": "juno",
+ "shortname": "Build for generic-arm64",
+ "MACHINE": "generic-arm64",
"BBTARGETS": "core-image-minimal core-image-sato core-im=
age-sato:do_populate_sdk",
"SANITYTARGETS" : "core-image-sato:do_testsdk"
}
--=20
2.25.1


Build ROS2 package that contains custom interfaces (msg, srv) #yocto

bojankoce
 

Hi, guys!

I have a DART-MX8M-Mini machine running Yocto Hardknott.

I properly added meta-ros layer and ROS2 foxy distro to our Yocto build by following instructions from here (Sanity Tests pass successfully).

With the help of devtool, I was able to build my custom ROS2 package (containing simple talker and listener nodes - link). For that to happen, I got some great support from the Yocto community - link.

Here is the content of my-first-yocto-pkg_git.bb recipe that enabled me to download my source code from the git and properly build the ROS2 package:

# Recipe created by recipetool
# This is the basis of a recipe and may need further editing in order to be fully functional.
# (Feel free to remove these comments when editing.)

# Unable to find any files that looked like license statements. Check the accompanying
# documentation and source headers and set LICENSE and LIC_FILES_CHKSUM accordingly.
#
# NOTE: LICENSE is being set to "CLOSED" to allow you to at least start building - if
# this is not accurate with respect to the licensing of the software being built (it
# will not be in most cases) you must specify the correct value before using this
# recipe for anything other than initial testing/development!

DESCRIPTION = "Examples of minimal publisher/subscriber using rclcpp."
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://package.xml;beginline=8;endline=8;md5=12c26a18c7f493fdc7e8a93b16b7c04f"

SRC_URI = "git://github.com/bojankoce/my_first_yocto_pkg;protocol=https"

# Modify these as desired
PV = "0.1.0"
SRCREV = "1312445de2e6861d9561c0f89f4827b94c2ff6b1"

S = "${WORKDIR}/git"

# NOTE: unable to map the following CMake package dependencies: rclcpp ament_lint_auto std_msgs ros_ament_cmake
inherit ros_distro_foxy
inherit ros_superflore_generated
inherit ros_ament_cmake

ROS_BUILD_DEPENDS = " \
    rclcpp \
    std-msgs \
"

ROS_BUILDTOOL_DEPENDS = " \
	ament-cmake-native \
"

ROS_EXPORT_DEPENDS = ""

ROS_BUILDTOOL_EXPORT_DEPENDS = ""

ROS_EXEC_DEPENDS = " \
    launch-ros \
    std-msgs \
"

DEPENDS = "${ROS_BUILD_DEPENDS} ${ROS_BUILDTOOL_DEPENDS}"

DEPENDS += "${ROS_EXPORT_DEPENDS} ${ROS_BUILDTOOL_EXPORT_DEPENDS}"

# Specify any options you want to pass to cmake using EXTRA_OECMAKE:
#EXTRA_OECMAKE = ""

I currently have a hard time building my ROS2 package that contains only custom ROS2 interfaces (messages and services).
CMakeLists.txt file of that package contains the following lines that are causing the build errors:

find_package(rosidl_default_generators REQUIRED)
...

rosidl_generate_interfaces(${PROJECT_NAME}
  "msg/MessageX.msg"
  "msg/MessageY.msg"
  "srv/SrvX.srv"
  "srv/SrvY.srv"
 )

Do you have any idea about what should be included as inherit xxxxx or within ROS_BUILD_DEPENDS/ROS_BUILDTOOL_DEPENDS /ROS_EXEC_DEPENDS ... in order to successfully generate the ROS2 package containing custom interfaces?

Thanks in advance for your time and efforts. It is appreciated.

Sincerely,
Bojan.


Re: QA notification for completed autobuilder build (yocto-3.1.12.rc1)

Teoh, Jay Shen
 

Hi all,

This is the full report for yocto-3.1.12.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.

new issue found

Bug 14622 - bsps-hw.bsps-hw.Test_Seek_bar_and_volume_control manual test case failure

======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14622

Thanks,
Jay

-----Original Message-----
From: yocto@... <yocto@...> On Behalf
Of Richard Purdie
Sent: Wednesday, 17 November, 2021 6:25 AM
To: <yocto@...> <yocto@...>
Cc: qa-build-notification <qa-build-notification@...>
Subject: [yocto] QA notification for completed autobuilder build (yocto-
3.1.12.rc1)

A build flagged for QA (yocto-3.1.12.rc1) was completed on the autobuilder and is
available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.1.12.rc1


Build hash information:

bitbake: c0348de8121c3a842bf44906f7e2f79e93f7275b
meta-agl: 0406cbb235fb08ce9e6f9d07e64e0932b20050a9
meta-arm: ce535dfb96de4d2529f091d7d85a7172c626001c
meta-aws: 2f72301f5a73279c4d2f12fc6218876629666e06
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 625da85e7b01b71cc310267b0ba7119eb139e9f7
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
meta-openembedded: 7889158dcd187546fc5e99fd81d0779cad3e8d17
oecore: 44b1970c40e9d73f6e63fb10cdc55837a26f5921
poky: 0839888394a6e42e96f9f0d201376eb38bc79b24



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...


Upgrade to version 1.40 broken WiFi

JH
 

Hi,

I built connman version 1.37 and wpa_supplicant in zeus, it worked
well. I have just upgraded OE / Yoctor to Honister, I built the
connman version 1.40 and ran it with wpa_applicant, but it is now
completely broken, no WiFi IP address assigned. I heard that a new
version of connman is going to replace wpa_supplicant by iwd, is that
correct? If it is true, I am not going to debug it with wpa_applicant,
I am not familiar with iwd, the Yocto does not have iwd option, are
there documents to build Honister connman with iwd?

Thank you.

Kind regards,

- JH


[meta-cgl][PATCH] resource-agents: Fix QA Issue:

leimaohui
 

ERROR: resource-agents-4.5.0-r0 do_package_qa: QA Issue: resource-agents installs files in /var/volatile, but it is expected to be empty [empty-dirs]

Signed-off-by: Lei Maohui <leimaohui@...>
---
.../cluster-resource-agents/resource-agents_4.5.0.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb
index 261681c..d6fb708 100644
--- a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb
+++ b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb
@@ -57,8 +57,7 @@ EXTRA_OECONF += "--disable-fatal-warnings \
--with-rsctmpdir=/var/run/heartbeat/rsctmp"

do_install:append() {
- rm -rf "${D}${localstatedir}/run"
- rmdir --ignore-fail-on-non-empty "${D}${localstatedir}"
+ rm -rf "${D}${localstatedir}"
}

# tickle_tcp is published under GPLv3, we just split it into ${PN}-extra,
--
2.25.1


Re: Problem installing python package from a wheel #bitbake #python

David Babich
 

I made it a little further by adding --no-cache-dir to the pip3 install command.  That got rid fo the warning about not being able to access the .cache/pip.  However I still have the error:

| ERROR: torch-1.10.0-cp36-cp36m-linux_aarch64.whl is not a supported wheel on this platform.


Problem installing python package from a wheel #bitbake #python

David Babich
 

Hi,
I'm attempting to create a recipe for pytorch for the TX2i using a wheel file obtained from here:

https://forums.developer.nvidia.com/t/pytorch-for-jetson-version-1-10-now-available/72048

Here is what I have so far for the recipe:

```

DESCRIPTION = "NVIDIA's Python Torch"

HOMEPAGE = "https://nvidia.com"

LICENSE = "BSD-3-Clause"

LIC_FILES_CHKSUM = "file://../LICENSE;md5=91a5dfdaccf53b27488cb3a639e986d5"

 

inherit setuptools3

 

SRC_URI = "\

        file://torch-1.10.0-cp36-cp36m-linux_aarch64.whl \

        file://LICENSE \

"

 

COMPATIBLE_MACHINE = "jetson-tx2-devkit-tx2i"

PACKAGE_ARCH = "${MACHINE_ARCH}"

 

S = "${WORKDIR}/${PN}-${PV}"

 

do_configure() {

        :

}

 

do_compile() {

        :

}

 

do_install() {

        pip3 install ${WORKDIR}/torch-1.10.0-cp36-cp36m-linux_aarch64.whl

}

 

DEPENDS = "python3-pip-native"

```

When I build I get the following ambiguous error during do_install:

| WARNING: The directory '/home/ddbabich/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.

| ERROR: torch-1.10.0-cp36-cp36m-linux_aarch64.whl is not a supported wheel on this platform.


It seems like I'm missing something with the host vs. the target settings?  But I really don't have any ideas.  Any help is appreciated.
THanks
-David

 

 


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

4

randy.macleod@...

2

ross@...

1

steve@...

1

akuster808@...

1

Grand Total

9

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

Stephen Jolley
 

All,

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

Who

Count

ross@...

36

michael.opdenacker@...

34

david.reyna@...

22

randy.macleod@...

20

trevor.gamblin@...

16

bruce.ashfield@...

16

timothy.t.orling@...

14

JPEWhacker@...

11

sakib.sajal@...

11

richard.purdie@...

8

mhalstead@...

7

kai.kang@...

7

saul.wold@...

6

bluelightning@...

6

kiran.surendran@...

5

chee.yang.lee@...

4

hongxu.jia@...

4

jon.mason@...

3

Qi.Chen@...

3

pokylinux@...

2

pgowda.cve@...

2

mshah@...

2

alejandro@...

2

yf3yu@...

1

angolini@...

1

mark.hatle@...

1

open.source@...

1

alexandre.belloni@...

1

yi.zhao@...

1

jay.shen.teoh@...

1

limon.anibal@...

1

TicoTimo@...

1

raj.khem@...

1

john.kaldas.enpj@...

1

steve@...

1

mingli.yu@...

1

aehs29@...

1

thomas.perrot@...

1

matthewzmd@...

1

vinay.m.engg@...

1

Martin.Jansa@...

1

mostthingsweb@...

1

kexin.hao@...

1

elberger@...

1

shachar@...

1

nicolas.dechesne@...

1

yoctoproject@...

1

Grand Total

265

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

 


Re: Honister version: ERROR: QA Issue: Files/directories were installed but not shipped

JH
 

Thanks Michael, greatly appreciate it.

On 11/23/21, Michael Opdenacker <michael.opdenacker@...> wrote:
Hi Jupiter,

On 11/22/21 10:51 AM, JH wrote:
Hi,

I was able to build my package in Zeus, I am now upgrading from Zeus
to Honister, the same package I could build in Zeus now failed in
Honister at do_package where I installed my libraries and symbolic
libraries links to my own RW locations:

ERROR: QA Issue: Files/directories were installed but not shipped

I purposely separate my application libraries and symbolic libraries
links from traditional system RO library location to my application RW
locations, I know how to handle it, it works perfectly built in Zeus,
I don't need the Yocto QA to police it, I tried to add an empty
do_package_qa() in my receipt, it does not work either. Are there any
ways to disable package QA?

Appreciate your advice either how to fix it or disable package QA.

These checks can be disabled. See
https://docs.yoctoproject.org/ref-manual/classes.html?highlight=insane#insane-bbclass
Cheers
Michael.


Re: wic crash when building image with multiple partitions

Marek Belisko
 

Actually I found a fix after some debugging. I'm not wic expert but
below patch fix issue for wks content above:

diff --git a/scripts/lib/wic/plugins/imager/direct.py
b/scripts/lib/wic/plugins/imager/direct.py
index 7e1c1c0..d37ecee 100644
--- a/scripts/lib/wic/plugins/imager/direct.py
+++ b/scripts/lib/wic/plugins/imager/direct.py
@@ -115,7 +115,7 @@ class DirectPlugin(ImagerPlugin):
updated = False
for part in self.parts:
if not part.realnum or not part.mountpoint \
- or part.mountpoint == "/":
+ or part.mountpoint == "/" or part.mountpoint == "swap":
continue
if part.use_uuid:

Does it make any sense or is it just hack?

On Tue, Nov 16, 2021 at 7:18 AM Belisko Marek <marek.belisko@...> wrote:

Hello,

I'm on dunfell release and building mender image with following wks file:
| + echo '### Contents of wks file ###'
| ### Contents of wks file ###
| + cat /home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/mender-sdimg.wks
| part --source rawcopy
--sourceparams="file=/home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/uboot.env"
--ondisk "mmcblk0" --align 8192 --no-table
| part --source rootfs --rootfs-dir
/home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/bootfs.image_sdimg
--ondisk "mmcblk0" --fstype=vfat --label boot --align 8192
--fixed-size 16 --active
| part --source rawcopy
--sourceparams="file=/home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-raspberrypi4.ext4"
--ondisk "mmcblk0" --align 8192 --fixed-size 172032k
| part --source rawcopy
--sourceparams="file=/home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-raspberrypi4.ext4"
--ondisk "mmcblk0" --align 8192 --fixed-size 172032k
| part swap --ondisk "mmcblk0" --fstype=swap --label swap --align 8192
--size 512
| part --source rawcopy
--sourceparams="file=/home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-raspberrypi4.dataimg"
--ondisk "mmcblk0" --align 8192 --fixed-size 128
|
| bootloader --ptable msdos
| + echo '### End of contents of wks file ###'
| ### End of contents of wks file ###

Without a swap partition image is built fine without any issue. When
swap partition is added to wks file I'm getting following error:

| INFO: Creating image(s)...
|
| Traceback (most recent call last):
| File "/home/marek/projects/kas-test/poky/scripts/wic", line 542, in <module>
| sys.exit(main(sys.argv[1:]))
| File "/home/marek/projects/kas-test/poky/scripts/wic", line 537, in main
| return hlp.invoke_subcommand(args, parser, hlp.wic_help_usage,
subcommands)
| File "/home/marek/projects/kas-test/poky/scripts/lib/wic/help.py",
line 83, in invoke_subcommand
| subcmd[0](args, usage)
| File "/home/marek/projects/kas-test/poky/scripts/wic", line 219,
in wic_create_subcommand
| engine.wic_create(wks_file, rootfs_dir, bootimg_dir, kernel_dir,
| File "/home/marek/projects/kas-test/poky/scripts/lib/wic/engine.py",
line 190, in wic_create
| plugin.do_create()
| File "/home/marek/projects/kas-test/poky/scripts/lib/wic/plugins/imager/direct.py",
line 96, in do_create
| self.create()
| File "/home/marek/projects/kas-test/poky/scripts/lib/wic/plugins/imager/direct.py",
line 180, in create
| self._image.prepare(self)
| File "/home/marek/projects/kas-test/poky/scripts/lib/wic/plugins/imager/direct.py",
line 354, in prepare
| part.prepare(imager, imager.workdir, imager.oe_builddir,
| File "/home/marek/projects/kas-test/poky/scripts/lib/wic/partition.py",
line 182, in prepare
| plugin.do_prepare_partition(self, srcparams_dict, creator,
| File "/home/marek/projects/kas-test/poky/scripts/lib/wic/plugins/source/rootfs.py",
line 112, in do_prepare_partition
| copyhardlinktree(orig_dir, new_rootfs)
| File "/home/marek/projects/kas-test/poky/meta/lib/oe/path.py",
line 121, in copyhardlinktree
| subprocess.check_output(cmd, shell=True, stderr=subprocess.STDOUT)
| File "/home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/recipe-sysroot-native/usr/lib/python3.8/subprocess.py",
line 411, in check_output
| return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
| File "/home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/recipe-sysroot-native/usr/lib/python3.8/subprocess.py",
line 512, in run
| raise CalledProcessError(retcode, process.args,
| subprocess.CalledProcessError: Command 'cd
/home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/bootfs.image_sdimg;
find . -type d -print | tar --xattrs --xattrs-include='*' -cf - -S -C
/home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/bootfs.image_sdimg
-p --no-recursion --files-from - | tar --xattrs --xattrs-include='*'
-xhf - -C /home/marek/projects/kas-test/build/tmp/work/raspberrypi4-poky-linux-gnueabi/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-raspberrypi4-20211115212420-sdimg/tmp.wic.1oe9hwjw/rootfs2'
returned non-zero exit status 2.

I tried to debug it but didn't find anything obvious. I'm sure this
was working fine in previous releases. Any ideas?

Thanks and 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
marek


Re: Honister version: ERROR: QA Issue: Files/directories were installed but not shipped

Michael Opdenacker
 

Hi Jupiter,

On 11/22/21 10:51 AM, JH wrote:
Hi,

I was able to build my package in Zeus, I am now upgrading from Zeus
to Honister, the same package I could build in Zeus now failed in
Honister at do_package where I installed my libraries and symbolic
libraries links to my own RW locations:

ERROR: QA Issue: Files/directories were installed but not shipped

I purposely separate my application libraries and symbolic libraries
links from traditional system RO library location to my application RW
locations, I know how to handle it, it works perfectly built in Zeus,
I don't need the Yocto QA to police it, I tried to add an empty
do_package_qa() in my receipt, it does not work either. Are there any
ways to disable package QA?

Appreciate your advice either how to fix it or disable package QA.

These checks can be disabled. See
https://docs.yoctoproject.org/ref-manual/classes.html?highlight=insane#insane-bbclass
Cheers
Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


Honister version: ERROR: QA Issue: Files/directories were installed but not shipped

JH
 

Hi,

I was able to build my package in Zeus, I am now upgrading from Zeus
to Honister, the same package I could build in Zeus now failed in
Honister at do_package where I installed my libraries and symbolic
libraries links to my own RW locations:

ERROR: QA Issue: Files/directories were installed but not shipped

I purposely separate my application libraries and symbolic libraries
links from traditional system RO library location to my application RW
locations, I know how to handle it, it works perfectly built in Zeus,
I don't need the Yocto QA to police it, I tried to add an empty
do_package_qa() in my receipt, it does not work either. Are there any
ways to disable package QA?

Appreciate your advice either how to fix it or disable package QA.

Thank you.

Kind regards,

- JH

2441 - 2460 of 57800