From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/gson/
Date: Fri, 28 Apr 2023 06:15:27 +0000 (UTC) [thread overview]
Message-ID: <1682662516.449e4810dc05a9b5aa3a6d8ef88ea64f389964fd.sam@gentoo> (raw)
commit: 449e4810dc05a9b5aa3a6d8ef88ea64f389964fd
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 28 06:15:16 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 28 06:15:16 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=449e4810
dev-java/gson: Stabilize 2.10.1 arm64, #905211
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-java/gson/gson-2.10.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-java/gson/gson-2.10.1.ebuild b/dev-java/gson/gson-2.10.1.ebuild
index 21fb6dfddbb7..b08bf22835e5 100644
--- a/dev-java/gson/gson-2.10.1.ebuild
+++ b/dev-java/gson/gson-2.10.1.ebuild
@@ -16,7 +16,7 @@ S="${WORKDIR}/gson-gson-parent-${PV}/gson"
LICENSE="Apache-2.0"
SLOT="2.6"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc64 ~x86"
+KEYWORDS="amd64 ~arm arm64 ~ppc64 ~x86"
DEPEND=">=virtual/jdk-17:*"
RDEPEND=">=virtual/jre-1.8:*"
next reply other threads:[~2023-04-28 6:15 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 6:15 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-17 8:18 [gentoo-commits] repo/gentoo:master commit in: dev-java/gson/ Miroslav Šulc
2024-08-16 14:07 Arthur Zamarin
2024-08-14 22:03 Sam James
2024-08-14 20:21 Sam James
2024-08-14 20:21 Sam James
2024-07-16 10:08 Miroslav Šulc
2024-07-13 11:54 Miroslav Šulc
2024-07-10 10:22 Miroslav Šulc
2024-05-25 7:50 Florian Schmaus
2024-01-05 10:38 Miroslav Šulc
2024-01-05 9:48 Sam James
2024-01-05 8:13 Sam James
2024-01-05 8:13 Sam James
2024-01-05 8:13 Sam James
2023-04-28 6:28 Miroslav Šulc
2023-04-28 6:15 Sam James
2023-04-28 6:15 Sam James
2023-04-28 6:15 Sam James
2023-03-29 5:42 Miroslav Šulc
2022-10-20 16:32 Miroslav Šulc
2022-10-20 10:56 Jakov Smolić
2022-10-20 10:52 Jakov Smolić
2022-10-19 8:25 Jakov Smolić
2022-10-18 18:51 Sam James
2022-09-18 10:21 Florian Schmaus
2022-09-01 4:31 Miroslav Šulc
2022-08-01 18:08 Arthur Zamarin
2022-07-31 17:12 Arthur Zamarin
2022-07-30 2:34 Sam James
2022-07-30 2:33 Sam James
2022-07-30 2:33 Sam James
2022-07-28 9:10 Sam James
2022-06-17 10:48 Arthur Zamarin
2022-06-11 23:28 Sam James
2022-06-11 7:36 Agostino Sarubbo
2022-06-10 20:20 Jakov Smolić
2022-05-11 17:16 Florian Schmaus
2022-05-11 17:16 Florian Schmaus
2022-05-11 13:36 Florian Schmaus
2022-05-06 11:46 Florian Schmaus
2022-01-27 7:53 Miroslav Šulc
2022-01-26 19:16 Arthur Zamarin
2022-01-25 22:16 Sam James
2022-01-25 8:50 Jakov Smolić
2022-01-25 8:50 Jakov Smolić
2022-01-20 10:20 Miroslav Šulc
2022-01-07 20:42 Arthur Zamarin
2022-01-07 20:41 Arthur Zamarin
2021-11-26 9:23 Sam James
2021-11-12 8:16 Agostino Sarubbo
2021-11-11 11:35 Agostino Sarubbo
2021-10-26 10:10 Miroslav Šulc
2021-07-18 9:39 Florian Schmaus
2021-07-01 14:37 Miroslav Šulc
2021-07-01 14:37 Miroslav Šulc
2021-06-14 6:39 Sergei Trofimovich
2021-04-27 13:45 Miroslav Šulc
2021-04-27 13:45 Miroslav Šulc
2021-04-27 13:25 Miroslav Šulc
2016-10-14 2:58 Austin English
2016-05-11 21:07 James Le Cuirot
2015-09-01 19:00 Tobias Klausmann
2015-08-18 19:47 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=1682662516.449e4810dc05a9b5aa3a6d8ef88ea64f389964fd.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