I built from Poky/Yocto master on 2015-02-22. I always create new tarballs from downloaded trees if they have changed BB_GENERATE_MIRROR_TARBALLS = "1" and I stash them in my local mirror.
On that date, glibc had just been updated to version 2.21 so it made sense that the tarball was updated. Since that date, I've done dozens of [full] builds for my various platforms. The glibc recipe has not been touched (at least not the git revision) since then. However, the tarball for its git repository has been refetched/rebuilt a number of times and it seems pretty hit-or-miss. For example a build on 2015-03-03 changed the tarball but one just two days later did not. Is there any sense to this? If the downloaded git+tarball contains the desired revision, why would it be re-downloaded and rebuilt? Sadly, I'm not sure I can give a good recipe for causing the behaviour to happen so the problem can be examined in detail. Note: this behaviour seems to be limited to only a few git trees. These are most often being touched although I suspect the underlying git tree is not: git2_git.yoctoproject.org.yocto-kernel-tools.git.tar.gz git2_sourceware.org.git.glibc.git.tar.gz ... very confused -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
