On Tue, 07 Jun 2016 17:20:12 Burton, Ross wrote:
> On 7 June 2016 at 17:02, Burton, Ross <ross.bur...@intel.com> wrote:
> > It means the hash calculated my the bitbake master was different to the
> > hash calculated when the worker started up. This usually means that
> > you're
> > using something like ${TIME} in the recipe but not marking it appropriatly
> > so the cache ignores it. Do you have a base-files bbappend that writes a
> > timestamp?
>
> The always wise Joshua reminds me that if your DISTRO_VERSION contains
> ${DATETIME} then this happens. If you're doing this then you'll want to
> set [vardepsexclude] on DISTRO_VERSION to stop the DATETIME from getting
> into the cache (or not put the current date/time into the distro version).
I think we need to handle this situation better - if it's really worth
producing an error about then it's worth producing an error message that
people can actually understand, particularly as it's recently added
validation.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
