Bug 6366 - Generated mirror tarballs are not always updated when the git repos are
Summary: Generated mirror tarballs are not always updated when the git repos are
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.9
Assignee: Christopher Larson
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-05-22 22:51 UTC by Christopher Larson
Modified: 2015-09-21 17:18 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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.