Andrei Gherzan
Andrei Gherzan
`LINUX_RPI_KMETA_BRANCH` is only used in the SRC_URI definition. I'm sure you can handle that as per your custom kernel fork requirements.
Is that now part of some default cfg? Why was it removed? A reference to oe-core would be useful.
> okay Did the above fix your issue?
That would require a backporting investigation of that in kirkstone. Have you checked the kirkstone kernel version provided by the layer?
> duplicate I'm not sure what this means. Could you explain?
I am not a kas user, so I'll let the community weigh in.
Sadly sato is not an image we test but it looks like you don't have this layer added. Have you added the rpi layer?
It's an edge case on the CI side. It falls apart when the incoming branch is the same as the destination branch (in name). "master" and "master" in this case....
@kluszon Can you please cleanup the merge commits?
@khimaros I'm unsure how you can have the same core-image-sato error while building core-image-base. I would suggest you create a new issue and clearly describe the issue with reproducible steps....