Re: [linux-yocto][linux-yocto-dev standard/xlnx-soc][PATCH 1/1] usb: dwc3: use PROPERTY_ENTRY_BOOL to initialize property entries
On 4/3/20 8:41 AM, quanyang.wang wrote:
From: Quanyang Wang
According to commit 5eb5afb07853d6e9 ("usb: dwc3: use proper initializers
for property entries"), property entries should be initialized by proper
initializer macros. If not, the elements "is_inline" and "length" in
structure property_entry will be zeros, and the function
"property_entry_copy_data" will return -ENODATA failure. This will result
that dwc3_host_init fails.
Signed-off-by: Quanyang Wang
---
Hi Bruce,
This patch is for linux-yocto-dev standard/xlnx-soc only.
Hi Bruce,
Sorry, I made a mistake.
This patch should be applied to the 3 branches as below:
linux-yocto-dev standard/xlnx-soc
linux-yocto-dev v5.4/standard/xlnx-soc
linux-yocto v5.4/standard/xlnx-soc
Thanks,
Quanyang
Thanks,
Quanyang
drivers/usb/dwc3/host.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3/host.c b/drivers/usb/dwc3/host.c
index ae23a7699a85..f9b603f502f4 100644
--- a/drivers/usb/dwc3/host.c
+++ b/drivers/usb/dwc3/host.c
@@ -103,7 +103,7 @@ int dwc3_host_init(struct dwc3 *dwc)
if (device_property_read_bool(_pdev->dev,
"snps,xhci-stream-quirk"))
- props[prop_idx++].name = "xhci-stream-quirk";
+ props[prop_idx++] = PROPERTY_ENTRY_BOOL("xhci-stream-quirk");
/**
* WORKAROUND: dwc3 revisions <=3.00a have a limitation
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8575):
https://lists.yoctoproject.org/g/linux-yocto/message/8575
Mute This Topic: https://lists.yoctoproject.org/mt/72739434/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][linux-yocto-dev standard/xlnx-soc][PATCH 1/1] usb: dwc3: use PROPERTY_ENTRY_BOOL to initialize property entries
From: Quanyang Wang
According to commit 5eb5afb07853d6e9 ("usb: dwc3: use proper initializers
for property entries"), property entries should be initialized by proper
initializer macros. If not, the elements "is_inline" and "length" in
structure property_entry will be zeros, and the function
"property_entry_copy_data" will return -ENODATA failure. This will result
that dwc3_host_init fails.
Signed-off-by: Quanyang Wang
---
Hi Bruce,
This patch is for linux-yocto-dev standard/xlnx-soc only.
Thanks,
Quanyang
drivers/usb/dwc3/host.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3/host.c b/drivers/usb/dwc3/host.c
index ae23a7699a85..f9b603f502f4 100644
--- a/drivers/usb/dwc3/host.c
+++ b/drivers/usb/dwc3/host.c
@@ -103,7 +103,7 @@ int dwc3_host_init(struct dwc3 *dwc)
if (device_property_read_bool(_pdev->dev,
"snps,xhci-stream-quirk"))
- props[prop_idx++].name = "xhci-stream-quirk";
+ props[prop_idx++] = PROPERTY_ENTRY_BOOL("xhci-stream-quirk");
/**
* WORKAROUND: dwc3 revisions <=3.00a have a limitation
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8574):
https://lists.yoctoproject.org/g/linux-yocto/message/8574
Mute This Topic: https://lists.yoctoproject.org/mt/72739434/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Building dependencies in yocto for GO language project
Solved... I had to add the following to the recipe and then it works.
DEPENDS += "go-dep-native"
do_compile_prepend() {
cd ${WORKDIR}/build/src/${GO_ IMPORT}
dep init
dep ensure
}
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49039): https://lists.yoctoproject.org/g/yocto/message/49039
Mute This Topic: https://lists.yoctoproject.org/mt/72734731/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] Building dependencies in yocto for GO language project
I am trying to build a GO project using yocto using the following recipe
DESCRIPTION = "An Identity Provider for ORY Hydra over LDAP"
SECTION = "examples"
HOMEPAGE = "https://github.com/i-core/werther;
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://src/${GO_IMPORT}/LICENSE;md5=c22a4ad704abf6e006791a40249a18cb"
GO_IMPORT = "github.com/i-core/werther"
SRC_URI = "git://${GO_IMPORT}"
SRCREV = "${AUTOREV}"
FILES_${PN} += "${GOBIN_FINAL}/*"
inherit go
DEPENDS += "go-dep"
*But I'm running into this error*
ERROR: werther-1.1.1-r0 do_compile: Function failed: do_compile (log file is
located at
/tmp/tala/tmp/work/cortexa9-neon-tala-linux-gnueabi/werther/1.1.1-r0/temp/log.do_compile.10723)
ERROR: Logfile of failure stored in:
/tmp/tala/tmp/work/cortexa9-neon-tala-linux-gnueabi/werther/1.1.1-r0/temp/log.do_compile.10723
Log data follows:
| DEBUG: Executing shell function do_compile
| src/github.com/i-core/werther/internal/ldapclient/ldapclient.go:20:2: cannot
find package "github.com/coocood/freecache" in any of:
|
/tmp/tala/tmp/work/cortexa9-neon-tala-linux-gnueabi/werther/1.1.1-r0/recipe-sysroot/usr/lib/go/src/github.com/coocood/freecache
(from $GOROOT)
|
/tmp/tala/tmp/work/cortexa9-neon-tala-linux-gnueabi/werther/1.1.1-r0/build/src/github.com/coocood/freecache
(from $GOPATH)
"github.com/coocood/freecache" is used by the project I am trying to build.
There are other dependencies which are also not found (I have omitted them from
the above error message).
Basically my question is how I can I resolve these dependencies. I dont think I
need to create and put separate recipes for all these go packages.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49038): https://lists.yoctoproject.org/g/yocto/message/49038
Mute This Topic: https://lists.yoctoproject.org/mt/72734731/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto][meta-spdxscanner][PATCH V2] Remove redundant code.
On 4/2/20 11:45 AM, Li, Xiaoming wrote:
FOLDER_ID has already been assigned a defalut value "1", so there is no
need add 'or "1"' here.
Signed-off-by: Li Xiaoming
---
classes/fossology-rest.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/classes/fossology-rest.bbclass b/classes/fossology-rest.bbclass
index 5c5ef70..69f4998 100644
--- a/classes/fossology-rest.bbclass
+++ b/classes/fossology-rest.bbclass
@@ -230,7 +230,7 @@ def get_folder_id(d):
folder_name = d.getVar('FOLDER_NAME')
folder_id = create_folder(d, folder_name)
else:
-folder_id = (d.getVar('FOLDER_ID', True) or "1")
+folder_id = d.getVar('FOLDER_ID', False)
You probably shouldn't be disabling variable expansion here (i.e.
passing False as the second argument)?
bb.note("Folder Id = " + str(folder_id))
return str(folder_id)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49037): https://lists.yoctoproject.org/g/yocto/message/49037
Mute This Topic: https://lists.yoctoproject.org/mt/72720682/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] apt-get destroying itself when trying to install package #apt #yocto
Thank you for your quick clarifications. Sadly we are limited by our hardware to use Yocto for now. I consider this thread closed. Thanks again, Stefan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49036): https://lists.yoctoproject.org/g/yocto/message/49036 Mute This Topic: https://lists.yoctoproject.org/mt/72720785/21656 Mute #yocto: https://lists.yoctoproject.org/mk?hashtag=yocto=6691583 Mute #apt: https://lists.yoctoproject.org/mk?hashtag=apt=6691583 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] initramfs with mdev: No match for argument: busybox-mdev
I am new to yocto. I have read some messages on this forum which suggest ways
to build an image with initramfs and mdev.
So far I have implemented all advises but I am getting this message:
>
>
>
> ERROR: image-argus-tiny-initramfs-1.0-r0 do_rootfs: Could not invoke dnf.
> Command
> '/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/recipe-sysroot-native/usr/bin/dnf
> -v --rpmverbosity=info -y -c
> /home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/rootfs/etc/dnf/dnf.conf
> --setopt=reposdir=/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/rootfs/etc/yum.repos.d
> --installroot=/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/rootfs
> --setopt=logdir=/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/temp
> --repofrompath=oe-repo,/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/oe-rootfs-repo
> --nogpgcheck install base-passwd busybox busybox-mdev dropbear
> initramfs-live-boot-tiny packagegroup-core-boot run-postinsts' returned 1:
>
>
>
>
> DNF version: 4.1.0
>
>
>
> cachedir:
> /home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/rootfs/var/cache/dnf
>
>
>
>
> Added oe-repo repo from
> /home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/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 Thu 02 Apr 2020 09:20:31 AM UTC.
>
>
>
> Last metadata expiration check: 0:00:01 ago on Thu 02 Apr 2020 09:20:36 AM
> UTC.
>
>
>
> No module defaults found
>
>
>
> No match for argument: busybox-mdev
>
>
I have added an mdev include fragment as follows:
>
>
> CONFIG_MDEV=y
> CONFIG_FEATURE_MDEV_LOAD_FIRMWARE=y
> PACKAGES =+ "${PN}-mdev"
> INITSCRIPT_PACKAGES = "${PN}-httpd ${PN}-syslog ${PN}-udhcpd ${PN}-mdev
> ${PN}-hwclock"
> INITSCRIPT_NAME_${PN}-mdev = "mdev"
> INITSCRIPT_PARAMS_${PN}-mdev = "start 04 S ."
> CONFFILES_${PN}-mdev = "${sysconfdir}/mdev.conf"
>
I also implemented a receipt for our image as follows:
>
> VIRTUAL-RUNTIME_dev_manager = " busybox-mdev "
> PACKAGE_INSTALL = "initramfs-live-boot-tiny packagegroup-core-boot
> dropbear ${VIRTUAL-RUNTIME_base-utils} ${VIRTUAL-RUNTIME_dev_manager}
> base-passwd ${ROOTFS_BOOTSTRAP_INSTALL}"
> ...
>
Any idea what I might be missing here?
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49035): https://lists.yoctoproject.org/g/yocto/message/49035
Mute This Topic: https://lists.yoctoproject.org/mt/72721355/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] initramfs with busybox: No match for argument: busybox-mdev
>
>
>
> I have read some messages on this forum which suggest way to build an
> image with initramfs and mdev.
> So far I have implemented all advises but I am getting this message:
>
>
>
>
>
> ERROR: image-argus-tiny-initramfs-1.0-r0 do_rootfs: Could not invoke dnf.
> Command
> '/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/recipe-sysroot-native/usr/bin/dnf
> -v --rpmverbosity=info -y -c
> /home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/rootfs/etc/dnf/dnf.conf
> --setopt=reposdir=/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/rootfs/etc/yum.repos.d
> --installroot=/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/rootfs
> --setopt=logdir=/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/temp
> --repofrompath=oe-repo,/home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/oe-rootfs-repo
> --nogpgcheck install base-passwd busybox busybox-mdev dropbear
> initramfs-live-boot-tiny packagegroup-core-boot run-postinsts' returned 1:
>
>
>
>
> DNF version: 4.1.0
>
>
>
> cachedir:
> /home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/1.0-r0/rootfs/var/cache/dnf
>
>
>
>
> Added oe-repo repo from
> /home/ubuntu/yocto_warrior/argus-build/tmp/work/raspberrypi3-poky-linux-gnueabi/image-argus-tiny-initramfs/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 Thu 02 Apr 2020 09:20:31 AM UTC.
>
>
>
> Last metadata expiration check: 0:00:01 ago on Thu 02 Apr 2020 09:20:36 AM
> UTC.
>
>
>
> No module defaults found
>
>
>
> *No match for argument: busybox-mdev*
>
>
I have added an mdev include fragment as follows:
>
>
> CONFIG_MDEV=y
> CONFIG_FEATURE_MDEV_LOAD_FIRMWARE=y
> PACKAGES =+ "${PN}-mdev"
> INITSCRIPT_PACKAGES = "${PN}-httpd ${PN}-syslog ${PN}-udhcpd ${PN}-mdev
> ${PN}-hwclock"
> INITSCRIPT_NAME_${PN}-mdev = "mdev"
> INITSCRIPT_PARAMS_${PN}-mdev = "start 04 S ."
> CONFFILES_${PN}-mdev = "${sysconfdir}/mdev.conf"
>
I also implemented a receipt for our image as follows:
>
> VIRTUAL-RUNTIME_dev_manager = " *busybox-mdev* "
> PACKAGE_INSTALL = "initramfs-live-boot-tiny packagegroup-core-boot
> dropbear ${VIRTUAL-RUNTIME_base-utils} ${VIRTUAL-RUNTIME_dev_manager}
> base-passwd ${ROOTFS_BOOTSTRAP_INSTALL}"
> ...
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49034): https://lists.yoctoproject.org/g/yocto/message/49034
Mute This Topic: https://lists.yoctoproject.org/mt/72721338/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] apt-get destroying itself when trying to install package #apt #yocto
Howdy! On Thu, Apr 02, 2020 at 02:31:44AM -0700, stefan.wennin...@evopro-ag.de wrote: > So basically our problem is trying to install .deb packages meant for > debian-apt with yocto-apt? > I take it we can only install the .deb packages built by bitbake > (deploy/deb/*)? Exactly. > Would it be possible to install the debian-apt on our system (outside of > yocto) and then use the debian.org packages? Nope. Whats the reason of using Yocto anyways if you are then jumping through all kinds of hoops to just make it behave like a Debian? If you want a Debian, you should probably be using a Debian :) Having said that, there are buliding tools for ingesting the debian repositories and spitting out an image, like Linutronix' ELBE or the ISAR project. Maybe thats what fits your needs? Greetz > > Thanks for pointing us towards that package management whitepaper, I am sure > it will help us properly setup packet management of our yocto-built .deb > packages. > > Stefan > -- ——— Josef Holzmayr Software Developer Embedded Systems Tel: +49 8444 9204-48 Fax: +49 8444 9204-50 R-S-I Elektrotechnik GmbH & Co. KG Woelkestrasse 11 D-85301 Schweitenkirchen www.rsi-elektrotechnik.de ——— Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393 Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg Ust-IdNr: DE 128592548 _ Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363 Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg USt-IdNr.: DE 128592548 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49033): https://lists.yoctoproject.org/g/yocto/message/49033 Mute This Topic: https://lists.yoctoproject.org/mt/72720785/21656 Mute #yocto: https://lists.yoctoproject.org/mk?hashtag=yocto=6691583 Mute #apt: https://lists.yoctoproject.org/mk?hashtag=apt=6691583 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] apt-get destroying itself when trying to install package #apt #yocto
So basically our problem is trying to install .deb packages meant for debian-apt with yocto-apt? I take it we can only install the .deb packages built by bitbake (deploy/deb/*)? Would it be possible to install the debian-apt on our system (outside of yocto) and then use the debian.org packages? Thanks for pointing us towards that package management whitepaper, I am sure it will help us properly setup packet management of our yocto-built .deb packages. Stefan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49032): https://lists.yoctoproject.org/g/yocto/message/49032 Mute This Topic: https://lists.yoctoproject.org/mt/72720785/21656 Mute #yocto: https://lists.yoctoproject.org/mk?hashtag=yocto=6691583 Mute #apt: https://lists.yoctoproject.org/mk?hashtag=apt=6691583 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] apt-get destroying itself when trying to install package #apt #yocto
Long story short: It does not work like this. Just because the tool has the same name and the packages have the same suffix, they are basically not related. You cannot use a debian package repository for your Yocto based build. Think about randomly injecting SLES packages into a Fedora. Its both RPMs too, right? But also won't work. Same reasons. If you need more information, have a look at https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/package-manager-white-paper.pdf Greetz On Thu, Apr 02, 2020 at 02:08:40AM -0700, stefan.wennin...@evopro-ag.de wrote: > Hi, > We are trying to install packages on our arm64 architecture directly from > debian.org. > Our sources.list contains "deb [ arch=arm64 ] http://ftp.de.debian.org/debian > buster main". > > 1. When executing apt-get update we get the following output: > > > > root@imx8mq-var-dart:~# apt-get update > > Get:1 http://ftp.de.debian.org/debian buster InRelease [122 kB] > > Ign:1 http://ftp.de.debian.org/debian buster InRelease > > Get:2 http://ftp.de.debian.org/debian buster/main arm64 Packages [7737 kB] > > > > Fetched 7858 kB in 5s (1424 kB/s) > > Reading package lists... Done > > W: GPG error: http://ftp.de.debian.org/debian buster InRelease: Unknown > > error executing apt-key > > W: The repository 'http://ftp.de.debian.org/debian buster InRelease' is > > not signed. > > N: Data from such a repository can't be authenticated and is therefore > > potentially dangerous to use. > > N: See apt-secure(8) manpage for repository creation and user > > configuration details. > > E: Failed to fetch / > > E: Some index files failed to download. They have been ignored, or old > > ones used instead. > > > > We did not worry about the missing gpg authentification since we were able to > apt-cache search this source successfully. > > 2. When we tried to apt-get install python3-psutil we were promted with a > large list of mainly perl related packages that were about to be removed: > > > > > 12 upgraded, 66 newly installed, 531 to remove and 212 not upgraded > > [complete output in attachments.] > Allowing these changes to be made led to dpkg trying to overwrite files that > are also in other packages. This caused the command to fail. > > 3. We then tried to pass the "--force-overwrite" option to dpkg with the > command: > > > > > > sudo apt-get -o Dpkg::Options::="--force-overwrite" install python3-psutil > > This command told us there were unmet dependencies: > > > > > The following packages have unmet dependencies: > > libc6-dev : Depends: libc6 (= 2.28-10) but 2.27-r0 is to be installed > > Depends: libc-dev-bin (= 2.28-10) but it is not going to be installed > > Depends: linux-libc-dev but it is not going to be installed > > python3-psutil : Depends: python3 (< 3.8) > > Depends: python3 (>= 3.7~) > > Depends: python3:any > > E: Unmet dependencies. Try 'apt-get -f install' with no packages (or > > specify a solution). > > > > [complete output in attachments] > > 4. We followed the suggestion and ran apt-get -f install. > [complete output in attachments] > That led to dpkg trying to unpack "libc6" but failing because /sbin/ldconfig > is not present. > We confirmed that /sbin/ldconfig is in place and an executable on a fresh > image. > > We have tried to install different packages and to use different orders of > commands, but ultimately we always end up with ldconfig being deleted and > dpkg failing because of that. > Our best guess it that the way apt-get is set up in our image is faulty. > > Relevant Yocto info: > > > > Version: Yocto sumo 2.5 > > Image: fsl-image-qt5 > > IMAGE_INSTALL += " apt " > > We have PACKAGE_CLASSES = "package_deb" and > > PACKAGE_FEED_URIS="http://:5678" in our local.conf. However we > > deleted the sources.list entries created by this. > > Is this a known issue? Are we missing an important configuration for apt > within Yocto? > Is there another way to install and setup apt-get in our image that does not > include Yocto? > > Thanks, > Stefan > root@imx8mq-var-dart:~# apt-get install python3-psutil > Reading package lists... Done > Building dependency tree... Done > The following additional packages will be installed: > adduser apt apt-utils debconf debconf-i18n debian-archive-keyring dh-python > gcc-8-base gpgv libapt-inst2.0 libapt-pkg5.0 libaudit-common libaudit1 > libbz2-1.0 libc-dev-bin libc6 libc6-dev > libcap-ng0 libdb5.3 libexpat1 libexpat1-dev libgcc1 libgcrypt20 > libgdbm-compat4 libgdbm6 libgmp-dev libgmp10 libgmpxx4ldbl libgnutls30 > libgpm2 libhogweed4 libidn2-0 liblocale-gettext-perl > liblz4-1 libmpdec2 libncursesw6 libnettle6 libp11-kit0 libpam-modules > libpam-modules-bin libpam0g libpcre3 libperl5.28 libpython3-dev > libpython3-stdlib libpython3.7 libpython3.7-dev > libpython3.7-minimal libpython3.7-stdlib libseccomp2 libselinux1 > libsemanage-common libsemanage1 libsepol1 libssl1.1 libtasn1-6 > libtext-charwidth-perl libtext-iconv-perl
[yocto] [meta-selinux][PATCH] selinux.bbclass: remove True option in getVar()
The getVar() defaults to expanding by default, thus remove the True
option from all getVar() calls.
Signed-off-by: Yi Zhao
---
classes/selinux.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/classes/selinux.bbclass b/classes/selinux.bbclass
index fb0df27..13256d5 100644
--- a/classes/selinux.bbclass
+++ b/classes/selinux.bbclass
@@ -2,8 +2,8 @@ def target_selinux(d, truevar = 'selinux', falsevar = ''):
if not bb.utils.contains("DISTRO_FEATURES", "selinux", True, False, d):
return falsevar
-pn = d.getVar("PN", True)
-type = pn.replace(d.getVar("BPN", True), "")
+pn = d.getVar("PN")
+type = pn.replace(d.getVar("BPN"), "")
if type in ("-native", "nativesdk-", "-cross", "-crosssdk"):
return falsevar
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49030): https://lists.yoctoproject.org/g/yocto/message/49030
Mute This Topic: https://lists.yoctoproject.org/mt/72720803/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] apt-get destroying itself when trying to install package #apt #yocto
Hi, We are trying to install packages on our arm64 architecture directly from debian.org. Our sources.list contains "deb [ arch=arm64 ] http://ftp.de.debian.org/debian buster main". 1. When executing apt-get update we get the following output: > > root@imx8mq-var-dart:~# apt-get update > Get:1 http://ftp.de.debian.org/debian buster InRelease [122 kB] > Ign:1 http://ftp.de.debian.org/debian buster InRelease > Get:2 http://ftp.de.debian.org/debian buster/main arm64 Packages [7737 kB] > > Fetched 7858 kB in 5s (1424 kB/s) > Reading package lists... Done > W: GPG error: http://ftp.de.debian.org/debian buster InRelease: Unknown > error executing apt-key > W: The repository 'http://ftp.de.debian.org/debian buster InRelease' is > not signed. > N: Data from such a repository can't be authenticated and is therefore > potentially dangerous to use. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > E: Failed to fetch / > E: Some index files failed to download. They have been ignored, or old > ones used instead. > We did not worry about the missing gpg authentification since we were able to apt-cache search this source successfully. 2. When we tried to apt-get install python3-psutil we were promted with a large list of mainly perl related packages that were about to be removed: > > 12 upgraded, 66 newly installed, 531 to remove and 212 not upgraded [complete output in attachments.] Allowing these changes to be made led to dpkg trying to overwrite files that are also in other packages. This caused the command to fail. 3. We then tried to pass the "--force-overwrite" option to dpkg with the command: > > > sudo apt-get -o Dpkg::Options::="--force-overwrite" install python3-psutil This command told us there were unmet dependencies: > > The following packages have unmet dependencies: > libc6-dev : Depends: libc6 (= 2.28-10) but 2.27-r0 is to be installed > Depends: libc-dev-bin (= 2.28-10) but it is not going to be installed > Depends: linux-libc-dev but it is not going to be installed > python3-psutil : Depends: python3 (< 3.8) > Depends: python3 (>= 3.7~) > Depends: python3:any > E: Unmet dependencies. Try 'apt-get -f install' with no packages (or > specify a solution). > [complete output in attachments] 4. We followed the suggestion and ran apt-get -f install. [complete output in attachments] That led to dpkg trying to unpack "libc6" but failing because /sbin/ldconfig is not present. We confirmed that /sbin/ldconfig is in place and an executable on a fresh image. We have tried to install different packages and to use different orders of commands, but ultimately we always end up with ldconfig being deleted and dpkg failing because of that. Our best guess it that the way apt-get is set up in our image is faulty. Relevant Yocto info: > > Version: Yocto sumo 2.5 > Image: fsl-image-qt5 > IMAGE_INSTALL += " apt " > We have PACKAGE_CLASSES = "package_deb" and > PACKAGE_FEED_URIS="http://:5678" in our local.conf. However we > deleted the sources.list entries created by this. Is this a known issue? Are we missing an important configuration for apt within Yocto? Is there another way to install and setup apt-get in our image that does not include Yocto? Thanks, Stefan root@imx8mq-var-dart:~# apt-get install python3-psutil Reading package lists... Done Building dependency tree... Done The following additional packages will be installed: adduser apt apt-utils debconf debconf-i18n debian-archive-keyring dh-python gcc-8-base gpgv libapt-inst2.0 libapt-pkg5.0 libaudit-common libaudit1 libbz2-1.0 libc-dev-bin libc6 libc6-dev libcap-ng0 libdb5.3 libexpat1 libexpat1-dev libgcc1 libgcrypt20 libgdbm-compat4 libgdbm6 libgmp-dev libgmp10 libgmpxx4ldbl libgnutls30 libgpm2 libhogweed4 libidn2-0 liblocale-gettext-perl liblz4-1 libmpdec2 libncursesw6 libnettle6 libp11-kit0 libpam-modules libpam-modules-bin libpam0g libpcre3 libperl5.28 libpython3-dev libpython3-stdlib libpython3.7 libpython3.7-dev libpython3.7-minimal libpython3.7-stdlib libseccomp2 libselinux1 libsemanage-common libsemanage1 libsepol1 libssl1.1 libtasn1-6 libtext-charwidth-perl libtext-iconv-perl libtext-wrapi18n-perl libtinfo6 libzstd1 linux-libc-dev mime-support passwd perl perl-base perl-modules-5.28 python3 python3-dev python3-distutils python3-lib2to3 python3-minimal python3.7 python3.7-dev python3.7-minimal xz-utils zlib1g Suggested packages: apt-doc aptitude | synaptic | wajig dpkg-dev gnupg | gnupg2 | gnupg1 powermgmt-base debconf-doc debconf-utils whiptail | dialog libterm-readline-gnu-perl libgtk3-perl libnet-ldap-perl debconf-kde-helper libdpkg-perl gnupg glibc-doc libc-l10n locales manpages-dev rng-tools gdbm-l10n gmp-doc libgmp10-doc libmpfr-dev gnutls-bin gpm libpam-doc sensible-utils perl-doc libterm-readline-gnu-perl | libterm-readline-perl-perl libb-debug-perl liblocale-codes-perl python3-doc python3-tk python3-venv python-psutil-doc python3.7-venv
[yocto][meta-spdxscanner][PATCH V2] Remove redundant code.
FOLDER_ID has already been assigned a defalut value "1", so there is no
need add 'or "1"' here.
Signed-off-by: Li Xiaoming
---
classes/fossology-rest.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/classes/fossology-rest.bbclass b/classes/fossology-rest.bbclass
index 5c5ef70..69f4998 100644
--- a/classes/fossology-rest.bbclass
+++ b/classes/fossology-rest.bbclass
@@ -230,7 +230,7 @@ def get_folder_id(d):
folder_name = d.getVar('FOLDER_NAME')
folder_id = create_folder(d, folder_name)
else:
-folder_id = (d.getVar('FOLDER_ID', True) or "1")
+folder_id = d.getVar('FOLDER_ID', False)
bb.note("Folder Id = " + str(folder_id))
return str(folder_id)
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49028): https://lists.yoctoproject.org/g/yocto/message/49028
Mute This Topic: https://lists.yoctoproject.org/mt/72720682/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Files get sporadically lost for native packages
To answer your others questions... see below
On 02.04.20 05:42, Randy MacLeod wrote:
On 2020-03-28 8:26 a.m., Konrad Weihmann wrote:
Hi,
I'm facing the following error message sporadically on all branches I
tried so far (master, zeus, warrior and thud)
The stack trace of python calls that resulted in this
exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function:
0001:
*** 0002:extend_recipe_sysroot(d)
0003:
File: '/build/poky/meta/classes/staging.bbclass', lineno: 551,
function: extend_recipe_sysroot
0547: dest = newmanifest[l]
0548: if l.endswith("/"):
0549: staging_copydir(l, targetdir,
dest, seendirs)
0550: continue
*** 0551: staging_copyfile(l, targetdir, dest,
postinsts, seendirs)
0552:
0553: bb.note("Installed into sysroot: %s" % str(msg_adding))
0554: bb.note("Skipping as already exists in sysroot: %s" %
str(msg_exists))
0555:
File: '/build/poky/meta/classes/staging.bbclass', lineno: 152,
function: staging_copyfile
0148: os.symlink(linkto, dest)
0149: #bb.warn(c)
0150: else:
0151: try:
*** 0152: os.link(c, dest)
0153: except OSError as err:
0154: if err.errno == errno.EXDEV:
0155: bb.utils.copyfile(c, dest)
0156: else:
Exception: FileNotFoundError: [Errno 2] No such file or directory:
'/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc'
->
'/build/poky/build/tmp/work/qemux86_64-mine-linux/core-image-minimal-mine/1.0-r0/recipe-sysroot-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc'
I already had a look at the manifest
cat manifest-x86_64-python3-msgcheck-native.populate_sysroot
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__init__.py
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/po.py
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/msgcheck.py
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/po.cpython-37.pyc
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/msgcheck.cpython-37.pyc
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/dependency_links.txt
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/requires.txt
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/top_level.txt
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/SOURCES.txt
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/PKG-INFO
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/entry_points.txt
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/bin/msgcheck
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/sysroot-providers/python3-msgcheck-native
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/sysroot-providers/
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/share/
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/bin/
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/
which states the file should be there, but when
Re: [yocto] Files get sporadically lost for native packages
HI,
sorry I didn't specify it further.
To me it seems to be a corner case scenario.
This happens when doing a from scratch build with a lot on native python
libraries (as it is setup in a test distribution I'm working on).
Roughly it pulls in ~100 native python site packages.
The setup where I almost every time can reproduce the issue
- Ubuntu 16.04 or 18.04 container
- 2 VCPUs (can't say what it actually is)
- 14GB of hard disk (I guess it's some virtual storage)
- 12GB of RAM
-> as offered by GitHub's Actions Azure interface
The setup where it occasionally happens
- Ubuntu 19.04/19.10
- 8 cores i7-6th gen
- 16GB Ram
- some Samsung-SSD with more than enough space
The setup where it never happened so far
- Ubuntu 18.04
- 48 core threadripper
- lots of RAM and SSD
and
- Debian 9
- 24 core XEN guest
- >80GB of RAM
- HDD doesn't matter as it was a ramdisk only build
This doesn't happen (afaik) on differential builds when the initial one
is good (same for sstate cache backed builds).
I just wanted to know if somebody ever encountered the same issue.
As the nature of this issue is hard to catch, I'm open to ideas...
What currently works for me is to remove all python cache files before
they are packaged - at least none of my recent build failed so far.
Any ideas how to tackle this problem, any suggestions?
Best
Konrad
On 02.04.20 05:42, Randy MacLeod wrote:
On 2020-03-28 8:26 a.m., Konrad Weihmann wrote:
Hi,
I'm facing the following error message sporadically on all branches I
tried so far (master, zeus, warrior and thud)
The stack trace of python calls that resulted in this
exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function:
0001:
*** 0002:extend_recipe_sysroot(d)
0003:
File: '/build/poky/meta/classes/staging.bbclass', lineno: 551,
function: extend_recipe_sysroot
0547: dest = newmanifest[l]
0548: if l.endswith("/"):
0549: staging_copydir(l, targetdir,
dest, seendirs)
0550: continue
*** 0551: staging_copyfile(l, targetdir, dest,
postinsts, seendirs)
0552:
0553: bb.note("Installed into sysroot: %s" % str(msg_adding))
0554: bb.note("Skipping as already exists in sysroot: %s" %
str(msg_exists))
0555:
File: '/build/poky/meta/classes/staging.bbclass', lineno: 152,
function: staging_copyfile
0148: os.symlink(linkto, dest)
0149: #bb.warn(c)
0150: else:
0151: try:
*** 0152: os.link(c, dest)
0153: except OSError as err:
0154: if err.errno == errno.EXDEV:
0155: bb.utils.copyfile(c, dest)
0156: else:
Exception: FileNotFoundError: [Errno 2] No such file or directory:
'/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc'
->
'/build/poky/build/tmp/work/qemux86_64-mine-linux/core-image-minimal-mine/1.0-r0/recipe-sysroot-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc'
I already had a look at the manifest
cat manifest-x86_64-python3-msgcheck-native.populate_sysroot
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__init__.py
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/po.py
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/msgcheck.py
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/po.cpython-37.pyc
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/msgcheck.cpython-37.pyc
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/dependency_links.txt
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/requires.txt
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/top_level.txt
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/SOURCES.txt
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/PKG-INFO
[yocto] post-install - how to "reset" an image
Hi, Newbie here. I've been handed a PCB with a Yocto image running on it. I'm reading up on Yocto to get a better understanding but in the meantime I would appreciate help with a, hopefully, quick question. I know the image has post-install actions (that talk to other peripherals) and I'm assuming there is flag somewhere that I can reset to make the post-install actions run again? My understanding is, the long way round would be to get a build host and build the image again. I'm currently waiting for a build host to be made available so I can try this out. I'm hoping for a quick resolution in the meantime. Thanks, Rob -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49024): https://lists.yoctoproject.org/g/yocto/message/49024 Mute This Topic: https://lists.yoctoproject.org/mt/72720185/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Using CROPS inside Kubernetes
Hi, Currently we have VMs that are created on demand and are used for build of versions of our distribution by Yocto. We want to use docker images (based on CROPS) inside Kubernetes. I found out that that buildbot supports Kubernetes (http://docs.buildbot.net/current/relnotes/1.x.html?highlight=kubernetes#features). But it isn't clear how to use it for building distribution by Yocoto. Is anyone try to do such configuration? We want to use OpenShift (Kubernetes), with full build system will be configured inside so any information will be useful :-) Thanks, Assaf Katz -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49023): https://lists.yoctoproject.org/g/yocto/message/49023 Mute This Topic: https://lists.yoctoproject.org/mt/72719618/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-selinux][PATCH] layer.conf: update LAYERSERIES_COMPAT for dunfell
Signed-off-by: Yi Zhao --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index cdee27a..da24359 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -23,7 +23,7 @@ BBFILE_PRIORITY_selinux = "5" # cause compatibility issues with other layers LAYERVERSION_selinux = "1" -LAYERSERIES_COMPAT_selinux = "zeus" +LAYERSERIES_COMPAT_selinux = "dunfell" LAYERDEPENDS_selinux = " \ core \ -- 2.17.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49022): https://lists.yoctoproject.org/g/yocto/message/49022 Mute This Topic: https://lists.yoctoproject.org/mt/72719344/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
