From c05698ab3a1f953a58079814502813ed6ced7569 Mon Sep 17 00:00:00 2001 From: Agostino Sarubbo Date: Mon, 5 Jul 2021 08:58:40 +0200 Subject: sys-fs/cryptsetup: ppc64 stable wrt bug #800434 Package-Manager: Portage-3.0.20, Repoman-3.0.2 RepoMan-Options: --include-arches="ppc64" Signed-off-by: Agostino Sarubbo --- sys-fs/cryptsetup/cryptsetup-2.3.6.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sys-fs') diff --git a/sys-fs/cryptsetup/cryptsetup-2.3.6.ebuild b/sys-fs/cryptsetup/cryptsetup-2.3.6.ebuild index a7866973e90d..7b5b46a4f7cb 100644 --- a/sys-fs/cryptsetup/cryptsetup-2.3.6.ebuild +++ b/sys-fs/cryptsetup/cryptsetup-2.3.6.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