1. Yocto
  2. Messages

Expanded

Topics Messages
   Date   
Re: [PATCH] u-boot: Add /boot in SYSROOT_DIRS

Alexandre Belloni
 

Hello,

This was not sent to the correct mailing list, you should send to openembedded-core@...

Please also set your git From:, else the mailing list is mangling your
address. this should work:

git config sendemail.from=sebastien.fabre@...

I've taken and fixed up the patch for now.

On 23/11/2022 12:40:53+0000, Sébastien Fabre via lists.yoctoproject.org wrote:
To be able to use /boot files, like UBOOT_ENV_BINARY, in other
recipes, like kernel-fitimage.bbclass.

Signed-off-by: Fabre Sébastien <sebastien.fabre@...>
---
meta/recipes-bsp/u-boot/u-boot.inc | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u-boot/u-boot.inc
index 15e949b8b4..4636dd733b 100644
--- a/meta/recipes-bsp/u-boot/u-boot.inc
+++ b/meta/recipes-bsp/u-boot/u-boot.inc
@@ -206,6 +206,7 @@ FILES:${PN}-env = " \
FILES:${PN}-extlinux = "${UBOOT_EXTLINUX_INSTALL_DIR}/${UBOOT_EXTLINUX_CONF_NAME}"
RDEPENDS:${PN} += "${@bb.utils.contains('UBOOT_EXTLINUX', '1', '${PN}-extlinux', '', d)}"

+SYSROOT_DIRS += "/boot"
FILES:${PN} = "/boot ${datadir}"
RDEPENDS:${PN} += "${PN}-env"

--
2.30.2


--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Re: how to specify the package version via RDEPENDS in package group #bitbake

Quentin Schulz
 

Hi Martin,

On 11/23/22 06:25, Martin wrote:
thanks for reply, i original method was specified the package version in local.conf by PREFEREED_VERSION.
i wondering if configure package version in package group via RDEPENDS makes it possible? but it seems impossible.
what situations allow REDPENDS to specify a version? thanks.
As far as I remember, RDEPENDS is handled by the package manager when installing the package. So I imagine this is a way to make sure that a filesystem is not built with two packages that are incompatible at runtime by failing when creating the filesystem. The choice of which version to build is a responsibility of Bitbake which happens way before RDEPENDS.

Also, chant #1 of Yocto applies:
recipe data is local, config data is global.
So you cannot impact one recipe from another, this implies you cannot pick a version of one recipe from another, you can only say whether you're compatible with it.

Cheers,
Quentin
[PATCH] u-boot: Add /boot in SYSROOT_DIRS

Sébastien Fabre
 

To be able to use /boot files, like UBOOT_ENV_BINARY, in other
recipes, like kernel-fitimage.bbclass.

Signed-off-by: Fabre Sébastien <sebastien.fabre@...>
---
meta/recipes-bsp/u-boot/u-boot.inc | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u-boot/u-boot.inc
index 15e949b8b4..4636dd733b 100644
--- a/meta/recipes-bsp/u-boot/u-boot.inc
+++ b/meta/recipes-bsp/u-boot/u-boot.inc
@@ -206,6 +206,7 @@ FILES:${PN}-env = " \
FILES:${PN}-extlinux = "${UBOOT_EXTLINUX_INSTALL_DIR}/${UBOOT_EXTLINUX_CONF_NAME}"
RDEPENDS:${PN} += "${@bb.utils.contains('UBOOT_EXTLINUX', '1', '${PN}-extlinux', '', d)}"

+SYSROOT_DIRS += "/boot"
FILES:${PN} = "/boot ${datadir}"
RDEPENDS:${PN} += "${PN}-env"

--
2.30.2
Re: pseudo issue in kirkstone

apoplawski@...
 

On Wed, Nov 23, 2022 at 10:25 AM, Marek Belisko wrote:
Hi,

On Wed, Nov 23, 2022 at 9:41 AM apoplawski via lists.yoctoproject.org
<apoplawski=kan-therm.com@...> wrote:
Hi,

