oe-selftest: no need to parse gpg output to determine the name of the signing key
The parsing fails on my machine, and we use a key with a hardcoded name, and so can provide it directly. (From OE-Core rev: b69bad2c4e51a24868422f39619a0598fd2a0533) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
5a3e1290cb
commit
55928d1237
|
@ -103,13 +103,7 @@ class Signing(oeSelfTest):
|
|||
self.add_command_to_tearDown('bitbake -c clean %s' % test_recipe)
|
||||
self.add_command_to_tearDown('rm -rf %s' % sstatedir)
|
||||
|
||||
# Determine the pub key signature
|
||||
ret = runCmd('gpg --homedir %s --list-keys' % self.gpg_dir)
|
||||
pub_key = re.search(r'^pub\s+\S+/(\S+)\s+', ret.output, re.M)
|
||||
self.assertIsNotNone(pub_key, 'Failed to determine the public key signature.')
|
||||
pub_key = pub_key.group(1)
|
||||
|
||||
feature = 'SSTATE_SIG_KEY ?= "%s"\n' % pub_key
|
||||
feature = 'SSTATE_SIG_KEY ?= "testuser"\n'
|
||||
feature += 'SSTATE_SIG_PASSPHRASE ?= "test123"\n'
|
||||
feature += 'SSTATE_VERIFY_SIG ?= "1"\n'
|
||||
feature += 'GPG_PATH = "%s"\n' % self.gpg_dir
|
||||
|
|
Loading…
Reference in New Issue