From 4eccf264e5de74e0fc6e511fd02795c67a15c185 Mon Sep 17 00:00:00 2001 From: "Sam James (sam_c)" Date: Sun, 17 May 2020 18:19:00 +0000 Subject: [PATCH] sys-fs/cryptsetup: arm64 stable (bug #723234) Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Sam James (sam_c) Signed-off-by: Mart Raudsepp --- sys-fs/cryptsetup/cryptsetup-2.3.2.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys-fs/cryptsetup/cryptsetup-2.3.2.ebuild b/sys-fs/cryptsetup/cryptsetup-2.3.2.ebuild index fefacf7ae7fb..c9775999f930 100644 --- a/sys-fs/cryptsetup/cryptsetup-2.3.2.ebuild +++ b/sys-fs/cryptsetup/cryptsetup-2.3.2.ebuild @@ -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 ~riscv s390 sparc x86" +KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~mips ppc ppc64 ~riscv s390 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