From 61c3af0c64856956a192edbff88dd6d496b88b4d Mon Sep 17 00:00:00 2001 From: Agostino Sarubbo Date: Wed, 31 Jul 2019 11:04:23 +0200 Subject: [PATCH] sys-fs/cryptsetup: s390 stable wrt bug #669640 Package-Manager: Portage-2.3.66, Repoman-2.3.16 RepoMan-Options: --include-arches="s390" Signed-off-by: Agostino Sarubbo --- sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild b/sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild index 92b25f4f9572..c8b41a45c12c 100644 --- a/sys-fs/cryptsetup/cryptsetup-2.1.0.ebuild +++ b/sys-fs/cryptsetup/cryptsetup-2.1.0.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" # cryptsetup does _not_ have a libressl backend. We only have this for REQUIRED_USE # and change "libressl" to "openssl" in our econf call. CRYPTO_BACKENDS="gcrypt kernel libressl nettle +openssl" -- 2.26.2