From 907be8a518eeca2cb27e24c84b0cb071a547d1c2 Mon Sep 17 00:00:00 2001 From: Markus Meier Date: Sat, 6 May 2017 15:16:14 +0200 Subject: [PATCH] sys-fs/cryptsetup: arm stable, bug #617314 Package-Manager: Portage-2.3.5, Repoman-2.3.1 RepoMan-Options: --include-arches="arm" --- sys-fs/cryptsetup/cryptsetup-1.7.4.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys-fs/cryptsetup/cryptsetup-1.7.4.ebuild b/sys-fs/cryptsetup/cryptsetup-1.7.4.ebuild index 3440d0d76ea0..853dfd6296e6 100644 --- a/sys-fs/cryptsetup/cryptsetup-1.7.4.ebuild +++ b/sys-fs/cryptsetup/cryptsetup-1.7.4.ebuild @@ -14,7 +14,7 @@ SRC_URI="mirror://kernel/linux/utils/${PN}/v$(get_version_component_range 1-2)/$ LICENSE="GPL-2+" SLOT="0" -KEYWORDS="~alpha amd64 ~arm hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc x86" +KEYWORDS="~alpha amd64 arm hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc x86" CRYPTO_BACKENDS="+gcrypt kernel nettle openssl" # we don't support nss since it doesn't allow cryptsetup to be built statically # and it's missing ripemd160 support so it can't provide full backward compatibility -- 2.26.2