I have a similar problem. First, you need to disable pseudo before executing.
On begin of the line containing sudo cryptsetup add environment variable
definition: PSEUDO_DISABLED=1. This, however, does not solve the problem
of executing sudo. I've noticed from the recipe point of view, all files you don't own
are nobody:nogroup. This happens whether the task is in fakeroot or not.
OK so adding PSEUDO_DISABLE=1 doesn't solve an issue. It's the same like before.
In my case, adding PSEUDO_DISABLE=1 makes /etc/sudoers.conf problem go away.
However, I am left with an error about running sudo:

| sudo must be owned by uid 0 and have the setuid bit set

I think main problem is ownership of files in task perspective. I don't know why files are nobody:nogroup.
I spent some time on that but not found solution.
Any idea what was changed and why it was working in dunfell and not in
kirkstone?
--
Adam Popławski
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
Re: how to specify the package version via RDEPENDS in package group #bitbake

Martin
 

thanks for reply, i original method was specified the package version in local.conf by PREFEREED_VERSION.

i wondering if configure package version in package group via RDEPENDS makes it possible? but it seems impossible.

what situations allow REDPENDS to specify a version? thanks.
Re: pseudo issue in kirkstone

Marek Belisko
 

Hi,

On Wed, Nov 23, 2022 at 9:41 AM apoplawski via lists.yoctoproject.org
<apoplawski=kan-therm.com@...> wrote:

Hi,

I have a similar problem. First, you need to disable pseudo before executing.
On begin of the line containing sudo cryptsetup add environment variable
definition: PSEUDO_DISABLED=1. This, however, does not solve the problem
of executing sudo. I've noticed from the recipe point of view, all files you don't own
are nobody:nogroup. This happens whether the task is in fakeroot or not.
OK so adding PSEUDO_DISABLE=1 doesn't solve an issue. It's the same like before.
Any idea what was changed and why it was working in dunfell and not in
kirkstone?

--
Adam Popławski

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
Re: pseudo issue in kirkstone

apoplawski@...
 

Hi,

I have a similar problem. First, you need to disable pseudo before executing.
On begin of the line containing sudo cryptsetup add environment variable
definition: PSEUDO_DISABLED=1. This, however, does not solve the problem
of executing sudo. I've noticed from the recipe point of view, all files you don't own
are nobody:nogroup. This happens whether the task is in fakeroot or not.

--
Adam Popławski
Fixing package dependencies across recipe versions?

Heinz Wrobel
 

Hi,

 

In my layer I have two older versions of glibc in addition to the 2.35 provided by kirkstone, and a the global conf for the build directory sets GLIBCVERSION to select which one to use.

 

The problem is that they don’t all provide exactly the same thing and that older version appear to influence newer versions, causing warnings.

2.27 and 2.31 build libsegfault, but 2.35 doesn’t anymore. If I prefer 2.35, then I get warnings like:

 

WARNING: preferred version 2.35 of glibc not available (for item libsegfault)

WARNING: versions of glibc available: 2.27 2.31+gitAUTOINC+1094741224

WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-libsegfault)

WARNING: versions of nativesdk-glibc available: 2.27 2.31+gitAUTOINC+1094741224

 

It seems that the unused/older recipe versions are still considered for dependencies somehow, just because they exist in the layer.

I understand that the old glibc versions provide libsegfault and that it can’t be found in the preferred version, but I really don’t care about the other versions as I have not selected them.

I could completely remove the packages from the old versions, but that seems like a brute force hack affecting what the recipes could provide when I select them.

 

Is there a clean way to modify/bbappend the recipes to best fix, or at least suppress such warnings when the recipe versions causing them are not selected?

Is there a way to do version based dependency declarations to be recipe version rather than recipe name specific?

 

Thanks,

 

Heinz
Multilib for core-image-minimal #kirkstone

Spore, David
 

I am new to Yocto, and am trying to build core-image-minimal with multilib using the latest Kirkstone release.  The image builds ok without the multilib config entries, but adding the entries (local.conf attached) generates this error:

