From fdaf1dc6869307241d4d3e5491a084aa8079f140 Mon Sep 17 00:00:00 2001 From: Agostino Sarubbo Date: Fri, 13 Sep 2019 19:27:18 +0200 Subject: [PATCH] sys-fs/cryptsetup: ia64 stable wrt bug #693818 Package-Manager: Portage-2.3.69, Repoman-2.3.16 RepoMan-Options: --include-arches="ia64" Signed-off-by: Agostino Sarubbo --- sys-fs/cryptsetup/cryptsetup-2.2.1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys-fs/cryptsetup/cryptsetup-2.2.1.ebuild b/sys-fs/cryptsetup/cryptsetup-2.2.1.ebuild index 64b6bb8cae77..485ea20367b1 100644 --- a/sys-fs/cryptsetup/cryptsetup-2.2.1.ebuild +++ b/sys-fs/cryptsetup/cryptsetup-2.2.1.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" 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