public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/byte-buddy/
Date: Sun, 16 Oct 2022 16:49:45 +0000 (UTC)	[thread overview]
Message-ID: <1665938977.43f8053b731507cc3b9463c4b475d412cabfb74e.sam@gentoo> (raw)

commit:     43f8053b731507cc3b9463c4b475d412cabfb74e
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 16 16:49:37 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Oct 16 16:49:37 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=43f8053b

dev-java/byte-buddy: Stabilize 1.12.14 arm64, #877085

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-java/byte-buddy/byte-buddy-1.12.14.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-java/byte-buddy/byte-buddy-1.12.14.ebuild b/dev-java/byte-buddy/byte-buddy-1.12.14.ebuild
index 61c20f47e67c..76862e0b7298 100644
--- a/dev-java/byte-buddy/byte-buddy-1.12.14.ebuild
+++ b/dev-java/byte-buddy/byte-buddy-1.12.14.ebuild
@@ -18,7 +18,7 @@ SRC_URI="https://github.com/raphw/${PN}/archive/${P}.tar.gz"
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ppc64 x86"
+KEYWORDS="amd64 ~arm arm64 ppc64 x86"
 
 DEPEND="
 	>=virtual/jdk-11:*


             reply	other threads:[~2022-10-16 16:49 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 16:49 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-15  6:13 [gentoo-commits] repo/gentoo:master commit in: dev-java/byte-buddy/ Miroslav Šulc
2025-01-14 12:24 Sam James
2025-01-14 12:07 Sam James
2025-01-14 12:07 Sam James
2025-01-10  8:51 Miroslav Šulc
2025-01-10  7:43 Arthur Zamarin
2024-12-20 15:43 Sam James
2024-12-16 14:30 Miroslav Šulc
2023-04-05 10:56 Miroslav Šulc
2023-04-04  5:10 Sam James
2023-04-03 21:40 Sam James
2023-04-03 21:40 Sam James
2023-04-03  8:11 Jakov Smolić
2023-03-04 13:03 Miroslav Šulc
2023-02-09 18:09 Arthur Zamarin
2023-02-09 18:09 Arthur Zamarin
2023-02-09 18:07 Sam James
2023-02-09 18:07 Sam James
2023-01-10 12:35 Florian Schmaus
2023-01-10 12:35 Florian Schmaus
2022-12-10 17:12 Arthur Zamarin
2022-12-10 14:56 Arthur Zamarin
2022-12-10 14:54 Arthur Zamarin
2022-12-10 14:33 Arthur Zamarin
2022-12-10 14:33 Arthur Zamarin
2022-10-17  4:49 Miroslav Šulc
2022-10-14 19:04 Sam James
2022-10-14 19:04 Sam James
2022-10-14  8:15 Arthur Zamarin
2022-09-16 18:58 Arthur Zamarin
2022-09-14 21:04 Sam James
2022-09-14 19:31 Arthur Zamarin
2022-09-14  9:35 Florian Schmaus
2022-09-09  8:08 Jakov Smolić
2022-09-09  8:08 Jakov Smolić
2022-08-23  4:41 Miroslav Šulc
2022-08-22  0:01 Sam James
2022-08-22  0:00 Sam James
2022-08-22  0:00 Sam James
2022-08-21 15:46 Arthur Zamarin
2022-08-21 15:46 Arthur Zamarin
2022-08-10  8:27 Florian Schmaus
2022-07-22 17:36 Florian Schmaus
2022-07-07 16:20 Arthur Zamarin
2022-07-07 14:29 Arthur Zamarin
2022-07-05 17:54 Sam James
2022-07-03 12:22 Jakov Smolić
2022-07-03 12:11 Jakov Smolić
2022-06-17 12:45 Arthur Zamarin
2022-06-16 15:15 Sam James
2022-06-16 15:15 Sam James
2022-06-03  8:54 Florian Schmaus
2022-04-15  9:36 Florian Schmaus
2022-04-10 15:16 Florian Schmaus

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=1665938977.43f8053b731507cc3b9463c4b475d412cabfb74e.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