AnsweredAssumed Answered

i.MX6 Yocto question about SHA

Question asked by Jay Marcinczyk Employee on Mar 9, 2015
Latest reply on Apr 29, 2015 by gusarambula

I have a customer with some questions about Yocto and SHA:

 

Some background - our yocto/linux releases are based on your releases, i.e. we start with the manifest from the Freescale release at meta-fsl-bsp-release.git (home of the Freescale i.MX Yocto BSP Release Layer), we add our stuff to it, and then we create our own manifest. Like your manifest, our release manifest locks down all of the components of the build by specifying each layer with its unique SHA (except that yours picks up meta-fsl-bsp-release.git by a branch name, ours specifies the SHA).

 

The problem - we cannot reproduce some of our builds because some of the versions in meta-fsl-bsp-release have been removed.

 

For example, one of our builds was looking for the commit with SHA 16c911d. It no longer exists, but with some investigation we were able to determine that the commit had moved to SHA 218af699b.

 

Was it an accident that commits were removed from the repository? Or is this part of your process and thus a recurring thing, and we'll have to adjust our process? Maybe we shouldn't be referring to your layer through a SHA? This seems somewhat untethered to reproduce builds reliably. But, maybe I'm missing something.

 

Thanks, any help or insight is appreciated.

 

Regards,

 

Jay

Outcomes