From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-build/cmake/
Date: Thu, 24 Oct 2024 07:43:33 +0000 (UTC) [thread overview]
Message-ID: <1729755810.c2dec9c2719d45a56708923be6519288c354af19.arthurzam@gentoo> (raw)
commit: c2dec9c2719d45a56708923be6519288c354af19
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 24 07:43:30 2024 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Thu Oct 24 07:43:30 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2dec9c2
dev-build/cmake: Stabilize 3.30.5 arm64, #941924
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-build/cmake/cmake-3.30.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-build/cmake/cmake-3.30.5.ebuild b/dev-build/cmake/cmake-3.30.5.ebuild
index 66578ec3ced2..e25164c6b69a 100644
--- a/dev-build/cmake/cmake-3.30.5.ebuild
+++ b/dev-build/cmake/cmake-3.30.5.ebuild
@@ -47,7 +47,7 @@ else
https://github.com/Kitware/CMake/releases/download/v$(ver_cut 1-3)/${MY_P}-SHA-256.txt.asc
)"
- KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~arm64-macos ~ppc-macos ~x64-macos ~x64-solaris"
+ KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~arm64-macos ~ppc-macos ~x64-macos ~x64-solaris"
BDEPEND="verify-sig? ( >=sec-keys/openpgp-keys-bradking-20230817 )"
fi
next reply other threads:[~2024-10-24 7:43 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 7:43 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-22 18:10 [gentoo-commits] repo/gentoo:master commit in: dev-build/cmake/ Sam James
2024-11-22 18:10 Sam James
2024-11-08 16:34 Sam James
2024-11-03 21:11 Andreas Sturmlechner
2024-10-30 17:27 Arthur Zamarin
2024-10-21 18:41 Arthur Zamarin
2024-10-21 18:41 Arthur Zamarin
2024-10-21 12:48 Sam James
2024-10-21 12:31 Sam James
2024-10-21 12:15 Sam James
2024-10-08 19:47 Sam James
2024-10-08 19:32 Sam James
2024-09-30 14:06 Sam James
2024-09-11 17:45 Arthur Zamarin
2024-09-07 14:27 Sam James
2024-09-07 14:27 Sam James
2024-09-02 7:29 Arthur Zamarin
2024-08-29 3:51 Sam James
2024-08-29 3:15 Sam James
2024-08-06 7:28 Sam James
2024-07-19 4:55 Sam James
2024-07-19 4:55 Sam James
2024-07-18 19:15 Fabian Groffen
2024-07-07 7:10 Eli Schwartz
2024-07-03 2:33 Sam James
2024-07-03 2:10 Sam James
2024-07-03 1:47 Sam James
2024-06-24 20:15 Andreas Sturmlechner
2024-06-01 3:56 Sam James
2024-06-01 3:46 Ionen Wolkens
2024-05-11 10:22 Arthur Zamarin
2024-05-11 7:23 Arthur Zamarin
2024-05-11 3:04 Sam James
2024-05-11 2:36 Sam James
2024-05-11 2:36 Sam James
2024-05-11 2:36 Sam James
2024-05-11 2:17 Sam James
2024-05-11 2:17 Sam James
2024-05-07 23:04 Sam James
2024-05-07 23:04 Sam James
2024-04-12 14:15 Sam James
2024-04-08 12:19 Sam James
2024-03-22 5:05 Sam James
2024-03-22 4:51 Sam James
2024-03-17 0:14 Sam James
2024-03-16 17:34 Arthur Zamarin
2024-03-16 16:56 Arthur Zamarin
2024-03-16 16:54 Arthur Zamarin
2024-03-16 16:45 Arthur Zamarin
2024-03-16 16:45 Arthur Zamarin
2024-03-16 16:42 Arthur Zamarin
2024-02-22 4:45 Ionen Wolkens
2024-02-06 3:26 Sam James
2024-01-31 20:35 Sam James
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=1729755810.c2dec9c2719d45a56708923be6519288c354af19.arthurzam@gentoo \
--to=arthurzam@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