From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/CryptX/
Date: Sat, 19 Aug 2023 06:33:08 +0000 (UTC) [thread overview]
Message-ID: <1692426718.fb6dd66770a8cd982c5bbf7b37007428f61afa06.sam@gentoo> (raw)
commit: fb6dd66770a8cd982c5bbf7b37007428f61afa06
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 19 06:31:58 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Aug 19 06:31:58 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fb6dd667
dev-perl/CryptX: Stabilize 0.78.0 sparc, #912495
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-perl/CryptX/CryptX-0.78.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/CryptX/CryptX-0.78.0.ebuild b/dev-perl/CryptX/CryptX-0.78.0.ebuild
index 55cb5118cd0d..5c96459d4358 100644
--- a/dev-perl/CryptX/CryptX-0.78.0.ebuild
+++ b/dev-perl/CryptX/CryptX-0.78.0.ebuild
@@ -14,7 +14,7 @@ DESCRIPTION="Self-contained crypto toolkit"
LICENSE="|| ( Artistic GPL-1+ ) public-domain"
SLOT="0"
-KEYWORDS="~alpha ~amd64 arm arm64 ~hppa ~ia64 ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 arm arm64 ~hppa ~ia64 ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 sparc ~x86"
IUSE="minimal"
RDEPEND="
next reply other threads:[~2023-08-19 6:33 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 6:33 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-17 3:12 [gentoo-commits] repo/gentoo:master commit in: dev-perl/CryptX/ Sam James
2024-01-04 18:11 Arthur Zamarin
2024-01-04 10:02 Sam James
2024-01-04 10:02 Sam James
2024-01-04 10:02 Sam James
2024-01-04 10:02 Sam James
2024-01-03 22:59 Sam James
2024-01-03 22:59 Sam James
2023-08-19 15:37 Arthur Zamarin
2023-08-19 7:42 Arthur Zamarin
2023-08-19 7:42 Arthur Zamarin
2023-08-19 6:18 Sam James
2023-08-19 6:10 Sam James
2023-08-05 12:42 Arthur Zamarin
2023-06-30 6:25 Sam James
2023-03-04 8:44 Arthur Zamarin
2023-03-04 8:31 Arthur Zamarin
2023-03-04 7:22 Arthur Zamarin
2023-03-04 7:04 Arthur Zamarin
2023-03-04 5:38 Arthur Zamarin
2023-03-04 5:35 Arthur Zamarin
2022-06-30 7:01 Agostino Sarubbo
2022-06-29 17:41 Arthur Zamarin
2022-06-29 17:15 Arthur Zamarin
2022-06-29 16:56 Sam James
2021-12-08 10:14 Yixun Lan
2021-11-21 4:58 Arthur Zamarin
2021-11-18 21:43 Arthur Zamarin
2021-10-16 17:17 Andreas K. Hüttel
2021-08-13 1:05 Sam James
2021-08-07 14:49 Sam James
2021-05-31 17:49 David Seifert
2021-05-25 0:52 Sam James
2021-05-25 0:19 Joshua Kinard
2021-05-16 0:13 Sam James
2021-05-15 1:55 Sam James
2021-05-13 16:18 Sam James
2021-05-13 16:15 Sam James
2021-05-13 16:15 Sam James
2021-05-11 18:41 Sergei Trofimovich
2021-05-11 15:45 Sergei Trofimovich
2021-05-07 18:18 Andreas K. Hüttel
2020-10-04 5:21 Kent Fredric
2020-08-26 18:30 Kent Fredric
2020-08-06 16:56 Kent Fredric
2020-07-02 17:53 Kent Fredric
2019-10-16 4:35 Andreas K. Hüttel
2018-09-08 5:30 Mikle Kolyada
2018-07-22 14:51 Thomas Deutschmann
2017-10-05 12:22 Kent Fredric
2017-06-03 11:14 Kent Fredric
2017-04-11 20:23 Kent Fredric
2017-04-06 8:37 Kent Fredric
2017-04-04 13:07 Kent Fredric
2016-12-04 17:16 Kent Fredric
2016-09-07 8:07 Kent Fredric
2016-09-07 8:07 Kent Fredric
2015-12-31 10:46 Andreas Hüttel
2015-09-07 19:32 Andreas Hüttel
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=1692426718.fb6dd66770a8cd982c5bbf7b37007428f61afa06.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