11:41 <simonew> for info: I have some time to go over the cve report for master this week: I could send a report on Monday.

17:38 <mischief> RP: i never worked it out, i wiped build and now i have a mips image :')

18:07 <jdiez> sstate files contain the absolute path of recipes, right? so if I clone the repository at a different path, the sstate cache is not used. is it possible to reuse sstate cache in this case?

18:15 <jdiez> context: i have a sstate cache for builds done on my computer inside a container, where the build dir is /workdir/build. I copied /workdir/build/sstate-cache to /home/build/sstate-cache on a build server

18:15 <jdiez> I tried building the image on the server (after adjusting the paths in bblayers) and it didnt seem to be using any of the sstate cache

18:15 <jdiez> (I also did set SSTATE_DIR)

18:38 <Saur_Home> jdiez: Sharing sstate between different build machines and different build paths work. However, if you do not have uninative enabled, then the native sstate must match. I.e., without uninative, if you build on Debian Bookworm in your container, then that sstate will only fully work on another Debian Bookworm host.

18:40 <jdiez> hmm... I don't think I enabled it or disabled it on purpose. It seems poky inherits bbnative, and my distro inherits from poky

18:41 <jdiez> s/bbnative/uninative/

18:42 <jdiez> NATIVELSBSTRING is "universal" in my build

18:43 <Saur_Home> You could try `bitbake-diffsigs -t <recipe> <task>` for one of the earliest recipes that is being rebuilt. If it works it should tell you why it is being rebuilt.

19:03 <Ad0> is there a guide to actually upgrade the kernel config to the current kernel with bitbake devshell etc?

19:32 <simonew> Ad0: I have now not checked, but I would go to https://docs.yoctoproject.org/dev/kernel-dev/index.html and check there. How to use menuconfig etc is described there