On Tue, Dec 06, 2016 at 07:04:31PM +0100, Herve Jourdain wrote: > Hi Andrei, > > But I believe that the core of the problem is not necessarily the patch in > oe-core to detect the kernel version itself, but like Khem mentioned the > fact that a "well known" SRCREV is only valid for a brief period of time > under the RPI tree "constant" rebasing we've been experiencing lately. > So basically, the SRCREV that is used is not corresponding to what it used > to be, if it's still there in the tree, and the oe-core detects that - the > SRCREV thought it was one version of the kernel, and it just happened that > it corresponds to a different codebase with a different linux version. > Killing the error reporting by a patch will probably not prevent the > mismatch happening behind the scene. > So like Khem mentioned, either we find a way to "prevent" the rebasing at > the source, or we need to track down every version we want to support, and > update SRCREV and corresponding kernel version for those.
Got it now. What do you mean by "track down every version we want"? -- Andrei Gherzan
signature.asc
Description: PGP signature
-- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
