<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 15, 2015 at 2:23 PM, Christopher Larson <span dir="ltr"><<a href="mailto:kergoth@gmail.com" target="_blank">kergoth@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">From: Christopher Larson <<a href="mailto:chris_larson@mentor.com">chris_larson@mentor.com</a>><br>
<br>
We were maintaining state in the form of ud.repochanged to determine whether<br>
we need to write the tarball in the case where the tarball already exists, but<br>
this state is maintained only in memory. If we need to update the git repo,<br>
set ud.repochanged to True, and then are interrupted or killed, the tarball<br>
will then be out of date.<br>
<br>
Rather than maintaining this state, simply remove the out of date tarball when<br>
we update the git repo, and it will be re-created with updated content in<br>
build_mirror_data.<br>
<br>
[YOCTO #6366]<br>
<br>
Signed-off-by: Christopher Larson <<a href="mailto:chris_larson@mentor.com">chris_larson@mentor.com</a>></span></blockquote></div><br>Ignore the v2, only removing it when write_tarballs is set could be problematic if the repo is updated with write_tarballs not set, then it's set afterward.<br>-- <br><div class="gmail_signature"><div dir="ltr">Christopher Larson<br>kergoth at gmail dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div></div>
</div></div>