and meta-yocto was renamed to meta-poky in one of those changes at the request of the members and community.

Related bug [6] [6] https://bugzilla.yoctoproject.org/show_bug.cgi?id=13376

If you look at the lmsensors recipe, the lmsensors-sensorsdetect [1] and lmsensors-sensorsconfconvert [2] subpackages both have perl-modules in RDEPENDS. One way to determine the ACTUAL dependencies i

BBEXTEND = “native” is a perfectly fine patch to submit to meta-python. We tend to only make those changes when needed (as in your use case) rather than universally. Please submit a patch :)

Thanks to Konrad Weihmann, we have some communication occurring with the Python pypa folks about an important change in Python packaging [1][2]. This change is defined in PEP 517 [3][4]. Essentially,

I have absolutely no need for python2, I made this abundantly clear when I created the meta-python2 layer. If you depend upon continuing support of python2 via the meta-python2 layer, this is your cal

Thank you so much for the revision. I was not clear enough in what I said earlier and we had not captured it in the wiki either. Richard and I have updated the wiki. https://www.openembedded.org/wiki/

Hi Ida! Thank you so much for the patch. Just a few things to help you along: (0) general guidelines https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines and https://www.openembedded.org/

From: Tim Orling <timothy.t.orling@...> Replace the hard-coded individual email addresses with the mailing list created for this purpose: qa-build-notification@... Signe

The key error is this: “ ERROR: Nothing PROVIDES 'core-image-sato' core-image-sato was skipped: 'package-managementtools-debug' in IMAGE_FEATURES is not a valid image feature. “ So you need to figure

#yocto

Captured notes and recent research/discovery in the bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13684 We have 49 commits since forking from patchwork-fdo. Upstream patchwork-fdo has 166 com

You don't need this as this is the default value. This has to be swig-native. When in doubt, DEPENDS should be the -native version. After this, you will be missing <winscard.h>, which comes from pcsc-

No data, but hunch that a link to the new mail address url is needed...

Does your recipe inherit pythonnative? If so, you could try switching to ‘python3native’. For example: http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-extras/recipes-connectivity/op

For both python3 built-in modules and Perl built-in modules it would be REALLY handy to have a post-build definitive list of what the provide.

Right. I remember a prior thread about you needing to update remotely. I assume this board is stuffed deep in ATLAS somewhere. (In a prior life I was a materials scientist) Are you stuck with "rocko"

I meant to say "zeus" was released in October 2019. I'm sure xilinx support was after that.

I see you are building for "rocko" and that your layer supports "sumo" and "rocko". Do you have a strong compelling reason to stay on these EOL releases? meta-xilinx has a zeus branch which was releas

Numpy is already part of oe-core: http://layers.openembedded.org/layerindex/recipe/51338/ Why not just use the existing recipe?

#yocto #python

You might also want to review the documentation on how PACKAGECONFIG is intended to be used: https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#var-PACKAGECONFIG In your recipe, each is