sys-fs/cryptsetup: stable 2.1.0 for hppa, bug #669640
authorRolf Eike Beer <eike@sf-mail.de>
Sat, 26 Oct 2019 20:31:25 +0000 (22:31 +0200)
committerSergei Trofimovich <slyfox@gentoo.org>
Sat, 26 Oct 2019 20:35:35 +0000 (21:35 +0100)
Package-Manager: Portage-2.3.76, Repoman-2.3.16
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Rolf Eike Beer <eike@sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild

index 5bd8ce20ba619fe450360fe560dd633456570790..0dea1f4cda00f5da271c7270f0ef3936ae3f61f5 100644 (file)
@@ -12,7 +12,7 @@ SRC_URI="https://www.kernel.org/pub/linux/utils/${PN}/v$(ver_cut 1-2)/${P/_/-}.t
 LICENSE="GPL-2+"
 SLOT="0/12" # libcryptsetup.so version
 [[ ${PV} != *_rc* ]] && \
-KEYWORDS="alpha amd64 arm arm64 ~hppa ia64 ~mips ppc ppc64 s390 ~sh sparc x86"
+KEYWORDS="alpha amd64 arm arm64 hppa ia64 ~mips ppc ppc64 s390 ~sh sparc x86"
 # cryptsetup does _not_ have a libressl backend. We only have this for REQUIRED_USE
 # and change "libressl" to "openssl" in our econf call.
 CRYPTO_BACKENDS="gcrypt kernel libressl nettle +openssl"