From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Crypt_CHAP/
Date: Sun, 13 Dec 2020 00:16:32 +0000 (UTC) [thread overview]
Message-ID: <1607818177.97c771fe3b9ce8daefd7282adc383ab7a34a163f.sam@gentoo> (raw)
commit: 97c771fe3b9ce8daefd7282adc383ab7a34a163f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 13 00:09:37 2020 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Dec 13 00:09:37 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=97c771fe
dev-php/PEAR-Crypt_CHAP: Keyword 1.5.0-r3 s390, #703372
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-php/PEAR-Crypt_CHAP/PEAR-Crypt_CHAP-1.5.0-r3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-php/PEAR-Crypt_CHAP/PEAR-Crypt_CHAP-1.5.0-r3.ebuild b/dev-php/PEAR-Crypt_CHAP/PEAR-Crypt_CHAP-1.5.0-r3.ebuild
index 316e144e79a..bf43b9f11c9 100644
--- a/dev-php/PEAR-Crypt_CHAP/PEAR-Crypt_CHAP-1.5.0-r3.ebuild
+++ b/dev-php/PEAR-Crypt_CHAP/PEAR-Crypt_CHAP-1.5.0-r3.ebuild
@@ -9,7 +9,7 @@ DESCRIPTION="Generating CHAP packets"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
+KEYWORDS="amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~sparc ~x86"
IUSE="test"
RESTRICT="!test? ( test )"
# Crypt_CHAP_MSv1 needs mcrypt which is gone in 7.2+
next reply other threads:[~2020-12-13 0:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 0:16 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-13 23:05 [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Crypt_CHAP/ Sergei Trofimovich
2020-05-10 8:47 Sergei Trofimovich
2020-05-05 22:13 Sergei Trofimovich
2020-01-26 20:25 Thomas Deutschmann
2019-12-26 9:49 Sergei Trofimovich
2019-12-24 14:26 Mikle Kolyada
2019-06-14 14:25 Brian Evans
2018-03-20 14:52 Brian Evans
2018-03-20 14:52 Brian Evans
2018-02-13 19:18 Brian Evans
2017-07-21 16:53 Brian Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1607818177.97c771fe3b9ce8daefd7282adc383ab7a34a163f.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox