From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/3] sign_rpm.bbclass: fix task dependencies
Date: Mon, 11 Jan 2016 18:13:17 +0200 [thread overview]
Message-ID: <1452528799-11292-2-git-send-email-markus.lehtonen@linux.intel.com> (raw)
In-Reply-To: <1452528799-11292-1-git-send-email-markus.lehtonen@linux.intel.com>
do_rootfs task needs to depend on signing-keys:do_export_public_keys.
The rpm signing public key needs to be present in order to prevent a
crash because it is imported into the rootfs rpmdb before rootfs
creation starts.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
---
meta/classes/sign_rpm.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/sign_rpm.bbclass b/meta/classes/sign_rpm.bbclass
index bc916a7..7906b64 100644
--- a/meta/classes/sign_rpm.bbclass
+++ b/meta/classes/sign_rpm.bbclass
@@ -71,3 +71,4 @@ python sign_rpm () {
}
do_package_index[depends] += "signing-keys:do_export_public_keys"
+do_rootfs[depends] += "signing-keys:do_export_public_keys"
--
2.1.4
next prev parent reply other threads:[~2016-01-11 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 16:13 [PATCH 0/3] Support remote RPM signing Markus Lehtonen
2016-01-11 16:13 ` Markus Lehtonen [this message]
2016-01-11 16:13 ` [PATCH 2/3] New lib module for handling GPG signing Markus Lehtonen
2016-01-11 16:13 ` [PATCH 3/3] oe.gpg_sign: support obs-signd Markus Lehtonen
2016-01-11 16:33 ` Mark Hatle
2016-01-12 16:24 ` Markus Lehtonen
2016-01-13 10:28 ` Markus Lehtonen
2016-01-13 14:56 ` Mark Hatle
2016-01-13 21:47 ` Mark Hatle
2016-01-21 15:28 ` Mark Hatle
[not found] ` <1453375237.13987.27.camel@linux.intel.com>
[not found] ` <56A0F794.7060603@windriver.com>
2016-01-22 10:43 ` Markus Lehtonen
2016-01-22 14:09 ` Mark Hatle
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=1452528799-11292-2-git-send-email-markus.lehtonen@linux.intel.com \
--to=markus.lehtonen@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