From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/jitterentropy/
Date: Sun, 22 Jun 2025 15:53:33 +0000 (UTC) [thread overview]
Message-ID: <1750607536.d00a3b40b7d42753eaf40e2f9ec769cc1e9b329d.sam@gentoo> (raw)
commit: d00a3b40b7d42753eaf40e2f9ec769cc1e9b329d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 22 15:52:16 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jun 22 15:52:16 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d00a3b40
app-crypt/jitterentropy: Stabilize 3.6.0 ppc64, #958770
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-crypt/jitterentropy/jitterentropy-3.6.0.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app-crypt/jitterentropy/jitterentropy-3.6.0.ebuild b/app-crypt/jitterentropy/jitterentropy-3.6.0.ebuild
index 987687b0feb5..fe695e5b6a67 100644
--- a/app-crypt/jitterentropy/jitterentropy-3.6.0.ebuild
+++ b/app-crypt/jitterentropy/jitterentropy-3.6.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -18,7 +18,7 @@ S="${WORKDIR}/${PN}-library-${PV}"
# Do not package these two components!
LICENSE="BSD"
SLOT="0/3"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~mips ~ppc ~ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~mips ~ppc ppc64 ~riscv ~sparc ~x86"
IUSE="static-libs"
src_prepare() {
next reply other threads:[~2025-06-22 15:53 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 15:53 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-18 14:46 [gentoo-commits] repo/gentoo:master commit in: app-crypt/jitterentropy/ Petr Vaněk
2025-07-04 8:45 Arthur Zamarin
2025-07-03 8:51 Sam James
2025-06-22 17:10 Arthur Zamarin
2024-10-07 7:41 Göktürk Yüksek
2023-12-14 4:15 Sam James
2023-09-09 13:17 David Seifert
2023-09-09 13:17 David Seifert
2023-01-05 0:19 Sam James
2023-01-05 0:19 Sam James
2023-01-05 0:19 Sam James
2023-01-05 0:19 Sam James
2023-01-05 0:19 Sam James
2023-01-05 0:19 Sam James
2022-09-19 3:05 Sam James
2022-06-28 6:41 Agostino Sarubbo
2022-06-27 7:37 Agostino Sarubbo
2022-06-27 7:36 Agostino Sarubbo
2022-06-27 7:36 Agostino Sarubbo
2022-06-27 7:35 Agostino Sarubbo
2022-06-27 7:35 Agostino Sarubbo
2022-02-15 20:17 Göktürk Yüksek
2022-02-12 9:29 Göktürk Yüksek
2021-03-06 6:04 Göktürk Yüksek
2021-03-06 6:04 Göktürk Yüksek
2020-10-06 13:43 Sam James
2020-10-04 16:59 Sam James
2020-09-30 1:49 Sam James
2020-09-26 10:06 Sergei Trofimovich
2020-09-26 9:18 Sergei Trofimovich
2020-09-25 8:46 Agostino Sarubbo
2020-04-05 20:06 Mart Raudsepp
2020-03-30 12:20 Göktürk Yüksek
2019-11-13 7:39 Agostino Sarubbo
2019-11-12 15:08 Agostino Sarubbo
2019-11-04 9:22 Agostino Sarubbo
2019-11-03 13:40 Mikle Kolyada
2019-11-03 9:13 Piotr Karbowski
2019-08-11 21:38 Matt Turner
2019-08-08 23:57 Matt Turner
2019-08-08 16:01 Matt Turner
2019-08-06 17:50 Matt Turner
2019-08-05 23:55 Göktürk Yüksek
2019-08-05 23:34 Aaron Bauman
2019-08-05 5:08 Matt Turner
2019-08-05 5:08 Matt Turner
2019-06-12 22:59 Göktürk Yüksek
2019-06-12 22:59 Göktürk Yüksek
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=1750607536.d00a3b40b7d42753eaf40e2f9ec769cc1e9b329d.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