All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yi Zhao" <yi.zhao@windriver.com>
To: <joe@deserted.net>, <yocto@lists.yoctoproject.org>
Subject: [meta-selinux][PATCH 11/16] restorecond: upgrade to 3.0 (20191204)
Date: Tue, 14 Apr 2020 15:41:53 +0800	[thread overview]
Message-ID: <20200414074158.32058-11-yi.zhao@windriver.com> (raw)
In-Reply-To: <20200414074158.32058-1-yi.zhao@windriver.com>

Fix typo in patch.

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
---
 .../policycoreutils-make-O_CLOEXEC-optional.patch          | 2 +-
 recipes-security/selinux/restorecond_2.9.bb                | 7 -------
 recipes-security/selinux/restorecond_3.0.bb                | 7 +++++++
 3 files changed, 8 insertions(+), 8 deletions(-)
 delete mode 100644 recipes-security/selinux/restorecond_2.9.bb
 create mode 100644 recipes-security/selinux/restorecond_3.0.bb

diff --git a/recipes-security/selinux/restorecond/policycoreutils-make-O_CLOEXEC-optional.patch b/recipes-security/selinux/restorecond/policycoreutils-make-O_CLOEXEC-optional.patch
index 2928aff..83250eb 100644
--- a/recipes-security/selinux/restorecond/policycoreutils-make-O_CLOEXEC-optional.patch
+++ b/recipes-security/selinux/restorecond/policycoreutils-make-O_CLOEXEC-optional.patch
@@ -14,7 +14,7 @@ compile-time option and generate a warning when it is not available.
 The actual impact of leaking these file descriptors is minimal, though
 it does produce curious AVC Denied messages.
 
-Uptream-Status: Inappropriate
+Upstream-Status: Inappropriate
 [O_CLOEXEC has been in Linux since 2007 and POSIX since 2008]
 
 Signed-off-by: Joe MacDonald <joe.macdonald@windriver.com>
diff --git a/recipes-security/selinux/restorecond_2.9.bb b/recipes-security/selinux/restorecond_2.9.bb
deleted file mode 100644
index 2ccac18..0000000
--- a/recipes-security/selinux/restorecond_2.9.bb
+++ /dev/null
@@ -1,7 +0,0 @@
-require selinux_20190315.inc
-require ${BPN}.inc
-
-LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
-
-SRC_URI[md5sum] = "1a24cb2a23d8bd01d3f8d9bb2031981f"
-SRC_URI[sha256sum] = "cbf9820583e641ee0462fa7bc89e6024676af281e025703e17b2d019b1a25a4f"
diff --git a/recipes-security/selinux/restorecond_3.0.bb b/recipes-security/selinux/restorecond_3.0.bb
new file mode 100644
index 0000000..8c840c9
--- /dev/null
+++ b/recipes-security/selinux/restorecond_3.0.bb
@@ -0,0 +1,7 @@
+require selinux_20191204.inc
+require ${BPN}.inc
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
+
+SRC_URI[md5sum] = "f32edbd8a1f724ef1e4fa70bf9e22685"
+SRC_URI[sha256sum] = "32a92c9f4bf48c613f9f467ced58d8c369eec8892239cd44d5d0e139b41926dc"
-- 
2.17.1


  parent reply	other threads:[~2020-04-14  7:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  7:41 [meta-selinux][PATCH 01/16] setools: upgrade 4.2.2 -> 4.3.0 Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 02/16] selinux: upgrade inc files to 3.0 (20191204) Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 03/16] libsepol: upgrade " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 04/16] libselinux: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 05/16] libselinux-python: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 06/16] libsemanage: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 07/16] checkpolicy: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 08/16] secilc: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 09/16] policycoreutils: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 10/16] mcstrans: " Yi Zhao
2020-04-14  7:41 ` Yi Zhao [this message]
2020-04-14  7:41 ` [meta-selinux][PATCH 12/16] selinux-python: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 13/16] selinux-dbus: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 14/16] selinux-sandbox: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 15/16] selinux-gui: " Yi Zhao
2020-04-14  7:41 ` [meta-selinux][PATCH 16/16] semodule-utils: " Yi Zhao

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=20200414074158.32058-11-yi.zhao@windriver.com \
    --to=yi.zhao@windriver.com \
    --cc=joe@deserted.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.