ERROR: core-image-minimal-1.0-r0 do_prepare_recipe_sysroot: Manifest /home/project/var-fsl-yocto/build_xwayland/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-lib32-qemuwrapper-cross.populate_sysroot not found in imx8mp_var_dart armv7at2-neon-mx8mp armv7a-neon-mx8mp armv7at2-vfp-mx8mp armv7a-vfp-mx8mp armv7a-mx8mp armv6t-vfp-mx8mp armv6-vfp-mx8mp armv6t-mx8mp armv6-mx8mp armv5te-vfp-mx8mp armv5e-vfp-mx8mp armv5te-mx8mp armv5e-mx8mp armv5t-vfp-mx8mp armv5-vfp-mx8mp armv5t-mx8mp armv5-mx8mp armv4t-mx8mp armv4-mx8mp arm-mx8mp armv8a-mx8mp armv8a-crc-crypto armv8a-crypto armv8a-crc armv8a aarch64 allarch x86_64_x86_64-nativesdk (variant 'lib32')?
ERROR: Logfile of failure stored in: /home/project/var-fsl-yocto/build_xwayland/tmp/work/imx8mp_var_dart-fslc-linux/core-image-minimal/1.0-r0/temp/log.do_prepare_recipe_sysroot.2763591
ERROR: Task (/home/project/var-fsl-yocto/sources/poky/meta/recipes-core/images/core-image-minimal.bb:do_prepare_recipe_sysroot) failed with exit code '1'

The bitbake output:
Loading cache: 100% |                                           | ETA:  --:--:--
Loaded 0 entries from dependency cache.
Parsing recipes: 100% |##########################################| Time: 0:04:58
Parsing of 3134 .bb files complete (0 cached, 3134 parsed). 7763 targets, 589 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
 
Build Configuration:
BB_VERSION           = "2.0.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-fslc-linux"
MACHINE              = "imx8mp-var-dart"
DISTRO               = "fslc-xwayland"
DISTRO_VERSION       = "4.0"
TUNE_FEATURES        = "aarch64 armv8a crc crypto"
TARGET_FPU           = ""
meta                 
meta-poky            = "HEAD:24a3f7b3648185e33133f5d96b184a6cb6524f3d"
meta-oe              
meta-multimedia      
meta-python          
meta-filesystems     
meta-gnome           
meta-networking      
meta-webserver       = "HEAD:744a4b6eda88b9a9ca1cf0df6e18be384d9054e3"
meta-freescale       = "HEAD:3747641f1e71d8e4edd5b587b49d09dc2d243942"
meta-freescale-3rdparty = "HEAD:6d8213fc5ec192c33f963b8095d1f01af1574eea"
meta-freescale-distro = "HEAD:d5bbb487b2816dfc74984a78b67f7361ce404253"
meta-freescale-ml    = "HEAD:08dcb7c67072907348cd235d9e110d4ba91e8235"
meta-qt5             = "HEAD:44d44933200287f7d17cf6981af4b4a0961c308d"
meta-swupdate        = "HEAD:fabbcc623d41794fbfa97c38b9da941ed2cdcdcc"
meta-virtualization  = "HEAD:5be54854139acb4796000478394afd66de0792c1"
meta-variscite-bsp   = "HEAD:a4dbd2cfe48a80d4362c9de0523500de05f15898"
meta-variscite-sdk   = "HEAD:5664513a0cf0f43afb60f92e63e60a86f3e53bd0"
meta-variscite-hab   = "HEAD:4acacfdbc4b89ace606b5d640e768b7561435324"
 
Initialising tasks: 100% |#######################################| Time: 0:00:13
Sstate summary: Wanted 469 Local 236 Mirrors 0 Missed 233 Current 1581 (50% match, 88% complete)
Removing 110 stale sstate objects for arch armv8a: 100% |########| Time: 0:00:00
Removing 12 stale sstate objects for arch imx8mp_var_dart: 100% || Time: 0:00:00
NOTE: Executing Tasks
 

I don't know what to do about the manifest file it is complaining about.   I've done a lot of searching for answers but haven't found a clear solution.  The ultimate goal is to be able to run modules which have the format shown below on my Variscite imx8mp board.  

ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=6ef3beb0dd7bd4432efc062e181069bf1f5382d7, stripped

Thanks!

David

local.conf

local.conf

Yocto Project Status 22 November 2022 (WW47)

Stephen Jolley
 

Current Dev Position: YP 4.2 M1

