From: Randy Witt <randy.e.witt@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] extensible sdk changes
Date: Thu, 7 Apr 2016 16:34:48 -0700 [thread overview]
Message-ID: <cover.1460071932.git.randy.e.witt@linux.intel.com> (raw)
This set of changes is to make sure the locked signatures are enforced as
part of the extensible sdk usage.
Therefore it also allows for the unlocking of recipes that are part of the
devtool workspace.
The following changes since commit 14e2b90893f57570c2002317b5afb0e61d15e9ca:
toasterconf.json: Add DL_DIR and SSTATE_DIR to poky toasterconf (2016-04-07 14:58:10 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib sigs
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=sigs
Randy Witt (5):
sstatesig.py: Split single locked sigs check into multiple checks
sstatesig.py: Improve the SIGGEN_LOCKEDSIGS_TASKSIG_CHECK message
populate_sdk_ext.bbclass: Enable locked sigs errors
sstatesig.py: Add a method to "unlock" recipes
devtool: Create unlocked-sigs.inc containing items in the workspace
meta/classes/populate_sdk_ext.bbclass | 16 +++++++--
meta/classes/sstate.bbclass | 8 ++++-
meta/lib/oe/sstatesig.py | 63 ++++++++++++++++++++++++++++-------
meta/lib/oeqa/selftest/signing.py | 4 +--
scripts/devtool | 20 +++++++++++
5 files changed, 94 insertions(+), 17 deletions(-)
--
2.5.5
next reply other threads:[~2016-04-07 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 23:34 Randy Witt [this message]
2016-04-07 23:34 ` [PATCH 1/5] sstatesig.py: Split single locked sigs check into multiple checks Randy Witt
2016-04-07 23:34 ` [PATCH 2/5] sstatesig.py: Improve the SIGGEN_LOCKEDSIGS_TASKSIG_CHECK message Randy Witt
2016-04-07 23:34 ` [PATCH 3/5] populate_sdk_ext.bbclass: Enable locked sigs errors Randy Witt
2016-04-07 23:34 ` [PATCH 4/5] sstatesig.py: Add a method to "unlock" recipes Randy Witt
2016-04-07 23:34 ` [PATCH 5/5] devtool: Create unlocked-sigs.inc containing items in the workspace Randy Witt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1460071932.git.randy.e.witt@linux.intel.com \
--to=randy.e.witt@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox