Hi again Darcy, I haven't managed to get such information yet, so I opened a bug to make sure I get an answer by Thursday, when we have our bug triage meeting. Here's the bug:

Hi Jared, That's not what I understand from the manual. From https://docs.yoctoproject.org/dev-manual/common-tasks.html#post-installation-scripts-and-read-only-root-filesystem, I understand that the

Hi Darcy, IANTM (I Am Not The Maintainers!), but I know that the old override syntax will be supported in the maintained releases as long as they are supported: * Dunfell 3.1, Long Term Support

Hi, Does anyone know how long (or how many releases) that the old override syntax will still be supported? (Like a deprecation EOL cycle). A corollary question: How far back in old releases

https://www.yoctoproject.org/docs/3.1.3/ref-manual/ref-manual.html#migration-2.1-miscellaneous-changes IMAGE_FEATURES="debug-tweaks read-only-rootfs" according to the manual having read-only-rootfs

Current Dev Position: YP 3.4 M3 Next Deadline: 23rd Aug. 2021 YP 3.4 M3 build (Feature Freeze) Next Team Meetings: Bug Triage meeting Thursday Aug. 12th at 7:30am PDT

All, YP M+ or high bugs which moved to a new milestone in WW32 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 12090 bitbake resident server reconnect

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.purdie@... 13 michael.opdenacker@... 2 Grand Total 15 Thanks, Stephen K.

Hi, Please correct me, but I think the system environment set up in Yocto Linux may not be the same as other distributions. I have a shell script to set up export PATH and LD_LIBRARY_PATH, I want to

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

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

Thanks for your great help. A native recipe is what I needed with data in it only. So my native recipe copies files into ${D}${datadir}/${PN}. Then my image build uses DEPENDS= to bring in the

Greetings, I'm trying to play an Ogg/Vorbis sample from an image I generated with Poky (master) and meta-oe (master), by adding "ogg123" and "alsa-utils" (for testing purposes) to

It is clear that the build system cannot find anything that is providing 'python-hello' recipe. Which means it parsed all layers in bblayers.conf and it didn't find any python-hello_*.bb file (the _*

Hello everyone, SO i ve been following this tutorial to be able to execute hello world on the raspberry pi, but i tried so much and still not working, please any help? e I followed the tutorial from

This fixes a bug in libselinux that gets triggered by loading another policy at runtime. Before this patch, the userspace class cache was not flushed when a new policy was loaded. This led to

Howdy! Am 07.08.2021 um 02:25 schrieb John Klug: From first glance, I'd guess that the approach is just not correct. If that thing to be fetched also needs to go *into* the image: make it a recipe on

Howdy! Am 08.08.2021 um 16:11 schrieb chiefsleepyeye@...: http://layers.openembedded.org respectively for you http://layers.openembedded.org/layerindex/branch/master/recipes/?q=hotplug

YP AB Intermittent failures meeting =================================== Aug 5, 2021, 9 AM ET https://windriver.zoom.us/j/3696693975 Attendees: Tony, Richard, Trevor, Randy,

I'm new to yocto so forgive me if this has been answered before. I searched a number of resources and wasn't able to find an answer. I've been able to install yocto and make modifications to the