Next Deadline: 5th December 2022 YP 4.2 Build

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 4.1.1 has passed QA and is likely to be released imminently.
  • We’d like to remind people of the importance of developing features on master. Once ready, these can then become available in the next LTS. We do not develop features against current LTS releases, that defeats their purpose.
  • A key bug in sstate reuse with hash equivalence where “hard” dependencies like pseudo-native and shadow-native rehash was found and is fixed in bitbake master.
  • We are thinking about more significant bitbake changes at the moment. Some ideas under consideration are:
    • Adding extra information about hashes to the bitbake cache (and the expense of slower loading cache files and slightly slower initial parsing). This would allow easier debugging of hash mismatch issues (e.g. basehash parsing mismatches or esdk hash issues).
    • Thinking about the idea of variable “filter” functions to help implementation of recipe class extensions (like native and nativesdk).
    • Extending bitbake’s recipe syntax to support structured data.
  • We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
  • We have a growing number of bugs in bugzilla, any help with them is appreciated.

 

Ways to contribute:

 

YP 4.2 Milestone Dates:

  • YP 4.2 M1 build date 2022/12/05
  • YP 4.2 M1 Release date 2022/12/16
  • YP 4.2 M2 build date 2023/01/23
  • YP 4.2 M2 Release date 2023/02/03
  • YP 4.2 M3 build date 2023/02/20
  • YP 4.2 M3 Release date 2023/03/03
  • YP 4.2 M4 build date 2023/04/03
  • YP 4.2 M4 Release date 2023/04/28

 

Upcoming dot releases:

  • YP 4.1.1 is ready for release
  • YP 3.1.21 build date 2022/11/28
  • YP 3.1.21 Release date 2022/12/09
  • YP 4.0.6 build date 2022/12/12
  • YP 4.0.6 Release date 2022/12/23
  • YP 4.1.2 build date 2023/01/09
  • YP 4.1.2 Release date 2023/01/20
  • YP 3.1.22 build date 2023/01/16
  • YP 3.1.22 Release date 2023/01/27
  • YP 4.0.7 build date 2023/01/30
  • YP 4.0.7 Release date 2023/02/10
  • YP 3.1.23 build date 2023/02/13
  • YP 3.1.23 Release date 2023/02/24
  • YP 4.0.8 build date 2023/02/27
  • YP 4.0.8 Release date 2023/03/10
  • YP 4.1.3 build date 2023/03/06
  • YP 4.1.3 Release date 2023/03/17
  • YP 3.1.24 build date 2023/03/20
  • YP 3.1.24 Release date 2023/03/31
  • YP 4.0.9 build date 2023/04/10
  • YP 4.0.9 Release date 2023/04/21
  • YP 4.1.4 build date 2023/05/01
  • YP 4.1.4 Release date 2023/05/13
  • YP 3.1.25 build date 2023/05/08
  • YP 3.1.25 Release date 2023/05/19
  • YP 4.0.10 build date 2023/05/15
  • YP 4.0.10 Release date 2023/05/26

 

Tracking Metrics:

 

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

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

 

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

 

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

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 
Re: how to specify the package version via RDEPENDS in package group #bitbake

Chen Qi
 

I think your major concern is “I have multiple version for opencv, but bibake installed the version 3.4.3 default.”.

It’s because layers have different layer priorities specified by BBFILE_PRIORITY in layer.conf, and for recipes with the same name in different layers, the one in higher priority layer will be selected regardless of the recipes’ versions.

In such case, you can set PREFERRED_VERSION to use the one you want.

Regards,

Qi

 

From: yocto@... <yocto@...> On Behalf Of Martin via lists.yoctoproject.org
Sent: Tuesday, November 22, 2022 3:59 PM
To: yocto@...
Subject: [yocto] how to specify the package version via RDEPENDS in package group #bitbake

 

I have multiple version for opencv, but bibake installed the version 3.4.3 default.

=== Matching recipes: ===
opencv:
  meta-rcar-gen3-adas  3.4.3+gitAUTOINC+b38c50b3d0_1f6d6f0626_bdb7bb85f3_34e4206aef_fccf7cd6a4
  meta-oe              4.1.0
  meta-rcar-gen3-adas  2.4.11+gitAUTOINC+707d10f115
  meta-rcar-gen3-adas  3.2+gitAUTOINC+70bbf17b13

 

