All of lore.kernel.org
 help / color / mirror / Atom feed
* tarballs from git
@ 2015-11-05 13:17 Gary Thomas
  2015-11-05 13:23 ` Gary Thomas
  0 siblings, 1 reply; 2+ messages in thread
From: Gary Thomas @ 2015-11-05 13:17 UTC (permalink / raw)
  To: Yocto Project

I use BB_GENERATE_MIRROR_TARBALLS = "1" to generate tarballs
from the various git-based recipes I use.  For the most part
this works great and once the tar file is generated, it just
gets reused.

However, just now I rebuilt my kernel which uses such a git
SRC_URI and the tar file was rebuilt even though I can't see
anything that was newly fetched.  I had built from the same
recipe yesterday (today I only touched a patch which changed
neither the recipe nor the SRCREV, etc) and the tar file from
last month was used.  Looking through the generated tar file,
I can see that the last file updated was last Oct 5, so there
should have been no reason to rebuild the tar file.

Is there some trace (log file, etc) that might tell me why
this happened?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: tarballs from git
  2015-11-05 13:17 tarballs from git Gary Thomas
@ 2015-11-05 13:23 ` Gary Thomas
  0 siblings, 0 replies; 2+ messages in thread
From: Gary Thomas @ 2015-11-05 13:23 UTC (permalink / raw)
  To: yocto

On 2015-11-05 06:17, Gary Thomas wrote:
> I use BB_GENERATE_MIRROR_TARBALLS = "1" to generate tarballs
> from the various git-based recipes I use.  For the most part
> this works great and once the tar file is generated, it just
> gets reused.
>
> However, just now I rebuilt my kernel which uses such a git
> SRC_URI and the tar file was rebuilt even though I can't see
> anything that was newly fetched.  I had built from the same
> recipe yesterday (today I only touched a patch which changed
> neither the recipe nor the SRCREV, etc) and the tar file from
> last month was used.  Looking through the generated tar file,
> I can see that the last file updated was last Oct 5, so there
> should have been no reason to rebuild the tar file.
>
> Is there some trace (log file, etc) that might tell me why
> this happened?
>

Never mind - there were some differences that I missed.

That said, I'm still not sure what made it refetch the GIT tree
as I didn't change the SRCREV nor the recipe (only updated a
patch in the recipe) so the necessary BRANCH+SRCREV should have
been in the previous tar file.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-11-05 13:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-05 13:17 tarballs from git Gary Thomas
2015-11-05 13:23 ` Gary Thomas

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.