Date   

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

David Babich
 

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

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


Problem installing python package from a wheel #bitbake #python

David Babich
 

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

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

Here is what I have so far for the recipe:

```

DESCRIPTION = "NVIDIA's Python Torch"

HOMEPAGE = "https://nvidia.com"

LICENSE = "BSD-3-Clause"

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

 

inherit setuptools3

 

SRC_URI = "\

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

        file://LICENSE \

"

 

COMPATIBLE_MACHINE = "jetson-tx2-devkit-tx2i"

PACKAGE_ARCH = "${MACHINE_ARCH}"

 

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

 

do_configure() {

        :

}

 

do_compile() {

        :

}

 

do_install() {

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

}

 

DEPENDS = "python3-pip-native"

```

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

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

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


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

 

 


Enhancements/Bugs closed WW47!

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

4

randy.macleod@...

2

ross@...

1

steve@...

1

akuster808@...

1

Grand Total

9

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Current high bug count owners for Yocto Project 3.5

Stephen Jolley
 

All,

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

Who

Count

ross@...

36

michael.opdenacker@...

34

david.reyna@...

22

randy.macleod@...

20

trevor.gamblin@...

16

bruce.ashfield@...

16

timothy.t.orling@...

14

JPEWhacker@...

11

sakib.sajal@...

11

richard.purdie@...

8

mhalstead@...

7

kai.kang@...

7

saul.wold@...

6

bluelightning@...

6

kiran.surendran@...

5

chee.yang.lee@...

4

hongxu.jia@...

4

jon.mason@...

3

Qi.Chen@...

3

pokylinux@...

2

pgowda.cve@...

2

mshah@...

2

alejandro@...

2

yf3yu@...

1

angolini@...

1

mark.hatle@...

1

open.source@...

1

alexandre.belloni@...

1

yi.zhao@...

1

jay.shen.teoh@...

1

limon.anibal@...

1

TicoTimo@...

1

raj.khem@...

1

john.kaldas.enpj@...

1

steve@...

1

mingli.yu@...

1

aehs29@...

1

thomas.perrot@...

1

matthewzmd@...

1

vinay.m.engg@...

1

Martin.Jansa@...

1

mostthingsweb@...

1

kexin.hao@...

1

elberger@...

1

shachar@...

1

nicolas.dechesne@...

1

yoctoproject@...

1

Grand Total

265

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 392 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.4”, “3.5, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


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

JH
 

Thanks Michael, greatly appreciate it.

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

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

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

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

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

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

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


Re: wic crash when building image with multiple partitions

Marek Belisko
 

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

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

Does it make any sense or is it just hack?

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

Hello,

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

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

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

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

Thanks and BR,

marek

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

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


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

Michael Opdenacker
 

Hi Jupiter,

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

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

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

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

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

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

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


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

JH
 

Hi,

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

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

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

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

Thank you.

Kind regards,

- JH


Re: Useradd recipe not generating /etc/passwd entries #dunfell

taylor.winning@...
 

Okay, I seem to have achieved this by adding:

ALLOW_EMPTY_${PN}="1"

To the adh-user-add recipe that everything is depending on (including the image recipe).

I'm a bit confused as to why that was such a hassle to achieve something I would have thought was a simple adding of a few users. Definitely would've appreciated a warning that the build system was attempting to add an empty package or something like that. I wouldn't think I'm on the fringe's of Yocto development here, but perhaps my use case is resulting in an 'empty package' being created via my image recipe that most other use-cases aren't triggering?

I would be very glad to hear any input despite having this resolved.

 


Useradd recipe not generating /etc/passwd entries #dunfell

taylor.winning@...
 

Hi,

I’m attempting to create a few service users for our software products. Initially I had inherited useradd in each recipe that required the user, then had a corresponding user added from within the image recipe. I know this is not ideal, however I have been unable to solve some issues I’m having so I’m hoping someone can help.

I'm on Dunfell branch.

I now have a recipe that creates two users, that all other recipes DEPENDS on. Here is the contents of that recipe (adh-user-add.bb):

 

