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: app-accessibility/espeak-ng/
Date: Sat, 08 Mar 2025 18:00:34 +0000 (UTC)	[thread overview]
Message-ID: <1741456796.1d2c7a6eba3ff1143c78527b60333b8036bba59a.sam@gentoo> (raw)

commit:     1d2c7a6eba3ff1143c78527b60333b8036bba59a
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Mar  8 17:59:56 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Mar  8 17:59:56 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1d2c7a6e

app-accessibility/espeak-ng: Stabilize 1.52.0 ppc64, #950911

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

 app-accessibility/espeak-ng/espeak-ng-1.52.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-accessibility/espeak-ng/espeak-ng-1.52.0.ebuild b/app-accessibility/espeak-ng/espeak-ng-1.52.0.ebuild
index 80291fda4c11..8ef95411cd5a 100644
--- a/app-accessibility/espeak-ng/espeak-ng-1.52.0.ebuild
+++ b/app-accessibility/espeak-ng/espeak-ng-1.52.0.ebuild
@@ -13,7 +13,7 @@ if [[ ${PV} == *9999* ]]; then
 	inherit git-r3
 else
 	SRC_URI="https://github.com/espeak-ng/espeak-ng/archive/${PV}.tar.gz -> ${P}.tar.gz"
-	KEYWORDS="~amd64 arm arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc x86"
+	KEYWORDS="~amd64 arm arm64 ~hppa ~ppc ppc64 ~riscv ~sparc x86"
 fi
 
 LICENSE="GPL-3+ unicode"


             reply	other threads:[~2025-03-08 18:00 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-08 18:00 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-09  9:11 [gentoo-commits] repo/gentoo:master commit in: app-accessibility/espeak-ng/ WANG Xuerui
2025-03-08 16:56 Sam James
2025-03-08 15:33 Sam James
2025-03-08 11:57 Arthur Zamarin
2025-01-18 15:50 Sam James
2024-12-27 12:19 Sam James
2024-12-26 22:50 William Hubbs
2023-06-10 20:13 William Hubbs
2023-06-10 20:13 William Hubbs
2023-04-08 23:20 Sam James
2022-06-12  8:32 Agostino Sarubbo
2022-06-11  7:40 Agostino Sarubbo
2022-06-11  7:40 Agostino Sarubbo
2022-06-11  7:39 Agostino Sarubbo
2022-06-11  7:37 Agostino Sarubbo
2022-06-11  7:37 Agostino Sarubbo
2022-06-11  7:36 Agostino Sarubbo
2022-05-26  5:20 WANG Xuerui
2022-04-04  2:19 William Hubbs
2022-04-04  1:48 William Hubbs
2022-04-03 18:14 William Hubbs
2022-03-07  3:51 Sam James
2022-03-07  3:47 Sam James
2022-03-02  9:08 Agostino Sarubbo
2022-03-01 11:42 Jakov Smolić
2022-03-01 11:30 Agostino Sarubbo
2022-03-01 11:29 Agostino Sarubbo
2022-03-01 11:28 Agostino Sarubbo
2022-02-15 18:31 Matt Turner
2022-02-13  8:48 William Hubbs
2022-02-13  8:48 William Hubbs
2022-02-11 22:39 William Hubbs
2022-02-11 22:24 Ulrich Müller
2022-02-11  9:09 Ulrich Müller
2022-01-30 13:12 Yixun Lan
2022-01-29  7:14 Sam James
2022-01-29  4:32 Sam James
2022-01-29  3:56 Sam James
2022-01-29  3:55 Sam James
2022-01-28  7:14 Sam James
2021-10-10 22:22 Sam James
2021-09-07 18:59 Sam James
2021-09-07  2:32 Sam James
2021-07-28  2:39 Sam James
2021-07-15 22:20 Sergei Trofimovich
2021-07-07 17:10 William Hubbs
2021-06-30 22:08 William Hubbs

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=1741456796.1d2c7a6eba3ff1143c78527b60333b8036bba59a.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