[meta-freescale] Question about SHA in Yocto

[Otavio Salvador]

Hello Gustavo,

On Fri, Mar 13, 2015 at 3:32 PM, Gustavo Ramon Arambula Aguilar
<gustavo.arambula at freescale.com> wrote:
> There is a question on the communities that I hope you can help me with:
>
> 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.
>
> https://community.freescale.com/thread/344949

First let's align some information. The meta-fsl-bsp-release is not
done by the community but Freescale itself :) You can learn more about
it in our release notes[1],

1. http://freescale.github.io/doc/release-notes/1.7/index.html#the-differences-between-project-name-and-freescale-release-name

and it should be been removed by mistake. The process is indeed right
about using hard-coded hashes for release (during development branches
are advised) so nothing to be changed except that who is pushing to
Freescale should avoid doing that removal again in future.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750