Merged.

I do not know if this precisely answers your question, but creating bbclass functionality to create a different type of image may be the way to go. What you are suggesting sounds similar to

Hi Nikhil, What exact steps did you take before getting this error and what build host are you using? Are you able to build core-image-minimal using oe-core/master and the default local.conf for

Hi Nikhil, $cd /tmp; wget http://xorg.freedesktop.org/releases/individual/lib/libXcursor-1.1.15.tar.bz2 works for me so it's not the upstream web server at least at this instant. Can you run this

All, YP M+ or high bugs which moved to a new milestone in WW42 are listed below: Priority Bug ID Short

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 WW42 of who have open medium or higher bugs and enhancements against YP 3.2 & 3.3. There are 8 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

Hi Stefano, Am Montag, den 19.10.2020, 18:23 +0200 schrieb Stefano Babic: my intention was a bit different I think. I actually wanted to generate the /app out of the rootfs image. But then re-use the

Signed-off-by: Ross Burton <ross.burton@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 1d41b3f..4ecd6a2

Hi Enrico, I had the same use case as you, and I could use something like part /app --source rawcopy --sourceparams="file=..." and the file points to the image I want to put on the partition. I

Hi, as I did not have much success with my question in the OR irc, let's try it here in a more verbose way. ;) Imagine I have an A+B redundant boot system, with additional bootloader and separate

Small typo in commit summary, but other than that please merge :).

Hi Robert, I'd say they either should be added to IMAGE_INSTALL one by one, or being put into a packagegroup or even use RRECOMMENDS instead of RDEPENDS. To me, it feels wrong too, if it's really not

Another question regarding recipe/coding style (based on actual examples I run across in existing code bases). In one vendor's layer, in file "lighttpd_1.4.%.bbappend", I read: RDEPENDS_${PN} += "

I feel that porting from an older Yocto release to a newer one is not the best approach. The delta can be very large, and it can be very painful and time consuming to handle it all at once. By the

Hi Steve, You have a few of the changes highlighted in: https://docs.yoctoproject.org/ref-manual/migration.html Obviously, you'd need to do all the changes between Rocko and the version you're

Hello: I am currently at Yocto release “Rocko 2.4.1” and I am looking into the effort to port to the latest Yocto release… We have been using this rocko platform revision for the last

I'm on record as strongly suggesting PACKAGECONFIG entries should be in the base recipes, there isn't a good reason I'm aware of not to do that. Obviously the system is very flexible

/var/run has been deprecated by systemd, so use /run instead, as suggested by systemd. Signed-off-by: Chen Qi <Qi.Chen@...> --- ...ervice.in-use-run-instead-of-var-run.patch | 31