]> code.ossystems Code Review - openembedded-core.git/commit
classes/sstate: don't use unsigned sstate when verification enabled
authorJoshua Lock via Openembedded-core <openembedded-core@lists.openembedded.org>
Fri, 26 Jul 2019 11:26:49 +0000 (11:26 +0000)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sat, 27 Jul 2019 21:45:23 +0000 (22:45 +0100)
commit571235978d98552e3734bf382454dd51272db782
treee82dec03b07277be39980890af717b9e6d60080e
parent06559c1ed86dbce53505f9ed98111fe9d0b97ed7
classes/sstate: don't use unsigned sstate when verification enabled

When signature verification of shared state objects is enabled
(SSTATE_VERIFY_SIG) use of an unsigned object, even though it produces a
warning, seems unexpected. Instead skip unsigned objects and force the
non-accelerated task to be run.

Signed-off-by: Joshua Lock <jlock@vmware.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/sstate.bbclass