Hi Robert, I'm not sure, but there might be a need to add it to SRC_DISTRIBUTE_LICENSES in openembedded-core/meta/conf/licenses.conf. Quentin

as long as this requires only adding an Unlicense file to that directory, i can do that shortly. rday

On Wed, 13 May 2020, Quentin Schulz wrote: ... snip ... > If it's really widely used, maybe something to add to > openembedded-core/files/common-licenses/ ? So that you don't need > any of the

... +1 for adding Unlicense to openembedded-core's common-licenses regards;rl

Hi Robert, You can add a license to your layer by doing the following in conf/layer.conf: LICENSE_PATH += "${LAYERDIR}/licenses" and in there you put the Unlicense file named exactly the same with

colleague added a new recipe to a build, got a warning "The license listed Unlicense was not in the licenses collected for recipe python-filelock" and, sure enough, that source was released under

OK I found. Yes "opkg configure" will call /var/lib/opkg/info/*.postinst for packages marked as "unpacked" in /var/lib/opkg/status ex: Package: test-deployment-lic Version: 1.0-r0 Status: install ok

Reading recipes-devtools/run-postinsts/run-postinsts/run-postinsts and_save_postinsts_common (in rootfs.py) once more, it seems /etc/ipk-postinsts is only used if there is no package manager on the

Hi, This is a common problem. It is likely that I know which SoC supplier you are talking about and have had the exact same issues. We have managed to fix or workaround all of them. In most cases by

Hi, I am using a build environment based on the yocto project from one of the big HW suppliers in the mobile industries. They are continuously breaking the principles behind the yocto project and at

Thanks Alex, When I do a factory reset, the system detects as a first boot and the script is executed. > cat /var/log/postinstall.log Configuring test-deployment. One thing which puzzles me: the

Hi, I have a project that generates a native artifact during the target build. Both the native and target artifacts are needed for other target recipes. What's the recommended pattern for handling

Bug #9917 has been update to "Review In Progress" https://bugzilla.yoctoproject.org/show_bug.cgi?id=9917

I'm migrating a yocto project that is working on sumo to warrior, so I set my layers to be the "warrior" branches. Everything runs fine until it fails in my node project layer on "do_compile" with the

Does your recipe inherit pythonnative? If so, you could try switching to ‘python3native’. For example:

Thanks for this. I did merge it however to be clear, the above files are under LGPL, not GPL. As such, I removed this part of the commit and added a second one of my own which resolves

Hi all - I'm working with rocko trying to build a recipe with python3 that used to be build with python2 using cmake. After changing things in the build files, when I run the devshell for the recipe,

All, YP M+ or high bugs which moved to a new milestone in WW19 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 12723 mysql requires unicode and char

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 50 bug owners as of the end of WW19 of who have open medium or higher bugs and enhancements against YP 3.2. There are 120 possible work days left until the final