From: aduskett at gmail.com <aduskett@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/refpolicy: bump to version 2.20190201
Date: Mon, 8 Apr 2019 14:50:13 -0400 [thread overview]
Message-ID: <20190408185013.71465-10-aduskett@gmail.com> (raw)
In-Reply-To: <20190408185013.71465-1-aduskett@gmail.com>
From: Adam Duskett <Aduskett@gmail.com>
Also change the site location to the non-archived URL.
Signed-off-by: Adam Duskett <Aduskett@gmail.com>
---
package/refpolicy/refpolicy.hash | 4 ++--
package/refpolicy/refpolicy.mk | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/package/refpolicy/refpolicy.hash b/package/refpolicy/refpolicy.hash
index f341566f28..856d8cb8a2 100644
--- a/package/refpolicy/refpolicy.hash
+++ b/package/refpolicy/refpolicy.hash
@@ -1,5 +1,5 @@
-# From https://github.com/TresysTechnology/refpolicy/wiki/DownloadRelease
-sha256 e826f7d7f899a548e538964487e9fc1bc67ca94756ebdce0bfb6532b4eb0d06b refpolicy-2.20180114.tar.bz2
+# From https://github.com/SELinuxProject/refpolicy/releases
+sha256 ed620dc91c4e09eee6271b373f7c61a364a82ea57bd2dc86ca1f7075304e2843 refpolicy-2.20190201.tar.bz2
# Locally computed
sha256 204d8eff92f95aac4df6c8122bc1505f468f3a901e5a4cc08940e0ede1938994 COPYING
diff --git a/package/refpolicy/refpolicy.mk b/package/refpolicy/refpolicy.mk
index 590e0ebd9a..78c17bad01 100644
--- a/package/refpolicy/refpolicy.mk
+++ b/package/refpolicy/refpolicy.mk
@@ -4,9 +4,9 @@
#
################################################################################
-REFPOLICY_VERSION = 2.20180114
+REFPOLICY_VERSION = 2.20190201
REFPOLICY_SOURCE = refpolicy-$(REFPOLICY_VERSION).tar.bz2
-REFPOLICY_SITE = https://raw.githubusercontent.com/wiki/TresysTechnology/refpolicy/files
+REFPOLICY_SITE = https://github.com/SELinuxProject/refpolicy/releases/download/RELEASE_2_20190201
REFPOLICY_LICENSE = GPL-2.0
REFPOLICY_LICENSE_FILES = COPYING
REFPOLICY_INSTALL_STAGING = YES
--
2.20.1
next prev parent reply other threads:[~2019-04-08 18:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 18:50 [Buildroot] [PATCH] package/audit: bump version to 2.8.5 aduskett at gmail.com
2019-04-08 18:50 ` [Buildroot] [PATCH] package/libsepol: bump version to 2.9 aduskett at gmail.com
2019-04-11 8:57 ` Thomas Petazzoni
2019-04-08 18:50 ` [Buildroot] [PATCH] package/libselinux: " aduskett at gmail.com
2019-04-11 12:22 ` Thomas Petazzoni
2019-04-08 18:50 ` [Buildroot] [PATCH] libsemanage: bump to version 2.9 aduskett at gmail.com
2019-04-11 12:23 ` Thomas Petazzoni
2019-04-08 18:50 ` [Buildroot] [PATCH] package/checkpolicy: " aduskett at gmail.com
2019-04-11 12:32 ` Thomas Petazzoni
2019-04-08 18:50 ` [Buildroot] [PATCH] package/policycoreutils: " aduskett at gmail.com
2019-04-11 12:33 ` Thomas Petazzoni
2019-04-08 18:50 ` [Buildroot] [PATCH] package/selinux-python: " aduskett at gmail.com
2019-04-11 13:00 ` Thomas Petazzoni
2019-04-08 18:50 ` [Buildroot] [PATCH] package/restorecond: " aduskett at gmail.com
2019-04-11 13:00 ` Thomas Petazzoni
2019-04-08 18:50 ` [Buildroot] [PATCH] package/semodule-utils: " aduskett at gmail.com
2019-04-11 13:00 ` Thomas Petazzoni
2019-04-08 18:50 ` aduskett at gmail.com [this message]
2019-04-11 13:00 ` [Buildroot] [PATCH] package/refpolicy: bump to version 2.20190201 Thomas Petazzoni
2019-04-11 8:56 ` [Buildroot] [PATCH] package/audit: bump version to 2.8.5 Thomas Petazzoni
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=20190408185013.71465-10-aduskett@gmail.com \
--to=aduskett@gmail.com \
--cc=buildroot@busybox.net \
/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