FILESEXTRAPATHS_prepend := "${THISDIR}:"

SUMMARY = "Add adh and adhX user for other recipes"

LICENSE="CLOSED"

PV = "${ADH_ADH_SVN_REVISION}"

require require/revisions.inc

PACKAGE_ARCH = "${MACHINE_ARCH}"

 

inherit useradd

 

USERADD_PACKAGES = "${PN}"

USERADD_PARAM_${PN} = "--system --uid 420 -g adh adh; --system --uid 421 -g adhX adhX "

GROUPADD_PARAM_${PN} = "-g 420 adh; -g 421 adhX "

 

Each recipe that needs these users simply DEPENDS on it from within its own recipe. I understand that is the preferred way of doing this?

 

However, inside my image (development-image.bb) once its built, my /etc/passwd file does not contain these users at all. I have tried the following things:

 

  1. IMAGE_INSTALL_append += “ adh-user-add”
  2. DEPENDS += “ adh-user-add”
  3. RDEPENDS += “ adh-user-add”

 

Each time I get a passwd file inside of adh-user-add/recipe-sysroots and development-image/recipe-sysroots that contains both users, however the passwd file on the device is missing those users entirely.

 

My image recipe looks like this:

 

SUMMARY = "Development image"

inherit core-image extrausers

require require/revisions.inc

 

PV = "${CUBE_IMAGE_VERSION}"

PR = "${CUBE_IMAGE_REVISION}"

 

IMAGE_FSTYPES_append += "wic wic.xz"

 

WKS_FILE = "sgc30cube.wks"

IMAGE_INSTALL = "packagegroup-core-boot ${CORE_IMAGE_EXTRA_INSTALL}  "

 

IMAGE_INSTALL_append = " \

                                                 *** packages removed ***

                                                 "

 

IMAGE_FEATURES_append = " ssh-server-dropbear"

MACHINE_FEATURES_remove = "kernel26 nc screen ext2 alsa gpu touchscreen qemu-usermode"

 

DEPENDS += "adh-user-add"

IMAGE_FEATURES_append = " debug-tweaks"

I feel like I'm going crazy trying to figure this out. I wish I could figure out how the final passwd file is generated. I've looked in some logs that I've seen suggested online, but have been unable to ascertain if there are any errors occurring.

Any help would be greatly appreciated,

Thanks,

Taylor W


Re: #yocto Remove hexdump from image #yocto

Randy MacLeod
 

On 2021-11-19 4:12 a.m., lucapirozzi via lists.yoctoproject.org wrote:
Hi Joseph,
thank you for replying.
Shall I use the oe-pkgdata-util find-path this way?
oe-pkgdata-util  find-path /usr/bin/hexdump
Because I'm encountering an error
ERROR: Unable to find any package producing path /usr/bin/hexdump
So I think I am doing something wrong

Hi Luca,

I think you either need the right key/string:

$ oe-pkgdata-util find-path /bin/ls.coreutils

coreutils: /bin/ls.coreutils


or to use a wildcard and quotes:

$ oe-pkgdata-util find-path "/bin/ls*"

coreutils: /bin/ls.coreutils

kmod: /bin/lsmod.kmod



For help:

$ oe-pkgdata-util

oe-pkgdata-util: error: the following arguments are required: <subcommand>

usage: oe-pkgdata-util [-h] [-d] [-p PKGDATA_DIR] <subcommand> ...



OpenEmbedded pkgdata tool - queries the pkgdata files written out during

do_package



options:

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

-d, --debug Enable debug output

-p PKGDATA_DIR, --pkgdata-dir PKGDATA_DIR

Path to pkgdata directory (determined automatically if

not specified)



subcommands:

lookup-pkg Translate between recipe-space package names and

runtime package names

list-pkgs List packages

list-pkg-files List files within a package

lookup-recipe Find recipe producing one or more packages

package-info Show version, recipe and size information for one or

more packages

find-path Find package providing a target path

read-value Read any pkgdata value for one or more packages

glob Expand package name glob expression

Use oe-pkgdata-util <subcommand> --help to get help on a specific command



--
# Randy MacLeod
# Wind River Linux


