From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Crypt-OpenSSL-Random/
Date: Sun, 12 Jul 2020 00:10:37 +0000 (UTC) [thread overview]
Message-ID: <1594512633.27169a08199833463d4743601ebf1e036f3a214f.sam@gentoo> (raw)
commit: 27169a08199833463d4743601ebf1e036f3a214f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 12 00:08:43 2020 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jul 12 00:10:33 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=27169a08
dev-perl/Crypt-OpenSSL-Random: s390 keyworded (bug #730668)
Package-Manager: Portage-2.3.99, Repoman-2.3.23
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-perl/Crypt-OpenSSL-Random/Crypt-OpenSSL-Random-0.150.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/Crypt-OpenSSL-Random/Crypt-OpenSSL-Random-0.150.0.ebuild b/dev-perl/Crypt-OpenSSL-Random/Crypt-OpenSSL-Random-0.150.0.ebuild
index dae6dd23e4c..0128e73a516 100644
--- a/dev-perl/Crypt-OpenSSL-Random/Crypt-OpenSSL-Random-0.150.0.ebuild
+++ b/dev-perl/Crypt-OpenSSL-Random/Crypt-OpenSSL-Random-0.150.0.ebuild
@@ -10,7 +10,7 @@ inherit perl-module
DESCRIPTION="OpenSSL/LibreSSL pseudo-random number generator access"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~sparc ~x86"
IUSE="libressl"
RDEPEND="
next reply other threads:[~2020-07-12 0:10 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 0:10 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-24 16:15 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Crypt-OpenSSL-Random/ Arthur Zamarin
2024-09-23 12:52 Sam James
2024-09-23 12:50 Sam James
2024-07-07 11:02 Sam James
2023-03-04 11:03 Arthur Zamarin
2023-03-04 11:03 Arthur Zamarin
2023-03-04 9:16 Arthur Zamarin
2023-03-04 9:07 Arthur Zamarin
2023-03-04 7:19 Arthur Zamarin
2023-03-04 6:12 Arthur Zamarin
2023-03-04 5:32 Arthur Zamarin
2022-12-24 7:11 Sam James
2021-10-16 10:43 Andreas K. Hüttel
2021-05-15 2:41 Sam James
2021-05-15 2:37 Sam James
2021-05-14 9:36 Agostino Sarubbo
2021-05-14 9:35 Agostino Sarubbo
2021-05-14 9:32 Agostino Sarubbo
2021-05-14 9:31 Agostino Sarubbo
2021-05-14 6:40 Agostino Sarubbo
2021-05-03 10:23 Mikle Kolyada
2020-12-05 4:20 Kent Fredric
2020-11-28 9:57 Sam James
2020-10-22 5:11 Joshua Kinard
2020-09-26 19:44 Matt Turner
2020-09-03 4:26 Yixun Lan
2020-07-09 21:58 Sam James
2020-07-07 6:58 Sergei Trofimovich
2020-07-06 16:44 Sergei Trofimovich
2020-07-06 11:57 Michał Górny
2020-07-05 11:37 Sergei Trofimovich
2020-07-05 11:35 Sergei Trofimovich
2020-07-04 8:56 Sergei Trofimovich
2020-07-02 7:03 Kent Fredric
2019-07-29 20:02 Aaron Bauman
2019-04-01 19:33 Andreas Sturmlechner
2018-10-27 12:31 Fabian Groffen
2018-10-14 13:29 Mikle Kolyada
2018-06-13 16:21 Lars Wendler
2018-06-03 3:31 Kent Fredric
2018-04-18 20:30 Mikle Kolyada
2018-04-18 7:05 Sergei Trofimovich
2018-04-07 21:13 Matt Turner
2018-04-07 4:01 Matt Turner
2018-04-06 21:09 Sergei Trofimovich
2018-04-06 17:13 Tobias Klausmann
2018-04-06 0:42 Aaron Bauman
2016-08-16 5:05 Kent Fredric
2016-08-03 19:50 Kent Fredric
2015-12-30 23:04 Andreas Hüttel
2015-09-20 16:39 Julian Ospald
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=1594512633.27169a08199833463d4743601ebf1e036f3a214f.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