From fd47fbc146c76c3a57a12479cdde1a5871e04864 Mon Sep 17 00:00:00 2001 From: Sergei Trofimovich Date: Sat, 23 Dec 2017 22:41:38 +0000 Subject: [PATCH] sys-fs/cryptsetup: stable 1.7.5 for ia64, bug #641712 Package-Manager: Portage-2.3.19, Repoman-2.3.6 RepoMan-Options: --include-arches="ia64" --- sys-fs/cryptsetup/cryptsetup-1.7.5.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys-fs/cryptsetup/cryptsetup-1.7.5.ebuild b/sys-fs/cryptsetup/cryptsetup-1.7.5.ebuild index a0678be69d40..35784d8a3463 100644 --- a/sys-fs/cryptsetup/cryptsetup-1.7.5.ebuild +++ b/sys-fs/cryptsetup/cryptsetup-1.7.5.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 ~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