sys-fs/cryptsetup: ppc stable wrt bug #590246
authorAgostino Sarubbo <ago@gentoo.org>
Sun, 15 Jan 2017 15:44:55 +0000 (16:44 +0100)
committerAgostino Sarubbo <ago@gentoo.org>
Sun, 15 Jan 2017 15:49:53 +0000 (16:49 +0100)
Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
sys-fs/cryptsetup/cryptsetup-1.7.2.ebuild

index 86c12f80eb116bff4e26484892065d8abf26ea08..3083bb956c80f104849558e019f28e9474f8262d 100644 (file)
@@ -15,7 +15,7 @@ SRC_URI="mirror://kernel/linux/utils/${PN}/v$(get_version_component_range 1-2)/$
 
 LICENSE="GPL-2+"
 SLOT="0"
-KEYWORDS="alpha amd64 arm hppa ~ia64 ~mips ~ppc ppc64 ~s390 ~sh sparc x86"
+KEYWORDS="alpha amd64 arm 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