the yocto offical documents mentioned the variable RDEPENDS supports operator for specify versions.

then i specified the version to 4.1.0 for opencv in package group.

SUMMARY = "Requirement packages"
PR = "r1"
 
inherit packagegroup
 
RDEPENDS:${PN} = " \
        opencv (>= 4.1.0)\
        libopencv-core-dev \
        libopencv-highgui-dev \
        libopencv-imgproc-dev \
        libopencv-objdetect-dev \
        libopencv-ml-dev \
        opencv-apps \
        opencv-dev \
        protobuf \
        gdb \
        libsdl2 \
        libgpiod \
        libgpiod-tools \
"

 

Appeared the failure message, why??

The version list has v4.1.0, but the error message show nothing provides v4.1.0 for opencv.

nothing provides opencv >= 4.1.0 needed by packagegroup-user-requirements-1.0-r1.noarch

ERROR: core-image-weston-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=info -y -c /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs/etc/yum.repos.d --installroot=/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs --setopt=logdir=/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/temp --repofrompath=oe-repo,/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/oe-rootfs-repo --nogpgcheck install bash coreutils dnf git htop i2c-tools inx-cluster kernel-module-qos matchbox-terminal omx-user-module optee-client packagegroup-base-extended packagegroup-bsp packagegroup-core-boot packagegroup-core-eclipse-debug packagegroup-core-sdk packagegroup-core-ssh-openssh packagegroup-core-standalone-sdk-target packagegroup-core-tools-debug packagegroup-core-tools-profile packagegroup-graphics-renesas-proprietary packagegroup-graphics-renesas-wayland packagegroup-gstreamer1.0-plugins packagegroup-user-requirements packagegroup-mm packagegroup-multimedia-kernel-modules packagegroup-multimedia-libs packagegroup-radio packagegroup-wayland-community psplash qosif-tp-user-module qosif-user-module rpm run-postinsts u-boot v4l-utils vim vspmif-tp-user-module weston weston-examples weston-init weston-xwayland locale-base-en-us locale-base-en-gb' returned 1:
DNF version: 4.2.2
cachedir: /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs/var/cache/dnf
Added oe-repo repo from /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/oe-rootfs-repo
repo: using cache for: oe-repo
not found other for:
not found modules for:
not found deltainfo for:
not found updateinfo for:
oe-repo: using metadata from Tue 22 Nov 2022 03:02:16 AM UTC.
Last metadata expiration check: 0:00:01 ago on Tue 22 Nov 2022 03:02:16 AM UTC.
No module defaults found
--> Starting dependency resolution
--> Finished dependency resolution
Error:
 Problem: conflicting requests
  - nothing provides opencv >= 4.1.0 needed by packagegroup-user-requirements-1.0-r1.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
 
