From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-i18n/opencc/
Date: Fri, 30 Aug 2019 18:39:06 +0000 (UTC) [thread overview]
Message-ID: <1567190331.a774e0fc2a6a690bd623a9339d78f7b6eed01aa3.slyfox@gentoo> (raw)
commit: a774e0fc2a6a690bd623a9339d78f7b6eed01aa3
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Fri Aug 30 17:48:46 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Aug 30 18:38:51 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a774e0fc
app-i18n/opencc: keyworded 1.0.5 for sparc, bug #693040
Package-Manager: Portage-2.3.69, Repoman-2.3.16
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
app-i18n/opencc/opencc-1.0.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-i18n/opencc/opencc-1.0.5.ebuild b/app-i18n/opencc/opencc-1.0.5.ebuild
index 309ec8cea25..763dbae7aee 100644
--- a/app-i18n/opencc/opencc-1.0.5.ebuild
+++ b/app-i18n/opencc/opencc-1.0.5.ebuild
@@ -20,7 +20,7 @@ HOMEPAGE="https://github.com/BYVoid/OpenCC"
LICENSE="Apache-2.0"
SLOT="0/2"
-KEYWORDS="amd64 ~arm64 hppa ppc ppc64 x86"
+KEYWORDS="amd64 ~arm64 hppa ppc ppc64 ~sparc x86"
IUSE="doc test"
DEPEND="doc? ( app-doc/doxygen )"
next reply other threads:[~2019-08-30 18:39 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 18:39 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-08 1:15 [gentoo-commits] repo/gentoo:master commit in: app-i18n/opencc/ Yixun Lan
2025-02-08 1:15 Yixun Lan
2025-01-05 12:15 WANG Xuerui
2024-12-09 20:16 Sam James
2024-12-09 20:04 Arthur Zamarin
2024-12-09 7:35 Arthur Zamarin
2024-12-09 7:20 Arthur Zamarin
2024-12-09 7:03 Arthur Zamarin
2024-08-27 15:16 Yixun Lan
2024-07-05 10:37 Arthur Zamarin
2024-07-05 10:37 Arthur Zamarin
2023-03-17 13:18 Yixun Lan
2022-08-12 14:27 Sam James
2022-08-03 7:49 Agostino Sarubbo
2022-08-02 19:54 Arthur Zamarin
2022-08-02 16:01 Arthur Zamarin
2022-08-02 16:01 Arthur Zamarin
2022-08-02 16:01 Arthur Zamarin
2022-07-07 13:59 Yixun Lan
2022-06-13 21:30 Jakov Smolić
2022-06-10 6:48 Agostino Sarubbo
2022-06-09 7:37 Agostino Sarubbo
2022-06-09 7:37 Agostino Sarubbo
2022-06-09 7:36 Agostino Sarubbo
2022-06-08 20:04 Arthur Zamarin
2022-05-19 5:08 WANG Xuerui
2022-05-17 12:38 Agostino Sarubbo
2022-03-09 8:59 Jakov Smolić
2022-01-31 20:26 Arthur Zamarin
2022-01-31 18:51 Sam James
2022-01-31 6:24 Sam James
2022-01-30 22:25 Sam James
2022-01-30 22:25 Sam James
2022-01-29 15:20 Yixun Lan
2022-01-29 15:20 Yixun Lan
2022-01-14 11:36 Arthur Zamarin
2021-09-06 21:34 Sam James
2021-09-06 21:34 Sam James
2021-07-27 21:54 Marek Szuba
2021-06-08 7:41 Sam James
2021-03-26 14:38 Mike Gilbert
2021-03-26 14:38 Mike Gilbert
2021-03-26 14:38 Mike Gilbert
2021-03-26 14:38 Mike Gilbert
2020-12-31 1:47 Sam James
2020-12-27 18:39 Mike Gilbert
2020-12-27 18:39 Mike Gilbert
2020-12-27 18:39 Mike Gilbert
2020-11-22 19:32 Mike Gilbert
2020-11-22 19:32 Mike Gilbert
2020-11-22 19:32 Mike Gilbert
2020-11-22 19:32 Mike Gilbert
2020-11-22 19:32 Mike Gilbert
2020-11-22 19:32 Mike Gilbert
2020-11-22 19:32 Mike Gilbert
2020-02-08 12:50 Sergei Trofimovich
2019-12-31 18:08 Aaron Bauman
2019-08-18 3:06 Aaron Bauman
2017-10-05 9:04 Sergei Trofimovich
2017-09-24 12:29 Sergei Trofimovich
2017-09-24 11:00 Sergei Trofimovich
2017-08-31 19:53 Mike Gilbert
2017-08-23 14:25 Akinori Hattori
2017-08-22 14:21 Mike Gilbert
2017-08-22 14:21 Mike Gilbert
2017-08-22 14:21 Mike Gilbert
2017-08-22 14:21 Mike Gilbert
2017-08-22 14:21 Mike Gilbert
2017-02-15 22:04 Yixun Lan
2017-02-03 21:49 Johannes Huber
2017-02-03 20:08 Jeroen Roovers
2017-02-03 20:05 Jeroen Roovers
2017-01-29 13:55 Agostino Sarubbo
2016-05-27 10:22 Yixun Lan
2015-09-01 18:52 Tobias Klausmann
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=1567190331.a774e0fc2a6a690bd623a9339d78f7b6eed01aa3.slyfox@gentoo \
--to=slyfox@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