summaryrefslogtreecommitdiffstats
path: root/meta/recipes-extended/man/man_1.6g.bb
diff options
context:
space:
mode:
authorClemens Lang <clemens.lang@bmw-carit.de>2015-03-06 15:28:54 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-03-09 14:57:00 +0000
commit36e47a99ae6668cb9a601f137f56011b7de13512 (patch)
tree7a7dda577ff8ee701eb880b171906f1e45edd823 /meta/recipes-extended/man/man_1.6g.bb
parent3c641e7238667d941b13aca9c5f3e392085f7a9f (diff)
downloadpoky-36e47a99ae6668cb9a601f137f56011b7de13512.tar.gz
bitbake: fetch2: Revalidate checksums, YOCTO #5571
[YOCTO #5571] -- https://bugzilla.yoctoproject.org/show_bug.cgi?id=5571 The following workflow (whether accidentally or deliberately) would previously not result in a checksum error, but would be helpful to do so: - Write a recipe with correct checksums - Fetch the sources for this recipe using bitbake - Change the checksums Since the bitbake fetcher writes a done stamp after the initial download and does not verify the checksums again (even if they are changed in the recipe afterwards), the change of checksums is silently ignored. Fix this without the overhead of computing the checksums from scratch on every do_fetch by storing them in pickled format in the done stamp and verifying that they still match those in the recipe. (Bitbake rev: fbd4a0d422cf7f43db2f9eab2e47c41246a9031e) Signed-off-by: Clemens Lang <clemens.lang@bmw-carit.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/man/man_1.6g.bb')
0 files changed, 0 insertions, 0 deletions