ERROR: Logfile of failure stored in: /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/temp/log.do_rootfs.855803
ERROR: Task (/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/../poky/meta/recipes-graphics/images/core-image-weston.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 9003 tasks of which 9002 didn't need to be rerun and 1 failed.
 
Summary: 1 task failed:
  /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/../poky/meta/recipes-graphics/images/core-image-weston.bb:do_rootfs
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

 

Successfully built the image after I try to set the version conditions as > 2.0, but the version still is v3.4.3 for opencv.

SUMMARY = "Requirement packages"
PR = "r1"
 
inherit packagegroup
 
RDEPENDS:${PN} = " \
        opencv (>= 2.0)\
        libopencv-core-dev \
        libopencv-highgui-dev \
        libopencv-imgproc-dev \
        libopencv-objdetect-dev \
        libopencv-ml-dev \
        opencv-apps \
        opencv-dev \
        protobuf \
        gdb \
        libsdl2 \
        libgpiod \
        libgpiod-tools \
"

 

How to specify the package version via RDEPENDS in package group? thanks

 
Re: how to specify the package version via RDEPENDS in package group #bitbake

Alexander Kanavin
 

You need to look up PREFERRED_VERSION rather.

Alex

On Tue, 22 Nov 2022 at 09:51, Martin <linmartin.tw@...> wrote:

I have multiple version for opencv, but bibake installed the version 3.4.3 default.

=== Matching recipes: ===
opencv:
meta-rcar-gen3-adas 3.4.3+gitAUTOINC+b38c50b3d0_1f6d6f0626_bdb7bb85f3_34e4206aef_fccf7cd6a4
meta-oe 4.1.0
meta-rcar-gen3-adas 2.4.11+gitAUTOINC+707d10f115
meta-rcar-gen3-adas 3.2+gitAUTOINC+70bbf17b13


the yocto offical documents mentioned the variable RDEPENDS supports operator for specify versions.

then i specified the version to 4.1.0 for opencv in package group.

SUMMARY = "Requirement packages"
PR = "r1"

inherit packagegroup

RDEPENDS:${PN} = " \
opencv (>= 4.1.0)\
libopencv-core-dev \
libopencv-highgui-dev \
libopencv-imgproc-dev \
libopencv-objdetect-dev \
libopencv-ml-dev \
opencv-apps \
opencv-dev \
protobuf \
gdb \
libsdl2 \
libgpiod \
libgpiod-tools \
"


Appeared the failure message, why??

The version list has v4.1.0, but the error message show nothing provides v4.1.0 for opencv.

nothing provides opencv >= 4.1.0 needed by packagegroup-user-requirements-1.0-r1.noarch

ERROR: core-image-weston-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=info -y -c /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs/etc/yum.repos.d --installroot=/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs --setopt=logdir=/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/temp --repofrompath=oe-repo,/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/oe-rootfs-repo --nogpgcheck install bash coreutils dnf git htop i2c-tools inx-cluster kernel-module-qos matchbox-terminal omx-user-module optee-client packagegroup-base-extended packagegroup-bsp packagegroup-core-boot packagegroup-core-eclipse-debug packagegroup-core-sdk packagegroup-core-ssh-openssh packagegroup-core-standalone-sdk-target packagegroup-core-tools-debug packagegroup-core-tools-profile packagegroup-graphics-renesas-proprietary packagegroup-graphics-renesas-wayland packagegroup-gstreamer1.0-plugins packagegroup-user-requirements packagegroup-mm packagegroup-multimedia-kernel-modules packagegroup-multimedia-libs packagegroup-radio packagegroup-wayland-community psplash qosif-tp-user-module qosif-user-module rpm run-postinsts u-boot v4l-utils vim vspmif-tp-user-module weston weston-examples weston-init weston-xwayland locale-base-en-us locale-base-en-gb' returned 1:
DNF version: 4.2.2
cachedir: /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs/var/cache/dnf
Added oe-repo repo from /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/oe-rootfs-repo
repo: using cache for: oe-repo
not found other for:
not found modules for:
not found deltainfo for:
not found updateinfo for:
oe-repo: using metadata from Tue 22 Nov 2022 03:02:16 AM UTC.
Last metadata expiration check: 0:00:01 ago on Tue 22 Nov 2022 03:02:16 AM UTC.
No module defaults found
--> Starting dependency resolution
--> Finished dependency resolution
Error:
Problem: conflicting requests
- nothing provides opencv >= 4.1.0 needed by packagegroup-user-requirements-1.0-r1.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

ERROR: Logfile of failure stored in: /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/temp/log.do_rootfs.855803
ERROR: Task (/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/../poky/meta/recipes-graphics/images/core-image-weston.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 9003 tasks of which 9002 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/../poky/meta/recipes-graphics/images/core-image-weston.bb:do_rootfs
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Successfully built the image after I try to set the version conditions as > 2.0, but the version still is v3.4.3 for opencv.

SUMMARY = "Requirement packages"
PR = "r1"

inherit packagegroup

RDEPENDS:${PN} = " \
opencv (>= 2.0)\
libopencv-core-dev \
libopencv-highgui-dev \
libopencv-imgproc-dev \
libopencv-objdetect-dev \
libopencv-ml-dev \
opencv-apps \
opencv-dev \
protobuf \
gdb \
libsdl2 \
libgpiod \
libgpiod-tools \
"


How to specify the package version via RDEPENDS in package group? thanks
how to specify the package version via RDEPENDS in package group #bitbake

Martin
 

I have multiple version for opencv, but bibake installed the version 3.4.3 default.

=== Matching recipes: ===
opencv:
  meta-rcar-gen3-adas  3.4.3+gitAUTOINC+b38c50b3d0_1f6d6f0626_bdb7bb85f3_34e4206aef_fccf7cd6a4
  meta-oe              4.1.0
  meta-rcar-gen3-adas  2.4.11+gitAUTOINC+707d10f115
  meta-rcar-gen3-adas  3.2+gitAUTOINC+70bbf17b13


the yocto offical documents mentioned the variable RDEPENDS supports operator for specify versions.

then i specified the version to 4.1.0 for opencv in package group.

SUMMARY = "Requirement packages"
PR = "r1"

inherit packagegroup

RDEPENDS:${PN} = " \
        opencv (>= 4.1.0)\
        libopencv-core-dev \
        libopencv-highgui-dev \
        libopencv-imgproc-dev \
        libopencv-objdetect-dev \
        libopencv-ml-dev \
        opencv-apps \
        opencv-dev \
        protobuf \
        gdb \
        libsdl2 \
        libgpiod \
        libgpiod-tools \
"


Appeared the failure message, why??

The version list has v4.1.0, but the error message show nothing provides v4.1.0 for opencv.

nothing provides opencv >= 4.1.0 needed by packagegroup-user-requirements-1.0-r1.noarch

ERROR: core-image-weston-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=info -y -c /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs/etc/yum.repos.d --installroot=/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs --setopt=logdir=/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/temp --repofrompath=oe-repo,/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/oe-rootfs-repo --nogpgcheck install bash coreutils dnf git htop i2c-tools inx-cluster kernel-module-qos matchbox-terminal omx-user-module optee-client packagegroup-base-extended packagegroup-bsp packagegroup-core-boot packagegroup-core-eclipse-debug packagegroup-core-sdk packagegroup-core-ssh-openssh packagegroup-core-standalone-sdk-target packagegroup-core-tools-debug packagegroup-core-tools-profile packagegroup-graphics-renesas-proprietary packagegroup-graphics-renesas-wayland packagegroup-gstreamer1.0-plugins packagegroup-user-requirements packagegroup-mm packagegroup-multimedia-kernel-modules packagegroup-multimedia-libs packagegroup-radio packagegroup-wayland-community psplash qosif-tp-user-module qosif-user-module rpm run-postinsts u-boot v4l-utils vim vspmif-tp-user-module weston weston-examples weston-init weston-xwayland locale-base-en-us locale-base-en-gb' returned 1:
DNF version: 4.2.2
cachedir: /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/rootfs/var/cache/dnf
Added oe-repo repo from /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/oe-rootfs-repo
repo: using cache for: oe-repo
not found other for:
not found modules for:
not found deltainfo for:
not found updateinfo for:
oe-repo: using metadata from Tue 22 Nov 2022 03:02:16 AM UTC.
Last metadata expiration check: 0:00:01 ago on Tue 22 Nov 2022 03:02:16 AM UTC.
No module defaults found
--> Starting dependency resolution
--> Finished dependency resolution
Error:
 Problem: conflicting requests
  - nothing provides opencv >= 4.1.0 needed by packagegroup-user-requirements-1.0-r1.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

ERROR: Logfile of failure stored in: /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/tmp/work/h3ulcb-poky-linux/core-image-weston/1.0-r0/temp/log.do_rootfs.855803
ERROR: Task (/home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/../poky/meta/recipes-graphics/images/core-image-weston.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 9003 tasks of which 9002 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/dell/workspace/yocto-v5.1.0-h3ulcb-kf/h3ulcb/build/../poky/meta/recipes-graphics/images/core-image-weston.bb:do_rootfs
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Successfully built the image after I try to set the version conditions as > 2.0, but the version still is v3.4.3 for opencv.

SUMMARY = "Requirement packages"
PR = "r1"

inherit packagegroup

RDEPENDS:${PN} = " \
        opencv (>= 2.0)\
        libopencv-core-dev \
        libopencv-highgui-dev \
        libopencv-imgproc-dev \
        libopencv-objdetect-dev \
        libopencv-ml-dev \
        opencv-apps \
        opencv-dev \
        protobuf \
        gdb \
        libsdl2 \
        libgpiod \
        libgpiod-tools \
"


How to specify the package version via RDEPENDS in package group? thanks
pseudo issue in kirkstone

Marek Belisko
 

Hi,

I have a class where I create a custom image with cryptsetup and for
that purpose I'm using sudo. AFAIK using sudo in image creation should
be OK as it runs in pseudo. sudo calls works fine in dunfell releases
but while on kirkstone I'm getting:

| sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
| sudo: /usr/lib/sudo/sudoers.so must be owned by uid 0
| sudo: fatal error, unable to load plugins

Is there any workaround available or it's a pseudo issue?

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
M+ & H bugs with Milestone Movements WW47

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

14896

Current autobuilder code incompatible with buildbot 3.5.0

richard.purdie@...

richard.purdie@...

4.2

4.2 M3

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 
Enhancements/Bugs closed WW47!

Stephen Jolley
 

All,

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

Who

Count

randy.macleod@...

2

ross.burton@...

2

sundeep.kokkonda@...

1

wei.qingjun@...

1

pavel@...

1

Grand Total

7

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

Stephen Jolley
 

All,

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

Who

Count

michael.opdenacker@...

35

ross.burton@...

32

randy.macleod@...

26

bruce.ashfield@...

24

david.reyna@...

23

richard.purdie@...

22

sakib.sajal@...

11

JPEWhacker@...

10

saul.wold@...

9

Zheng.Qiu@...

4

sundeep.kokkonda@...

4

pavel@...

4

tim.orling@...

4

akuster808@...

2

sgw@...

2

jon.mason@...

2

Naveen.Gowda@...

2

aehs29@...

2

hongxu.jia@...

2

rybczynska@...

1

ptsneves@...

1

tvgamblin@...

1

sundeep.kokkonda@...

1

thomas.perrot@...

1

Qi.Chen@...

1

hummerbliss@...

1

alexandre.belloni@...

1

Anton.Antonov@...

1

Martin.Jansa@...

1

martin.beeger@...

1

mhalstead@...

1

Grand Total

232

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 413 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.2”, “4.3”, "4.99" and "Future", the more pressing/urgent issues being in "4.2" and then “4.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: build 2 sdk toolchain

Johann Obermayr
 

Hello,

build mingw sdk get follow error:

configure: error: linux/capability.h is required in order to build libcap-ng

$ SDKMACHINE=x86_64-mingw” bitbake my-image -c populate_sdk

We use kernel 5.15
Any idea ?

Best regards
Johann

-----Ursprüngliche Nachricht-----
Von: Alexander Kanavin <alex.kanavin@...>
Gesendet: Dienstag, 15. November 2022 13:06
An: Johann Obermayr <johann.obermayr@...>
Cc: yocto@...
Betreff: Re: [yocto] build 2 sdk toolchain

CAUTION: External E-Mail !

This is the correct way, yes. You can put SDKMACHINE into local.conf (default
is 'linux sdk'), or you can specify it on command line (in which case it will
override the local.conf setting).

Alex

On Tue, 15 Nov 2022 at 13:02, Johann Obermayr via lists.yoctoproject.org
<johann.obermayr=sigmatek.at@...> wrote:

Hello,



we use kirkstone.

We will build

Image
Toolchain for linux
Toolchain for windows



Now we can build a image + linux sdk toolchain.

That work correct.



$ bitbake my-image

$ bitbake my-image -c populate_sdk



Now we will build a Toolchain for windows

We have add meta-mingw



$ SDKMACHINE=x86_64-mingw” bitbake my-image -c populate_sdk



Is this the correct way ?

Or what is a better solution for this.



Best regards

Johann
Re: [meta-rockchip][PATCH] rockchip-defaults: remove xf86-input-keyboard

Trevor Woerner
 

On Sat 2022-11-19 @ 08:45:18 AM, Trevor Woerner via lists.yoctoproject.org wrote:
xf86-input-keyboard was removed from openembedded-core at its commit:
f1d7c33b64 (xf86-input-keyboard: remove the recipe, 2022-07-20). Therefore
remove it from the XSERVER definition.

Signed-off-by: Trevor Woerner <twoerner@...>
---
conf/machine/include/rockchip-defaults.inc | 1 -
1 file changed, 1 deletion(-)
Applied to meta-rockchip master (with Quentin's Reviewed-by).
Thanks!
1601 - 1620 of 60175