[meta-security][PATCH 1/2] openssl-tpm-engine: fix warning for append operator combined with +=

Yi Zhao
 

Fixes:
WARNING: openssl-tpm-engine_0.5.0.bb: CFLAGS:append += is not a
recommended operator combination, please replace it.

Signed-off-by: Yi Zhao <yi.zhao@...>
---
.../openssl-tpm-engine/openssl-tpm-engine_0.5.0.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-tpm/recipes-tpm/openssl-tpm-engine/openssl-tpm-engine_0.5.0.bb b/meta-tpm/recipes-tpm/openssl-tpm-engine/openssl-tpm-engine_0.5.0.bb
index ef663eb..2b969ed 100644
--- a/meta-tpm/recipes-tpm/openssl-tpm-engine/openssl-tpm-engine_0.5.0.bb
+++ b/meta-tpm/recipes-tpm/openssl-tpm-engine/openssl-tpm-engine_0.5.0.bb
@@ -35,10 +35,10 @@ inherit autotools-brokensep pkgconfig
srk_dec_pw ?= "\\"\\\x1\\"\\"nc\\"\\"\\\x3\\"\\"nd\\"\\"\\\x1\\"\\"a\\""
srk_dec_salt ?= "\\"r\\"\\"\\\x00\\\x00\\"\\"t\\""

-CFLAGS:append += "-DSRK_DEC_PW=${srk_dec_pw} -DSRK_DEC_SALT=${srk_dec_salt}"
+CFLAGS:append = " -DSRK_DEC_PW=${srk_dec_pw} -DSRK_DEC_SALT=${srk_dec_salt}"

# Uncomment below line if using the plain srk password for development
-#CFLAGS_append += "-DTPM_SRK_PLAIN_PW"
+#CFLAGS:append = " -DTPM_SRK_PLAIN_PW"

