From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/guava/
Date: Wed, 6 Sep 2023 06:47:36 +0000 (UTC) [thread overview]
Message-ID: <1693982806.01ed4629b653942f0c8166a437ecb7b7a656d33f.sam@gentoo> (raw)
commit: 01ed4629b653942f0c8166a437ecb7b7a656d33f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 6 06:46:46 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Sep 6 06:46:46 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01ed4629
dev-java/guava: Stabilize 32.1.2 amd64, #913690
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-java/guava/guava-32.1.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-java/guava/guava-32.1.2.ebuild b/dev-java/guava/guava-32.1.2.ebuild
index 651e60a092af..d97d736a8dd6 100644
--- a/dev-java/guava/guava-32.1.2.ebuild
+++ b/dev-java/guava/guava-32.1.2.ebuild
@@ -15,7 +15,7 @@ S="${WORKDIR}/${P}"
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="~amd64 ~arm arm64 ppc64 x86"
+KEYWORDS="amd64 ~arm arm64 ppc64 x86"
CP_DEPEND="
dev-java/checker-framework-qual:0
next reply other threads:[~2023-09-06 6:47 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 6:47 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-18 16:40 [gentoo-commits] repo/gentoo:master commit in: dev-java/guava/ Miroslav Šulc
2024-10-18 15:40 Arthur Zamarin
2024-10-18 0:18 Sam James
2024-10-18 0:18 Sam James
2024-09-18 12:14 Miroslav Šulc
2024-06-21 7:45 Miroslav Šulc
2024-06-20 21:46 Sam James
2024-06-20 18:40 Arthur Zamarin
2024-06-20 17:43 Sam James
2024-06-20 17:40 Arthur Zamarin
2024-05-21 8:01 Miroslav Šulc
2024-01-21 17:17 Arthur Zamarin
2024-01-21 10:06 Sam James
2024-01-21 10:06 Sam James
2024-01-21 10:06 Sam James
2024-01-21 10:06 Sam James
2024-01-10 8:29 Florian Schmaus
2024-01-07 12:42 Arthur Zamarin
2024-01-07 7:10 Sam James
2024-01-07 6:14 Sam James
2024-01-07 6:14 Sam James
2023-12-22 15:13 Miroslav Šulc
2023-12-08 9:53 Miroslav Šulc
2023-09-18 6:50 Miroslav Šulc
2023-09-06 7:58 Florian Schmaus
2023-09-06 6:47 Sam James
2023-09-06 6:47 Sam James
2023-09-06 6:47 Sam James
2023-09-05 7:43 Miroslav Šulc
2023-01-28 6:52 Arthur Zamarin
2023-01-27 20:31 Arthur Zamarin
2023-01-27 20:18 Arthur Zamarin
2023-01-27 20:18 Arthur Zamarin
2023-01-27 19:45 Arthur Zamarin
2022-12-28 18:59 Florian Schmaus
2022-06-17 13:50 Arthur Zamarin
2022-02-25 21:07 Sam James
2022-02-21 7:47 Agostino Sarubbo
2022-02-21 3:45 Sam James
2022-02-20 20:32 Sam James
2022-02-13 23:13 Jakov Smolić
2022-01-20 9:38 Arthur Zamarin
2022-01-20 8:47 Arthur Zamarin
2022-01-20 8:46 Arthur Zamarin
2022-01-19 2:36 Sam James
2021-12-22 18:47 Arthur Zamarin
2021-12-21 8:04 Miroslav Šulc
2021-11-10 16:47 Sam James
2021-11-10 16:47 Sam James
2021-06-14 6:39 Sergei Trofimovich
2021-03-31 8:24 Miroslav Šulc
2017-11-05 13:56 James Le Cuirot
2017-08-31 19:55 James Le Cuirot
2017-07-13 18:32 Alexis Ballier
2016-11-05 22:56 James Le Cuirot
2016-11-05 22:49 James Le Cuirot
2016-01-02 23:15 James Le Cuirot
2015-12-06 23:06 James Le Cuirot
2015-10-27 20:36 Patrice Clement
2015-09-12 9:32 Patrice Clement
2015-09-10 16:47 Patrice Clement
2015-09-04 22:05 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=1693982806.01ed4629b653942f0c8166a437ecb7b7a656d33f.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