Hi, Good! Just a hint that you might want to set SDK_VERSION to the same. Cheers, -Mikko

Did you include the bbclass? Well I have in distro config: require classes/distroversion.bbclass which has a single python function def get_distro_version(d, dirty=True, abbrev=None): which basically

Hi, I would also add --always and --dirty to be sure non-tagged clones of repo work and builds with local modifications get marked as such. DISTRO_VERSION := "${@my_distro_version(d)}" That should do

Hi, util-linux is a meta package. Install the needed util-linux utilities separately, e.g. util-linux-mount, util-linux-umount. Also ptest you can build as distro feature if you don't install ptest pa

Hi I set INCOMPATIBLE_LICENSE_append = " GPLv3 GPLv3+ LGPLv3 LGPLv3+" but then allow compiling several recipes with those licenses as long as they don't end up on images and in the product. For exampl

Hi, This is a common problem. I run to this almost weekly basis doing a lot yocto compiles on my developer machine. Solution for me is to manually check before compiling that I still have 100's gigaby

Hi, Please don't include CVE twice in the variable name, that's was annoying and just got used to the CVE_CHECK_WHITELIST one. CVE_CHECK_IGNORE would do. Cheers, -Mikko

From: Armin Kuster <akuster808@...> Include example send-email Signed-off-by: Armin Kuster <akuster808@...> Signed-off-by: Joe MacDonald <joe@...> (cherry picked from commit 48038

Hi, Multiple ways to fix this. One is to switch to using dunfell branches for the BSP SW stack, if they are available. Alternatively you can use the old zeus based BSP SW stack but for that you need t

#imx6 #yocto #dunfell #swupdtae #libubootenv

Hi, FWIW, the mapping from binary package names recipes and recipe metadata like LICENSE is available from buildhistory. Also binary package content of images is available from buildhistory. With some

Hi, A kernel recipe will provide linux-libc-headers after a "make headers_install" call... So the SRC_URI of linux-libc-headers can be the same as from the linux kernel recipe, or linux kernel recipe

Yes, we're talking about the same thing :) A lot of yocto things don't work well if major changes happen and WORKDIR isn't completely cleaned in between. With various BSP layers things can be even wor

Hi, I know it's not the best or recommended approach, but I find it hard to avoid merging linux-libc-headers recipe with the actual kernel recipe that a distro is using. At least a static copy of some

Hi, When both yocto update and your own changes are modifying the same recipes, then conflicts can occur. If builds are failing, then your environment is breaking something. It might even be the BSP l

Hi, We do SYSTEMD_SERVICE_${PN} = "" a lot but reasons are a lot more complex. To properly tune target system boot, one really needs to fork most systemd service files. This is needed to set cgroups,

From: Matt Hoosier <matt.hoosier@...> Insert an explicit pass to fetch all blobs needed by Git LFS, during the fetch() function. This avoids the default behavior of Git LFS to wait until 'git c

From: Mauro Queirós <maurofrqueiros@...> Function "contains_lfs" was only looking at the master branch when searching for LFS content. LFS may be configured in specific branches only, so we need

From: Mauro Queirós <maurofrqueiros@...> Git-LFS objects were being fetched even when lfs=0 was not set. This patch disables LFS smudging when lfs=0. That way, only the LFS pointers are download

Sorry, third patch needs to be backported from master for git lfs to work nicely on dunfell. Will send a v2. -Mikko

From: Matt Hoosier <matt.hoosier@...> Insert an explicit pass to fetch all blobs needed by Git LFS, during the fetch() function. This avoids the default behavior of Git LFS to wait until 'git c