do_configure:prepend() {
cd ${B}
--
2.25.1


[meta-security][PATCH 2/2] meta-parsec/README.md: fix for append operator combined with +=

Yi Zhao
 

Signed-off-by: Yi Zhao <yi.zhao@...>
---
meta-parsec/README.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta-parsec/README.md b/meta-parsec/README.md
index c5635d3..bb4c2b9 100644
--- a/meta-parsec/README.md
+++ b/meta-parsec/README.md
@@ -80,7 +80,7 @@ Manual testing with runqemu
This layer also contains a recipe for pasec-tool which can be used for
manual testing of the Parsec service:

- IMAGE_INSTALL:append += " parsec-tools"
+ IMAGE_INSTALL:append = " parsec-tools"

There are a series of Parsec Demo videos showing how to use parsec-tool
to test the Parsec service base functionality:
@@ -104,7 +104,7 @@ enabled. No changes required.
The Software HSM can be used for manual testing of the provider by
including it into your test image:

- IMAGE_INSTALL:append += " softhsm"
+ IMAGE_INSTALL:append = " softhsm"

Inside the running VM:
- Stop Parsec
@@ -135,7 +135,7 @@ systemctl start parsec
The IBM Software TPM service can be used for manual testing of the provider by
including it into your test image:

- IMAGE_INSTALL:append += " ibmswtpm2 tpm2-tools libtss2 libtss2-tcti-mssim"
+ IMAGE_INSTALL:append = " ibmswtpm2 tpm2-tools libtss2 libtss2-tcti-mssim"

Inside the running VM:
- Stop Parsec
--
2.25.1


Re: Private: Re: [yocto] #yocto Remove hexdump from image #yocto

Jason Andryuk
 

On Fri, Nov 19, 2021 at 4:14 AM Josef Holzmayr
<jester@...> wrote:

(re-adding list)

Am 19.11.2021 um 10:11 schrieb lucapirozzi via lists.yoctoproject.org:
Hi Joseph,

thank you for replying.

Shall I use oe-pkgdata-util find-patch this way?

oe-pkgdata-util find-path /usr/bin/hexdump

Because it gives me an error
ERROR: Unable to find any package producing path /usr/bin/hexdump
You have to use the path you found hexdump at. Check in your running
target by using "which", or inspect the image contents.
You may not be getting any result because /usr/bin/hexdump is an
alternatives symlink to
/usr/bin/hexdump.util-linux for example (util-linux-hexdump).

Regards,
Jason


Re: [meta-raspberrypi][PATCH] linux-firmware-rpidistro: add branch in SRC_URI

Andrei Gherzan
 

On Fri, 19 Nov 2021, at 10:26, Devendra Tewari wrote:

Looks good. Waiting for CI and I will merge.

---
Andrei


Re: [meta-raspberrypi][PATCH] linux-firmware-rpidistro: add branch in SRC_URI

Devendra Tewari
 

On 18 Nov 2021, at 19:17, Devendra Tewari <devendra.tewari@...> wrote:

Thanks.

Em 18 de nov. de 2021, à(s) 18:17, Martin Jansa <martin.jansa@...> escreveu:


On Thu, Nov 18, 2021 at 9:01 PM Devendra Tewari <devendra.tewari@...> wrote:
Branch master has been renamed to buster. Also setting protocol to
https as GitHub is migrating away from unencrypted git protocol

Signed-off-by: Devendra Tewari <devendra.tewari@...>
---
 .../linux-firmware-rpidistro/linux-firmware-rpidistro_git.bb    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux-firmware-rpidistro/linux-firmware-rpidistro_git.bb b/recipes-kernel/linux-firmware-rpidistro/linux-firmware-rpidistro_git.bb
index a091585..874e444 100644
--- a/recipes-kernel/linux-firmware-rpidistro/linux-firmware-rpidistro_git.bb
+++ b/recipes-kernel/linux-firmware-rpidistro/linux-firmware-rpidistro_git.bb
@@ -34,7 +34,7 @@ LIC_FILES_CHKSUM = "\
 NO_GENERIC_LICENSE[Firmware-broadcom_bcm43xx-rpidistro] = "LICENCE.broadcom_bcm43xx"
 NO_GENERIC_LICENSE[WHENCE] = "WHENCE"

-SRC_URI = "git://github.com/RPi-Distro/firmware-nonfree"
+SRC_URI = "git://github.com/RPi-Distro/firmware-nonfree;protocol=https;branch=buster"

 SRCREV = "83938f78ca2d5a0ffe0c223bb96d72ccc7b71ca5"
 PV = "20190114-1+rpt11"
--
2.33.1






Re: Private: Re: [yocto] #yocto Remove hexdump from image #yocto

Josef Holzmayr
 

(re-adding list)

Am 19.11.2021 um 10:11 schrieb lucapirozzi via lists.yoctoproject.org:
Hi Joseph,

thank you for replying.

Shall I use oe-pkgdata-util find-patch this way?

oe-pkgdata-util  find-path /usr/bin/hexdump

Because it gives me an error
ERROR: Unable to find any package producing path /usr/bin/hexdump
You have to use the path you found hexdump at. Check in your running target by using "which", or inspect the image contents.


Greetz


So I think I am doing something wrong. Maybe the folder I am launching the script from?


Re: #yocto Remove hexdump from image #yocto

lucapirozzi@...
 

Hi Joseph,

thank you for replying.

Shall I use the oe-pkgdata-util find-path this way?

oe-pkgdata-util  find-path /usr/bin/hexdump

Because I'm encountering an error
ERROR: Unable to find any package producing path /usr/bin/hexdump

So I think I am doing something wrong


Re: #yocto Remove hexdump from image #yocto

Josef Holzmayr
 

Am 19.11.2021 um 10:02 schrieb lucapirozzi via lists.yoctoproject.org:

Hi everyone,

I'm trying to remove some application, some of them packages and other being busybox parts.

I'm trying to remove hexdump from my image and I configured every busybox defconfig to have CONFIG_HEXDUMP and its REVERSE CONFIG to =n.

But I'm finding hexdump in my image filesystem nevertheless.
Check oe-pkgdata-util find-path in your build to find out which package/recipe to actually look at.


Greetz


Any help?

Thank you and Regards.

2441 - 2460 of 57789