Bug 6366

Summary: Generated mirror tarballs are not always updated when the git repos are
Product: [Build System, Metadata & Runtime] BitBake Reporter: Christopher Larson <kergoth>
Component: bitbakeAssignee: Christopher Larson <kergoth>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: poky.bs.watcher, poky.watcher, richard.purdie, sgw
Version: unspecified   
Target Milestone: 1.9   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Christopher Larson 2014-05-22 22:51:41 UTC 
The handling of 'ud.repochanged' is flawed, in that it's state which is only held in-memory. If the process is interrupted after it's marked but before the updated tarball is written, the git repository becomes out of sync with the tarball. At Mentor, we're seeing cases where a mirror tarball is fetched which doesn't contain the necessary revisions, but an updated tarball isn't written after the fetch.
Comment 1 Christopher Larson 2015-09-15 20:54:57 UTC 
Patch submitted to the bitbake-devel list for review.