Hello, some news about this issue. Tim pointed me to the docker and the reason why crops container have some UID:GID manipulation: see there. I used an ubuntu 20.04 VM to setup a build without docker

A ticket has been open for backporting the fix: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14971

#dunfell

Yes I do, I build under docker (ubuntu 20.04), I didn't mention that in my original post , sorry. Do you think it is related to my issue ?

Hello list, Doesn't ring a bell to anybody ? Even the slightest clue will help me to continue to track down this weird behavior , nobody have ever problem of files/directories rights during image gene

In my setup I have: KERNEL_IMAGETYPES=fitImage (coming from KERNEL_IMAGETYPE of my machine configuration) KERNEL_IMAGETYPE_FOR_MAKE=Image (used only internally by kernel.bbclass and setting to Image b

#dunfell

Hello, I'm currently migrating our system from warrior to dunfell and I have an issue on fitImage support for aarch64 architecture. We use KERNEL_IMAGETYPE = "fitImage" and INITRAMFS_IMAGE_BUNDLE = "1

#dunfell

Hello list, I currently migrate our project from warrior to dunfell and we experience some issues during the image generation step. We have a custom IMAGE_FSTYPES to meet our need and in one of our cu

Hello, instead of creating a new variable (don't sure of its possible usefulness), you can use BBMASK or review dependencies between your layer PS: I did a similar answer on your stackoverflow questio

Hello, I dug further into yocto classes and I think I found what is going on. All seems to come from the fact that gcc debug-prefix-map and macro-prefix-map options are statically defined in bitbake.c

Hello, you can customize QB_OPT_APPEND by removing options you don't want, e.g. QB_OPT_APPEND_remove = "-device usb-tablet" and add your own after. But maybe a lazy operator in the original conf file

It it can help to understand, I rechecked the full content of source packages and glib-2.0 / networkamanager are not ok like I said earlire. There are not empty but they seem to contain only build gen

Hello, I currently used yocto warrior and I encounter an issue during packaging of recipes. I would like to embed some source package (to be able to run coverage on target) , this work without issues