Date   

Re: #yocto llvm support #yocto

Monsees, Steven C (US)
 

 

I noticed similar behavior…

 

I am running zeus 3.0.4, “devtool sdk-install llvm” will get llvm 8.0.1…

 

When I build meta-clang, and I set TOOLCHAIN?=”clang” in local.conf it appears to grab llvm-project-source-9.0.1-9.0.1…

 

From: yocto@... <yocto@...> On Behalf Of Anton Antonov
Sent: Tuesday, April 20, 2021 9:51 AM
To: yocto@...
Subject: Re: [yocto] #yocto llvm support

 

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


Hi Steven,

  I used meta-clang in my recipes and I noticed that:
1. The current release of poky uses LLVM v11.1.0 by default (poky/meta/recipes-devtools/llvm/llvm_git.bb)
2. Meta-clang requires LLVM v12.0.0 (meta-clang/conf/layer.conf defines LLVMVERSION = "12.0.0")

As a result just including meta-clang into bblayers.conf will require bitbake to build a new version of LLVM and rebuild everything which uses it

Anton


Re: #yocto llvm support #yocto

Anton Antonov
 

Hi Steven,

  I used meta-clang in my recipes and I noticed that:
1. The current release of poky uses LLVM v11.1.0 by default (poky/meta/recipes-devtools/llvm/llvm_git.bb)
2. Meta-clang requires LLVM v12.0.0 (meta-clang/conf/layer.conf defines LLVMVERSION = "12.0.0")

As a result just including meta-clang into bblayers.conf will require bitbake to build a new version of LLVM and rebuild everything which uses it

Anton


Re: #yocto #sdk SDK_EXTRA_TOOLS inclussion of python-native and devtool #yocto #sdk

Monsees, Steven C (US)
 

 

Any one seen this before… ?

 

SDK appears to be working okay without the inclusion of native python3 components, not sure how the inclusion breaks devtool…

 

From: Monsees, Steven C (US)
Sent: Wednesday, April 14, 2021 2:23 PM
To: 'yocto@...' <yocto@...>
Subject: #yocto #sdk SDK_EXTRA_TOOLS inclussion of python-native and devtool

 

 

Working with zeus 3.0.4, extended SDK…

 

Could someone explain what I overlooked, or why this issue pops up with python-native support inclusion ?

 

Thanks…

 

When I add in native-python3 support

 

#

# Additional SDK Setup variables

#

 

SDKIMAGE_FEATURES_append = " staticdev-pkgs"

 

SDK_EXTRA_TOOLS = "  \

     nativesdk-python3-pprint \

     nativesdk-python3-pickle \

     nativesdk-python3-shell \

     nativesdk-python3-modules \

     nativesdk-python3-distutils \

     nativesdk-python3-xml \

     nativesdk-python3-compile \

     nativesdk-python3-six \

     nativesdk-cmake \

     "

 

TOOLCHAIN_HOST_TASK_append = "${SDK_EXTRA_TOOLS}"

 

I see the following error with devtool:

 

13:07 smonsees@yix490016 /disk0/scratch/smonsees> unset LD_LIBRARY_PATH

13:08 smonsees@yix490016 /disk0/scratch/smonsees>. /disk0/scratch/smonsees/aioxSDK_EXT_FULL/environment-setup-aarch64-poky-linux

SDK environment now set up; additionally you may now run devtool to perform development tasks.

Run devtool --help for further details.

13:08 smonsees@yix490016 /disk0/scratch/smonsees>devtool --help

/disk0/scratch/smonsees/aioxSDK_EXT_FULL/sysroots/x86_64-pokysdk-linux/usr/bin/python3: /disk0/scratch/smonsees/aioxSDK_EXT_FULL/sysroots/x86_64-pokysdk-linux/usr/bin/python3.7.real: /opt/limws/3.0.4/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory

/disk0/scratch/smonsees/aioxSDK_EXT_FULL/sysroots/x86_64-pokysdk-linux/usr/bin/python3: line 5: /disk0/scratch/smonsees/aioxSDK_EXT_FULL/sysroots/x86_64-pokysdk-linux/usr/bin/python3.7.real: Success

 

If I remove the “native-python” components, the issue goes away:

 

SDK_EXTRA_TOOLS = "  \

    nativesdk-cmake \

    "

 

14:09 smonsees@yix490016 /disk0/scratch/smonsees> unset LD_LIBRARY_PATH

14:11 smonsees@yix490016 /disk0/scratch/smonsees>. /disk0/scratch/smonsees/aioxSDK_EXT_FULL/environment-setup-aarch64-poky-linux

SDK environment now set up; additionally you may now run devtool to perform development tasks.

Run devtool --help for further details.

14:11 smonsees@yix490016 /disk0/scratch/smonsees>devtool --help

NOTE: Starting bitbake server...

usage: devtool [--basepath BASEPATH] [--bbpath BBPATH] [-d] [-q]

               [--color COLOR] [-h]

               <subcommand> ...

 

OpenEmbedded development tool

 

options:

  --basepath BASEPATH   Base directory of SDK / build directory

  --bbpath BBPATH       Explicitly specify the BBPATH, rather than getting it

                        from the metadata

  -d, --debug           Enable debug output

  -q, --quiet           Print only errors

  --color COLOR         Colorize output (where COLOR is auto, always, never)

  -h, --help            show this help message and exit

 

subcommands:

  Beginning work on a recipe:

    add                   Add a new recipe

    modify                Modify the source for an existing recipe

    upgrade               Upgrade an existing recipe

  Getting information:

    status                Show workspace status

    search                Search available recipes

    latest-version        Report the latest version of an existing recipe

    check-upgrade-status  Report upgradability for multiple (or all) recipes

  Working on a recipe in the workspace:

    build                 Build a recipe

    rename                Rename a recipe file in the workspace

    edit-recipe           Edit a recipe file

    find-recipe           Find a recipe file

    configure-help        Get help on configure script options

    update-recipe         Apply changes from external source tree to recipe

    reset                 Remove a recipe from your workspace

    finish                Finish working on a recipe in your workspace

  Testing changes on target:

    deploy-target         Deploy recipe output files to live target machine

    undeploy-target       Undeploy recipe output files in live target machine

    package               Build packages for a recipe

    build-image           Build image including workspace recipe packages

    runqemu               Run QEMU on the specified image

  Advanced:

    build-sdk             Build a derivative SDK of this one

    extract               Extract the source for an existing recipe

    sync                  Synchronize the source tree for an existing recipe

    export                Export workspace into a tar archive

    import                Import exported tar archive into workspace

    menuconfig            Alter build-time configuration for a recipe

  SDK maintenance:

    sdk-update            Update SDK components

    sdk-install           Install additional SDK components

Use devtool <subcommand> --help to get help on a specific command

14:11 smonsees@yix490016 /disk0/scratch/smonsees>

 

 


Re: [PATCH] linux-yocto/5.4: fix arm defconfig warnings

Bruce Ashfield
 

Obviously this is to the wrong list!

It escaped before I could stop it :D

I've already resent to oe-core.

Bruce

On Tue, Apr 20, 2021 at 8:31 AM Bruce Ashfield via
lists.yoctoproject.org
<bruce.ashfield=gmail.com@lists.yoctoproject.org> wrote:


From: Bruce Ashfield <bruce.ashfield@gmail.com>

A recent fix to the kern-tools promoted some previously unseen
issues to warnings. This commit fixes them by tagging some BT
options as non-hardware so they won't generate warnings if they
don't appear in the final .config. These are sub BT options and
shouldn't warn when/if their controlling option is disabled by
a fragment.

d7fd0213b75 base: exclude some BT options as non-hardware

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index e52c9ebe0e..a802a570a1 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -12,7 +12,7 @@ python () {
}

