From 7448f9a180e46ee404b05f50437b55c79bc601e5 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Mon, 9 Dec 2019 17:28:38 +0000 Subject: bitbake: siggen: Ensure new unihash propagates through the system Its possible the new unihash may not exist in sstate. Currently the code would create an sstate object with the old hash however this updates it to create the object with the new unihash. (Bitbake rev: 0aee83e4e31dff7f4354e4eb4cbd35dd592e9f06) Signed-off-by: Richard Purdie (cherry picked from commit abcaa1398031fa5338a43859c661e6d4a9ce863d) Signed-off-by: Richard Purdie --- bitbake/lib/bb/siggen.py | 1 + 1 file changed, 1 insertion(+) (limited to 'bitbake') diff --git a/bitbake/lib/bb/siggen.py b/bitbake/lib/bb/siggen.py index de85326872..dbf510238f 100644 --- a/bitbake/lib/bb/siggen.py +++ b/bitbake/lib/bb/siggen.py @@ -513,6 +513,7 @@ class SignatureGeneratorUniHashMixIn(object): bb.debug(1, 'Task %s unihash changed %s -> %s by server %s' % (taskhash, unihash, new_unihash, self.server)) bb.event.fire(bb.runqueue.taskUniHashUpdate(fn + ':do_' + task, new_unihash), d) self.set_unihash(tid, new_unihash) + d.setVar('BB_UNIHASH', new_unihash) else: bb.debug(1, 'Reported task %s as unihash %s to %s' % (taskhash, unihash, self.server)) except hashserv.client.HashConnectionError as e: -- cgit v1.2.3-54-g00ecf