From: "akuster" <akuster808@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [meta-security][PATCH 6/6] openscap: update to 1.3.3
Date: Fri, 12 Jun 2020 10:14:22 -0700 [thread overview]
Message-ID: <20200612171422.3380-6-akuster808@gmail.com> (raw)
In-Reply-To: <20200612171422.3380-1-akuster808@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
.../openscap/{openscap_1.3.1.bb => openscap_1.3.3.bb} | 2 +-
.../recipes-openscap/openscap/openscap_git.bb | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
rename meta-security-compliance/recipes-openscap/openscap/{openscap_1.3.1.bb => openscap_1.3.3.bb} (76%)
diff --git a/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.3.bb
similarity index 76%
rename from meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb
rename to meta-security-compliance/recipes-openscap/openscap/openscap_1.3.3.bb
index ad29efd..51fa9ee 100644
--- a/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.3.bb
@@ -2,7 +2,7 @@ SUMARRY = "NIST Certified SCAP 1.2 toolkit"
require openscap.inc
-SRCREV = "3a4c635691380fa990a226acc8558db35d7ebabc"
+SRCREV = "0cb55c55af6be9934d6fd0caf4563b206f289732"
SRC_URI = "git://github.com/OpenSCAP/openscap.git;branch=maint-1.3 \
"
diff --git a/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb b/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
index 963d3de..73a4729 100644
--- a/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
@@ -5,8 +5,8 @@ SUMARRY = "NIST Certified SCAP 1.2 toolkit with OE changes"
include openscap.inc
-SRCREV = "4bbdb46ff651f809d5b38ca08d769790c4bfff90"
+SRCREV = "a85943eee400fdbe59234d1c4a02d8cf710c4625"
SRC_URI = "git://github.com/akuster/openscap.git;branch=oe-1.3 \
"
-PV = "1.3.1+git${SRCPV}"
+PV = "1.3.3+git${SRCPV}"
--
2.17.1
prev parent reply other threads:[~2020-06-12 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 17:14 [meta-security][PATCH 1/6] tpm2-tools: update to 4.1.3 akuster
2020-06-12 17:14 ` [meta-security][PATCH 2/6] tpm2-tss: update to 2.4.1 akuster
2020-06-12 17:14 ` [meta-security][PATCH 3/6] tpm2-tss-engine: add branch to SRC_URI & update to tip akuster
2020-06-12 17:14 ` [meta-security][PATCH 4/6] tpm2-pkcs11: update 1.2.0 akuster
2020-06-12 17:14 ` [meta-security][PATCH 5/6] libtpm: update to 0.7.2 akuster
2020-06-12 17:14 ` akuster [this message]
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=20200612171422.3380-6-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=yocto@lists.yoctoproject.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