SRCREV_machine ?= "324e77d816cf6434507ab29140beb24044009efa"
-SRCREV_meta ?= "5017570a130f142365dfdcd043d84143fdd6e255"
+SRCREV_meta ?= "d7fd0213b75ce9b6206f63dbdd435ab326598642"

SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index f07375c761..1edc632de7 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -17,7 +17,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"

SRCREV_machine_qemuarm ?= "8463db325b93f0669446f68c19334cfe11ffb9c2"
SRCREV_machine ?= "5f54b437b6502d3febee553100b2cb2a9e0c5f8a"
-SRCREV_meta ?= "5017570a130f142365dfdcd043d84143fdd6e255"
+SRCREV_meta ?= "d7fd0213b75ce9b6206f63dbdd435ab326598642"

PV = "${LINUX_VERSION}+git${SRCPV}"

diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 4f056d6d82..3a9463af6a 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -23,7 +23,7 @@ SRCREV_machine_qemux86 ?= "5f54b437b6502d3febee553100b2cb2a9e0c5f8a"
SRCREV_machine_qemux86-64 ?= "5f54b437b6502d3febee553100b2cb2a9e0c5f8a"
SRCREV_machine_qemumips64 ?= "996fe040c8d8d01a9af6be42dae3844d127471bf"
SRCREV_machine ?= "5f54b437b6502d3febee553100b2cb2a9e0c5f8a"
-SRCREV_meta ?= "5017570a130f142365dfdcd043d84143fdd6e255"
+SRCREV_meta ?= "d7fd0213b75ce9b6206f63dbdd435ab326598642"

# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
--
2.19.1



--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


#yocto llvm support #yocto

Monsees, Steven C (US)
 

 

Under ../poky/meta/recipes-devtools the is “llvm”…

 

Devtool search <component>

Devtool sdk-install <component>

 

Will add this component to my EXT SDK…

 

Is this a fully functional llvm drop ?,

(i.e. is it compatible with meta-clang?, and can I use them together to build 3rd party extensions for my platform ?)

 

Is it better to add supported components this way rather than building them in directly to EXT SDK ?

 

Thanks,

Steve


Re: what to include in a "hardware bringup image"?

Yoann Congal
 

Hello,

