From 2eb66a6cbb0c2815ed38c35e47f7627e88760b29 Mon Sep 17 00:00:00 2001 From: Agostino Sarubbo Date: Thu, 18 Jul 2019 12:03:29 +0200 Subject: [PATCH] sys-fs/cryptsetup: alpha stable wrt bug #669640 Signed-off-by: Agostino Sarubbo Package-Manager: Portage-2.3.66, Repoman-2.3.11 RepoMan-Options: --include-arches="alpha" --- sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild b/sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild index 095fb0b3fc6a..0318b8a875a9 100644 --- a/sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild +++ b/sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild @@ -12,7 +12,7 @@ SRC_URI="mirror://kernel/linux/utils/${PN}/v$(ver_cut 1-2)/${P/_/-}.tar.xz" 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" -- 2.26.2