From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/bcprov/
Date: Sat, 2 Nov 2024 22:51:52 +0000 (UTC) [thread overview]
Message-ID: <1730587881.04806546092d3aad69ddcd17e9da5191140338c9.sam@gentoo> (raw)
commit: 04806546092d3aad69ddcd17e9da5191140338c9
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 2 22:51:21 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 2 22:51:21 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=04806546
dev-java/bcprov: Stabilize 1.78.1 amd64, #942768
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-java/bcprov/bcprov-1.78.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-java/bcprov/bcprov-1.78.1.ebuild b/dev-java/bcprov/bcprov-1.78.1.ebuild
index 8eedb146a281..0a5297bd21a2 100644
--- a/dev-java/bcprov/bcprov-1.78.1.ebuild
+++ b/dev-java/bcprov/bcprov-1.78.1.ebuild
@@ -18,7 +18,7 @@ S="${WORKDIR}/bc-java-${MY_PV}"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ppc64"
+KEYWORDS="amd64 ~arm64 ~ppc64"
DEPEND=">=virtual/jdk-11:*"
RDEPEND=">=virtual/jre-1.8:*"
next reply other threads:[~2024-11-02 22:51 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 22:51 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-04 7:18 [gentoo-commits] repo/gentoo:master commit in: dev-java/bcprov/ Miroslav Šulc
2024-11-03 13:31 Michał Górny
2024-11-03 4:40 Sam James
2024-10-10 10:29 Miroslav Šulc
2024-07-02 6:58 Miroslav Šulc
2024-01-06 21:52 Miroslav Šulc
2024-01-06 8:11 Sam James
2024-01-06 8:11 Sam James
2023-12-07 10:37 Miroslav Šulc
2023-10-28 8:23 Miroslav Šulc
2023-10-26 13:04 Sam James
2023-10-20 20:18 Arthur Zamarin
2023-10-20 20:18 Arthur Zamarin
2023-10-19 13:37 Sam James
2023-10-19 12:17 Sam James
2023-10-19 12:17 Sam James
2023-09-19 14:10 Miroslav Šulc
2023-09-19 14:10 Miroslav Šulc
2022-12-15 8:43 Miroslav Šulc
2022-12-15 4:23 Arthur Zamarin
2022-12-15 4:23 Arthur Zamarin
2022-12-15 2:05 Sam James
2022-12-15 2:05 Sam James
2022-11-14 14:48 Florian Schmaus
2022-07-09 13:00 Arthur Zamarin
2022-07-09 12:35 Arthur Zamarin
2022-07-07 6:35 Agostino Sarubbo
2022-07-07 6:34 Agostino Sarubbo
2022-07-06 8:40 Arthur Zamarin
2022-06-06 7:42 Florian Schmaus
2022-06-06 7:42 Florian Schmaus
2022-06-02 6:14 Sam James
2022-05-22 17:57 Florian Schmaus
2022-01-05 20:49 Florian Schmaus
2021-11-26 7:53 Miroslav Šulc
2021-11-25 7:20 Miroslav Šulc
2021-11-25 4:11 Sam James
2021-11-25 2:06 Sam James
2021-11-24 22:26 Miroslav Šulc
2021-11-11 14:20 Miroslav Šulc
2021-08-11 19:11 Sam James
2021-08-09 0:31 Sam James
2021-07-09 13:14 Miroslav Šulc
2021-07-09 6:26 Agostino Sarubbo
2021-07-08 3:53 Sam James
2021-06-07 8:52 Miroslav Šulc
2021-06-06 8:20 Miroslav Šulc
2021-06-06 8:20 Miroslav Šulc
2021-06-06 8:20 Miroslav Šulc
2021-06-05 7:12 Miroslav Šulc
2021-06-05 7:12 Miroslav Šulc
2021-06-05 7:12 Miroslav Šulc
2021-06-05 6:50 Miroslav Šulc
2021-06-05 6:50 Miroslav Šulc
2021-02-24 9:00 Miroslav Šulc
2021-02-24 9:00 Miroslav Šulc
2020-12-02 0:32 Aaron Bauman
2020-09-24 6:59 Agostino Sarubbo
2020-09-24 6:53 Agostino Sarubbo
2020-08-23 16:33 Miroslav Šulc
2020-08-23 16:33 Miroslav Šulc
2020-07-25 2:21 Sam James
2020-07-20 1:10 Sam James
2018-04-08 22:42 Patrice Clement
2018-03-01 8:39 Michał Górny
2017-07-13 17:27 Alexis Ballier
2016-02-07 19:27 Patrice Clement
2015-10-17 15:16 Patrice Clement
2015-10-17 15:16 Patrice Clement
2015-10-09 9:25 Patrice Clement
2015-10-09 8:59 Patrice Clement
2015-10-09 8:59 Patrice Clement
2015-10-09 7:24 Patrice Clement
2015-10-09 7:24 Patrice Clement
2015-10-08 22:11 Patrice Clement
2015-10-08 22:11 Patrice Clement
2015-10-08 22:11 Patrice Clement
2015-10-08 22:11 Patrice Clement
2015-10-08 22:11 Patrice Clement
2015-09-05 10:03 Patrice Clement
2015-09-05 9:53 Patrice Clement
2015-08-10 18:39 Patrice Clement
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=1730587881.04806546092d3aad69ddcd17e9da5191140338c9.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