Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Yi Zhao" <yi.zhao@windriver.com>
To: <yocto@yoctoproject.org>, <joe@deserted.net>, <Joe_MacDonald@mentor.com>
Subject: [meta-selinux][PATCH 5/6] refpolicy: add UPSTREAM_CHECK_GITTAGREGEX
Date: Mon, 23 Dec 2019 16:21:51 +0800	[thread overview]
Message-ID: <20191223082152.7706-5-yi.zhao@windriver.com> (raw)
In-Reply-To: <20191223082152.7706-1-yi.zhao@windriver.com>

Add UPSTREAM_CHECK_GITTAGREGEX to make devtool check-upgrade-status
works.

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
---
 recipes-security/refpolicy/refpolicy_2.20190201.inc | 2 ++
 recipes-security/refpolicy/refpolicy_git.inc        | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/recipes-security/refpolicy/refpolicy_2.20190201.inc b/recipes-security/refpolicy/refpolicy_2.20190201.inc
index 78c6e74..4030b36 100644
--- a/recipes-security/refpolicy/refpolicy_2.20190201.inc
+++ b/recipes-security/refpolicy/refpolicy_2.20190201.inc
@@ -2,6 +2,8 @@ SRC_URI = "https://github.com/SELinuxProject/refpolicy/releases/download/RELEASE
 SRC_URI[md5sum] = "babb0d5ca2ae333631d25392b2b3ce8d"
 SRC_URI[sha256sum] = "ed620dc91c4e09eee6271b373f7c61a364a82ea57bd2dc86ca1f7075304e2843"
 
+UPSTREAM_CHECK_GITTAGREGEX = "RELEASE_(?P<pver>\d+_\d+)"
+
 FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-2.20190201:"
 
 include refpolicy_common.inc
diff --git a/recipes-security/refpolicy/refpolicy_git.inc b/recipes-security/refpolicy/refpolicy_git.inc
index 8aeaf27..8de07c0 100644
--- a/recipes-security/refpolicy/refpolicy_git.inc
+++ b/recipes-security/refpolicy/refpolicy_git.inc
@@ -4,6 +4,8 @@ SRC_URI = "git://github.com/SELinuxProject/refpolicy.git;protocol=git;branch=mas
 
 SRCREV_refpolicy ?= "df696a325404b84c2c931c85356510005e5e6916"
 
+UPSTREAM_CHECK_GITTAGREGEX = "RELEASE_(?P<pver>\d+_\d+)"
+
 FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-git:"
 
 include refpolicy_common.inc
-- 
2.17.1


  parent reply	other threads:[~2019-12-23  8:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23  8:21 [meta-selinux][PATCH 1/6] python-ipy: remove recipe Yi Zhao
2019-12-23  8:21 ` [meta-selinux][PATCH 2/6] libselinux-python: fix race issue in parallel build Yi Zhao
2019-12-23  8:21 ` [meta-selinux][PATCH 3/6] libsemanage: " Yi Zhao
2019-12-23  8:21 ` [meta-selinux][PATCH 4/6] selinux-initsh.inc: install selinux-init.sh and selinux-labeldev.sh when using systemd Yi Zhao
2019-12-24 14:22   ` Joe MacDonald
2019-12-25  7:44     ` Yi Zhao
2019-12-23  8:21 ` Yi Zhao [this message]
2019-12-23  8:21 ` [meta-selinux][PATCH 6/6] refpolicy: switch to python3 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=20191223082152.7706-5-yi.zhao@windriver.com \
    --to=yi.zhao@windriver.com \
    --cc=Joe_MacDonald@mentor.com \
    --cc=joe@deserted.net \
    --cc=yocto@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