From b4020291e5bd8ae83f18b0bb203e9b9f81202b51 Mon Sep 17 00:00:00 2001 From: Mikle Kolyada Date: Fri, 15 May 2020 16:46:11 +0300 Subject: sys-fs/cryptsetup: amd64 stable wrt bug #723234 Package-Manager: Portage-2.3.99, Repoman-2.3.22 RepoMan-Options: --include-arches="amd64" Signed-off-by: Mikle Kolyada --- sys-fs/cryptsetup/cryptsetup-2.3.2.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sys-fs') diff --git a/sys-fs/cryptsetup/cryptsetup-2.3.2.ebuild b/sys-fs/cryptsetup/cryptsetup-2.3.2.ebuild index 3470a2253748..24930bec305f 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 -- cgit v1.2.3-65-gdbad