It might be a bit heavy but I usually install a text editor and python-periphery (https://github.com/vsergeev/python-periphery)
(It did not know c-periphery but this is the same author)

Before having full fledged linux drivers, it allows to check devices IDs, make simple requests like get a sensor value or enable a PMIC regulator.

I'm interested in the list of packages you'll end up with... Will you share it here ?

Regards,
--
Yoann Congal
Smile ECS - Expert technique


[PATCH] linux-yocto/5.4: fix arm defconfig warnings

Bruce Ashfield
 

From: Bruce Ashfield <bruce.ashfield@gmail.com>

A recent fix to the kern-tools promoted some previously unseen
issues to warnings. This commit fixes them by tagging some BT
options as non-hardware so they won't generate warnings if they
don't appear in the final .config. These are sub BT options and
shouldn't warn when/if their controlling option is disabled by
a fragment.

d7fd0213b75 base: exclude some BT options as non-hardware

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index e52c9ebe0e..a802a570a1 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -12,7 +12,7 @@ python () {
}

SRCREV_machine ?= "324e77d816cf6434507ab29140beb24044009efa"
-SRCREV_meta ?= "5017570a130f142365dfdcd043d84143fdd6e255"
+SRCREV_meta ?= "d7fd0213b75ce9b6206f63dbdd435ab326598642"

SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index f07375c761..1edc632de7 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -17,7 +17,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"

SRCREV_machine_qemuarm ?= "8463db325b93f0669446f68c19334cfe11ffb9c2"
SRCREV_machine ?= "5f54b437b6502d3febee553100b2cb2a9e0c5f8a"
-SRCREV_meta ?= "5017570a130f142365dfdcd043d84143fdd6e255"
+SRCREV_meta ?= "d7fd0213b75ce9b6206f63dbdd435ab326598642"

PV = "${LINUX_VERSION}+git${SRCPV}"

diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 4f056d6d82..3a9463af6a 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -23,7 +23,7 @@ SRCREV_machine_qemux86 ?= "5f54b437b6502d3febee553100b2cb2a9e0c5f8a"
SRCREV_machine_qemux86-64 ?= "5f54b437b6502d3febee553100b2cb2a9e0c5f8a"
SRCREV_machine_qemumips64 ?= "996fe040c8d8d01a9af6be42dae3844d127471bf"
SRCREV_machine ?= "5f54b437b6502d3febee553100b2cb2a9e0c5f8a"
-SRCREV_meta ?= "5017570a130f142365dfdcd043d84143fdd6e255"
+SRCREV_meta ?= "d7fd0213b75ce9b6206f63dbdd435ab326598642"

# remap qemuarm to qemuarma15 for the 5.4 kernel
# KMACHINE_qemuarm ?= "qemuarma15"
--
2.19.1


Re: what to include in a "hardware bringup image"?

Mike Looijmans
 

I tend to use a reasonably standard image, usually the one that will evolve into the product, and once the network (usb, ethernet or wifi) is up, use "opkg install" to grab whatever else I need from my build machine on demand.




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.topic.nl

Please consider the environment before printing this e-mail

On 15-04-2021 10:24, Robert P. J. Day via lists.yoctoproject.org wrote:
for a current project (and subsequent projects), i want to define a
hardware bringup image; that is, a really basic image chock-full of
low-level utilities for debugging initial board bringup. this means
precious little unnecessary userspace crud that has no value in that
context. (at the moment, the target is aarch64 but, naturally, the
ideal image would be maximally applicable no matter the target.)

i'm thinking of recipes that allow probing/configuration of memory
and busses and that sort of thing. off the top of my head:

* pciutils
* usbutils
* libgpiod
* phytool (or other MDIO probe/debug tools)
* devmem2
* spidev-test/spitools
* i2c-tools

the list can go on and on, and i just ran across this which i had
never seen before:

http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/c-periphery/c-periphery_2.3.1.bb?h=master

suggestions? i suspect numerous folks on this list have already done
something like this.

rday

--
Mike Looijmans


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

Sangeeta Jain
 

Hi All,

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

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

no new issue found

Thanks,
Sangeeta

-----Original Message-----
From: qa-build-notification@lists.yoctoproject.org <qa-build-
notification@lists.yoctoproject.org> On Behalf Of Pokybuild User
Sent: Wednesday, 14 April, 2021 5:55 AM
To: yocto@lists.yoctoproject.org
Cc: qa-build-notification@lists.yoctoproject.org
Subject: [qa-build-notification] QA notification for completed autobuilder build
(yocto-3.1.7.rc1)


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


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


Build hash information:

bitbake: 017a39ed05d065bf28fd38f91bcde8a098300551
meta-arm: 1cf8b975e1c40bf8e8c0bf315db5d4cddcb01a7b
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 4bd62a7e154b8c9e8a114f452d3b062d8d058118
meta-kernel: 29329d7cacc71595cecfdd05a455a0cfb164564d
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
oecore: a3de6239e98efafe3668396e69133ffee3d9b27f
poky: 13f4ddf50eccaeed96a40a5f1a1d4173e677e98a



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







Re: Yocto Dunfell: u-boot-fw-utils ERROR #imx6 #yocto #dunfell #swupdtae #libubootenv

Mikko Rapeli
 

Hi,

On Tue, Apr 20, 2021 at 03:24:25AM -0700, anthony.marchand@navocap.com wrote:
Hello,
I'm actually migrating a yocto project zeus version to dunfell LTS to build my imx6 Linux system on this LTS release.

Almost all works fine except the following message I try to understand when I try to compile the image:

---------------------------------------------------------------------------------------------------------------------------------------------------------
ERROR: Multiple .bb files are due to be built which each provide u-boot-fw-utils:                       | ETA:  0:00:01
Dunfell/build/../meta-mymeta/recipes-bsp/u-boot/u-boot-fw-utils_2018.09.bb
Dunfell/build/../openembedded-core/meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb
A list of tasks depending on these providers is shown and may help explain where the dependency comes from.
Dunfell/build/../meta-mymeta/recipes-bsp/u-boot/u-boot-fw-utils_2018.09.bb has unique dependees:

Dunfell/build/../openembedded-core/meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb has unique dependees:
Dunfell/build/../meta-swupdate/recipes-support/swupdate/swupdate_2020.11.bb:do_build
Dunfell/build/../meta-swupdate/recipes-support/swupdate/swupdate_2020.11.bb:do_package
Dunfell/build/../meta-swupdate/recipes-support/swupdate/swupdate_2020.11.bb:do_prepare_recipe_sysroot
It could be that one recipe provides something the other doesn't and should. The following provider and runtime provider differences may be helpful.
Dunfell/build/../meta-mymeta/recipes-bsp/u-boot/u-boot-fw-utils_2018.09.bb has unique provides:

Dunfell/build/../meta-mymeta/recipes-bsp/u-boot/u-boot-fw-utils_2018.09.bb has unique rprovides:
u-boot-fw-utils-dev
u-boot-fw-utils-locale
u-boot-fw-utils-dbg
u-boot-fw-utils-staticdev
u-boot-fw-utils-doc
^u-boot-fw-utils-locale-.*
u-boot-fw-utils-src
Dunfell/build/../openembedded-core/meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb has unique provides:
libubootenv
Dunfell/build/../openembedded-core/meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb has unique rprovides:
libubootenv
libubootenv-src
libubootenv-bin
libubootenv-dbg
libubootenv-doc
^libubootenv-locale-.*
libubootenv-locale
libubootenv-dev
libubootenv-staticdev
---------------------------------------------------------------------------------------------------------------------------------------------------------
Does someone already meet this problem? Do you know what I should look in for to solve it?
Multiple ways to fix this. One is to switch to using dunfell branches for the
BSP SW stack, if they are available. Alternatively you can use the old
zeus based BSP SW stack but for that you need to copy the files which
BSP SW stack depends on poky side from zeus branch to the BSP SW meta layer.

Then things will work out with minor bug fixes or API changes.

For IMX*, I copied the old u-boot recipe files from poky zeus branch over to
the BSP so that meta-freescale* and meta-imx find them and prefer over
the newer u-boot version from poky dunfell branch.

Hope this helps,

-Mikko

Thanks by advance, best reguards.



Yocto Dunfell: u-boot-fw-utils ERROR #imx6 #yocto #dunfell #swupdtae #libubootenv

anthony.marchand@...
 

Hello,
I'm actually migrating a yocto project zeus version to dunfell LTS to build my imx6 Linux system on this LTS release.

Almost all works fine except the following message I try to understand when I try to compile the image:

---------------------------------------------------------------------------------------------------------------------------------------------------------
ERROR: Multiple .bb files are due to be built which each provide u-boot-fw-utils:                       | ETA:  0:00:01
  Dunfell/build/../meta-mymeta/recipes-bsp/u-boot/u-boot-fw-utils_2018.09.bb
  Dunfell/build/../openembedded-core/meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb
A list of tasks depending on these providers is shown and may help explain where the dependency comes from.
Dunfell/build/../meta-mymeta/recipes-bsp/u-boot/u-boot-fw-utils_2018.09.bb has unique dependees:
  
Dunfell/build/../openembedded-core/meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb has unique dependees:
  Dunfell/build/../meta-swupdate/recipes-support/swupdate/swupdate_2020.11.bb:do_build
  Dunfell/build/../meta-swupdate/recipes-support/swupdate/swupdate_2020.11.bb:do_package
  Dunfell/build/../meta-swupdate/recipes-support/swupdate/swupdate_2020.11.bb:do_prepare_recipe_sysroot
It could be that one recipe provides something the other doesn't and should. The following provider and runtime provider differences may be helpful.
Dunfell/build/../meta-mymeta/recipes-bsp/u-boot/u-boot-fw-utils_2018.09.bb has unique provides:
  
Dunfell/build/../meta-mymeta/recipes-bsp/u-boot/u-boot-fw-utils_2018.09.bb has unique rprovides:
  u-boot-fw-utils-dev
  u-boot-fw-utils-locale
  u-boot-fw-utils-dbg
  u-boot-fw-utils-staticdev
  u-boot-fw-utils-doc
  ^u-boot-fw-utils-locale-.*
  u-boot-fw-utils-src
Dunfell/build/../openembedded-core/meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb has unique provides:
  libubootenv
Dunfell/build/../openembedded-core/meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb has unique rprovides:
  libubootenv
  libubootenv-src
  libubootenv-bin
  libubootenv-dbg
  libubootenv-doc
  ^libubootenv-locale-.*
  libubootenv-locale
  libubootenv-dev
  libubootenv-staticdev
---------------------------------------------------------------------------------------------------------------------------------------------------------
Does someone already meet this problem? Do you know what I should look in for to solve it?

Thanks by advance, best reguards.


[PATCH] [yocto-autobuilder-helper 2/2] scripts/utils.py: Add reporting for yocto-check-layer

Yi Fan Yu
 

The default behavior is to look for a bitbake command,
which fails and produces a confusing output of [-1:].

[YOCTO #14208]

Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com>
---
scripts/utils.py | 3 +++
1 file changed, 3 insertions(+)

diff --git a/scripts/utils.py b/scripts/utils.py
index bf1d989..4c73f81 100644
--- a/scripts/utils.py
+++ b/scripts/utils.py
@@ -330,6 +330,9 @@ class ErrorReport(object):
elif 'oe-selftest' in command:
report['error_type'] = 'oe-selftest'
failure['task'] = command[command.find('oe-selftest'):]
+ elif 'yocto-check-layer' in command:
+ report['error_type'] = 'check-layer'
+ failure['task'] = command[command.find('yocto-check-layer'):]
else:
report['error_type'] = 'core'
failure['task'] = command[command.find('bitbake'):]
--
2.29.2


[PATCH] [yocto-autobuilder-helper 1/2] config.json: Add default MACHINE qemux86-64

Yi Fan Yu
 

This is the default oe-core MACHINE value.

Prevent error-reporting tool to report simply False.
It was seen in check-layer where the MACHINE wasn't specified.

[YOCTO #14208]

Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com>
---
config.json | 1 +
1 file changed, 1 insertion(+)

diff --git a/config.json b/config.json
index 962d8ae..2d1a698 100644
--- a/config.json
+++ b/config.json
@@ -26,6 +26,7 @@
"defaults" : {
"NEEDREPOS" : ["poky"],
"DISTRO" : "poky",
+ "MACHINE" : "qemux86-64",
"SDKMACHINE" : "i686",
"PACKAGE_CLASSES" : "package_rpm package_deb package_ipk",
"DLDIR" : "DL_DIR = '${BASE_SHAREDDIR}/current_sources'",
--
2.29.2


M+ & H bugs with Milestone Movements WW16

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

High

14334

open-vm-tools not present in layer index

randy.macleod@...

bluelightning@...

3.3 M4

3.4 M1

Medium+

5322

Global DNS fallback mechanism not present in poky distro

kai.kang@...

kai.kang@...

3.3 M4

3.4 M2

 

10748

Means of querying history for a single variable

richard.purdie@...

richard.purdie@...

Future

3.4 M1

 

11449

Allow overriding classes to override overridden classes

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

11746

oe-selftest: capture self.logger messages in XML output

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

11766

nobody group added by systemd sysusers.d

randy.macleod@...

yi.zhao@...

3.4

3.3 M1

 

 

yi.zhao@...

yi.zhao@...

3.3 M4

3.4

 

12060

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

kai.kang@...

kai.kang@...

3.3 M4

3.4 M2

 

12090

bitbake resident server reconnect needed ?

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

12279

enhance manifest not found warning

kai.kang@...

kai.kang@...

3.3 M4

3.3 M1

 

 

 

 

3.3 M1

3.4 M1

 

12342

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

kai.kang@...

kai.kang@...

3.3 M4

3.4 M1

 

12368

persistent bitbake server does not re-parse if previous build was ctrl+C'd

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

12917

Warnings from nightly-multilib builds (build-deps)

kai.kang@...

kai.kang@...

3.3 M4

3.4 M2

 

12970

uninative file should be versionned

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

12986

Failed to expand SRCPV on updateding SRC_URI using pn overrides and BBCLASSEXTEND

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13183

bitbake-layers crashes with incorrect layer configuration data is given (expected proper error printing and exit with error)

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13278

If git protocol doesn't work, you get a tar.gz clone from PREMIRROR which has git protocol origin

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13424

devupstream doesn't work with mutilib

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13448

bitbake master appears to expand variables it should not need to

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13599

Enhancement: Detect variables that shouldn't be defined in image scope, but in global (distro) scope

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13699

Prolonged recipe parsing times after removing tmp when the resident bitbake server is used

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13711

Parsing fails on externalsrc recipe containing both git and file in SRC_URI

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13729

Changing siteinfo files doesn't change task checksum

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13823

fetch2: PREMIRROR and SRC_URI with users on both url yields invalid username

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13886

bitbake resident server does not honour --runonly or --runall options

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

13973

change siginfo data format to json for reproducibility? (siginfo files currently not reproducible)

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

14088

Attempting to override RDEPENDS_${PN} from global config doesn't work

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

14118

systemd services not enabled when using package feed

kai.kang@...

kai.kang@...

3.3 M4

3.4 M3

 

14156

gitsm: submodules are fetched as mirrored and not working as expected

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

14262

runcmd.RunCmdTests.test_stdin_timeout times out

randy.macleod@...

unassigned@...

3.3 M4

3.4 M1

 

14277

oe-selftest: test_maintainers fails with oe-core works with poky

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

 

14282

Allow % and @ in working dir path

richard.purdie@...

richard.purdie@...

3.3 M4

3.4 M1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Enhancements/Bugs closed WW16!

Stephen Jolley
 

All,

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

Who

Count

ross@...

2

akuster808@...

2

randy.macleod@...

2

richard.purdie@...

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 3.4

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

35

ross@...

25

david.reyna@...

23

bruce.ashfield@...

20

bluelightning@...

16

akuster808@...

12

timothy.t.orling@...

12

mark.morton@...

11

JPEWhacker@...

10

sakib.sajal@...

10

yifan.yu@...

10

trevor.gamblin@...

10

kai.kang@...

8

hongxu.jia@...

7

raj.khem@...

6

randy.macleod@...

6

chee.yang.lee@...

6

Qi.Chen@...

6

mingli.yu@...

5

stacygaikovaia@...

4

nicolas.dechesne@...

3

saul.wold@...

3

idadelm@...

3

yi.zhao@...

3

mostthingsweb@...

3

michael.opdenacker@...

2

jaewon@...

2

jon.mason@...

2

pokylinux@...

2

alejandro@...

2

jeanmarie.lemetayer@...

2

matthewzmd@...

2

ydirson@...

2

shachar@...

1

kexin.hao@...

1

yoctoproject@...

1

open.source@...

1

dorindabassey@...

1

twoerner@...

1

mister_rs@...

1

changqing.li@...

1

john.kaldas.enpj@...

1

Martin.Jansa@...

1

kergoth@...

1

mshah@...

1

mhalstead@...

1

steve@...

1

liezhi.yang@...

1

devendra.tewari@...

1

naveen.kumar.saini@...

1

matt.ranostay@...

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: [meta-gplv2] [PATCH] conf/distro: Add removal of btrfs-tools from util-linux ptest depends

Robert Joslyn
 

Just to clarify, btrfs-tools has always had an LGPL-3.0 library (libbtrfsutil), the recipe just never declared it before. Upstream is relicensing that library to LGPL-2.1+, which should be done for the next release.

Sorry about this, I sent the update and didn’t realize it broke the non-gplv3 builds. I’ll keep an eye out for the next upstream release which should allow this patch to be reverted.

Thanks,
Robert

On Apr 19, 2021, at 2:29 PM, Ross Burton <ross@burtonini.com> wrote:

+1.

Ross

On Mon, 19 Apr 2021 at 21:47, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:

btrfs-tools has changed to LGPL-3.1 so to allow util-linux to build,
remove the dependency from its ptest package. This may regress some
ptests but keeps the gplv2 layer working.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
conf/distro/include/disable-gplv3.inc | 1 +
1 file changed, 1 insertion(+)

diff --git a/conf/distro/include/disable-gplv3.inc b/conf/distro/include/disable-gplv3.inc
index bded378..3285543 100644
--- a/conf/distro/include/disable-gplv3.inc
+++ b/conf/distro/include/disable-gplv3.inc
@@ -1,3 +1,4 @@
INCOMPATIBLE_LICENSE = '*GPLv3*'
WARN_QA_remove = 'incompatible-license'
RDEPENDS_${PN}-ptest_remove_pn-glib-2.0 = "python3-dbusmock"
+RDEPENDS_${PN}-ptest_remove_pn-util-linux = "btrfs-tools"
--
2.30.2




[ANNOUNCEMENT] Yocto Project 3.3 (hardknott-25.0.0) is Released

Vineela
 

Hello,

We are pleased to announce the Yocto Project 3.3 (hardknott-25.0.0) Release is now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/poky-hardknott-25.0.0.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3/poky-hardknott-25.0.0.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/testreport.txt

Thank you for everyone's contributions to this release.

Vineela Tummalapalli
Yocto Project Build and Release
vineela.tummalapalli@intel.com


--------------------------
yocto-3.3 Release Notes
--------------------------

--------------------------
Repositories/Downloads
--------------------------

Repository Name: poky
Repository Location: https://git.yoctoproject.org/git/poky
Branch: hardknott
Tag: yocto-3.3
Git Revision: e1839b58ebe05242a52fe050aa9a08140136aa0a
Release Artefact: poky-hardknott-25.0.0
sha: 2d08ed735badad119a4228e113115f91615837127b62176fb570be6929417292
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/poky-hardknott-25.0.0.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3/poky-hardknott-25.0.0.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: hardknott
Tag: 2021-04-hardknott
Git Revision: 14241ed09f9ed317045cf75a6d08416d3579bb8d
Release Artefact: oecore-hardknott-25.0.0
sha: 4f00bfd3804517ea5e68502af896e5a162a5cef86d00f5170e9748ffe77386a6
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/oecore-hardknott-25.0.0.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3/oecore-hardknott-25.0.0.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/git/meta-mingw
Branch: hardknott
Tag: yocto-3.3
Git Revision: 422b96cb2b6116442be1f40dfb5bd77447d1219e
Release Artefact: meta-mingw-hardknott-25.0.0
sha: 39bfa386f04111d8cfa8791977a416344bbb0a1fd5167e42bd9c9d6923f0e009
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/meta-mingw-hardknott-25.0.0.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3/meta-mingw-hardknott-25.0.0.tar.bz2

Repository Name: meta-intel
Repository Location: https://git.yoctoproject.org/git/meta-intel
Branch: hardknott
Tag: yocto-3.3
Git Revision: 01cfc99a8f960917433a8a46b41bb4febb5b1993
Release Artefact: meta-intel-hardknott-25.0.0
sha: 671c2a7f7080bd0dc4049c0ceef8d9ca561e6b1412586d2c218834e13d8f99c7
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/meta-intel-hardknott-25.0.0.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3/meta-intel-hardknott-25.0.0.tar.bz2

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: hardknott
Tag: yocto-3.3
Git Revision: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
Release Artefact: meta-gplv2-hardknott-25.0.0
sha: 2679412d6a3c8db0471d1d91f5667c2ebc10558ad574b6169e2e572608c0e6c6
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/meta-gplv2-hardknott-25.0.0.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3/meta-gplv2-hardknott-25.0.0.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: 1.50
Tag: 2021-04-hardknott
Git Revision: a1848a481e36b729c8e4130c394b1d462d4b488a
Release Artefact: bitbake-hardknott-25.0.0
sha: 09e6ebcb579a3eaf3760ff53e0da71cd55b5eed557918230bd5cddd5b5c53c72
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/bitbake-hardknott-25.0.0.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.3/bitbake-hardknott-25.0.0.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/git/yocto-docs
Branch: hardknott
Tag: yocto-3.3
Git Revision:4f7f451df266a307b34bf145b29291ca85eb882f

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Abdellatif El Khlifi
Adrian Fiergolski
Adrian Herrera
Alan Perry
Alban Bedel
Alejandro Hernandez Samaniego
Alexander Kamensky
Alexander Kanavin
Alexander Vickberg
Alex Stewart
Alistair Francis
Anatol Belski
Andreas Müller
Andrei Gherzan
Andrej Valek
Andrey Mozzhuhin
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton D. Kachalov
Anton Kachalov
Anuj Mittal
Armin Kuster
Awais Belal
Bartosz Golaszewski
Brett Warren
Bruce Ashfield
Cedric Hombourger
Chaitanya Vadrevu
Chandana Kalluri
Changhyeok Bae
Changqing Li
Charlie Davies
Chee Yang Lee
Chen Qi
Chris Laplante
Christophe Priouzeau
Christopher Larson
Colin Finck
Dan Callaghan
Deepak Rawat
Denys Dmytriyenko
Denys Zagorui
Diego Santa Cruz
Diego Sueiro
Dmitry Baryshkov
Dorinda Bassey
Douglas Royds
Easwar Hariharan
Elvis Stansvik
Fabio Berton
Federico Pellegrin
Fedor Ross
Florian Bezdeka
Fredrik Gustafsson
Gratian Crisan
Guillaume Champagne
He Zhe
Hongxu Jia
Jack Mitchell
Jan Brzezanski
Jan Vermaete
Janne Kiiskila
Jan-Simon Möller
Jason Wessel
Jate Sujjavanich
Joel Stanley
Joey Degges
Jonathan Richardson
Jon Mason
Joseph Reynolds
Jose Quaresma
Joshua Watt
Kai Kang
Kamel Bouhara
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khasim Mohammed
Khem Raj
Klaus Heinrich Kiwi
Konrad Weihmann
Lee Chee Yang
Leon Anavi
Li Wang
Loic Domaigne
Luca Boccassi
Mans Rullgard
Manuel Leonhardt
Marek Vasut
Mark Hatle
Mark Jonas
Martin Jansa
Matt Hoosier
Matt Madison
Maxime Roussin-Bélanger
Max Krummenacher
Meh Mbeh Ida Delphine
Mert Kirpici
Michael Halstead
Michael Ho
Michael Opdenacker
Michael Trensch
Mike Crowe
Mike Looijmans
Mikko Rapeli
Milan Shah
Ming Liu
Mingli Yu
Minjae Kim
Nathan Rossi
Naveen Saini
Nicolas Dechesne
Norbert Kaminski
Oleksandr Kravchuk
Oleksiy Obitotskyy
Ovidiu Panait
Paul Barker
Paul Eggleton
Paul Gortmaker
Peter Bergin
Peter Kjellerstedt
Petr Vorel
Purushottam Choudhary
Quentin Schulz
Randy Li
Randy MacLeod
Randy Witt
Ricardo Salveti
Richard Leitner
Richard Purdie
Robert P. J. Day
Robert Rosengren
Robert Yang
Ross Burton
Sakib Sajal
Saloni Jain
Sangeeta Jain
Saul Wold
Scott Branden
Scott Murray
Shachar Menashe
Sinan Kaya
Stacy Gaikovaia
Stefan Ghinea
Stefan Schmidt
Steve Sakoman
Suji Velupillai
Tanu Kaskinen
Teoh Jay Shen
Thomas Perrot
Thomas Viehweger
Tim Orling
Tomasz Dziendzielski
Tom Hochstein
Trevor Woerner
Tyler Hicks
Ulrich Ölmann
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
Wonmin Jung
Yanfei Xu
Yann Dirson
Yann E. MORIN
Yi Fan Yu
Yi Zhao
Yoann Congal
Yongxin Liu
Zang Ruochen
Zheng Ruoqin
Zhixiong Chi



-----------------------------
New Features / Enhancements
-----------------------------
* Linux kernel 5.10, glibc 2.33 and ~280 other recipe upgrades
* New recipes: glslang, gst-devtools, libgit2, libmd, libportal, libssh2, numactl, packagegroup-core-weston, python3-atomicwrites, python3-attrs, python3-hypothesis, python3-importlib-metadata, python3-iniconfig, python3-more-itertools, python3-packaging, python3-pathlib2, python3-pluggy, python3-py, python3-pytest, python3-setuptools-scm, python3-sortedcontainers, python3-toml, python3-wcwidth, python3-zipp, shaderc, spirv-headers, spirv-tools, util-linux-libuuid, vulkan-samples, wayland-utils, xxhash, zstd
* Python 3.6 or newer is required to be on build host.
* New PACKAGECONFIG options in: binutils, coreutils, elfutils, epiphany, ffmpeg, gdb, gstreamer1.0-plugins-*, iproute2, json-glib, libomxil, openssl, p11-kit, parted, psplash, pulseaudio, qemu, socat, systemd, systemd-conf, webkitgtk
* New meta/conf/distro/include/lto.inc for enabling Link-Time Optimisation (LTO)
* Added support for elfutils debug info server (debuginfod)
* Added infrastructure to support u-boot SPL verified boot with optional separate signing key
* Reduce poky-tiny size by over 15% by enabling size optimisation by default, enabling section removal and tweaking busybox configuration
* Increased package granularity for dbus, sudo, iproute2, net-tools, procps, rpm, systemtap
* Added support for vhd/vhdx format in IMAGE_FSTYPES
* New extrausers "passwd-expire" command to force password change on first login
* buildhistory now records LICENSE
* Architecture-specific improvements:
- New qemuriscv32 machine
- New qemuppc64 machine
- python-numpy: Add support for riscv32
- arch-riscv: Enable qemu-usermode on rv32
- grub: Add support for RISC-V
- Enable systemd-boot and grub-efi for Arm targets
- core-image-tiny-initramfs: add compatibility for aarch64
- linux-yocto/cfg: qemuppc: set CONFIG_SCSI to '=y'
- linux-yocto/cfg: qemuarm64-gfx.cfg: add CONFIG_INPUT_UINPUT
- Enabled bochs-display on qemuriscv* machines
- go: Enable CGO and pie buildmode on rv64
- tune-power9: Enable qemu-usermode
- glibc: Build for power9 cpu when using powerpc64le tunes
- tune-octeontx2.inc: Add tune for Marvell OCTEON TX2 core
- tune-cortexa32: Add hard FPU
- beaglebone-yocto: allow other virtual/bootloader
* SDK-related changes:
- New ppc64le SDK machine
- Extended to nativesdk: apt, ccache, diffstat, dpkg, grep, grub, rsync, sed, vim, which
- New SDK_PS1 variable to allow custom prompt string for SDKs
- New SDK_CUSTOM_TEMPLATECONF variable to enable custom templateconf.cfg in eSDK
- do_populate_sdk can now run in parallel with do_rootfs
* Kernel related improvements:
- linux-yocto*: add features/gpio/mockup.scc to KERNEL_FEATURES
- kern-tools: non-gcc config support and option re-classification
- kernel-module-split.bbclass: identify kernel modconf files as configuration files for package upgrade purposes
- kernel-devicetree: Introduce KERNEL_DTC_FLAGS to pass dtc flags
* u-boot fitImage related improvements:
- Added support for Initramfs bundle and u-boot script
- Support both KERNEL_DEVICETREE and EXTERNAL_KERNEL_DEVICETREE
- Allow substituting mkimage command and add additional signing options
- Added ability to sign individual images
- Added variable for description
- Allow kernel image compression to be disabled
* wic image creator improvements:
- New "empty" plugin to create unformatted empty partitions
- Warn if an ext filesystem affected by the Y2038 problem is used
- Add workdir argument and option to preserve it for debugging
* runqemu improvements:
- New "novga" option to disable VGA emulation
- Added QB_GRAPHICS for QEMU video card type options
- Added support for VHD/VHDX rootfs
* BitBake improvements:
- Added Azure Storage (az://) fetcher
- Added zstd support to unpack
- hashserv: new -r/--readonly option to disable writes
- hashserv: new -u/--upstream option to enable upstream server
- hashserv: added Dockerfile under bitbake/contrib/ for building hash server
- Added REQUIRED_VERSION variable
- PREFERRED_VERSION is now a warning instead of a note
- bitbake-layers create-layer: added optional --layerid option
- Added BB_DEFAULT_UMASK to avoid having to set umask flag everywhere
- Show an appropriate error when a task name contains reserved keywords (e.g. _remove)
- Print pseudo.log if a fakeroot task fails
* cve-check improvements:
- New CVE_VERSION_SUFFIX variable to indicate suffix in versioning
- Fixed handling of pre-release version numbers
- Record layer in cve log
- Added ability to include/exclude layers
- cve-update-db-native: enable overriding the URL to allow local mirror usage
* Wayland/weston related changes:
- weston-init: Weston can now run using non-root user
- weston-init: introduce WESTON_GROUP
- core-image.bbclass: add a weston IMAGE_FEATURES feature, similar to x11-base
* Extension of package management is now possible from custom layers
* build-appliance: enabled VHD/VHDX generation
* buildstats: add functionality to collect build system stats
* base-files: better support for terminal resizing over serial connections
* Added /sysroot-only dir to install files to sysroot but not include in packages
* Removed some extraneous files that were installed into the sysroot
* New python3targetconfig class to enable using python3-native but with target configuration
* isoimage-isohybrid.py: Support adding files/dirs
* distutils3: allow setup.py to be run from a different directory to ${S}
* busybox-inittab: implemented SYSVINIT_ENABLED_GETTYS and USE_VT
* busybox: Run mdev as daemon
* psplash (sysvinit): add textual updates
* libyaml: Enable static lib on native/nativesdk
* rootfs: add option to allow delayed postinsts on read-only rootfs
* npm.bbclass: make shrinkwrap file optional
* initrdscripts: init-install-efi.sh install extra files for ESP
* openssl: add support for mingw64 as target
* mpg123: Add support for FPU-less targets
* mesa: enable dri in native/nativesdk through gallium drivers
* security_flags.inc: Add same O<level> as in SELECTED_OPTIMIZATION
* systemd: add hostname fallback when polkit is not available
* Use canonical SPDX license names in image license manifests
* gcr: Add support for building without x11
* gstreamer1.0: add support for coretracers
* file: enable all built-in compression checkers
* linux-firmware: package firmware for Lontium lt9611uxc bridge, ath11k
* sstate-diff-machines.sh: support rpm, deb and tar package types in analysis
* systemd-serialgetty: Switch to TERM=linux for better xterm compatibility
* volatile-binds: add /srv to mount and install
* New oe-time-dd-test.sh script for testing build system I/O loading
* packagegroup-base: make hdparm and e2fsprogs RRECOMMENDS so they can be optional
* New QA check for native/nativesdk inherit order
* GitLab /archive/ URLs in SRC_URI now trigger a warning
* Added descriptive error message to getpwuid/getgrgid "uid/gid not found" KeyError
* Added additional checks for PSEUDO_IGNORE_PATHS validity
* Split sstate summary display into locally and network found artifacts
* report-error.bbclass: added layer and bitbake version info to error report
* perl: allow empty lines and comments in perl-rdepends.txt
* contrib/git-hooks: add a sendemail-validate example hook that adds FROM: lines to outgoing patch emails
* common-licenses: add BSD-3-Clause-Clear license
* common-licenses: Add GPL-3.0-with-bison-exception
* Renamed GPL-family common license files so that "-only" and "-or-later" is explicitly specified to match with current SPDX.

--------------
Known Issues
--------------
N/A

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

* alsa-utils: GPLv2+ -> GPLv2 (as some parts of the source are GPLv2 only)
* busybox: included bzip2 source is the 1.0.4 version not 1.0.6, so tweak the LICENSE value to reflect that
* libbsd: specify per-package licensing to reflect that BSD-4-Clause doesn't cover contents of main package (only some documentation)
* libdnf: LGPLv2.1 -> LGPLv2.1+ to match with what is specified in header comments
* openssh: expand "BSD" to specifically include BSD-2-Clause, BSD-3-Clause and BSD-4-Clause
* ptest-runner: GPLv2 -> GPLv2+ to match with what is specified in header comments


------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.3 release from previous releases, please see the following manual section:

http://www.yoctoproject.org/docs/3.3/ref-manual/ref-manual.html#moving-to-the-yocto-project-3.3-release



----------------
Security Fixes
----------------

* binutils: CVE-2020-35448
* connman: CVE-2021-26675, CVE-2021-26676
* cups: CVE-2020-10001
* curl: CVE-2020-8284, CVE-2020-8285, CVE-2020-8286
* ffmpeg: CVE-2020-35964, CVE-2020-35965
* gdk-pixbuf: CVE-2020-29385
* git: CVE-2021-21300
* glibc: CVE-2019-25013, CVE-2020-27618, CVE-2020-29562, CVE-2020-29573, CVE-2021-27645
* grub: CVE-2014-4607, CVE-2020-10713, CVE-2020-14308, CVE-2020-14309, CVE-2020-14310, CVE-2020-14311, CVE-2020-14372, CVE-2020-15705, CVE-2020-15706, CVE-2020-15707, CVE-2020-25632, CVE-2020-25647, CVE-2020-27749, CVE-2020-27779, CVE-2021-3418, CVE-2021-20225, CVE-2021-20233
* libcroco: CVE-2020-12825
* libexif: CVE-2020-0198, CVE-2020-0452
* libproxy: CVE-2020-26154
* openssl: CVE-2020-1971, CVE-2021-3449, CVE-2021-3450
* p11-kit: CVE-2020-29361, CVE-2020-29362, CVE-2020-29363
* patch: CVE-2019-20633
* python3: CVE-2020-27619, CVE-2021-3177
* qemu: CVE-2020-24352, CVE-2020-25624, CVE-2020-25723, CVE-2020-28916, CVE-2020-29129, CVE-2020-29130, CVE-2021-20203
* ruby: CVE-2020-25613
* screen: CVE-2021-26937
* sudo: CVE-2021-3156
* u-boot: CVE-2021-27097, CVE-2021-27138
* wpa-supplicant: CVE-2021-0326, CVE-2021-27803



-----------------
Recipe Upgrades
-----------------

* acpica 20200717 -> 20210105
* adwaita-icon-theme 3.36.1 -> 3.34.3, 3.38.0
* alsa-lib 1.2.3.2 -> 1.2.4
* alsa-topology-conf 1.2.3 -> 1.2.4
* alsa-ucm-conf 1.2.3 -> 1.2.4
* alsa-utils 1.2.3 -> 1.2.4
* alsa-utils-scripts 1.2.3 -> 1.2.4
* apt 1.8.2.1 -> 2.2.2
* asciidoc 9.0.2 -> 9.1.0
* at 3.1.23 -> 3.2.1
* at-spi2-atk 2.34.2 -> 2.38.0
* at-spi2-core 2.36.1 -> 2.38.0
* attr 2.4.48 -> 2.5.1
* autoconf 2.69 -> 2.71
* automake 1.16.2 -> 1.16.3
* bash 5.0 -> 5.1
* bind 9.16.7 -> 9.16.12
* binutils 2.35.1 -> 2.36.1
* bison 3.7.2 -> 3.7.5
* bluez5 5.55 -> 5.56
* bmap-tools 3.5+gitX -> 3.6+gitX
* boost 1.74.0 -> 1.75.0
* btrfs-tools 5.7 -> 5.10.1
* busybox 1.32.0 -> 1.33.0
* busybox-inittab 1.32.0 -> 1.33.0
* cantarell-fonts 0.0.25 -> 0.301
* ccache 3.7.11 -> 4.2
* cmake 3.18.2 -> 3.19.5
* cmake-native 3.18.2 -> 3.19.5
* createrepo-c 0.16.0 -> 0.17.0
* cross-localedef-native 2.32 -> 2.33
* cryptodev-linux 1.11 -> 1.12
* cryptodev-module 1.11 -> 1.12
* cryptodev-tests 1.11 -> 1.12
* curl 7.72.0 -> 7.75.0
* debianutils 4.11.1 -> 4.11.2
* dhcpcd 9.2.0 -> 9.4.0
* diffoscope 160 -> 172
* diffstat 1.63 -> 1.64
* distcc 3.3.3 -> 3.3.5
* dmidecode 3.2 -> 3.3
* dnf 4.2.23 -> 4.6.0
* dos2unix 7.4.1 -> 7.4.2
* dosfstools 4.1 -> 4.2
* dpkg 1.20.5 -> 1.20.7.1
* dropbear 2020.80 -> 2020.81
* e2fsprogs 1.45.6 -> 1.46.1
* ed 1.16 -> 1.17
* elfutils 0.180 -> 0.183
* ell 0.33 -> 0.38
* enchant2 2.2.9 -> 2.2.15
* epiphany 3.36.4 -> 3.38.2
* ethtool 5.8 -> 5.10
* eudev 3.2.9 -> 3.2.10
* expat 2.2.9 -> 2.2.10
* ffmpeg 4.3.1 -> 4.3.2
* findutils 4.7.0 -> 4.8.0
* freetype 2.10.2 -> 2.10.4
* gcr 3.36.0 -> 3.38.1
* gdb 9.2 -> 10.1
* gdbm 1.18.1 -> 1.19
* ghostscript 9.52 -> 9.53.3
* git 2.28.0 -> 2.31.1
* glib-2.0 2.64.5 -> 2.66.7
* glib-networking 2.64.3 -> 2.66.0
* glibc 2.32 -> 2.33
* gmp 6.2.0 -> 6.2.1
* gnu-config 20200831+gitX -> 20210125+gitX
* gnupg 2.2.23 -> 2.2.27
* gnutls 3.6.14 -> 3.7.1
* go 1.15.8 -> 1.16.2
* gobject-introspection 1.64.1 -> 1.66.1
* gpgme 1.14.0 -> 1.15.1
* gptfdisk 1.0.5 -> 1.0.7
* grep 3.4 -> 3.6
* grub 2.04 -> 2.04+2.06~rc1
* grub-efi 2.04 -> 2.04+2.06~rc1
* gsettings-desktop-schemas 3.36.1 -> 3.38.0
* gst-examples 1.16.0 -> 1.18.4
* gstreamer1.0 1.16.3 -> 1.18.4
* gstreamer1.0-libav 1.16.3 -> 1.18.4
* gstreamer1.0-omx 1.16.3 -> 1.18.4
* gstreamer1.0-plugins-bad 1.16.3 -> 1.18.4
* gstreamer1.0-plugins-base 1.16.3 -> 1.18.4
* gstreamer1.0-plugins-good 1.16.3 -> 1.18.4
* gstreamer1.0-plugins-ugly 1.16.3 -> 1.18.4
* gstreamer1.0-python 1.16.3 -> 1.18.4
* gstreamer1.0-rtsp-server 1.16.3 -> 1.18.4
* gstreamer1.0-vaapi 1.16.3 -> 1.18.4
* gtk+3 3.24.22 -> 3.24.25
* gtk-doc 1.32 -> 1.33.2
* harfbuzz 2.7.2 -> 2.7.4
* hdparm 9.58 -> 9.60
* help2man 1.47.15 -> 1.48.2
* hwlatdetect 1.1 -> 1.10
* i2c-tools 4.1 -> 4.2
* icu 67.1 -> 68.2
* ifupdown 0.8.35 -> 0.8.36
* inetutils 1.9.4 -> 2.0
* init-system-helpers 1.58 -> 1.60
* iproute2 5.8.0 -> 5.11.0
* iptables 1.8.5 -> 1.8.7
* iso-codes 4.5.0 -> 4.6.0
* iw 5.8 -> 5.9
* jquery 3.5.1 -> 3.6.0
* json-glib 1.4.4 -> 1.6.2
* kbd 2.3.0 -> 2.4.0
* kea 1.7.10 -> 1.8.2
* kern-tools-native 0.2+gitX (df4390b18a...) -> 0.2+gitX (8f6aaab7f6...)
* kexec-tools 2.0.20 -> 2.0.21
* kmod 27 -> 28
* kmod-native 27 -> 28
* kmscube git (4660a7dca6...) -> git (9f63f359fa...)
* less 562 -> 563
* libaio 0.3.111 -> 0.3.112
* libarchive 3.4.3 -> 3.5.1
* libassuan 2.5.3 -> 2.5.4
* libbsd 0.10.0 -> 0.11.3
* libcap 2.43 -> 2.48
* libcap-ng 0.7.11 -> 0.8.2
* libdazzle 3.36.0 -> 3.38.0
* libdnf 0.48.0 -> 0.58.0
* libdrm 2.4.102 -> 2.4.104
* libedit 20191231-3.1 -> 20210216-3.1
* libepoxy 1.5.4 -> 1.5.5
* libevdev 1.9.1 -> 1.11.0
* libfm-extra 1.3.1 -> 1.3.2
* libgcrypt 1.8.6 -> 1.9.2
* libgloss 3.3.0 -> 4.1.0
* libgpg-error 1.39 -> 1.41
* libgudev 233 -> 234
* libhandy 0.0.13 -> 1.2.0
* libical 3.0.8 -> 3.0.9
* libinput 1.16.1 -> 1.16.4
* libjitterentropy 2.2.0 -> 3.0.1
* libjpeg-turbo 2.0.5 -> 2.0.6
* libksba 1.4.0 -> 1.5.0
* libmodulemd 2.9.4 -> 2.12.0
* libmpc 1.2.0 -> 1.2.1
* libpam 1.3.1 -> 1.5.1
* libpcap 1.9.1 -> 1.10.0
* libpcre2 10.35 -> 10.36
* libproxy 0.4.15 -> 0.4.17
* librepo 1.12.1 -> 1.13.0
* libsdl2 2.0.12 -> 2.0.14
* libsecret 0.20.3 -> 0.20.4
* libsolv 0.7.14 -> 0.7.17
* libsoup-2.4 2.70.0 -> 2.72.0
* libtirpc 1.2.6 -> 1.3.1
* libunwind 1.4.0 -> 1.5.0
* liburcu 0.12.1 -> 0.12.2
* liburi-perl 1.74 -> 5.08
* libusb1 1.0.23 -> 1.0.24
* libuv 1.39.0 -> 1.41.0
* libva 2.8.0 -> 2.10.0
* libva-initial 2.8.0 -> 2.10.0
* libva-utils 2.8.0 -> 2.10.0
* libwebp 1.1.0 -> 1.2.0
* libwpe 1.7.1 -> 1.8.0
* libx11 1.6.12 -> 1.7.0
* libxcrypt 4.4.17 -> 4.4.18
* libxcrypt-compat 4.4.17 -> 4.4.18
* libxkbcommon 0.10.0 -> 1.0.3
* libxt 1.2.0 -> 1.2.1
* lighttpd 1.4.55 -> 1.4.59
* linux-libc-headers 5.8 -> 5.10
* linux-yocto 5.4.103+gitX, 5.8.18+gitX -> 5.4.107+gitX, 5.10.25+gitX
* linux-yocto-dev 5.10-rc++gitX -> 5.12++gitX
* linux-yocto-rt 5.4.103+gitX, 5.8.18+gitX -> 5.4.107+gitX, 5.10.25+gitX
* linux-yocto-tiny 5.4.103+gitX, 5.8.18+gitX -> 5.4.107+gitX, 5.10.25+gitX
* llvm 10.0.1 -> 11.1.0
* log4cplus 2.0.5 -> 2.0.6
* logrotate 3.17.0 -> 3.18.0
* ltp 20200515 -> 20210121
* lttng-modules 2.12.3 -> 2.12.5
* lttng-tools 2.12.2 -> 2.12.3
* lttng-ust 2.12.0 -> 2.12.1
* lz4 1.9.2 -> 1.9.3
* lzip 1.21 -> 1.22
* man-db 2.9.3 -> 2.9.4
* man-pages 5.08 -> 5.10
* mc 4.8.25 -> 4.8.26
* mesa 20.1.8 -> 21.0.1
* mesa-gl 20.1.8 -> 21.0.1
* meson 0.55.1 -> 0.57.1
* mpg123 1.26.3 -> 1.26.4
* msmtp 1.8.12 -> 1.8.15
* mtools 4.0.24 -> 4.0.26
* musl 1.2.1+gitX -> 1.2.2+gitX
* nativesdk-meson 0.55.1 -> 0.57.1
* net-tools 1.60-20181103+gitX -> 2.10
* netbase 6.1 -> 6.2
* nettle 3.6 -> 3.7.1
* newlib 3.3.0 -> 4.1.0
* nfs-utils 2.5.1 -> 2.5.3
* ninja 1.10.1 -> 1.10.2
* opensbi 0.8 -> 0.9
* openssh 8.3p1 -> 8.5p1
* openssl 1.1.1j -> 1.1.1k
* opkg 0.4.3 -> 0.4.4
* orc 0.4.31 -> 0.4.32
* ovmf edk2-stable202005 -> edk2-stable202102
* pango 1.46.2 -> 1.48.2
* parted 3.3 -> 3.4
* pcmanfm 1.3.1 -> 1.3.2
* perl 5.32.0 -> 5.32.1
* piglit 1.0+gitrX (2a6a8f954d...) -> 1.0+gitrX (d4d9353b72...)
* pigz 2.4 -> 2.6
* pinentry 1.1.0 -> 1.1.1
* ppp 2.4.8 -> 2.4.9
* procps 3.3.16 -> 3.3.17
* psmisc 23.3 -> 23.4
* ptest-runner 2.4.0+gitX -> 2.4.1+gitX
* pulseaudio 13.0 -> 14.2
* puzzles 0.0+gitX (9aa7b7cdfb...) -> 0.0+gitX (84cb4c6701...)
* python3 3.8.5 -> 3.9.2
* python3-cython 0.29.21 -> 0.29.22
* python3-dbusmock 0.19 -> 0.22.0
* python3-git 3.1.7 -> 3.1.14
* python3-jinja2 2.11.2 -> 2.11.3
* python3-magic 0.4.18 -> 0.4.22
* python3-mako 1.1.3 -> 1.1.4
* python3-numpy 1.19.1 -> 1.20.1
* python3-pycairo 1.19.1 -> 1.20.0
* python3-pycryptodome 3.9.8 -> 3.10.1
* python3-pycryptodomex 3.9.8 -> 3.10.1
* python3-pyelftools 0.26 -> 0.27
* python3-pygments 2.6.1 -> 2.8.1
* python3-pygobject 3.36.1 -> 3.38.0
* python3-setuptools 49.6.0 -> 54.1.1
* python3-smmap 3.0.4 -> 4.0.0
* qemu 5.1.0 -> 5.2.0
* quota 4.05 -> 4.06
* readline 8.0 -> 8.1
* resolvconf 1.83 -> 1.87
* rng-tools 6.10 -> 6.11
* rpm 4.15.1 -> 4.16.1.2
* rt-tests 1.1 -> 1.10
* ruby 2.7.1 -> 3.0.0
* sbc 1.4 -> 1.5
* shared-mime-info 2.0 -> 2.1
* socat 1.7.3.4 -> 1.7.4.1
* sqlite3 3.33.0 -> 3.35.0
* strace 5.8 -> 5.11
* stress-ng 0.11.21 -> 0.12.05
* subversion 1.14.0 -> 1.14.1
* sudo 1.9.3 -> 1.9.6p1
* sysklogd 2.1.2 -> 2.2.2
* sysstat 12.4.0 -> 12.4.3
* systemd 246.9 -> 247.4
* systemd-boot 246.9 -> 247.4
* systemd-bootchart 233+gitX -> 234
* systemd-conf 246.9 -> 247.3
* systemtap 4.3 -> 4.4
* systemtap-native 4.3 -> 4.4
* systemtap-uprobes 4.3 -> 4.4
* sysvinit 2.97 -> 2.99
* taglib 1.11.1 -> 1.12
* tar 1.32 -> 1.34
* tcl 8.6.10 -> 8.6.11
* tiff 4.1.0 -> 4.2.0
* u-boot 2020.07 -> 2021.01
* u-boot-tools 2020.07 -> 2021.01
* usbutils 012 -> 013
* util-linux 2.36 -> 2.36.2
* util-macros 1.19.2 -> 1.19.3
* vala 0.48.9 -> 0.50.4
* vte 0.60.3 -> 0.62.2
* vulkan-headers 1.2.135.0 -> 1.2.170.0
* vulkan-loader 1.2.135.0 -> 1.2.170.0
* vulkan-tools 1.2.135.0 -> 1.2.170.0
* wayland 1.18.0 -> 1.19.0
* webkitgtk 2.28.4 -> 2.30.5
* wget 1.20.3 -> 1.21.1
* wpebackend-fdo 1.7.1 -> 1.8.0
* x264 r3011+gitX -> r3039+gitX
* xf86-video-vesa 2.4.0 -> 2.5.0
* xkbcomp 1.4.3 -> 1.4.4
* xkeyboard-config 2.30 -> 2.32
* xprop 1.2.4 -> 1.2.5
* xserver-xorg 1.20.9 -> 1.20.10


Re: [meta-gplv2] [PATCH] conf/distro: Add removal of btrfs-tools from util-linux ptest depends

Ross Burton
 

+1.

Ross

On Mon, 19 Apr 2021 at 21:47, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:

btrfs-tools has changed to LGPL-3.1 so to allow util-linux to build,
remove the dependency from its ptest package. This may regress some
ptests but keeps the gplv2 layer working.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
conf/distro/include/disable-gplv3.inc | 1 +
1 file changed, 1 insertion(+)

diff --git a/conf/distro/include/disable-gplv3.inc b/conf/distro/include/disable-gplv3.inc
index bded378..3285543 100644
--- a/conf/distro/include/disable-gplv3.inc
+++ b/conf/distro/include/disable-gplv3.inc
@@ -1,3 +1,4 @@
INCOMPATIBLE_LICENSE = '*GPLv3*'
WARN_QA_remove = 'incompatible-license'
RDEPENDS_${PN}-ptest_remove_pn-glib-2.0 = "python3-dbusmock"
+RDEPENDS_${PN}-ptest_remove_pn-util-linux = "btrfs-tools"
--
2.30.2



1641 - 1660 of 54798