sys-fs/cryptsetup: amd64 stable wrt bug #617314
authorAgostino Sarubbo <ago@gentoo.org>
Wed, 3 May 2017 14:56:14 +0000 (16:56 +0200)
committerAgostino Sarubbo <ago@gentoo.org>
Wed, 3 May 2017 14:56:14 +0000 (16:56 +0200)
Package-Manager: Portage-2.3.5, Repoman-2.3.1
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
sys-fs/cryptsetup/cryptsetup-1.7.4.ebuild

index 531ebe5732249785859882fa25f87d657c129f64..9341638132d2793bead0de87f306ffb0ccb1c6cc 100644 (file)
@@ -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 ~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